Reconciling Invoice, Packing List, B/L and Shipping Bill Before LEO

The Let Export Order converts working documents into a sworn record. Under Section 50(2) of the Customs Act, the exporter presenting a Shipping Bill "shall at the foot thereof make and subscribe to a declaration as to the truth of its contents" — every value, weight, count and identifier on the Shipping Bill is declared to customs as fact, including every field that was copied from an invoice or packing list nobody cross-checked. Under Section 51, the proper officer's clearance order rests on that declaration.

After export, the correction window is narrow in law and gated in practice. Section 149 permits amendment only at the proper officer's discretion and, post-export, only on documentary evidence in existence at the time of export. The machinery under it — the Export Entry (Post export conversion in relation to instrument-based scheme) Regulations, 2025, implemented by CBIC Circular No. 11/2025-Customs of 03.04.2025 — allows amendment of a specified field list only (ports, country of final destination, AD Code, invoice value, HS code, description, quantity), each change requiring Additional/Joint Commissioner approval, within one year of the Section 51 clearance order, extensible by six months by the jurisdictional Commissioner and a further six by the Chief Commissioner, on recorded reasons. The refund pipeline is stricter still — Chennai Customs' rectification procedures state flatly that no amendment can be made to the Shipping Bill once the EGM has been filed, and the invoice number is not on the amendable list at all. Correction migrates to whichever record is still writable: the GST return, the manifest, or an officer-verified mapping.

The identifiers that link the four documents — invoice number, GSTIN, IEC, container numbers, Shipping Bill number in the GST return — are matched by machine as exact strings, and each has a named failure code. The invoice number on the Shipping Bill against GSTR-1 Table 6A is the SB005 check, where a one-character formatting divergence (EXP/2026/0042 against EXP-2026-0042) blocks the IGST refund; its formatting mechanics are dissected in Invoice Number Formatting: How Tally and ICEGATE Disagree. The GSTIN on the Shipping Bill against the GSTIN filing the returns is the SB003 check — a live risk for multi-registration exporters. The container numbers on the Shipping Bill against the EGM is error flag C in the manifest validation.

The pre-LEO verification standard for this family is character equality against the issuing system, not visual similarity between PDFs. The invoice number is verified against the accounting system's tax invoice; the GSTIN against the registration that will file GSTR-1 for the supply; container and seal numbers against the final stuffing report rather than the booking. Consignee name and address should also be verbatim-consistent across invoice, packing list and B/L draft — they are not machine-matched by ICES, but they are read side by side by banks and, later, by insurers and surveyors.

Package counts and weights reconcile across all four documents, and the manifest validation names their failure flags: N (number of containers mismatched between Shipping Bill and EGM), P (number of packets), T (nature of cargo). The DG Systems guide's Annexure B sets out the repair choreography when these fire at a gateway port — EGM amendment where the manifest is wrong, and where the Shipping Bill is wrong, a sequence that runs through LEO cancellation, amendment, re-registration and fresh LEO. Every step of that sequence is avoidable at the draft stage by counting once, carefully, in one place.

Three consistency rules cover most quantity failures. First, the package count in the Packing List's detail must equal its own header total — internally inconsistent packing lists (a header declaring 10 packages over a table listing 9) are a documented pattern in MSME documentation. Second, net and gross weights must be the same figures, in the same unit, on the Packing List, the B/L draft and the Shipping Bill, with rounding applied once rather than at each transcription. Third, the unit of measurement declared on the Shipping Bill must be the statutory unit for the tariff item, not the commercial unit the invoice happens to use — pieces against kilograms is a units mismatch even when both figures are individually right.

The Commercial Invoice's value, the Shipping Bill's declared value and the GST return's taxable value must tell one arithmetic story: line totals summing to the invoice total, the invoice total reconciling to the Shipping Bill's FOB and invoice-value declarations under the stated currency and Incoterm, and the taxable value and IGST in GSTR-1 Table 6A matching what the Shipping Bill claims. CBIC's Circular 05/2018 lists value-and-tax consistency between GSTR-1, GSTR-3B and the Shipping Bill among the prerequisites for refund processing — the invoice-mismatch code SB005 covers "mis-match in taxable value and IGST paid," not only the invoice number.

Two structural traps sit in this family. The delivery term governs what the invoice total contains: an invoice issued CIF whose total is declared as FOB on the Shipping Bill misstates the FOB value and every FOB-derived figure downstream, including drawback and RoDTEP bases. And the currency must be declared as an ISO code consistently — an invoice totalled in one currency with the Shipping Bill assessed in another is a value mismatch regardless of the numbers. MSME invoice templates that embed the delivery term inside a price line ("CIF Jebel Ali" against the total) rather than a labelled field make this reconciliation a reading exercise; it should be a field comparison.

Goods descriptions and tariff classifications must be consistent at the level each document requires, which is not the same level on all four. The Shipping Bill requires the full eight-digit ITC(HS) tariff item; commercial invoices frequently carry four- or six-digit headings from the accounting master. A six-digit invoice heading and an eight-digit Shipping Bill item are not automatically a contradiction — the reconciliation question is whether the invoice's heading is the ancestor of the Shipping Bill's item, and whether one consistent classification underlies duty, incentive and any licensing determination. Divergent classifications across documents invite assessment queries and misapplied incentive rates; classification itself is a determination that requires human review and is not settled by reconciliation.

Descriptions differ by design and must be reconciled by containment rather than equality. A B/L describing "auto components" over an invoice specifying lithium-ion battery modules is conventional manifest abbreviation; the check is that the generic description truthfully contains the specific one, that any dangerous-goods character visible in the specific description is not laundered out of the generic one, and that marks and numbers on the Packing List match what is actually stencilled on the cargo the B/L will carry.