Tiếng Việt
中文 (中国)
Common Errors That Cause Import–Export Documents to Mismatch
Each document may look correct on its own, yet the set can still conflict when the invoice, packing list, transport document, origin document, licence and customs declaration are compared side by side. Small discrepancies in product description, package count, weight, trade term or reference number can trigger amendments, delay declaration, jeopardise preferential duty or require an explanation. This guide groups the most common mismatches, identifies the fields that must be cross-checked and presents a version-control process before filing or presenting the document set.
QUICK FACTS
Mismatches often arise because departments use different source data or amend one document without synchronising dependent documents.
Parties, goods description, model, quantity, unit, weight, value, Incoterms, route, origin and reference numbers.
Abbreviations or formatting may differ if the same data remain identifiable; risk rises when the difference changes the goods, tax treatment or regulatory conditions.
Use a shipment data sheet, assign an authoritative source to each field and lock the final version before release.
SCOPE
This article covers commercial import and export document sets transported by sea, air, road, rail or multimodal transport. It is intended for importers, exporters, procurement, sales, documentation, warehouse, accounting, forwarders and customs brokers.
The comparison may include the contract or purchase order, commercial invoice, packing list, bill of lading or air waybill, certificate or declaration of origin, licence/specialised inspection document, catalogue, certificate and customs declaration. The actual set varies by customs regime, commodity, route, payment method and counterparty requirements.
KEY TERMS
| Term | Meaning | Operational role |
|---|---|---|
| Document consistency | Consistency across documents for the same transaction or shipment. | Allows authorities, banks and counterparties to identify the same goods, parties and movement. |
| Data field | An individual item such as product name, invoice number, packages, weight or price. | The smallest comparison unit; each field needs a source and an owner. |
| Source of truth | The approved authoritative source for a data group. | Prevents staff from using obsolete emails, drafts or superseded files. |
| Document version | The status of a document at issuance or amendment. | Distinguishes the current final file from replaced versions. |
| Cross-check | Comparing the same field across several documents. | Finds conflicts before customs filing, bank presentation or customer delivery. |
WHY MISMATCHES OCCUR
The document set is not created at one time or by one person. Sales or procurement may own the contract, the packing list reflects final packing, the transport document follows shipping instructions, the origin document draws on commercial, transport and origin evidence, while the customs declaration consolidates several sources. A mismatch therefore occurs not only through incorrect data entry but also when source data change and dependent documents are not updated together.
| Data group | Preferred control source | Documents to align | Suitable approver |
|---|---|---|---|
| Parties, addresses and identifiers | Contract, legal records and approved master data | Invoice, transport document, origin document, licence, declaration | Sales/procurement and compliance |
| Goods, model and specifications | Contract, PO, catalogue, technical file or licence | Invoice, packing list, transport document, origin document, declaration | Product/technical and customs team |
| Quantity, packages and weight | Final packing/weighing result and warehouse record | Packing list, transport document, VGM, declaration | Warehouse and transport documentation |
| Price, currency, discount and charges | Contract/PO and final commercial invoice | Invoice, customs value data and payment file | Commercial team and accounting |
| Route, conveyance, container and seal | Booking, final B/L or AWB and carrier confirmation | Transport document, manifest, origin document, declaration | Forwarder/logistics documentation |
| Origin | Production evidence, origin rule and proof of origin | Origin document, invoice, declaration, labels and preference file | Origin/compliance owner |
COMMON DOCUMENT MISMATCHES
| Error group | Typical sign | Documents affected | Possible impact | Control |
|---|---|---|---|---|
| Party name or address error | Missing legal entity, trade name used inconsistently, wrong postcode, seller/shipper or buyer/consignee confused | Invoice, B/L/AWB, origin document, licence, declaration | Unclear party identity; explanation or amendment request | Use locked master data and distinguish all party roles |
| Reference number/date conflict | Origin document cites an old invoice; declaration uses the wrong date; transport document contains a draft reference | Invoice, origin document, declaration, L/C set | Broken audit trail and difficulty proving one shipment | Run a reference-number matrix after final issue |
| Goods description conflict | Invoice uses a trade name, licence a technical name and declaration omits model, use or material | Entire set | Doubt over the goods; HS, specialised control or origin issues | Use a standard description: name – model – characteristics – use – condition |
| Quantity or unit error | PCS, SET, CTN or KGS converted incorrectly; invoice quantity differs from packing list | Invoice, packing list, transport document, declaration | Value, package count or physical inspection discrepancy | Maintain unit conversions and separate commercial quantity from packing quantity |
| Weight, volume or packages conflict | Gross below net, pallet omitted, CBM inconsistent with dimensions, B/L not updated after final weighing | Packing list, B/L, VGM, booking, declaration | Manifest amendment, transport correction or shortage/surplus concern | Use final packing and weighing data; document rounding and packaging |
| Value or currency mismatch | Unit price × quantity differs from total; USD/CNY confused; discount, freight or insurance omitted | Invoice, contract, customs value and payment file | Incorrect customs value, tax or payment | Recalculate totals and review valuation components |
| Incomplete or inconsistent Incoterms | FOB/CIF without a named place; contract and invoice differ; edition omitted | Contract, invoice, customs valuation and insurance | Unclear allocation of costs and risk; valuation errors | State rule + named place/port + Incoterms edition |
| Transport-data error | Wrong port, voyage, container, seal, B/L number or on-board date | B/L/AWB, manifest, origin document, declaration | Manifest mismatch, poor traceability, delayed origin document or delivery | Update only from the final carrier-issued transport data |
| Origin inconsistency | Country of origin differs; invoice number, criterion, description or quantity on origin document is wrong | Origin document, invoice, declaration, labels | Preference may be rejected or verification initiated | Cross-check all origin-document fields against commercial and origin evidence |
| Licence/technical-file mismatch | Model, brand, power, composition or intended use differs from commercial documents | Licence, specialised inspection, catalogue, invoice, declaration | Goods cannot be linked to the licence or inspection result | Map each item line to its model and technical evidence |
| Illogical chronology | Issue date predates the transaction, transport dates conflict, amendments are not traceable | Entire set | Questions about authenticity or version | Maintain a shipment timeline and change log |
| Poor draft/final control | Draft sent by mistake, identical file names, PDF changed but source spreadsheet not updated | All documents | Wrong data spreads to customs, bank and counterparty | Use naming rules and DRAFT/FINAL/SUPERSEDED status |
DOCUMENTS AND DATA TO CHECK
| Document | Fields to verify | Main cross-reference | Often missed |
|---|---|---|---|
| Contract/PO | Parties, goods, quantity, price, currency, Incoterms, payment | Invoice, licence, payment file | Amendments, seller different from shipper, partial shipments |
| Commercial invoice | Number/date, seller–buyer, description, quantity, unit price, total, currency and terms | Contract, packing list, declaration, origin document | Discount, freight, insurance and third-party invoice |
| Packing list | Packages, packing type, marks, net/gross, dimensions and item allocation | Invoice, warehouse record, B/L/AWB, inspection | Pallet count, packing weight and mixed cartons |
| B/L or AWB | Shipper, consignee, notify, route, voyage, packages, weight, container/seal | Shipping instruction, packing list, manifest and origin document | House/master document and receipt/delivery locations |
| Proof of origin | Exporter, importer, invoice, description, quantity, criterion and transport data | Invoice, transport document, declaration and production evidence | Third-party invoice, back-to-back and electronic reference |
| Licence/specialised inspection | Goods, model, brand, manufacturer, capacity, quantity and validity | Catalogue, invoice and declaration | Line coverage, deduction balance and model changes |
| Customs declaration | Regime, parties, item code, description, quantity, value, origin, transport and supporting documents | All source documents | Reusing old files and losing item mapping when lines are combined/split |
CROSS-CHECK AND VERSION-LOCK PROCESS
- Define the file scope: list required documents by regime, commodity, route, transport mode, payment and preference claim.
- Create the shipment master data sheet: record each value, source, approver and lock status.
- Map item lines: use an internal code or line reference across PO, invoice, packing list, licence and declaration.
- Check commercial documents: contract – invoice – packing list for parties, description, quantity, price, currency and delivery term.
- Check transport documents: shipping instruction – B/L/AWB – manifest – container/seal – weight and route.
- Check regulatory and origin documents: compare licences, technical files and origin proof against commercial data and special arrangements.
- Review the draft customs declaration: verify critical system data against the authoritative source, not only the printed preview.
- Lock and release: mark FINAL and retain approver, lock time and distribution list.
- Control amendments: identify dependent documents, amend together and withdraw replaced versions.
CONTROL FAILURES AND RISKS
| Control failure | Cause | Effect | Measure |
|---|---|---|---|
| Checking each document separately | No cross-document matrix | Two values for the same field remain unnoticed | Review by data field, not file order |
| Using the invoice as the source for everything | No distinction between commercial, warehouse and transport data | Weight, route or origin may be inaccurate | Assign a separate authoritative source to each data group |
| Editing another issuer’s document | Urgency or no amendment process | Authenticity and version-control risk | Require the issuer to amend and retain the audit trail |
| Accepting differences without explanation | Assuming a small difference is harmless | No evidence when questioned | Define tolerances, rounding and packaging explanations |
| Ignoring L/C or origin-specific conditions | Only a customs checklist is used | Customs may accept the set while the bank or origin authority rejects it | Add payment- and origin-specific review layers |
| Not withdrawing obsolete versions | Multiple channels and no distribution log | Agent, customer or declarant uses the wrong file | Mark SUPERSEDED and notify every recipient |
LEGAL BASIS AND OFFICIAL SOURCES
The following instruments provide the framework for customs dossiers and supporting documents. The exact file depends on the customs regime, commodity and specialised legislation.
| Instrument/source | Reference role | Application note |
|---|---|---|
| Customs Law No. 54/2014/QH13 | Framework for customs dossiers and the declarant’s duty to lodge or present supporting documents. | The Law is partly no longer in force and must be read with subsequent amendments. |
| Law No. 90/2025/QH15 | Amends provisions of the Customs Law and other related laws. | Effective 1 July 2025; verify the relevant provision for the shipment. |
| Decree No. 08/2015/ND-CP, Decree No. 59/2018/ND-CP and Decree No. 167/2025/ND-CP | Detailed and updated customs procedures, inspection, supervision and control. | Decree No. 167/2025/ND-CP has applied since 15 August 2025; use the provisions currently in force. |
| Consolidated Document No. 46/VBHN-BTC | Consolidated reference for detailed implementation of the Customs Law on procedures, inspection, supervision and control. | Issued on 24 November 2025; useful for review but does not replace checking the legal status of each provision. |
| Circular No. 38/2015/TT-BTC, Circular No. 39/2018/TT-BTC and Circular No. 121/2025/TT-BTC | Detailed dossier, declaration data and customs procedures. | Circular No. 121/2025/TT-BTC has applied since 1 February 2026; use the updated regulatory chain. |
| Circular No. 33/2023/TT-BTC | Rules on origin determination for exports and imports. | Relevant where a C/O, origin declaration, preference or origin-control requirement applies. |
Translation note: References to Vietnamese legislation are for operational guidance. This English text is not an official legal translation.
FAQ
1. Must the goods description on the invoice and customs declaration be word-for-word identical?
No. They must describe the same goods and provide enough information for classification and regulatory review. A customs description may need model, material, use or technical details beyond the trade name.
2. Is a small weight difference between the packing list and transport document acceptable?
The cause should be identified, such as rounding, different weighing points or packaging. The difference must remain reasonable and supported by packing or weighing evidence.
3. If the invoice is amended, must the origin document and customs declaration also be amended?
Assess which fields changed. If the number/date, description, quantity, value or referenced data changed, dependent documents may require corresponding action under the applicable procedure and timing.
4. Can a pro forma invoice replace a commercial invoice?
Only where the applicable procedure or receiving party accepts it and it reflects the transaction. A pro forma is normally preliminary and should not automatically replace the final commercial invoice for a payable sale.
5. Is it automatically wrong if the B/L shipper differs from the invoice seller?
No. It may reflect a triangular transaction, agency or different physical shipper. The relationship must be documented, and third-party invoice, origin, payment and licensing conditions require separate review.
6. Who should approve the final set?
A document controller or shipment owner should coordinate final approval, while each data owner confirms its specialist fields: commercial, warehouse, logistics, technical, origin and customs.
7. Can software fully replace manual review?
Software can validate calculations, required fields and exact comparisons, but professional review remains necessary for goods descriptions, party relationships, valuation, origin rules and specialised controls.
NEED TO REVIEW IMPORT PROCEDURES OR A SHIPPING PLAN?
Send us the product name, shipping route, current dossier, or implementation request in advance so we can suggest a suitable approach that is practical, focused, and aligned with your shipment.
Cargo Damage at a Port or Warehouse: An Immediate Response Checklist
What Is General Average? How Cargo Interests Should Respond to a GA Notice
When should businesses photograph or video container stuffing and opening?
When Can Cargo Insurers Reject or Reduce a Claim?
Risks of Failing to Inspect a Container Before Cargo Stuffing
Risks of Failing to Inspect a Container Before Cargo Stuffing
What Documents Are Required for a Cargo Insurance Claim?
What Information Should a Cargo Damage Survey Record Contain?
Total Loss vs Partial Loss in Cargo Insurance: What Is the Difference?
Cargo Dented, Wet or Missing Packages: What Should a Business Do?
Who Must Arrange Insurance under CIF and CIP?
Export Process: From Purchase Order to Final Document Set
How Is Cargo Insurance Value Determined?
How Do ICC-A, ICC-B and ICC-C Cargo Insurance Conditions Differ?
When Should a Business Buy Separate Cargo Insurance?