SHIPMENT RECORD / 01
Make visible which order, goods and packing configuration the two files actually describe.
Commercial records may be drafted by different people and updated at different times. This guide is a comparison framework, not a universal document template or a statement of what a carrier, bank, customs authority or destination market requires.
01 / CONTROLLED BASELINE
Start with the order and product version, not the document title
Record the purchase-order number, seller and buyer, product or model revision, approved packing version, quantity, lot or shipment ID, intended route and relevant delivery notation. A document title alone does not reveal which commercial decision it belongs to.
Where the product definition changed, first identify the current product and packing baseline →. Where the order changed, retain the buyer’s specific revision decision.
A product name, broad destination or previous invoice is not evidence that the current invoice and packing list refer to the same approved order.
02 / COMMERCIAL INVOICE
Read the invoice as a current commercial description
Record the invoice number, issue date, issuing seller, buyer, currency, goods description, quantity, unit and total values where stated, order or shipment reference, delivery notation and current revision. Keep a draft separate from a final or amended record; do not replace a prior version without retaining why it changed.
The invoice needs the same seller and order context that was actually agreed. Keep quotation assumptions visible before comparing totals →
An invoice can describe a commercial transaction. It is not, by itself, proof of payment, title, export declaration, customs clearance or delivery.
03 / PACKING LIST
Make the physical packing description traceable
Record the packing-list number and date, package count, package type, shipping marks, item-to-package mapping where used, and declared net or gross weight, dimensions or volume where stated. Match the list to the controlled packaging revision and record which party supplied the figures.
Packaging marks and counts should be treated as shipment-specific data, not copied forward solely because a prior order used the same product name.
A packing list describes the stated packages. It does not prove that every item was packed, weighed, inspected, loaded or accepted for carriage.
04 / SHARED FIELD COMPARISON
Compare the fields that should describe the same shipment
Compare seller and buyer names, order or shipment reference, goods description, quantity, package count, packing marks, delivery notation, dates and the current version. Record a difference exactly as seen, who can clarify it and whether it affects the buyer’s next instruction.
The WCO Data Model distinguishes goods-transaction documents such as invoices and packing lists from transport-contract records. Keep transport responsibility and named points in a separate handover record →
A field match is a reason to continue the review. It is not evidence that all regulatory, carrier, banking or destination-market data requirements have been met.
05 / VERSION AND OWNER
Retain who prepared, checked, sent and received each version
For each record, keep its source, date received, version or amendment ID, preparer, checker and intended recipient. Note whether the supplier, buyer, forwarder or another party must provide a correction. Record references to transport instructions separately; their absence should remain visible rather than being filled from assumption.
If documents changed because the product, packing, factory or timing changed, record the affected scope and buyer decision →.
A forwarded file does not establish that its sender has authority to approve a commercial change or issue an instruction for the buyer.
06 / EXCEPTIONS AND NEXT DECISION
Keep differences open until the right party resolves them
Record missing order references, a changed seller or buyer name, a different goods description, quantity or package count, an unrecognised document number, changed packing marks, missing date, or a revised delivery notation. State the affected record, evidence, owner, deadline if one is agreed, and the buyer instruction still required.
Inspection answers what was checked under its scope. Keep an inspection report separate from invoice, packing and release decisions →
A consistent pair of records, or an inspection result, is not an automatic instruction to release goods, pay a balance, accept a charge or waive an exception.
CONTROL TABLE / 02
Minimum fields for an invoice and packing-list comparison record
| Control | Record | Question to resolve | Do not infer |
|---|---|---|---|
| Order baseline | PO, product and packing revision, quantity, seller, buyer and shipment ID | What current commercial decision do these files describe? | That a familiar product name identifies the same order |
| Invoice identity | Number, date, issuer, buyer, currency, value fields and revision | Which invoice version is being reviewed? | That an invoice proves payment, title or clearance |
| Packing identity | Number, date, package count/type, marks and stated weight or measure fields | Which packing configuration does it describe? | That a list proves packing, loading or carriage acceptance |
| Shared fields | Names, order/shipment ID, goods, quantities, marks, dates and delivery notation | Which differences need clarification? | That agreement proves all external requirements are met |
| Version trail | Source, received date, preparer, checker, recipient and amendment reason | Who owns the next correction? | That a forwarded file is authorised |
| Exception | Affected scope, visible evidence, owner and buyer decision state | What must be resolved before relying on the record? | That a file match is an automatic release or payment decision |
DECISION STATES / 03
Keep document agreement distinct from transport, customs and commercial decisions
| State | Visible meaning | Permitted next action |
|---|---|---|
| Baseline incomplete | Order, product or packing version is unclear | Clarify the controlled baseline before comparing files |
| Draft comparison | Invoice and packing-list fields can be reviewed against the baseline | Identify and assign visible differences |
| Version aligned | The two records identify the same known order and packing context; limitations remain visible | Obtain any required party-specific confirmation |
| Exception pending | A difference or missing record affects the current instruction | Hold the affected decision for the appropriate process |
| Buyer instruction recorded | The buyer’s scope-specific decision is retained with the current version | Proceed only within that recorded scope; revisit when facts change |
METHOD AND LIMITATIONS / 04
This is a comparison guide, not a customs, carrier, banking or legal service.
WCO Data Model guidance on main class levels distinguishes goods-transaction documents, including invoices and packing lists, from transport-contract information. China Customs’ goods-declaration guide is an official reference for its own service context. Neither source makes this page a universal list of required documents for a particular transaction or destination.
We did not inspect any supplier, goods, invoice, packing list, carrier booking, declaration, payment or destination-market requirement described by a reader. The current page language is English; the workflow is not limited to English-speaking countries or markets.
OFFICIAL SOURCES / 05
Use primary sources for the applicable procedure, then retain the actual record version.
WCO Data Model guidance
Explains how goods-transaction documentation and transport-contract records belong to different procedural contexts.
Read WCO guidance →China Customs goods declaration
Official service guidance for its declared goods process; actual requirements depend on the applicable procedure and current authority instructions.
Read China Customs guide →QUESTIONS / 06
Common comparison questions
Does an invoice have to match a packing list word for word?
Not necessarily. Compare the fields that should identify the same order and shipment, record any difference and ask the appropriate owner to explain it. This page does not decide which fields a specific authority, carrier, bank or buyer requires.
Does a matching pair mean that the shipment can proceed?
No. Transport acceptance, export or import procedure, inspection, payment and buyer release are separate decisions with their own evidence and responsible parties.
What if the supplier sends an amended invoice?
Keep the prior and new references, the affected fields, reason given, source and the person whose instruction is required. Do not silently overwrite the record used for the prior review.