A cleared customs declaration does not automatically mean that a company can immediately prove the lawful provenance of the goods when customs, market surveillance, tax authorities, customers or auditors ask questions. The main difficulty is usually not one missing document. It is the inability to connect the product name, model, quantity, origin, ownership and movement of the goods into one consistent evidence trail. This guide shows how to organize the file around the actual review logic: identify the goods, prove the import event, substantiate origin, trace domestic transactions and reconcile quantities to the current stock or final outbound movement.

Prepared by: TGIMEX Updated: 20 July 2026 Scope: Commercial imports into Vietnam

QUICK FACTS

There is no universal file

The package must reflect the authority’s question, the product, the importer of record and the stage of domestic circulation.

Four evidence chains are required

Product identity, import event, origin, and lawful ownership and movement in Vietnam.

A declaration or C/O alone is not enough

Each document proves only part of the story; the value comes from cross-document consistency.

Quantity reconciliation is central

Imported, received, transferred, sold, lost and remaining quantities must reconcile under one conversion method.

Regulated goods need extra modules

Licences, inspection results, registrations, stamps, labels and business conditions must be added as applicable.

Illustration for How to Build an Imported-Goods Provenance Explanation File — Illustration of the logistics topic, document or operation discussed in the article.

SCOPE OF APPLICATION

This guide is intended for direct importers, import entrustment parties, domestic purchasers of imported goods, distributors and warehouse operators. The file may support explanations requested by customs, post-clearance audit teams, market surveillance, tax authorities, buyers or internal auditors.

It focuses on ordinary commercial imports. Personal baggage, gifts, border-resident trade, temporary import–re-export, processing, export manufacturing, export processing enterprises, CITES goods, import-stamped goods and other special regimes require sector-specific adaptation.

Lock this distinction first: lawful provenance and origin are not the same. Lawful provenance addresses where the goods came from, who owned them and which transactions created legal title. Origin identifies the country or territory attributed to the goods under the applicable rules of origin.

KEY TERMS

Term	Operational meaning	Role in the file
Lawful provenance	The evidence trail showing that goods were imported, purchased, owned and circulated lawfully.	The overall objective of the explanation file.
Origin	The country or territory determined under the relevant rules of origin.	Relevant to customs declaration, labelling, trade measures and preferential duty when applicable.
Traceability	The ability to trace goods in stock or sold back to a specific import consignment and source record.	Connects SKU, serial, lot or model to the declaration.
Reconciliation	Matching imported, received, transferred, sold, lost and remaining quantities.	Shows whether the goods under review can be quantitatively linked to the import.
Audit trail	Documents, approvals and system data that allow a transaction to be reconstructed.	Demonstrates that the file was not assembled without control only after a query arose.
Supporting evidence	Emails, label photos, delivery records, ERP data and partner confirmations.	Clarifies facts but does not replace primary legal or commercial documents.

SUBSTANCE AND OPERATING LOGIC

A strong explanation file is not a thick PDF bundle. It is a question-and-evidence system. Each conclusion should follow the same sequence: fact to be proven → primary document → cross-check data → supporting evidence → responsible owner.

The four connected evidence pillars

1. Product identity

Commercial name, declared name, model, SKU, specifications, use, brand, serial/lot, unit and declared HS code.

2. Import event

Importer, customs declaration, invoice, packing list, transport document, taxes, licences and specialised inspection results.

3. Origin

Original label, applicable proof of origin, origin declaration, manufacturer documents and customs data.

4. Ownership and movement

Contracts, domestic invoices, delivery, receipt, transfer, sales, stock and entrustment or distribution records.

Evidence hierarchy

Official records: customs declaration, tax payment, licence and inspection result.
Transaction and transport records: contract, invoice, packing list, bill of lading/air waybill and payment.
Origin and manufacturer records: C/O or valid origin declaration, manufacturer confirmation, catalogue and original label.
Domestic and internal movement records: goods receipt, issue note, transfer, sales invoice and serial/lot log.
Supplementary evidence: emails, photographs, camera data and system screenshots. These should only clarify timing or discrepancies.

Single-source principle: build one master data table for the entire review scope. The explanation letter and all annexes should draw from that controlled table so that quantities and descriptions do not change between versions.

EVIDENCE MATRIX

Question to answer	Preferred evidence	Data that must match	Red flag	Control
What exactly are the goods?	Label, catalogue, photo, model/SKU, serial or lot	Name, model, specification and unit	Internal name is unrelated to the declared description	Create a commercial-name to declared-name mapping
Under which declaration were they imported?	Declaration and item-line details	Importer, declaration number/date, line and quantity	Only a declaration number is given, without the item line	Map each SKU to a specific declaration line
Was the purchase genuine?	Contract, invoice, payment and transport	Seller, buyer, value and delivery terms	Counterparty or value differs without explanation	Reconcile trade and payment records
What supports the origin statement?	Applicable origin document, original label and manufacturer record	Origin country, manufacturer, description and relevant HS data	C/O conflicts with invoice or transport; shipping country is treated as origin	Review applicability and consistency before submission
Where did the goods move after import?	Delivery, receipt, issue, transfer and sales records	Date, warehouse, quantity, SKU and receiver	Invoice exists but no receipt or physical movement trail	Reconcile ERP data with source documents
Do quantities reconcile?	Lot-based import–movement–stock table	Unit, conversion, samples, loss, destruction and returns	Negative stock or sales exceeding imports	Use one base unit and explain every variance
Were sector rules met?	Licence, registration, declaration, inspection and label/stamp	Model, product code, lot, holder and validity	Document covers a different model or was not valid at import	Build a regulatory annex by product group
Who is accountable for the file?	Assignment decision, authorization and valid signature	Title, authority scope and signing date	Signatory lacks authority or certifies data outside their control	Use a responsibility matrix and two-level approval

DOCUMENTS AND DATA TO REVIEW

Organize the file into numbered volumes or controlled electronic folders. The structure below is an operating framework and must be adapted to the receiving authority’s actual request.

File module	Main documents	Owner	Mandatory cross-checks	Control output
A. Cover, index and request	Official request, scope, period, goods and contact point	Legal/compliance	Reference, deadline, authority and goods list	Scope confirmation sheet
B. Entity and authority	Business registration, authorization, entrustment or distribution agreement	Administration/legal	Name, tax ID and role of each party	Entity and responsibility map
C. International trade	Contract, purchase order, invoice, packing list and payment	Procurement/finance	Parties, description, quantity, value and Incoterms	Transaction reconciliation
D. Customs and transport	Declaration, transport record, tax record and related arrival data where needed	Import team	Declaration, line, container/AWB and import date	Declaration-to-SKU matrix
E. Origin and labelling	Applicable proof of origin, original/supplementary labels and manufacturer record	Import/QA	Origin, manufacturer, model, HS data and issuance date	Origin and label review sheet
F. Sector compliance	Licence, registration, declaration, inspection result or conformity record	Regulatory/QA	Product, model, lot, holder and validity	Compliance status table
G. Warehouse and domestic movement	Delivery, receipt, issue, transfer, domestic invoice and return	Warehouse/accounting/sales	SKU, serial/lot, quantity, warehouse and customer	Movement ledger
H. Quantity reconciliation	Declaration- and lot-based import–movement–stock table	Inventory accounting/data	Base unit, conversion, loss and closing balance	Approved reconciliation
I. Gaps and remediation	Gap log, partner confirmation, correction record and variance explanation	File owner with relevant teams	Cause, alternative evidence, action and deadline	Open-issue register and disposition

Minimum master-data fields

Internal code/SKU; label name; customs description; model/specification; declared HS code; origin country; manufacturer; declaration number/date; item line; invoice; declaration unit; imported quantity; received quantity; transferred/sold quantity; loss/destruction; balance; current warehouse; serial/lot; regulatory document; discrepancy note.

BUILD PROCESS

Lock the request scope

Identify the requesting authority, purpose, period, goods, location and questions. Do not collect the entire company archive when the request concerns only one product group.

Output: scope sheet and named file owner.

Freeze the data

Set a cut-off for inventory, sales and accounting data and retain the ERP export used for the review.

Output: dated source-data package and extraction owner.

Create the reviewed item list

Standardize product name, SKU, model, specification, serial/lot and unit. Record name conversions between internal, commercial and customs descriptions.

Output: approved item master.

Connect trade records to declarations

Cross-check contract, invoice, packing list, transport and each declaration line. Every SKU must point to a specific import basis.

Output: declaration–invoice–SKU matrix.

Review origin, labels and sector controls

Verify the origin basis, applicability of origin documents, consistency of original/supplementary labels and coverage of licences or inspection results.

Output: product-level legal review sheet.

Reconcile import, movement and stock

Convert to one base unit and separate sales, transfers, samples, warranty, destruction, loss and stock. Do not hide differences in a generic adjustment line.

Output: balanced reconciliation or itemized variance explanations.

Prepare the gap log

Record missing documents, conflicting data, impact, owner and lawful alternative evidence. Never fabricate or backdate documents.

Output: issue register and remediation plan.

Draft the explanation letter

State the request, company information, goods, import event, origin basis, movement chain, reconciliation result and annex index.

Output: concise letter with annex references.

Run a two-level review

Operations verifies logic and quantities; legal/compliance verifies authority, current rules, signing authority, sensitive data and the scope of commitments.

Output: QA record or internal approval.

Submit, track and preserve the audit trail

Record the submitted version, channel, recipient and response. Every supplement should have a version history.

Output: closed-version file and communication log.

RISKS AND COMMON ERRORS

Error	Cause	Impact	Control
Treating origin as lawful provenance	Assuming a C/O proves everything	Ownership and domestic movement remain unproven	Separate origin and movement annexes
Submitting only the cleared declaration	No item-line mapping	The reviewed goods cannot be tied to the declaration	Map SKU/model/serial to the line
Inconsistent product names	Warehouse, accounting, label and customs use different names	Goods may appear to be different products	Use a controlled name and technical-description mapping
Conflicting origin document	Mismatch with invoice, transport, model or applicable rule	Origin basis or preference may be rejected	Review each document before including it
Quantity does not balance	Mixed units or missing samples, warranty, destruction or repacking	Negative stock or sales above imports	Use one base unit and evidence each movement
Lots are mixed in the warehouse	No lot/serial control	Current goods cannot be traced backward	Maintain lot/location records and an approved allocation method
Using screenshots instead of source records	Original documents are missing	Evidence is weak and hard to verify	Obtain reissued or confirmed records; use screenshots only as support
Late-added documents have no chronology	The file was completed after the request	Documents may appear to have been created after the event	State creation date, source, reason and version history
Overloading the submission	Scope was not locked	More contradictions, data exposure and longer review	Use a question-based index and sufficient-but-minimum evidence
Unauthorized signature	No review of corporate authority or authorization	The explanation may carry less evidentiary weight	Verify title, authorization and signing scope

LEGAL BASIS AND OFFICIAL SOURCES

The sources below play different roles and do not all apply to every consignment. Product-specific rules and the relevant preferential-origin instrument must be reviewed separately.

Instrument/source	Role	Application note	Official source
Law on Customs No. 54/2014/QH13	Accuracy, responsibility and record-retention duties.	Article 18 requires customs records for cleared goods to be retained for five years from declaration registration, unless another rule applies.	National legal database
Circular 38/2015/TT-BTC, as amended by Circular 39/2018/TT-BTC and Circular 121/2025/TT-BTC	Customs procedures and import documentation framework.	Used to identify import customs-file components, data consistency requirements and procedures applicable from 1 February 2026.	Circular 121/2025/TT-BTC
Circular 33/2023/TT-BTC	Determination of origin for exported and imported goods.	Review proof-of-origin requirements, forms and verification rules under the applicable mechanism.	Government portal
Decree 31/2018/ND-CP	Detailed rules under the Law on Foreign Trade Management regarding origin.	Foundation for origin determination, certification and verification.	Government portal
Decree 43/2017/ND-CP and Decree 111/2021/ND-CP	Goods labelling, including origin/place-of-production information.	Cross-check original and supplementary labels and the responsible entity.	Amending decree
Decree 98/2020/ND-CP, as amended by Decree 17/2022/ND-CP and Decree 24/2025/ND-CP	Commercial administrative sanctions and concepts concerning smuggled or untraceable goods.	Shows the combined relevance of labels, origin evidence, contracts, invoices, declarations and documents proving lawful ownership or use rights.	Decree 24/2025/ND-CP
Decree 123/2020/ND-CP, Decree 70/2025/ND-CP and Circular 32/2025/TT-BTC	Current invoice and document framework.	Review domestic sales and transfer invoices in the provenance chain.	Decree 70/2025/ND-CP

Translation note: English descriptions in this article are for operational reference only and are not official legal translations.

FAQ

1. Must every imported consignment always have a C/O?

No universal conclusion should be made. The requirement depends on preferential-duty claims, origin-control rules, treaties and the specific regime. The company must still have a consistent basis for the origin stated in customs and on labels.

2. Is a cleared customs declaration enough?

Not necessarily. It proves a customs event, but the company must still link the goods under review to the relevant declaration line and explain ownership, delivery, receipt, sale or remaining stock.

3. What if the company bought imported goods from a domestic distributor?

At minimum, retain the order/contract, lawful invoice, delivery and receipt records. Depending on risk and the request, obtain evidence linking the goods to the distributor’s import file, especially for serial-controlled, lot-controlled, stamped or regulated goods.

4. How should multiple products on one declaration be presented?

Map to the item-line level. Each SKU/model should identify the declaration, registration date, line number, invoice, quantity and unit.

5. Does repacking or adding a supplementary label break traceability?

Not if the original label, before/after photos, repacking record, conversion ratio, lot/serial and warehouse data are retained. The actual labelling must comply with the applicable rules.

6. Can missing documents be recreated or backdated?

No. Use a gap log, request lawful reissuance or confirmation, state when and why the supplement was obtained and rely on valid alternative evidence where appropriate.

7. How long should the file be retained?

The Law on Customs sets a five-year retention period for customs records of cleared goods from declaration registration, unless another rule applies. Accounting, invoice and sector records follow their own periods; internal policy may retain records longer where goods remain in circulation, under warranty, dispute or review.

APPLICATION NOTE: The file must reflect the receiving authority’s request and the actual facts. Do not assume that any one document is always mandatory or always sufficient. If there are discrepancies in importer identity, HS code, origin, quantity, labels, licences or taxes, stop the conclusion and review the consignment-specific record before signing.

TGIMEX IMPLEMENTATION SUPPORT

TGIMEX helps businesses turn the article into a shipment-ready checklist, covering input-data review, dossier preparation, milestone control, and coordination with the relevant parties.

Convert guidance into checks

Assign an owner and deadline to every operational control point.

Reconcile shipment data

Compare booking, transport, commercial, customs, and delivery evidence.

Manage operational risk

Record discrepancies, actions, and decision evidence to prevent recurrence.

Discuss your shipment dossier

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B

MACHINERY

HOUSEHOLD GOODS

COSMETICS – PERSONAL CARE