The Discrepancy #003: When 'Clean on Board' Isn't Clean Enough

On a Tuesday afternoon in Geneva, after four days of SWIFT messages, the issuing bank withdrew the discrepancy. The presenting bank's final message had cited ISBP 745 paragraph E13 verbatim and warned of a referral to the ICC Banking Commission. The documents were honored. The cargo was released.

The paragraph that ended the argument reads: "Clauses on a transport document such as 'shipper's load and count' and 'said by shipper to contain' are not considered to be clauses or notations that indicate a defective condition of the goods or their packaging."

That is the resolution. Now here is how a routine soybean shipment became a four-day standoff over six words that appear on virtually every bulk commodity bill of lading in the world.

The shipment

A bulk carrier loads 25,000 MT of Brazilian soybeans at Santos. The bill of lading is stamped "CLEAN ON BOARD" by the carrier's agent, with the notation: "cargo loaded per shipper's count and weight."

Standard language. Every voyage charter B/L for bulk commodities carries some version of it. The carrier was not present when the cargo was weighed. The carrier did not count the bags. The carrier is stating, accurately, that the shipper provided the figures. This is how bulk shipping works.

The LC, issued by a bank in Geneva and valued at approximately $11.4 million, required presentation of a "clean on board bill of lading." The exporter's bank presented the documents. The rejection notice, reviewed by tradefinance.news, stated:

"Bill of lading bears qualifying notation 'per shipper's count and weight' which renders the document unclean."

The cargo was already at sea.

Why the issuing bank was wrong

The presenting bank. And it is not close.

UCP 600 Article 27 defines a clean transport document as one that "bears no clause or notation expressly declaring a defective condition of the goods or their packaging." The word that matters is condition. A defective condition means damaged goods, torn packaging, rust stains, wet cargo. The clause "per shipper's count and weight" says nothing about condition. It addresses who provided the quantity figures. These are different categories entirely.

ISBP 745, the ICC's international standard banking practice guidance, makes this explicit at paragraph E13. "Shipper's load and count," "said by shipper to contain," and similar clauses are not discrepancies. The ICC Banking Commission has ruled on nearly identical cases multiple times, according to a person at the presenting bank who handled the dispute. The answer is always the same.

The issuing bank's position was that any notation qualifying the carrier's acceptance of the cargo introduces doubt about the quantity or condition of the goods. That conflates two separate concepts. Quantity responsibility and cargo condition are not the same thing, and UCP 600 does not treat them as the same thing. The examiner who flagged this either did not understand the distinction or chose to ignore it.

Four days, $60,000 to $80,000

Four days does not sound like much. On a Supramax or Handysize bulk carrier running the Santos-to-Geneva corridor, demurrage runs roughly $15,000 to $20,000 per day. That is $60,000 to $80,000 in costs that did not need to exist, on top of an $11.4 million shipment, because an examiner treated a standard industry clause as a document defect.

According to a person at the presenting bank, the exporter's trade finance team spent those four days assembling UCP citations, coordinating with legal counsel, and drafting SWIFT responses. The presenting bank's operations desk, which had processed hundreds of bulk commodity B/Ls with identical language, treated the rejection as frivolous from the first message. But procedure is procedure. Each response cycled through compliance review on both sides, burning 24 to 48 hours per message.

The knowledge problem

This is the third case in this series. The comma (#001), the word order (#002), and now a standard carrier clause. Each case shares a pattern: an examiner applies a rule without understanding the commercial context that the rule was written for.

A senior trade finance consultant who reviewed the case for tradefinance.news said: "Ten years ago, no examiner would have flagged this. The people who knew bulk commodity documentation have retired. The new generation works from checklists."

That observation deserves more than a passing mention. Over the past decade, banks have cut trade finance operations headcount substantially. The 2020s wave of compliance cost pressures, automation investments, and strategic retreats from correspondent banking all contributed. Senior document examiners who had spent twenty or thirty years reviewing commodity B/Ls, who could tell you from memory which carrier clauses were standard and which were genuinely anomalous, have left the industry. Some retired. Some were made redundant in restructuring rounds. Some moved to advisory or consulting roles.

What replaced them, in many institutions, is a compliance-driven checking process built around checklists and keyword matching. These systems are good at catching the obvious: missing signatures, expired documents, wrong port names. They are not good at distinguishing between a genuine discrepancy and a clause that has appeared on bulk commodity bills of lading for decades. The knowledge that was accumulated over entire careers is being replaced by frameworks that cannot exercise judgment. The result is what happened here: a clause that every experienced examiner would recognize instantly gets flagged by someone, or something, that does not know what it is looking at.

The incentive structure makes this worse. An examiner who approves a questionable document bears personal accountability. An examiner who rejects one faces, at worst, a query from the presenting bank. Caution is rewarded even when it is wrong. Combine that with the knowledge gap, and you get a system that over-flags by design.

What beneficiaries should do

If you are presenting bulk commodity B/Ls under a letter of credit, do not assume the examiner on the other side has seen one before. Protect yourself.

Include a cover letter citing ISBP E13. When your presentation includes a B/L with "shipper's load and count," "said by shipper to contain," or any standard carrier qualification, attach a cover note that cites ISBP 745 paragraph E13 by name. State that the clause is explicitly addressed by international standard banking practice and does not constitute a discrepancy. This does not guarantee the examiner will read it. But it creates a paper trail and gives whoever reviews the rejection an immediate reference point.

Request permissive LC language upfront. At the LC structuring stage, ask the applicant's bank to include language such as: "Bills of lading bearing standard carrier clauses including but not limited to 'shipper's load and count' and 'said by shipper to contain' are acceptable." This eliminates the argument before it starts. It adds one line to the LC. That one line is worth more than any amount of post-rejection correspondence.

Brief the examiner before presentation, when possible. If you have a relationship with the issuing bank's trade operations desk, a phone call before presentation can save days. "We are presenting a bulk commodity B/L with standard carrier clauses. Here is the ISBP reference." Not every bank will engage. But the ones that do will flag it internally before the document hits the checking queue.

Keep your ISBP citations ready. Do not wait for the rejection to start assembling your argument. Have a standard response template with UCP 600 Article 27 and ISBP 745 paragraph E13 pre-drafted. When the refusal lands, your first response should go out the same day with the full legal basis. Speed matters. Every day spent drafting a response is another day of demurrage.

None of this should be necessary. The rules are clear. But the gap between what the rules say and how they get applied at 11 p.m. in a back office is where the money disappears.

-- Tamara

---

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