Many customs errors do not begin with the “transmit” command. They originate earlier, when data from the contract, commercial invoice, packing list, technical files, transport document, licence and accounting system have not been converted into one controlled dataset. A mismatch in customs regime, declarant, HS code, unit, customs value, customs office, bill number or container number may cause registration rejection, alter tax treatment, require a supplementary declaration or, in certain cases, lead to cancellation and re-registration. Pre-transmission review should therefore operate as a Document & Data Gate rather than an informal last-minute check. This article sets out the data groups to freeze, the source documents to reconcile, the approval sequence and the warning signs that should stop transmission until the discrepancy is resolved.

Updated: 17 July 2026 | Scope: electronic import and export declarations for commercial goods and comparable customs regimes

QUICK FACTS

Eight data groups

Review parties and regime; goods and HS; quantity and units; value and tax; transport; licences and sectoral control; origin and preference; and linked data.

One source of truth

Every declaration field should trace back to an approved contract, invoice, packing list, technical file, transport document or permit.

Completeness is not enough

Data must also be consistent with commodity-management and tax policies.

Freeze high-risk fields

Identify fields that can be supplemented and fields whose error may require cancellation or re-registration.

Four-eyes approval

The preparer and reviewer should be independent, with an auditable approval record.

Illustration for What data should be reviewed before transmitting a customs declaration? — Illustration of the logistics topic, document or operation discussed in the article.

SCOPE OF APPLICATION

This article applies to enterprises filing directly or through a customs agent for commercial imports and exports. It may be adapted for processing, export production, export-processing enterprises, temporary import/re-export, temporary export/re-import and on-the-spot transactions.

Not every field appears on every declaration. The exact dataset depends on direction, regime, transport mode, commodity policy, transaction structure and the current customs system/software version. This article does not replace Appendix II or regime-specific guidance.

KEY TERMS

Term	Meaning	Control role
Pre-transmission review	Review before sending data for official declaration registration.	Prevents errors before a declaration number and legal status arise.
Draft declaration	Internal working dataset or pre-declaration information; not every draft is a registered declaration.	Allows reconciliation before official registration.
Master Data	Controlled data for entities, locations, items, units, partners and accounts.	Reduces manual-entry and recurring errors.
HS Code	Goods-classification code under Vietnam’s export and import nomenclature.	Drives commodity policy, tax and related fields.
Customs Value	Value determined under customs valuation law for management and tax purposes.	May differ from the amount paid or a single invoice line.
Document & Data Gate	A control point that releases transmission only after approval criteria are met.	Creates ownership and an audit trail.
Supplementary declaration	Lawful amendment or addition to declaration data with supporting documents.	Not all fields and timing points are handled in the same way.

HOW PRE-TRANSMISSION CONTROL WORKS

Under Article 18 of Circular 38/2015/TT-BTC as amended, the declarant must provide all declaration information under Form 01 or Form 02 of Appendix II and customs-dossier document data under Form 03. Where the electronic system does not yet support receipt of Form 03 data, digitally signed scans are submitted through the system under the prescribed fallback mechanism. The system then checks registration conditions, including completeness, consistency and compliance with commodity-management and tax policies.

An internal process should therefore test three layers: (1) source documents are valid and current; (2) fields reconcile across documents; and (3) declared data reflects the true transaction and applicable policy. Software can validate formats and certain codes, but it cannot determine the real nature of goods, customs value, origin or entitlement to use a licence.

Stop-transmission rule: do not transmit when the regime is unresolved, HS/policy evidence is incomplete, customs value cannot be reconciled, a licence does not match or transport data may still change the mode or customs gate.

Do not classify errors by habit: Article 20 excludes the information fields listed in Section 3 of Appendix II from supplementary declaration. If such a field is wrong, Article 22 and the actual status of the declaration and goods must be checked to determine whether cancellation applies; not every error is automatically cancellable or supplementable.

DATA REVIEW MATRIX

Data group	Critical fields	Source	Control point	Risk if wrong
1. Parties and regime	Exporter/importer, entrusting party, agent, regime code, customs office and storage/assembly location.	Corporate records, entrustment contract, investment certificate, regime file and master data.	Correct entity, import/export right, transaction model, registration location and tax responsibility.	Wrong regime or office may distort documents, tax and require re-registration.
2. Goods and HS	Description, model/part number, use, material, condition, HS, origin and internal item code.	Catalogue, datasheet, BOM, photos, contract, invoice and classification results.	Description identifies the goods; HS has a reasoned file; dissimilar goods are not improperly grouped.	Wrong policy, tax, licence, origin and assessment risk.
3. Quantity and units	Quantity, statistical/supplementary unit, packages, gross/net weight and packing.	Packing list, weighbridge ticket, warehouse record, invoice and booking.	Declaration unit matches HS requirements; conversions are documented.	Physical-examination variance, wrong unit value or supervision mismatch.
4. Value and tax	Invoice value, currency, Incoterm, payment method, exchange rate, adjustments, tax rate and exemption codes.	Contract, invoice, debit/credit note, freight/insurance file, valuation file and origin document.	No duplicate or omitted adjustments; preferential treatment has evidence and conditions.	Under/overpayment, valuation consultation or supplementary filing.
5. Transport and customs gate	B/L or AWB, mode, loading/discharge ports, gate, conveyance, dates, container, seal and cargo reference.	Transport document, booking, arrival notice, manifest, SI and EIR.	Correct version; one bill/multiple declarations or multiple bills/one declaration handled properly.	Manifest/supervision mismatch or movement blockage.
6. Licences and sectoral control	Number/date, issuing authority, goods/model, authorised quantity, validity and result.	Licence, deduction sheet, registration/exemption/result and National Single Window.	Valid; matching entity, item, quantity, gate and shipment.	Registration/clearance failure or licence overuse.
7. Origin and preference	Country of origin, tariff schedule, C/O or origin statement and criterion.	Origin document, BOM, production record and transport evidence.	Do not confuse export country with origin; verify form, validity and logical consistency.	Preference denial, reassessment or verification.
8. Linked data	Related declaration, internal reference, processing/export-production contract, duty-free list, norms and on-the-spot declaration.	ERP, regime file, prior declarations, lists and management reports.	Correct relationship and direction; no reference from another shipment.	Broken audit trail and incorrect inventory/tax tracking.

Special control: for containerised exports, current Article 18 requires full container numbers and the export-cargo management reference at registration. Road motor vehicles imported or exported as goods require additional vehicle data under Form 03 of Appendix II.

SOURCE DOCUMENTS AND DATA

Each declaration field needs a defined source of truth. Do not use isolated emails when an approved or officially issued document exists.

Source	Issuer/controller	Fields frozen	Reconciliation fields	Required status
Contract/PO/addendum	Commercial, legal and finance teams	Parties, Incoterm, payment, price and documentary obligations.	Legal names, goods, quantity, price, currency and adjustment terms.	Signed or otherwise legally valid; latest addendum.
Commercial Invoice	Seller/accounting	Commercial value and transaction data.	Number/date, seller/buyer, description, quantity, price, total, currency and Incoterm.	Official version; proforma used only where legally and factually appropriate.
Packing List/warehouse/weight record	Factory, warehouse and weighing provider	Packages, quantity, gross/net, container and packing.	Marks, package count, weights, dimensions and item allocation.	Matches actual goods and final approved version.
Catalogue/datasheet/BOM/photos	Engineering/manufacturer	Description, HS, policy and origin analysis.	Model, construction, material, function, capacity and new/used condition.	Correct model and sufficient classification detail.
Booking/B/L/AWB/manifest data	Carrier, forwarder and logistics team	Mode, bill, ports/gates, voyage, container and seal.	Parties, route, packages, weight, description, container and seal.	Version selected for declaration; later changes reopen the gate.
Freight, insurance, royalty and adjustment file	Forwarder, insurer, licensor and accounting	Customs value and adjustments.	Scope, currency, payer, amount, allocation and timing.	Documented allocation; no estimated amount where final data exists.
Licence/sectoral result	Competent authority or designated body	Import/export condition, exemption or inspection result.	Entity, item/model, HS if applicable, quantity, validity and gate.	Valid, sufficient balance and correct system reference.
Origin document and working file	Exporter/issuing body	Origin and tariff preference.	Invoice, HS, criterion, route, exporter/producer and quantity.	Logic reviewed and filing timing determined.
ERP/master and linked declarations	IT, accounting and trade teams	Item, UOM, entity, references and regime links.	Item code, conversion, tax code, partner and declaration reference.	Edit rights frozen and approval log retained.

Version-control rule: labels such as “final”, “revised” or “approved” are meaningful only when the approver, timestamp and changes from the prior version are traceable.

PRE-TRANSMISSION WORKFLOW

Step	Input	Control action	Output	Owner
1. Determine transaction and regime	Contract, cash flow, title and purpose.	Select direction, proposed regime, parties and customs office.	Approved regime determination.	Trade + accounting/legal.
2. Freeze commodity policy	Technical file, proposed HS and origin.	Check restrictions, permits, sectoral control, labelling, tax and preference.	Policy matrix per item.	Compliance/trade.
3. Standardise item data	Invoice, packing list, technical file and ERP.	Map item–model–HS–UOM–origin–quantity.	Shipment item master.	Engineering + warehouse + trade.
4. Build declaration dataset	Item master, commercial and transport documents.	Populate Form 01/02 fields and corresponding Form 03 dossier data.	Version-controlled draft.	Declaration preparer.
5. Three-way reconciliation	Draft, documents and actual goods.	Reconcile quantity/value/weight, HS/policy and transport/manifest.	Exception list and evidence of resolution.	Independent reviewer.
6. Review high-risk fields	Regime, office, mode, HS, value, permit and container data.	Check Section 3 of Appendix II and Articles 20 and 22; do not classify amendment or cancellation solely by software capability or past practice.	Approval or stop-transmission decision.	Authorised manager.
7. Transmit and read response	Approved dataset, digital signature and system.	Submit registration and review acceptance/rejection reason.	Declaration number/status or issue ticket.	Declarant.
8. Freeze records and manage change	Registered declaration and source file.	Save snapshot; later changes follow lawful amendment, supervision-update or cancellation procedures.	Complete audit trail.	Trade + IT/document control.

Four-eyes principle: the reviewer should trace high-risk fields back to source documents rather than merely rereading the software screen. Complex shipments may require engineering, tax or legal approval before Step 6.

COMMON RISKS AND ERRORS

Error	Cause	Impact	Control
Habit-based regime selection	Copying an old declaration without analysing the new transaction.	Wrong tax, documents and material/goods tracking.	Mandatory regime memo for each transaction model.
Generic goods description	No technical file or poor product understanding.	Weak HS and policy basis.	Describe construction, use, model, material and condition.
Uncontrolled unit conversion	Invoice, warehouse and HS use different units.	Wrong quantity, unit value and examination variance.	Approved conversion table with formula.
Confusing payment price with customs value	Incoterms and adjustments not reviewed.	Under/overpaid tax or valuation query.	Reconciliation from invoice value to customs value.
Using an obsolete B/L draft	Route, bill or container changed after review.	Manifest/supervision mismatch and amendment/cancellation.	Transport-data freeze and gate reopening process.
Licence matches name but not model/quantity	Only the document number is checked.	The document cannot support the shipment.	Field-by-field and balance review.
Blind reliance on copy function	Software carries old or default data.	Hidden recurring errors.	Diff report and no-copy rule for sensitive fields.
No approved snapshot	Direct edits before transmission without log.	No accountability or evidence.	Versioned snapshot and approval record.

LEGAL BASIS AND OFFICIAL SOURCES

Instrument/source	Authority	Status	Role
Customs Law 54/2014/QH13, amended by Law 90/2025/QH15	National Assembly	Customs Law effective 1 Jan 2015; Law 90/2025 effective 1 Jul 2025.	Declaration principles, declarant responsibility, dossier and retention.
Decree 08/2015/NĐ-CP, amended by Decrees 59/2018 and 167/2025	Government	Decree 167/2025 effective 15 Aug 2025.	Registration conditions, procedures, inspection and supervision.
Circular 38/2015/TT-BTC, amended by Circulars 39/2018 and 121/2025	Ministry of Finance	Circular 121/2025 effective 1 Feb 2026.	Article 18 data filing, Article 19 registration, Article 20 supplementation, Article 22 cancellation and Appendix II.
Appendix II under the Circular 38 framework and amendments	Ministry of Finance	Apply the current version and system configuration.	Form 01/02 declaration data, Form 03 dossier data and non-supplementable fields.
VNACCS/customs-software operating guidance	Issued by Vietnam Customs or the software provider	Operational support only; verify publication date and applicable version.	Explains transaction codes and technical responses; it is not legislation and does not replace classification, valuation or commodity-policy analysis.

Circular 121/2025/TT-BTC Nghị định 167/2025/NĐ-CP Circular 38/2015/TT-BTC Circular 39/2018/TT-BTC

FREQUENTLY ASKED QUESTIONS

Can a declaration be transmitted before the final transport document is issued?

It depends on direction, mode and system fields. Draft or expected transport data may be used in some cases, but the change risk and update procedure must be controlled. Do not transmit where a likely change may alter the mode, gate or a sensitive field.

Should the packing list be reviewed even if it is not always a mandatory filing document?

Yes. It is a key source for quantity, packages, weight, packing and item allocation.

Can an HS code from a previous shipment be copied?

Only where the goods are truly identical in name, composition, construction, properties, function and classification criteria, and the legal basis remains current. Keep a comparison file.

Does a wrong container number always require cancellation?

No. Point a.7, Clause 2 of Article 20 provides a mechanism to update the container number at the customs-supervision stage where the actual number differs from the declaration and appropriate carrier evidence or a container list is presented. Other changes still depend on direction, declaration status, supervision stage and Section 3 of Appendix II.

Is the customs exchange rate the bank payment rate?

Not automatically. Customs tax and valuation rates follow customs rules for the relevant time; the payment rate is commercial data and may differ.

Who should give final approval?

At minimum, a competent person independent of the data preparer. HS, valuation, licensing or regime risks may require specialist approval.

Does system acceptance prove the declaration is correct?

No. Acceptance means registration conditions and automated checks were met at that time. The declarant remains responsible for accuracy, truthfulness and consistency with documents and actual goods.

APPLICATION NOTE: Vietnamese legal instruments are summarised for operational reference; this English version is not an official legal translation. This is an operational control framework, not a reproduction of all Appendix II fields. Before each transmission, use the dataset for the relevant direction, regime, software and current policy. Errors discovered after registration must be handled through the proper supplementary declaration, supervision-data change or cancellation process.

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