The five most common reasons for BL rejection
Banks operating under a Letter of Credit don't read documents for meaning. They compare them against the LC terms character by character. Under UCP 600, the rules that govern most LC transactions, a bank has the right to refuse any document that contains a discrepancy from the LC, no matter how trivial it looks to you.
Here are the five issues that generate the most rejections, in order of how often they appear:
1. Name discrepancy between BL and LC
The LC says "ABC Trading Co. Ltd", your BL says "ABC Trading Company Limited." To you, these are the same. To the bank, they are different. The consignee name, notify party, and shipper name on the BL must match the LC exactly, including punctuation, abbreviations, and capitalisation. This is the single most common discrepancy, and it is entirely avoidable.
2. Late presentation beyond the LC expiry or presentation period
Most LCs specify a presentation period, typically 21 days after the on-board date, but sometimes less. If your BL is dated correctly but you present it to the bank on day 22, the bank can and will refuse it. Physical courier delays, internal approval chains, and lost originals are the usual culprits here. The problem is systemic, not accidental.
3. Port names not matching the LC exactly
The LC specifies "Port of Hamburg", the BL says "Hamburg, Germany." Or the LC says "any Chinese port" and the BL says "Ningbo." Whether that's acceptable is a judgment call the bank may make against you. Always use the exact port wording from the LC on your BL, even if an alternative phrasing seems equivalent.
4. Goods description mismatch
The LC specifies "100% cotton woven fabric, 150cm width." The BL says "textile goods." Under UCP 600, the goods description on the BL doesn't have to be identical to the LC, but it must not conflict with it. In practice, vague descriptions on shipping documents are routinely flagged. The safest approach is to use the exact LC language verbatim or a more specific version of it.
5. Missing or incorrect endorsement
If the LC requires a BL endorsed "to order of issuing bank," that endorsement must appear on the reverse of the original BL in exactly that form. An unendorsed BL, or one endorsed to the wrong party, is a clean discrepancy. This is especially common when documents pass through multiple hands before presentation.
Why these keep happening
The root cause is straightforward: the same information is typed by multiple people, in multiple systems, at multiple stages of the transaction. The LC is issued by the buyer's bank with specific wording. The exporter types the BL details. The freight forwarder prepares the packing list. The export manager compiles the commercial invoice. None of these parties are checking each other's work against the LC before submission.
Each re-entry of data is a chance for a discrepancy. "Ltd" becomes "Limited." A hyphen gets dropped. A port gets abbreviated differently. No single person is responsible for the final cross-check, so no final cross-check happens.
Banks routinely report discrepancy rates above 60% on first presentation under LCs. That means more than half of all trade finance document sets are rejected at least once. This is not a problem unique to small operators or inexperienced teams, it affects large trading companies with dedicated documentation departments.
What a discrepancy actually costs you
Banks charge a discrepancy fee, typically USD $75 to $150 per document set, when they accept documents under reserve or handle a discrepancy waiver. That fee is the least of your problems.
The real cost is time. A rejected BL has to be corrected, re-issued, and re-presented. In the meantime, the cargo is at the destination port. If your consignee cannot produce the original BL, the goods cannot be released. Demurrage accrues at the port. Depending on the commodity and the shipping line, this can run to several hundred dollars per day per container, and it starts from the moment free time expires, not from when your dispute with the bank is resolved.
There is also the LC expiry risk. If you are close to the LC's expiry date when the discrepancy is identified, you may not be able to re-present corrected documents in time. You then lose the security of the LC entirely and are exposed to buyer credit risk with no payment guarantee.
And there is the relationship cost. Buyers who receive a shipment late, or who have to deal with port delays because of a documentation error, remember it. It becomes a mark against your reliability, regardless of whose fault the discrepancy technically was.
How to prevent them
These discrepancies are not mysterious. They have a clear cause and a clear solution. Here is the checklist that any documentation coordinator should be running before every presentation:
Pre-presentation checklist
- 1.Pull the original LC and read the exact wording for consignee, notify party, port of loading, port of discharge, and goods description before the BL is issued, not after.
- 2.Copy-paste the consignee name and address from the LC directly into the BL instruction to the carrier. Do not retype it. One character difference is a discrepancy.
- 3.Check port names against the LC. If the LC says 'Port of Rotterdam,' the BL must say 'Port of Rotterdam', not 'Rotterdam' or 'RTM.'
- 4.Verify the on-board date and calculate the presentation deadline. Put that date in a visible place. Chase the bank if you are within five business days of it.
- 5.Confirm the endorsement requirement before the originals leave your hands. Check: who must sign, what the wording must say, which copies require endorsement.
- 6.When the complete document set is assembled, BL, commercial invoice, packing list, certificate of origin, any other required documents, lay them side by side and check the following fields across all documents: shipper name, consignee name, goods description, quantities, container numbers.
The structural fix
The checklist above reduces discrepancies significantly. But it does not eliminate the fundamental problem, which is that multiple documents are being produced from multiple data entries.
When the Bill of Lading, commercial invoice, and packing list are all generated from a single data source, one entry, one point of truth, the cross-document discrepancy problem disappears at the root. There is no rekeying, so there is no divergence between documents.
This is one of the things DocuShield was built to do. When you create a shipment in DocuShield, the trade data you enter populates all associated documents. The consignee name is the same on every document because it comes from the same field. Port names, goods descriptions, container references, they are all consistent, because they are generated, not manually replicated.
The result is not just fewer discrepancies. It is a documentation process that is faster, auditable, and significantly less stressful for your team.
Interested?
See it in practice
Book a 20-minute walkthrough to see how DocuShield handles document generation, consistency, and electronic BL transfer.
Book a demo