Ask anyone who's presented documents to the same bank twice and they'll tell you: every bank has its quirks. The problem is, nobody writes them down.
UCP 600 and ISBP 745 provide the universal rules. But individual banks layer their own preferences on top — unstated requirements, interpretation habits, formatting expectations that aren't in the LC and aren't in the rulebook but will absolutely show up in a refusal notice if you don't follow them.
In the trade finance world, these are called house rules. And they live almost entirely inside people's heads.
What house rules look like
A bank in the Gulf that always requires the LC number to appear on every page of the packing list, not just the first. The LC doesn't say this. ISBP 745 doesn't say this. But present a packing list without it, and the discrepancy notice arrives like clockwork.
A European bank that treats "pcs" and "pieces" as different units of measurement. Both obviously mean the same thing. But the bank's document examination team flags any inconsistency between the LC wording and the documents, and if the LC says "pieces" and your invoice says "pcs," you're getting a call.
A bank in East Asia that refuses certificates of origin unless the signature is in blue ink. The scanned PDF you submitted — which is a perfectly legitimate presentation format — shows black ink because that's what scanners produce. Refused.
These aren't hypothetical examples. Variations of all three happen regularly, across hundreds of banks, in dozens of countries. Each one, individually, seems petty. Collectively, they represent a significant source of discrepancies that have nothing to do with the quality of your documents and everything to do with institutional knowledge you're expected to have but nobody gives you.
Where this knowledge lives
In the mind of the person in your office who has dealt with that bank before. In a note someone scribbled on a printout three years ago that may or may not still be in a filing cabinet. In the memory of the freight forwarder's documentation team, who've been presenting to that bank for a decade and know to add the LC number to every page.
When that person retires, or leaves, or is off sick, the knowledge goes with them. The replacement prepares a perfectly standard presentation. The bank refuses it for a house rule that isn't written in any document the replacement has access to.
This is a genuine operational risk. It's not quantified, it's not managed, and it's not discussed — partly because admitting that your company's compliance depends on one person's memory is uncomfortable, and partly because it sounds like a minor problem until you calculate the cost of discrepancy fees and delayed payments across a year.
The pattern behind the problem
Banks develop house rules for defensible reasons. Their document examiners are trained to look for consistency, and individual examiners develop preferences based on their experience and their institution's internal guidelines. Over time, these preferences calcify into practice, and practice becomes expectation.
The issue isn't that banks have preferences. It's that those preferences aren't communicated. They're discovered by trial and error — you present documents, get refused, learn the preference, adjust next time. If you're lucky, the refusal notice is specific enough to identify the actual requirement. If you're unlucky, it's a vague "documents not in compliance" that requires a phone call and some interpretation.
Some banks are better than others. A handful publish examination guidelines. Others provide feedback when they refuse documents, explaining not just the discrepancy but the underlying expectation. Most, though, operate on the assumption that you should already know — even if there's no way you could.
What should exist but doesn't
A structured, searchable record of bank-specific preferences and requirements. Not a substitute for UCP 600 — an addition to it. A knowledge base that captures: this bank requires blue ink signatures. That bank treats "pcs" and "pieces" as non-equivalent. The other bank wants the LC number on every page.
Updated over time, as you learn. Shared across the team, not locked in one person's head. Referenced automatically during document preparation, not recalled from memory under deadline pressure.
This kind of institutional knowledge management is standard practice in every other compliance-heavy industry. Law firms maintain precedent databases. Audit firms maintain client-specific methodology files. Medical practices maintain patient-specific protocols. Trade finance? Trade finance maintains nothing. The knowledge walks in and out of the building with the people who carry it.
The interim fix
If you can't build or buy a system for this yet, at least start documenting. A shared spreadsheet with three columns — bank name, requirement, and source — is better than nothing. Every time you receive a discrepancy notice that reflects a bank preference rather than a genuine compliance failure, add it to the list.
Over six months, you'll have a remarkably useful document. Over a year, you'll wonder how you ever operated without it.
The goal isn't to memorise every bank's quirks. It's to stop treating institutional knowledge as something that lives in people's heads and start treating it as an operational asset that belongs to the company.
David Berney is the founder of SmartLC, a trade finance platform for managing the Letter of Credit lifecycle. He builds software for the people who actually prepare, check, and present trade documents.