The LC Was Confirmed. The Bank Still Did Not Pay.
Quote from chief_editor on May 16, 2026, 3:30 pmA confirmed letter of credit doesn't guarantee payment. Document discrepancies give the confirming bank grounds to refuse. Traders learn this late.
The seller presented documents under a confirmed, irrevocable LC issued by a first-tier bank in Singapore. The LC had been confirmed by a major European bank. From the seller's perspective, this was maximum security — an irrevocable payment undertaking confirmed by a bank with no credit risk. The goods had shipped. The documents were in hand.
The confirming bank examined the documents and issued a notice of discrepancy within five banking days, as permitted under UCP 600. Two discrepancies. First, the description of goods in the commercial invoice read "iron ore fines, Fe content min 58%" while the LC specified "iron ore fines, Fe 58% minimum guaranteed." Second, the date on the certificate of origin was one day after the bill of lading date, while the LC required all documents to be dated no later than the bill of lading date.
Payment was refused. The seller had three options: correct the documents if possible (the certificate of origin date could not be corrected; it reflected when the issuing authority had stamped the document), request buyer's waiver of discrepancies, or accept payment under reserve, which would unwind if the issuing bank ultimately rejected the documents.
The buyer, for reasons unrelated to the documents, was experiencing cash flow pressure. They declined to waive the discrepancies.
The Document Must Match the LC, Not the Cargo
This is the mechanism that surprises sellers who have shipped good cargo and expect to be paid. The LC is not a quality verification system. It is a document verification system. Under UCP 600, which governs the overwhelming majority of international documentary credits, banks deal in documents, not in goods. The confirming bank's obligation is to pay against complying documents. If documents do not comply, the obligation does not arise — regardless of whether the cargo is exactly what was contracted for, regardless of whether it has already been shipped and cannot be recovered.
The "Fe 58% minimum guaranteed" versus "Fe content min 58%" discrepancy illustrates how fine the compliance standard is. Both phrases describe the same commercial reality. A reasonable person reading both would understand them as equivalent. The bank's document examiner, operating under UCP 600 Article 14, is not applying a reasonableness standard. They are checking whether the invoice description matches the LC description on its face. It does not match. The discrepancy is valid.
Industry estimates suggest that in global trade finance, somewhere between 60 and 70 percent of first presentations under documentary credits contain at least one discrepancy. A significant portion of these are waived by buyers without disruption to payment. But the waiver requires the buyer to be willing and solvent — and the waiver mechanism is precisely the point where a buyer experiencing financial difficulty or commercial dispute can introduce delay without explicitly defaulting.
The timing dimensions compound the problem. Under UCP 600, banks have five banking days to examine documents and notify of discrepancies. Sellers may not know they have a discrepancy problem until five days after presentation. If the buyer declines to waive, the seller must decide whether to accept payment under reserve, go back to try to correct documents (not always possible), or pursue other remedies. None of these options are fast.
The LC Conditions That Only the Seller Can Create
A particular category of LC risk involves conditions written into the LC that require the seller to produce documents that only the buyer can arrange or that are contingent on buyer action. Requirements for a "buyer's inspection certificate" issued at destination, or for a certificate signed by a specific buyer's representative, or for a "release order" from the buyer — these conditions make payment contingent on buyer cooperation after the goods have shipped.
In normal commercial relationships, these conditions get satisfied routinely. When the commercial relationship deteriorates, the buyer's refusal to issue the required certificate becomes a mechanism for blocking payment under an LC that the seller believed was their protection.
The operationally clear principle: the protection offered by a confirmed LC is strictly limited to situations where the presented documents are fully compliant with the LC terms. Every deviation, however commercially trivial, is a potential ground for refusal. Sellers who want the protection of the LC mechanism need to ensure that the LC terms, as written, can actually be satisfied by documents they control — and that no condition in the LC requires buyer participation after shipment. That review happens before shipment, not after the documents are presented.
A confirmed letter of credit doesn't guarantee payment. Document discrepancies give the confirming bank grounds to refuse. Traders learn this late.
The seller presented documents under a confirmed, irrevocable LC issued by a first-tier bank in Singapore. The LC had been confirmed by a major European bank. From the seller's perspective, this was maximum security — an irrevocable payment undertaking confirmed by a bank with no credit risk. The goods had shipped. The documents were in hand.
The confirming bank examined the documents and issued a notice of discrepancy within five banking days, as permitted under UCP 600. Two discrepancies. First, the description of goods in the commercial invoice read "iron ore fines, Fe content min 58%" while the LC specified "iron ore fines, Fe 58% minimum guaranteed." Second, the date on the certificate of origin was one day after the bill of lading date, while the LC required all documents to be dated no later than the bill of lading date.
Payment was refused. The seller had three options: correct the documents if possible (the certificate of origin date could not be corrected; it reflected when the issuing authority had stamped the document), request buyer's waiver of discrepancies, or accept payment under reserve, which would unwind if the issuing bank ultimately rejected the documents.
The buyer, for reasons unrelated to the documents, was experiencing cash flow pressure. They declined to waive the discrepancies.
The Document Must Match the LC, Not the Cargo
This is the mechanism that surprises sellers who have shipped good cargo and expect to be paid. The LC is not a quality verification system. It is a document verification system. Under UCP 600, which governs the overwhelming majority of international documentary credits, banks deal in documents, not in goods. The confirming bank's obligation is to pay against complying documents. If documents do not comply, the obligation does not arise — regardless of whether the cargo is exactly what was contracted for, regardless of whether it has already been shipped and cannot be recovered.
The "Fe 58% minimum guaranteed" versus "Fe content min 58%" discrepancy illustrates how fine the compliance standard is. Both phrases describe the same commercial reality. A reasonable person reading both would understand them as equivalent. The bank's document examiner, operating under UCP 600 Article 14, is not applying a reasonableness standard. They are checking whether the invoice description matches the LC description on its face. It does not match. The discrepancy is valid.
Industry estimates suggest that in global trade finance, somewhere between 60 and 70 percent of first presentations under documentary credits contain at least one discrepancy. A significant portion of these are waived by buyers without disruption to payment. But the waiver requires the buyer to be willing and solvent — and the waiver mechanism is precisely the point where a buyer experiencing financial difficulty or commercial dispute can introduce delay without explicitly defaulting.
The timing dimensions compound the problem. Under UCP 600, banks have five banking days to examine documents and notify of discrepancies. Sellers may not know they have a discrepancy problem until five days after presentation. If the buyer declines to waive, the seller must decide whether to accept payment under reserve, go back to try to correct documents (not always possible), or pursue other remedies. None of these options are fast.
The LC Conditions That Only the Seller Can Create
A particular category of LC risk involves conditions written into the LC that require the seller to produce documents that only the buyer can arrange or that are contingent on buyer action. Requirements for a "buyer's inspection certificate" issued at destination, or for a certificate signed by a specific buyer's representative, or for a "release order" from the buyer — these conditions make payment contingent on buyer cooperation after the goods have shipped.
In normal commercial relationships, these conditions get satisfied routinely. When the commercial relationship deteriorates, the buyer's refusal to issue the required certificate becomes a mechanism for blocking payment under an LC that the seller believed was their protection.
The operationally clear principle: the protection offered by a confirmed LC is strictly limited to situations where the presented documents are fully compliant with the LC terms. Every deviation, however commercially trivial, is a potential ground for refusal. Sellers who want the protection of the LC mechanism need to ensure that the LC terms, as written, can actually be satisfied by documents they control — and that no condition in the LC requires buyer participation after shipment. That review happens before shipment, not after the documents are presented.