Export Documents for a Letter of Credit: One-File Workflow

A letter of credit pays only if the documents you present agree with each other and with the credit. For a one-to-ten-person exporter building those documents in Excel and Word, the thing that gets you rejected is rarely the goods. It is re-typing the same buyer, description, quantity, and value into each file and letting one copy drift. This guide covers the document set an L/C asks for, the UCP 600 rule that turns a small mismatch into a refusal, and a one-file workflow that removes the second copy.

What documents does a letter of credit require?

A commercial letter of credit pays the exporter (the beneficiary) against a stipulated set of documents, not against the shipment itself. The credit's own document clause is controlling, but a typical export L/C asks the beneficiary to present a recurring core set.

• Commercial invoice — the priced statement of the goods.
• Packing list — quantities, package count, net and gross weight, marks.
• Bill of lading or transport document — proof the goods were shipped.
• Certificate of origin — where the goods were made.
• Insurance certificate — usually when the term is CIF or CIP.
• Bill of exchange (draft) and, if the credit calls for it, an inspection certificate.

According to the U.S. International Trade Administration (trade.gov), the bank checks these documents for compliance, and "document errors and discrepancies must be amended and resubmitted." The exact list is always whatever the specific credit names — so the first thing to read is the credit, not a template.

Why are most L/C presentations rejected on the first try?

Because the documents have to be consistent, and most exporters present a set that conflicts somewhere. The ICC Banking Commission's Technical Advisory Briefing No. 3 (June 2022) states that discrepancies "impact 65–80% of documentary credits" refused on first presentation. The long-standing rule of thumb, from the surveys that drove the UCP 600 revision, is around 70%.

The load-bearing rule is UCP 600 Article 14(d): data in a document "need not be identical to, but must not conflict with, data in that document, any other stipulated document or the credit." The standard is even stricter for the invoice. Article 18(c) says the description of the goods on the commercial invoice "must correspond with that appearing in the credit" — correspond, not merely "not conflict." A bank reading your invoice against the credit applies the harder test there.

Timing is a second trap. Article 14(c) requires presentation no later than 21 calendar days after the shipment date, and never after the credit expires. So a discrepancy is not free: it costs a discrepancy fee, a round of amend-and-resubmit, and — if the credit expires before you fix it — the bank's payment obligation ends and you are left with a contract claim. The ICC briefing names the root cause plainly: the "production, shipment and document collation processes," plus excessive data added to documents.

How does building documents in Excel create the discrepancy?

The discrepancy is usually manufactured at the keyboard. The same fields — buyer name and address, goods description, quantity, package count, net and gross weight, unit price, total value, currency, Incoterms, marks — appear on the invoice, the packing list, and the bill of lading. In a spreadsheet workflow you type them into each document separately.

Two failure modes follow. First, a value gets entered three times and one of the three is wrong. Second, and more common, you copy last shipment's file as a starting point and an old buyer name, an old amount, or an old quantity stays behind in one document while you update the others. Article 14(d) does not care that it was a copy-paste slip. The bank sees a net weight of 1,080 kg on the packing list and 1,008 kg on the invoice, and that is a discrepancy. The cost is the credential here: one transposed digit can hold up a five- or six-figure payment.

What is the one-file workflow?

The one-file workflow removes the second copy. You enter the shipment once into a single master file, and every document reads from it instead of being typed again. In ovrseas, you fill one shipment record and the commercial invoice, packing list, bill of lading, and certificate of origin all read the same buyer, description, quantity, and value. There is no second place for the consignee to be spelled differently, because there is only one source.

The tool generates 12 trade document types from that one record, including the L/C staples above. You sign each document in the browser three ways — type it, draw it, or upload a signature image — and download the finished PDF. A 14-day free trial covers 30 documents on one seat; paid plans start at $20 a month.

One honest limit, because it matters here: ovrseas removes the re-typing that creates conflicts. It does not read your letter of credit, check your documents against UCP 600, or flag a discrepancy for you. That judgment stays with you and your bank. The point of the single source is prevention — the same value shows up on every document because it was only entered once — not validation after the fact.

What should you check before you present?

Before the documents go to the bank, confirm that these fields read identically across the invoice, packing list, bill of lading, and the credit. A single source removes most of this work, but the final read-through against the credit is yours. This is the checklist:

• Buyer (applicant) name and address — spelled the same on every document and as in the credit.
• Goods description — must correspond to the wording in the credit (Article 18(c)); do not paraphrase or reorder.
• Quantity and number of packages — the invoice and packing list agree.
• Net and gross weight — the packing list and B/L agree.
• Unit price, total value, and currency — same currency as the credit (Article 18(a)).
• Incoterms and named place — one term, with its place, on every document.
• Shipping marks and country of origin — consistent across the set.
• Shipment and expiry dates — present within 21 days of shipment and before the credit expires (Article 14(c)).

For the invoice specifically, the rules a bank applies to a commercial invoice under an L/C go deeper, and the fields that must match between the invoice and packing list are the same fields that trigger a customs hold.

When does the one-file workflow fit — and when not?

It fits a one-to-ten-person exporter shipping five to thirty containers a month, building documents off Excel, with repeat L/C shipments where the same fields are typed over and over. The payoff there is the re-keying errors removed, not raw speed.

It does not replace a trade-finance desk or a bank's document checker, and it is not export-compliance or AES-filing software. If you already have someone who checks every document set against the credit line by line, a single-source tool saves the typing but not the review. If the typing and the stray old value are your real problem — and for most small exporters they are — moving to one master file is where the discrepancy rate drops. The same single source also keeps your documents consistent for customs, where mismatched figures trigger a hold. You can start a free trial and build one L/C set to see whether it removes the step you keep getting wrong.