Packing List Weight Discrepancy: The Quantity Boundary Under UCP 600

Introduction: The Figure That Must Reconcile

A packing list details how goods are packed — quantities, weights, and measures. When the weights on the packing list diverge from the commercial invoice, the transport document, or field 45A, the examining bank applies a binary data-consistency determination under UCP 600 Article 14(d) and ISBP 745. The error is rarely a measurement dispute; it is a compilation mutation, where the packing list is generated from a warehouse system using a different unit or rounding basis than the invoice. The bank does not negotiate the warehouse reality; it compares figures and rejects variance.

Failure Mode Analysis

Failure Mode 1: Unit-Basis Mutation

The invoice states weight in kilograms; the packing list in pounds, without conversion. The bank reads the raw figures as conflicting and rejects under Article 14(d). The failure was pre-compiled at the warehouse-export layer.

Failure Mode 2: Rounding Divergence

The invoice rounds to the nearest 10 kg; the packing list states exact kg. The small delta is treated as a data conflict by the examining bank, which applies no tolerance to weight discrepancies.

Failure Mode 3: Partial-Shipment Weight Drift

For a partial shipment, the invoice reflects the shipped portion while the packing list reflects the full order. The bank isolates the weight mismatch and transmits a discrepancy notice.

Deterministic Resolution Architecture

1. Compile the quantity basis before presentation. Parse field 45A and the invoice for the mandated weights and units. The credit's text is the only binding specification.
2. Isolate weight divergence at the compilation layer. Flag any packing-list weight that conflicts with the invoice or 45A. This flag is a pre-compiled failure mode that downstream verification cannot repair.
3. Decouple packing-list generation from shipment timing. Generate the packing list from the same data source as the invoice before the presenting bank receives the set. Re-issuance after presentation races the examination clock.
4. Validate unit reconciliation. Ensure all weights share a unit or are explicitly converted so the bank can verify consistency.

Conclusion

The packing-list weight discrepancy is a quantity boundary problem, not a measurement problem. UCP 600 Article 14(d) grants no tolerance for variance from the invoice. The moment the invoice states the weight, consistency becomes a binary condition. Pre-compile the basis, isolate divergence, and decouple timing — the only regime under which Article 14(d) functions as designed.

FAQ

Q1: Must the packing list match the invoice weight exactly?
It must not conflict with it. A different unit without conversion is a conflict; an exact match or a generic description is acceptable.

Q2: If the packing list is correct and the invoice is wrong, who is discrepant?
The set is discrepant. Article 14(d) looks at conflict between documents; whichever carries the wrong weight, the presentation fails.

Q3: Can the applicant waive the weight conflict after a discrepancy notice?
The applicant may accept under Article 16, but that is a post-discrepancy remedy. The cost — delayed payment, impaired trust — is already incurred.

Q4: Does a 5% quantity tolerance cover packing-list weight?
Article 30 permits quantity tolerance only where the credit allows; it never permits conflicting data. A packing-list/invoice weight conflict is discrepant regardless of tolerance.