Automated LC review — now right here in the GuildUpload documents → AI discrepancy analysis → correction guide.
NEW Start LC Review →
← Blog

Packing List Discrepancies: The Mismatch Banks Catch Before You Do

0

Search intent: exporters preparing documents against a letter of credit (LC) want to know exactly which packing list details trigger a bank rejection, so they can fix them before submission instead of after.

What Actually Counts as a Packing List Discrepancy

A packing list feels like the least risky document in an LC document set. There is no price on it, no payment terms, nothing that looks financially sensitive. That is exactly why exporters relax on it, and exactly why banks do not.

Under UCP600 Article 2, a "complying presentation" has to satisfy three layers at once: the letter of credit's own terms, UCP600 itself, and the International Standard Banking Practice (ISBP). Article 14 sets the actual examination standard banks apply, and that standard does not treat the packing list as a formality. Examiners read it the same way they read every other document in the set: on its face, and against every other document in the presentation.

That second part is where most packing list discrepancies come from. A packing list is rarely rejected because it is wrong on its own. It is rejected because it disagrees with something else in the file.

The Quantity and Weight Mismatch Problem

The most frequent packing list issue is not a formatting mistake. It is a number that does not match. Net weight, gross weight, quantity per carton, total quantity, marks and numbers on the cartons: any one of these can be off by a small amount and still cause a hold.

This connects directly to the quantity and shipment rules covered in Chapter 12 of the standard exporter case reference, which deals with over/short shipment and partial shipment issues. The pattern shows up the same way across cases: a factory packs slightly more or fewer units than the invoice states, someone rounds a weight figure for convenience, or a last-minute carton is added without updating every document that references carton count. None of this is intentional. All of it is a discrepancy once it hits a bank examiner's desk.

Reality check: the packing list does not get evaluated in isolation. It gets evaluated against the invoice, the bill of lading, and the letter of credit terms, all at once.

When the Packing List Disagrees With the Invoice or the Bill of Lading

This is the failure mode exporters underestimate most. The packing list can be internally perfect, correctly formatted, correctly signed, and still get flagged because the total quantity does not match the commercial invoice, or the marks and numbers do not match what is printed on the bill of lading.

Under ISBP821 (the current edition, in force since July 2023, superseding ISBP745), examiners are instructed to check exactly this kind of cross-document consistency. A single typo in a carton count on one document, left uncorrected on another, is enough to create a documentary discrepancy even though the physical shipment is completely fine.

This is also why fixing a packing list discrepancy after the fact is expensive. It usually is not a one-document fix. It is a three-document reconciliation, done under time pressure, against a shipment that has already left the port.

The 5-Business-Day Rule Is Working Against You, Not For You

Under UCP600 Article 16, the issuing bank has five banking days after receiving the documents to decide whether they contain a discrepancy, and it must notify the beneficiary of that decision. Exporters often hear this rule and assume it works in their favor: five days sounds like a grace period.

It is not. It is a deadline for the bank, not for you. Once documents are presented, the five-day clock is the bank's opportunity to find a mismatch, not yours to fix one. By the time a discrepancy notice comes back, the shipment is already at sea or already at the destination port, and the exporter is negotiating from a much weaker position than if the mismatch had been caught before the documents were ever presented.

Why a 1% Agent Fee Doesn't Buy You Protection From This

We keep coming back to the same anonymized composite case across this series: a mid-sized exporter using a traditional trade agency that charges roughly a 1% commission per transaction to prepare and check LC documents. On paper, that fee looks like it should cover exactly this kind of cross-document check. In practice, it usually buys a manual read-through by one person, once, before the deadline. It does not buy a systematic, line-by-line comparison of every quantity, weight, and mark across every document in the set.

That is not a criticism of the agents themselves. It is a limitation of doing cross-document reconciliation by hand under a deadline. A 1% fee does not scale into the kind of exhaustive check that catches a rounding difference between a packing list and an invoice.

How T flow L/C Checker Catches These Before You Submit

This is the specific gap T flow L/C Checker is built to close. Instead of one person reading three documents once, it cross-checks every packing list field against the corresponding invoice and bill of lading fields, and against the letter of credit's own terms, automatically, before submission. Quantity, weight, marks and numbers, carton counts: the fields most likely to drift apart between documents are exactly the fields it is built to compare.

T flow is not a narrower version of what a trade agent does. It is part of a broader, full-stack trade operations and finance infrastructure, and document consistency checking is one layer of that stack, not a standalone product.

Check your packing list before the bank does

T flow L/C Checker cross-checks your packing list, invoice, and bill of lading against your letter of credit terms before you submit, so a small mismatch never becomes a discrepancy notice.

#packing list discrepancy #letter of credit (LC) #UCP600 #LC document rejection #export documentation #ISBP821 #trade finance compliance #T flow L/C Checker


Comments 0

No comments yet