Discrepancies: Why Banks Refuse LC Documents — and the Top Ten Reasons

The letter of credit pays against complying documents. Everything depends on the word complying — and the standard the banks apply is strict compliance: the presentation must conform to the credit's terms on its face. Not substantially. Not commercially. Literally.

Sellers experience this as betrayal: the cargo is on the water, conforming to the contract, and the bank refuses payment because the invoice says "stainless steel water pumps" where the credit said "stainless-steel water pumps." Buyers experience the mirror image. The documentary standard was the whole reason they offered a bank's promise instead of open account.

Strict compliance is not going to soften. The practical response is to know where presentations actually fail — the failure modes are few and repetitive — and to build the prevention into the documentary flow before documents exist. That, plus a clear head about what the days after a refusal notice can and cannot fix. This article covers both.

1. Strict Compliance: The Machine Reads Literally

Under the UCP 600 framework, a bank must refuse a presentation that does not comply, and may refuse one whose data conflicts across documents. Three principles drive most outcomes:

• The credit governs, not the contract. The bank has never seen your sale contract and will not read it. What the credit requires is the whole world of compliance.
• Documents, not goods. The bank pays the paper. Whether the paper is true is nobody's examination task — that is the LC's great strength and its great vulnerability, and it is why the contract around the credit matters more than the credit itself (see the structural defects article).
• Data consistency across documents. The same facts — goods description, quantities, parties, ports, dates — appear in the invoice, transport document, packing list, certificates. Each repetition is a chance to conflict, and any conflict is discrepancy material.

Keep these in view and the top ten below stop looking arbitrary. Every one of them is a literal-reading consequence.

2. The Top Ten Discrepancies, with Prevention

#	Discrepancy	What it looks like	Prevention
1	Late shipment	Transport document dated after the latest shipment date in the credit.	Set a realistic latest shipment date at issuance, with production buffer. Don't book a vessel that sails on day 45 of a 45-day credit.
2	Late presentation / expired credit	Documents presented after the expiry date, or outside the stated presentation period after the transport date.	Diary the expiry and presentation window at the moment of shipping; documents go to the nominated bank days before expiry, not on it.
3	Inconsistency between documents	Quantity on invoice vs. packing list vs. B/L conflicts; gross weight differs between documents; container numbers don't match.	One document clerk prepares the set from a single source sheet; cross-check every repeated field before lodgment.
4	Mismatched data vs. the credit	Goods description not mirroring the credit; wrong consignee or notify party; ports differing from the credit's fields.	Type the goods description into the invoice directly from the credit's field — no paraphrasing, no shortcuts on ports and parties.
5	Spelling of names and addresses	Beneficiary or applicant name misspelled vs. the credit; "Co., Ltd." vs "Company Limited"; transposed characters.	Copy names character-for-character from the credit into every document template once, at credit receipt, and lock the templates.
6	Unclean (claused) bill of lading	The carrier has annotated defects on the goods or packaging — "cartons wet," "drums dented."	Pre-shipment inspection and proper packing supervision; if the carrier wants to clause, resolve it at the port, not on the paper.
7	Overdrawn credit	Invoice amount exceeds the credit's amount or tolerance.	Reconcile invoice, unit price, and quantity against the credit before issuance of the commercial documents; watch tolerance fields.
8	Insurance shortfall (CIF/ CIP deals)	Coverage below the credit's required percentage; currency or risks not matching the credit; policy dated after the shipment date.	Have the policy issued and checked against the credit's insurance clause before the vessel sails — not after.
9	Missing or unauthorized documents	A required certificate absent; an extra document presented that the credit didn't ask for, creating new data conflicts.	A document checklist built directly from the credit's list of required documents; present what is required, and nothing that isn't.
10	Presentation through the wrong channel	Documents delivered to a bank other than the stated available-with bank, or after the credit's transfer/availability rules were ignored.	Confirm the available-with bank and availability method on day one; route the documents exactly as the credit says.

Note the profile of this list: nothing on it is legally difficult. It is clerical discipline under time pressure — which is precisely why it keeps happening, and why a buyer who understands these mechanics reads a "discrepancy refusal" with more nuance than a seller might expect.

3. Why Discrepancies Cluster Where They Do

Two observations from disputes I have handled around refused presentations. First, discrepancies cluster at the end of the credit's life. Documents assembled in the last 48 hours, couriers chasing the nominated bank on expiry day, corrections made under deadline pressure — the error rate is a function of the timeline, and the timeline is set at issuance. A credit issued with a realistic validity and presentation period refuses less, whatever the skill of the document clerk.

Second, not every refusal is innocent, and not every refusal is sharp practice. A genuine discrepancy sometimes hands the buyer a commercial lever it did not plan to use: goods have fallen in price, and the refusal — perfectly legitimate — becomes the opening position for a renegotiation. Conversely, some buyers instruct refusals on trivia as a delay tactic. You cannot tell which from the refusal notice alone. What you can do is control the response clock, which is where the five banking days come in.

4. The Refusal Notice and the Five Banking Days

Under UCP 600 practice, the bank that takes up documents to examine has up to five banking days following presentation to determine compliance and, if it refuses, to give a single notice stating each discrepancy and what it is doing with the documents — hold them pending instructions, return them, or hold them pending the applicant's waiver decision.

Practical points that matter when the notice arrives:

• The notice must list every discrepancy. A bank cannot come back later with new ones. If the notice cites one spelling issue, that is the entire case against the presentation — which also means an early, precise refusal notice is a kind of respect: you know exactly where you stand.
• The clock belongs to the bank, but the calendar belongs to you. The beneficiary should treat the five-day window as a preparation period for its own next move, not as time to wait for the applicant's mood to improve.
• Who refuses matters. The nominated bank, the confirming bank, and the issuing bank each have their own posture. A refusal from a confirming bank that took up the documents is a different event than a message from an issuing bank with no confirmation in the structure. Confirm your exposure to each before reacting.

5. The Beneficiary's Options, Honestly Assessed

Inside and around that window, the realistic moves, roughly in the order they should be considered:

1. Cure and re-present, if the credit still allows. The strongest option, and only available while the credit is unexpired and the discrepancy is curable — a correctable certificate, a reissued invoice. If the presentation window has closed, the option is gone; if the credit has expired, it never existed. This is why presentation periods should be drafted with cure room.
2. Seek the applicant's waiver. The bank that refused will typically contact the applicant for a decision to waive the discrepancies and take the documents. Commercially, this is where most refusals end — the buyer wants the goods and waives the spelling. The beneficiary's job is to make waiving easy: contact the applicant directly, explain the discrepancy is formal, not substantial, and ask them to instruct their bank. Note the candid risk: while the applicant deliberates, the beneficiary has shipped and been unpaid. That exposure is the price of the structure.
3. Authorization to release documents against payment or on other terms. If the applicant will pay but the banks are stuck on formality, the parties can agree the beneficiary instructs the bank to release documents to the applicant — against payment outside the credit, or against a written undertaking. The LC stops being the payment vehicle; the contract and the parties' credit take over. Legal effect of such undertakings should be checked with counsel before relying on them — this is a commercial instrument, not a bank payment obligation.
4. Payment under reserve or against a refund guarantee. Some banks will advance against a discrepant presentation with the beneficiary's counter-indemnity: pay now, and if the applicant ultimately refuses the documents, the beneficiary repays. For a solvent beneficiary confident in its goods and its buyer, this converts a documentary fight into a credit decision. For a beneficiary under financial stress, it converts a payment problem into a debt problem. Assess it as the borrowing it is.
5. Preserve the underlying claim. Whatever happens at the document level, the goods were shipped under a contract, and the contract's remedies — payment claim, demurrage, interest — survive the refusal. The demand-letter and enforcement track operates on the contract, not the credit. Keep the contract's time limits in view while the banks correspond.

What there is not: a mechanism to force a bank to accept a discrepant presentation. The banks' documentary defenses are strong. The leverage in a discrepancy situation is almost never legal compulsion of the bank — it is the commercial fact that the buyer wants the goods sitting in its port.

6. Building the Prevention Into the Deal

Because the ten failure modes are clerical, the prevention is procedural, and it attaches at three moments:

• At contract and credit issuance: realistic expiry, presentation period, and shipment dates; a documents list matched to what the beneficiary can actually produce; tolerance fields deliberate, not inherited. A well-drafted credit is a discrepancy-prevention device — the same logic as the structural review in the mineral sands article.
• At credit receipt: read the advice against the contract immediately, and for soft clauses and impossible conditions use the checks in the soft clauses article. Some discrepancies are manufactured at issuance, not at presentation — an unfixable date or an applicant-signed certificate is a refusal waiting to be scheduled.
• At presentation: a single source sheet feeding all documents; every repeated field cross-checked; names copied character-for-character; the set lodged with days to spare. None of this is sophisticated. All of it is decisive.

What To Do With This

For exporters drawing under LCs — and for buyers structuring them:

1. Draft time into the credit: shipment, presentation, and expiry dates with buffers, so cure-and-represent remains possible.
2. Build the document checklist from the credit's required-documents list — present exactly that, and nothing extra.
3. Lock names and goods descriptions character-for-character from the credit into every template.
4. Cross-check every repeated field — quantities, weights, container numbers, ports — across the set before lodgment.
5. On refusal, move on day one: read the notice's complete list, classify each item as curable or not, and open the waiver conversation with the applicant immediately.
6. Never surrender original transport documents to the applicant while payment is unresolved — control of the documents is control of the cargo.
7. Keep the contract claim alive in parallel — the credit's refusal is not the end of the money; the contract still is.

Discrepancy risk is not a reason to avoid letters of credit. It is a reason to treat the documentary chain as part of the transaction's legal engineering — drafted at issuance, checked at receipt, executed with discipline at presentation.

This article is general information, not legal advice, and does not create an attorney–client relationship. References to UCP 600 are general and non-exhaustive; banking practice varies by institution and jurisdiction — confirm specifics with counsel. Outcomes vary by case; nothing here is a guarantee of results.