How to Prepare a Compliant Commercial Invoice Under a Letter of Credit

Why the Commercial Invoice Is the Most-Rejected LC Document

Of all the documents presented under a letter of credit, the commercial invoice generates the highest rate of discrepancies. ICC Banking Commission surveys consistently show that invoice errors account for 30–40% of all first-presentation refusals. The reason is structural: the invoice is the anchor document against which banks cross-check every other paper in the package. If the invoice is wrong, the entire presentation unravels.

Under UCP 600 Article 18, a commercial invoice must be made out in the name of the applicant, issued by the beneficiary, and must describe the goods, services, or performance in a way that corresponds to the description in the LC. Banks do not apply a "close enough" standard — any deviation that a bank determines to be a discrepancy entitles it to refuse the documents and withhold payment under UCP 600 Article 16.

The stakes are concrete. A rejected first presentation typically costs 5–10 business days of delay, bank re-examination fees of $150–$500 per re-presentation, and — in worst-case scenarios — missed payment deadlines that push settlement past the LC expiry date entirely.

Required Fields for LC Invoice Compliance

The following fields must appear on the commercial invoice and must align precisely with the LC terms. Work through these in order before finalizing any invoice draft.

1. Beneficiary Name and Address

Your company name and address on the invoice must be an exact character-for-character match with the beneficiary field in the LC. This is not a judgment call — it is a mechanical comparison. Common failure modes include:

• Using a trading name instead of the registered legal entity name stated in the LC (e.g., "Acme Chemicals" vs. "Acme Chemical Manufacturing Ltd.")
• Abbreviating a state or province that the LC spells out in full ("ON" vs. "Ontario")
• Including a suite number the LC omits, or omitting one the LC includes
• Using a comma or period that differs from the LC format

ISBP 745 paragraph A18 clarifies that an address of the beneficiary need not be the same as the one stated in the LC, provided it is in the same country. However, when the LC specifies an address, exact conformity is safest practice — deviations invite refusal even when technically debatable.

2. Applicant Details

The invoice must be addressed to the applicant (the buyer / importer). Under UCP 600 Article 18(a)(ii), the invoice must be made out in the name of the applicant. Use the exact applicant name as it appears in the LC field 50 (Applicant). Do not substitute a parent company, affiliate, or abbreviated name without a corresponding LC amendment.

3. Description of Goods

This is the most litigated field in invoice disputes. UCP 600 Article 18(c) states: "The description of the goods, services or performance in a commercial invoice must correspond with that appearing in the credit." The word correspond is critical — it does not mean identical verbatim, but it does mean no contradictions, no material omissions, and no additions that create ambiguity.

Practical rules:

• Copy the exact goods description from LC field 45A into your invoice template as the baseline
• You may add technical or commercial detail that does not conflict with the LC description
• Do not include goods not covered by the LC on the same invoice
• Do not use a trade name if the LC specifies a chemical name, or vice versa, unless the LC explicitly allows both

Example discrepancy: An LC for "Polyethylene Terephthalate (PET) Resin, virgin grade, CAS 25038-59-9" was presented with an invoice describing "PET Resin — Industrial Grade." The bank refused on the grounds that "industrial grade" was not equivalent to "virgin grade" and the CAS number was absent. Re-presentation delay: 8 business days.

4. Quantity, Unit Price, Total Amount, and Currency

All four elements must reconcile precisely:

• Quantity: Must not exceed the LC-stated quantity unless the LC or UCP 600 Article 30 tolerances apply (±5% for bulk goods unless the LC states otherwise). For packaged goods with a stated unit count, there is zero tolerance.
• Unit price: Must match the contract price reflected in the LC. If the LC states a unit price cap, the invoice must not exceed it.
• Total amount: Must not exceed the LC credit amount. Under UCP 600 Article 18(b), a bank will refuse an invoice that exceeds the LC value even if a partial drawing is permitted.
• Currency: Must exactly match the LC currency code. USD and US$ are technically the same but some banks flag the difference — use the ISO 4217 code (USD, EUR, GBP) that appears in the LC.

5. Incoterms

The Incoterms rule on the invoice must match the LC exactly, including the year version. "FOB Shanghai" and "FOB Shanghai (Incoterms 2020)" are different — if the LC specifies a year, include it. Mismatched Incoterms create a discrepancy because they imply different risk-transfer and freight-responsibility obligations, which affects the consistency test across the invoice and transport document.

6. LC Reference Number

Always quote the LC number (field 20 of the SWIFT MT700) on the invoice. While UCP 600 does not explicitly mandate this, ISBP 745 paragraph A29 notes that the LC number must appear on the invoice in many LCs as an explicit requirement. Even when not required, its absence creates unnecessary cross-referencing difficulty for the examining bank and may trigger a query.

7. Marks and Numbers

If the LC or the packing list references shipping marks, those marks must appear consistently on the invoice, packing list, and transport documents. Under ISBP 745, shipping marks on the invoice need not be identical to those on the B/L, but any marks shown must not conflict. A zero-marks invoice is acceptable if no marks are required — but if you show marks, they must be consistent throughout the document set.

8. Country of Origin

Many LCs require the invoice to state the country of origin. If required, the origin declared on the invoice must match any Certificate of Origin presented. Origin statements such as "Made in USA" are acceptable; formal preferential origin declarations should be left to the Certificate of Origin unless the LC specifically requires the statement on the invoice face.

Common Invoice Discrepancies with Examples

Discrepancy Type	Real Example	Consequence
Goods description mismatch	LC: "Sodium Hydroxide Flakes, 98% min purity" / Invoice: "Caustic Soda Flakes"	Refused — common name ≠ chemical name without LC authorization
Amount exceeds LC value	Invoice total USD 502,000 against LC ceiling of USD 500,000	Refused under UCP 600 Art. 18(b); requires amendment or reduced invoice
Beneficiary name abbreviated	LC: "Brenntag Deutschland GmbH" / Invoice: "Brenntag GmbH"	Discrepancy — legal form suffix matters
Missing LC reference	Invoice omits LC number when LC field 46A requires it	Minor but citable discrepancy; bank may query or refuse
Incoterms year mismatch	LC: "CIF Hamburg Incoterms 2020" / Invoice: "CIF Hamburg Incoterms 2010"	Discrepancy — different liability regime
Quantity tolerance exceeded	LC: 500 MT; Invoice: 512 MT (2.4% over) — but goods are bagged, not bulk	Refused — 5% tolerance under Art. 30(b) applies only to credit amount and quantity in bulk; packaged goods have zero tolerance

Invoice vs. Other Documents: Consistency Rules

Under ISBP 745 and UCP 600 Article 14(d), data in a document need not be identical to but must not conflict with data in any other document. For the commercial invoice, this means performing cross-checks against:

• Bill of Lading: Shipper name, description of goods (need not be identical to LC description — B/L can use a general description — but must not contradict the invoice), port of loading, and vessel name should be consistent where both documents show the detail.
• Packing List: Total quantity, number of packages, net/gross weights, and marks must reconcile with the invoice line items.
• Certificate of Origin: Consignee details and country of origin must align.
• Insurance Certificate: Insured amount, goods description, and voyage route must be consistent with the invoice.
• Inspection Certificate: If the inspection certificate references a specific quantity or quality specification, it must not contradict what the invoice states.

The safest workflow is to prepare the invoice first (as the anchor document) and then populate all other documents from the invoice, rather than preparing each document independently and hoping they reconcile.

Special Considerations for Chemical Exports

Chemical exporters face additional invoice requirements that sit at the intersection of trade finance and regulatory compliance:

HS Codes

Many LCs for chemical shipments require the Harmonized System (HS) code to appear on the invoice. If an HS code is required, it must be the correct 6-digit international code (or extended national code as required by the importing country). An incorrect HS code on the invoice may not only create an LC discrepancy — it can trigger customs delays, anti-dumping duty issues, or import licensing problems in the destination country. Cross-check the HS code against the goods description every time, as a single transposition (e.g., 2905.11 vs. 2905.12 for methanol vs. ethanol) can have significant consequences.

REACH References

When shipping chemical substances to EU buyers under an LC, the invoice frequently needs to either incorporate or align with REACH registration data. Some LC terms require the invoice to reference the REACH registration number (EC/REACH No.) for the substance. If your LC includes such a requirement, the registration number on the invoice must match your REACH dossier exactly. A mismatch — or absence of the number when required — constitutes an invoice discrepancy independent of any regulatory consequence.

Additionally, where a Safety Data Sheet (SDS) is a required LC document, the substance identification data on the SDS (CAS number, IUPAC name, EC number) should mirror the goods description on the invoice. Inconsistencies between the SDS header and the invoice description are a common source of bank queries on chemical presentations.

Dangerous Goods Notation

For hazardous chemicals subject to IMDG, ADR, or IATA dangerous goods regulations, some LCs require the invoice to reference the UN number, proper shipping name, hazard class, and packing group. If your LC requires this, place it in a clearly labeled section of the invoice — typically below the goods description line — and ensure it matches the Dangerous Goods Declaration or MSDS presented alongside.

Template and Format Recommendations

Format discipline prevents discrepancies before they start:

1. Create a per-LC invoice template. When an LC is received, extract the beneficiary name, applicant name, goods description, currency, and Incoterms from the LC directly and lock them into a template. Do not rely on retyping these fields from memory.
2. Use a four-eyes check. One person prepares; a second person performs a character-by-character comparison of the invoice against LC fields 46A (Documents Required), 45A (Description of Goods), and the applicant/beneficiary fields. Do not skip this step under deadline pressure — that is exactly when errors occur.
3. Version-control your invoice drafts. If an LC amendment is issued after you have begun invoice preparation, explicitly update your template. Presentations against amended LCs using pre-amendment invoice templates are a common and avoidable error.
4. Avoid auto-populated fields from ERP systems without validation. ERP master data for customer names, addresses, and goods descriptions may not exactly match LC wording. Never trust an ERP output for LC compliance without a manual comparison to the LC text.