Free Beneficiary's Certificate Generator

What a beneficiary's certificate is

A beneficiary's certificate is a statement you write about yourself, on your own letterhead, and hand to a bank as evidence. Every other document in a letter of credit presentation is issued by someone else — the carrier issues the bill of lading, a chamber of commerce issues the certificate of origin, a surveyor issues the inspection report. This one has no third party in it. You are the beneficiary of the credit, and you are certifying that something the credit asked for actually happened.

It exists because of field 46A. When a credit is issued, field 46A lists the documents required, and issuing banks routinely add conditions that no ordinary shipping document can evidence: that a set of non-negotiable copies was couriered to the applicant within so many days of shipment, that the carrying vessel meets an age or classification requirement, that no transhipment took place, that the packing carries a particular marking. There is no institution in the world that issues a document saying "the exporter couriered the copies on Tuesday". So the credit names a document that only you can issue, and this is it. If your trade has no credit — you sell on open account, or against cash in advance — there is no field 46A and no beneficiary's certificate to make; this tool requires the L/C number for exactly that reason.

UCP 600 Article 14(f) is what makes that workable: where a credit requires a document without stipulating who is to issue it or what data it must contain, banks accept the document as presented if its content appears to fulfil the function of the document required. A beneficiary's certificate is the archetypal case. The bank is not checking whether your statement is true — it has no way to — it is checking that a document exists, that it says what the credit told it to say, and that nothing else in the presentation contradicts it.

That is also why the document deserves more care than its length suggests. It is one page of prose with your signature under it, and it is the page on which you personally assert facts to a bank that will pay out against them.

The clauses must mirror the credit, word for word

This is the single rule that decides whether the certificate is paid against or refused, and it is the reason this tool refuses to pre-fill a clause for you. A beneficiary's certificate whose wording came from a template rather than from your credit is a document the checker cannot tick off, because their job is to hold your sentence next to field 46A and see the requirement satisfied. A clause that means the same thing in different words invites the checker to decide whether it does — and a checker who has to decide has already found a discrepancy.

So take field 46A, read the condition, and convert it from an instruction into a statement of fact. "Beneficiary's certificate certifying that one set of non-negotiable documents has been sent to the applicant by courier within 5 days of B/L date" becomes "One set of non-negotiable documents has been sent to the applicant by courier within five (5) days of the bill of lading date." Same nouns, same numbers, same order. Where the credit says five days, write five days — not "promptly", not "within a week". UCP 600 Article 3 in fact tells banks to disregard terms like "prompt" and "immediately" altogether.

Then read what you have written as a lawyer would, because that is what it is. Some clauses banks ask for are assertions you are in no position to make. You can certify the courier receipt number, because you hold it. You can certify the temperature the reefer was set to, because your own people set it. Whether the carrying vessel is under 25 years of age and classed with a full member of IACS is a fact about someone else's ship, and whether the goods fall under a sanctions regime on the date of shipment is a legal conclusion, not an observation. If the credit demands those, get them from the carrier or your counsel in writing before you sign — do not certify them because a form offered to.

And keep every clause consistent with the rest of the presentation. UCP 600 Article 14(d) does not require the data in a document to be identical to the data elsewhere, but it does require that it not conflict. A certificate saying the goods shipped on 5 August, sitting beside a bill of lading with an on-board date of 7 August, is two documents in conflict, and that is a discrepancy on its own — even though nothing on the certificate is untrue.

What has to be on it

The credit number, first and unmistakably. A trade finance department is processing dozens of presentations; a certificate that does not carry the L/C number on its face is a page they cannot file, and a bank is entitled to refuse a document it cannot link to a credit. Add the issuing bank, the issue and expiry dates, the amount and currency, and any tolerance the credit carries in field 39A, and the checker has everything they need to open the right file without looking anything up.

The applicant, named as the credit names them. This is worth a moment: the applicant is often not your buyer. Credits are opened by parent companies, by buying agents, by group treasury desks. Field 50 is the truth here, and if it differs from the party you invoiced, name field 50 on the certificate and let the invoice name the buyer. This tool asks for the applicant, not "the buyer", for exactly that reason — the applicant is the only party this document names.

The bank you are presenting to, in the addressee line. Usually that is the advising or nominated bank named in the credit; if you present directly to the issuing bank, name it there instead. The line is not decoration — it is the "To" of a document being handed to a named institution, and a certificate addressed to nobody looks unfinished on the counter.

The shipment the certificate is about — the invoice number, your order reference, the vessel and voyage where there is a vessel, the date of shipment. None of this is decorative. It is what lets the bank read the certificate as part of one coherent presentation rather than as a loose page, and it is what makes Article 14(d)'s no-conflict test something you can check yourself before you present. On an air, road or courier movement there is no vessel to name; the order and invoice still tie the page to the rest of the pack.

And a signature block that names a human being. Banks reject certificates signed "Authorised Signatory" over an illegible scrawl, because the whole point of the exercise is verification against the specimen signature card the bank holds for your company. Print the name and the title under the signature. UCP 600 Article 3 is generous about how a document may be signed — handwriting, facsimile signature, perforated signature, stamp, symbol, or any mechanical or electronic method of authentication all count — but it says nothing that saves an anonymous signatory. The template leaves the name, title, signature and date lines blank on purpose: this document is signed by a person, in ink, after they have read it.

How it fails, and where it sits among the other documents

The failure mode is Article 16. A bank that decides a presentation is not complying must give a single notice of refusal, by the close of the fifth banking day following presentation, stating each discrepancy for which it refuses. "Each" is the word that hurts: the notice lists everything, and the clock is unforgiving. Under Article 14(b) the bank has a maximum of five banking days after presentation to examine, and under Article 14(c) a presentation including an original transport document must be made no later than 21 calendar days after the date of shipment and in any event no later than the expiry date. A certificate that comes back for rewording can burn a week you do not have, and when the discrepancy cannot be cured the payment undertaking is gone — you are back to asking the applicant to waive, which is asking the buyer you were protecting yourself from to do you a favour.

There is a subtler failure worth knowing, because it is the reason this document exists at all. Article 14(h) says that if a credit contains a condition without stipulating the document to show compliance with it, banks will deem the condition as not stated and disregard it. That is a non-documentary condition. The beneficiary's certificate is the instrument that converts an unenforceable condition into a document the bank must examine — which is precisely why the certificate's wording, and not the credit's intention, is what gets checked.

Around it sits the rest of the pack. The commercial invoice states the goods and the amount and must be made out in the credit's currency. The bill of lading carries the on-board date every deadline runs from. The packing list and the VGM declaration describe the physical shipment. The bill of exchange is the demand for payment itself. The beneficiary's statement is its close cousin — a general assertion about the presentation and its documents, rather than a certification of specific 46A conditions — and the two are sometimes both required. Every one of these is read against every other under Article 14(d).

The contrast worth holding onto is with a documentary collection. Under URC 522, the bank handles your documents as an agent and checks only that it received what your instruction letter lists; nobody examines your clauses, because no bank has undertaken to pay. Under UCP 600 a bank has undertaken to pay, and the price of that undertaking is that your sentences are examined like contract terms. That is a good trade. It just means the sentences have to be yours, deliberate, and true.

Common questions