The Discrepancy #001: The $600,000 Comma

The SWIFT message landed on the Frankfurt ops desk at 7:14 a.m. on a Monday. MT734, advice of refusal. The issuing bank in New York had found a discrepancy in the document presentation.

The cargo was already on the water. A Panamax bulk carrier, loaded with 12,500 metric tons of hot-rolled steel coil, steaming toward the US East Coast. The LC value: approximately $8.7 million, confirmed by the New York bank, documents presented in Frankfurt the previous Thursday. Routine deal. Baltic loading, US discharge, standard commodity terms, according to people involved in the transaction.

The discrepancy notice read:

"Quantity on commercial invoice (12.500 MT) and packing list (12.500 MT) does not match LC requirement of 12,500 MT."

A period where a comma should be. That was it.

Continental arithmetic

The LC, issued in New York, stated the quantity as:

"12,500 MT (TWELVE THOUSAND FIVE HUNDRED METRIC TONS) OF HOT ROLLED STEEL COIL"

The German seller's ERP system generated the commercial invoice and packing list using continental European formatting. In Germany, and across most of continental Europe, the comma and period serve opposite roles. Where an American writes 12,500 to mean twelve thousand five hundred, a German writes 12.500. Where an American writes 12.500 to mean twelve and a half, a German writes 12,500.

The invoice read "12.500 MT." The packing list read "12.500 MT." To any European reader, unambiguous. To the document checking team at a US bank reviewing presentations late on a Friday, it read as twelve point five metric tons.

This is the kind of discrepancy that UCP 600 was designed to handle. Article 14(d) says document data need not be identical to the LC but must not conflict with it. The word description on the invoice, "TWELVE THOUSAND FIVE HUNDRED METRIC TONS," was right there on the same page. It did not conflict with "12.500 MT" under European notation. A contextual reading resolves the ambiguity. ISBP 745 paragraph A26 reinforces this: when data in a document can be read in context with other data in the same document, the document should not be considered discrepant. The ICC Banking Commission has addressed regional number formatting in multiple opinions, and the consensus is consistent. Formatting differences do not constitute discrepancies when intent is clear from context.

The issuing bank was wrong. But proving that took eighteen days.

Eighteen days

The beneficiary's bank in Frankfurt responded within 24 hours. European notation, word description confirms intent, no conflict under Article 14(d). Straightforward.

The New York bank's compliance team rejected the explanation. Their position: the LC was issued in US format, the documents must match the LC format, and the numeric discrepancy creates ambiguity about the quantity of goods. "We flagged it because our system treats any numeric mismatch as a hard stop," said a person at the issuing bank who spoke on condition of anonymity. "In hindsight, the word description should have resolved it."

Meanwhile, the vessel was approaching the US discharge port. The buyer wanted the steel. But the bank had not released the documents. The buyer's credit department would not authorize a discrepancy waiver without legal review. Legal review takes time.

Days one through five: SWIFT messages back and forth. Each one cycling through compliance review on both sides, 24 to 48 hours per response.

Days six through twelve: the buyer's legal team reviewed the UCP 600 position, concluded the documents were likely compliant, and recommended the waiver as a precaution anyway.

Days thirteen through eighteen: waiver processed, documents released, cargo discharged.

Eighteen days of a Panamax sitting at anchor. Demurrage on a vessel that size runs approximately $22,000 to $28,000 per day. Total demurrage: roughly $430,000. Add legal fees on both sides, bank amendment fees, extended insurance coverage, and the total exceeded $600,000. Documents reviewed by tradefinance.news confirm the final figure.

All because a comma was in the wrong place. Or the right place, depending on which continent you are standing on.

According to ICC surveys, approximately 70 to 75 percent of first-time LC presentations are refused for discrepancies. Most are caught and corrected before they cost real money. This one was not.

What it costs to ignore your ERP settings

If you are preparing documents for an LC issued in a different regional format, three things will save you.

Override your ERP defaults. Most European enterprise systems default to continental formatting: period as thousands separator, comma as decimal. When preparing documents for a US or UK-issued LC, override the output formatting to match the LC's convention. Five minutes in system configuration. That is the trade. Five minutes against six figures.

Include word descriptions for quantities and values. UCP 600 does not require it. Do it anyway. If your invoice says "12.500 MT (TWELVE THOUSAND FIVE HUNDRED METRIC TONS)," the worst outcome is a phone call. Without the words, you are in dispute territory with no fallback.

Brief every party in the document chain. You control the commercial invoice. But the packing list, weight certificate, and other supporting documents may come from freight forwarders, warehouses, inspection companies. Every document in the presentation needs consistent number formatting that matches the LC. One mismatched certificate from a third party is enough to trigger refusal.

These are not sophisticated fixes. They are operational hygiene. The kind of thing that gets skipped when the ops desk is processing thirty presentations a week and the ERP just outputs what it outputs.

A comma is not just punctuation. In trade finance, it is a liability.

-- Tamara

---

Have a discrepancy story? We anonymize everything. Send it to stories@tradefinance.news.