A declaration may reconcile to the invoice total and still contain the wrong procedure code, party identifier, Incoterm, customs-value adjustment or an insufficient goods description. Once a business confirms official submission, internally prepared data is sent for registration in the customs system. A field-by-field visual review often misses systemic errors that only surface during document review, valuation consultation or post-clearance audit. This guide establishes a pre-submission control gate based on risk groups, cross-document reconciliation and clear maker–checker–approver responsibilities.

Operational update: 17 July 2026 · B2B Logistics

QUICK FACTS

Do not review isolated fields

Review the chain: procedure → parties → goods → HS/policy → value/tax → transport → evidence.

A draft does not remove legal responsibility

The declarant remains responsible for authenticity and consistency between filed data and company records.

Green channel is not a correctness certificate

Routing reflects processing at registration; errors may still be identified after clearance.

Every critical field needs evidence

HS, tax, origin, value, licence and procedure code must not be approved solely from experience or an old declaration.

Apply the four-eyes principle

This is a recommended internal control model. Vietnam’s Customs Law does not require businesses to use three statutory job titles called Maker, Checker and Approver.

SCOPE OF APPLICATION

This guide applies to electronic commercial import and export declarations prepared by an enterprise or customs broker before the final registration submission. It can support trading, processing, export manufacturing, export-processing enterprises, temporary import/re-export and other regimes after regime-specific controls are added.

Do not apply mechanically: passenger baggage, postal/express procedures, means of transport, incomplete declarations and specialised data forms require dedicated checklists.

KEY TERMS

Term	Meaning	Control purpose
Draft / pre-declaration	Data being prepared internally and not yet accepted for registration by customs.	Allows correction and internal approval before registration status arises.
Official submission	Operational term for sending/confirming data to request customs registration; transmission does not by itself mean the declaration is registered.	Software buttons and transaction codes vary; registration status must be determined from the customs system’s acceptance response.
Control gate	An internal stop point before a difficult-to-reverse action.	Blocks submission where a critical field lacks evidence or approval.
Maker–Checker–Approver	Preparer, independent reviewer and authorised approver under an internal governance model.	Separates duties and reduces copy-forward errors; these are not mandatory statutory customs positions.
Audit trail	Version, editor, timestamp and approval evidence.	Supports amendment, explanation and post-clearance review.
Locked indicator	A field that cannot be assumed amendable in every declaration status.	Requires enhanced pre-registration review; an error may require cancellation or another procedure.

WHY OFFICIAL SUBMISSION IS A CONTROL POINT

Article 29 of Vietnam’s Customs Law requires complete, accurate and clear declaration criteria. A registered declaration is valid for customs procedures and, as a general rule, goods-management and tax policies apply at registration. Article 30 provides that registration occurs after customs accepts the filing.

The approval step must therefore answer three questions: does the data match the documents, do the documents match the actual goods, and does the filing method match the legal regime? Invoice–Packing List matching is only the first layer.

Separate the duties: legal responsibility for an accurate declaration rests with the customs declarant. Approval levels, reviewer counts and the Maker–Checker–Approver matrix are internal controls designed by the business according to scale and risk.

Stop rule: do not submit a critical field marked “estimate”, “same as last declaration”, “supplier confirmed verbally” or “to be added later” unless the applicable law expressly supports that treatment.

TWELVE CONTROL GROUPS

Control group	Question	Primary evidence	Approval condition
1. Direction and procedure	Import or export; which procedure code reflects the transaction?	Contract, purpose, material flow, procedure-code guidance.	Code is explained by substance, not habit.
2. Declarant and parties	Who is owner, entrusting party, taxpayer, seller and buyer?	Business registration, entrustment agreement, invoice, authorisation.	Identifiers and legal roles match.
3. Office and location	Where is registration made, where are goods stored and routed?	Booking, arrival notice, port/warehouse codes.	Location codes match the actual movement.
4. Transport documents	Do bill, means of transport, packages and weight reconcile?	B/L, AWB, manifest, booking, weighing record.	No unresolved difference remains.
5. Invoice and delivery term	Are invoice date/number, currency, Incoterm and payment correct?	Commercial invoice, contract, amendment, payment record.	Delivery term aligns with value components.
6. Goods description	Is there enough information for classification and policy review?	Catalogue, datasheet, MSDS, photos, labels, BOM.	Description states nature, material, function and key model/specification.
7. HS and controls	What supports HS; are licences or inspections required?	Tariff, Explanatory Notes, technical evidence, sector rules.	Review is model-specific, not based on a generic trade name.
8. Quantity and units	Are customs unit, trade unit and conversion correct?	Packing list, invoice, weight record, packing specification.	Conversion formula and totals reconcile.
9. Customs value	Are additions/deductions, freight, insurance and related fees considered?	Contracts, invoice, debit notes, transport quotations.	Value is rebuilt from evidence, not copied from a total.
10. Tax and relief	Are rates and exemption/relief codes correct?	Tariffs, origin proof, exemption list, guarantee.	System calculation matches an independent worksheet.
11. Origin	Do declared origin and preference evidence align?	C/O or origin declaration, invoice, transport and production records.	Form, criterion, reference and movement conditions are supported.
12. Linked references	Are source declarations, processing contracts or internal references valid?	ERP, inventory, source declarations, licences.	Every reference exists and is traceable.

PROCEDURE CODE, PARTIES AND LOCATIONS

These fields establish the legal framework of the declaration. Correct goods and HS data do not cure an incorrect procedure code that changes tax treatment, material-management duties or reporting obligations.

Control	Review method	Stop signal	Approver
Procedure code	Review transaction purpose, goods source and applicable customs regime.	Code selected because it was used last time.	Trade compliance lead.
Importer/exporter	Match tax code, legal name and address to corporate and transaction documents.	Trade name used instead of legal entity or wrong branch code.	Preparer plus legal/accounting reviewer.
Entrustment/brokerage	Confirm agreement, authorisation and taxpayer role.	Third party appears without supporting authority.	Legal or authorised manager.
Registration office	Check jurisdiction, regime and storage/production location.	Office selected solely for convenience.	Customs reviewer.
Storage/inspection location	Validate port, warehouse, ICD, CFS, airport and inspection location codes.	Goods moved but the declaration still follows the old booking.	Operations plus declarant.

GOODS, HS CLASSIFICATION AND REGULATORY CONTROLS

Review each model or SKU where structure, material, power, function or new/used condition may alter classification or regulatory treatment. Do not merge goods merely because their trade names are similar.

Field	Required support	Common error	Control
Vietnamese goods description	Identification, material/structure, use, model and decisive specifications.	Generic terms such as accessories, machine or electronic parts.	Standard descriptions linked to technical evidence.
HS code	Classification rules, notes, technical evidence and prior rulings/analysis where available.	Supplier code or another model copied without review.	Internal classification sheet and approval.
Condition	New/used, complete/disassembled, set/non-set.	Actual condition or packing not reflected.	Photos and pre-shipment inspection.
Regulatory controls	Prohibition, licence, quality inspection, quarantine, food safety, energy efficiency and labelling.	Reviewing HS only and ignoring function or end use.	Policy map using HS + description + model.
Non-preferential origin	Actual country of production, not automatically seller or shipment country.	Declaring invoice country as origin.	Origin statement, labels and producer evidence.

CUSTOMS VALUE, TAX AND PREFERENTIAL ORIGIN

Area	Control question	Evidence	Risk
Delivery term	Which freight, insurance and border charges are included?	Contract, invoice, logistics quotation.	Incoterm conflicts with price composition.
Additions	Are commissions, packing, assists, royalties, proceeds, freight or insurance relevant?	Side agreements, debit notes, licence agreements.	Off-invoice payment omitted from the value file.
Deductions	Is a component included in price and legally separable?	Detailed invoice, contract and payment proof.	Deduction taken without separate evidence.
Tax rates	Which import/export duty, VAT, excise, environmental or trade-remedy measure applies?	Tariff and rules at intended registration date.	Only import duty reviewed.
Origin proof	Are form, criterion, issuer, date, third-party invoice and direct transport correct?	C/O/e-CO/origin declaration and transport evidence.	Proof exists but declaration data does not match.
Tax reconciliation	Does the independent worksheet equal the system result?	Locked tax worksheet.	Different exchange rate, unit, line value or tax code.

TRANSPORT, CONTAINERS AND QUANTITY DATA

Group	Data to reconcile	Priority source	Note
Transport document	B/L or AWB number, master/house type and issue date.	Final transport document and manifest.	Do not use a draft after a carrier amendment.
Conveyance	Vessel/voyage, flight, vehicle or transport mode.	Booking, arrival notice and manifest.	Transshipment may change the final conveyance.
Packages and weight	Package count/type and gross/net weight.	Packing list, weighing record and bill.	Decimal and kg/lb errors can be material.
Container/seal	Container number/type, seal and allocation.	EIR, VGM, packing report and booking.	Update changes made after stuffing.
Customs unit	Official unit and converted quantity per line.	Invoice, PL, packing specification and catalogue.	Trade unit may differ from customs unit.
Loading/discharge/storage location	Port, warehouse, ICD/CFS, border gate and destination codes.	Booking, arrival notice and delivery order.	Similar location names may have different codes.

DOCUMENTS AND DATA TO RECONCILE

Document/data	Issuer/preparer	Control use	Fields that must match
Contract and amendments	Buyer and seller	Transaction substance, Incoterms, payment and goods.	Parties, description, quantity, price and term.
Commercial invoice	Seller/exporter	Value, currency and parties.	Number/date, currency, total and lines.
Packing list	Packer/exporter	Packages, weights, packing and container.	Totals, gross/net and SKU/model.
B/L, AWB, manifest and booking	Carrier/forwarder	Transport, ports, packages and weight.	Bill number, ports, voyage/flight, packages and gross weight.
Catalogue/datasheet/MSDS/photos	Manufacturer	Description, HS and regulatory controls.	Model, material, rating, function and composition.
Licence/inspection result	Competent authority/body	Import/export conditions.	Goods, model, quantity, party and validity.
Origin proof	Authorised issuer/certifier	Preference and origin declaration.	Form, reference, date, criterion, invoice and quantity.
Value and tax worksheet	Business/declarant	Independent calculation.	Exchange rate, adjustments, rates and line values.
ERP/inventory/source declaration	Business	Special regimes and material traceability.	SKU, lot, quantity, source declaration and use.

Classify the evidence: the table combines documents that may form part of the statutory customs dossier in a particular case and internal evidence retained to support the business’s filing conclusion. Not every listed document must be submitted to customs for every declaration.

PRE-SUBMISSION APPROVAL WORKFLOW

Step	Input	Action	Output/lock
1. Freeze document version	Invoice, PL, transport, contract and technical files.	Assign version and cut-off timestamp.	One final customs-document set.
2. Establish legal framework	Transaction purpose and goods flow.	Confirm direction, procedure, party, office and location.	Approved regime and office note.
3. Review each line	SKU/model list.	Review description, HS, origin, policy, quantity and unit.	Evidence attached to every material line.
4. Rebuild value and tax	Invoice, freight, insurance and related payments.	Calculate independently from filing software.	Value-tax reconciliation.
5. Reconcile transport	B/L/AWB, manifest, booking, EIR/VGM.	Match packages, weight, container/seal, ports and conveyance.	No unexplained difference.
6. Run system validation	Completed draft.	Read all warnings, tax outputs and mandatory indicators.	No unresolved technical errors; every warning is reviewed and recorded. This does not replace the substantive customs review.
7. Checker review	Preview plus final document set.	Review by risk group, not in the maker’s sequence.	Named and timestamped review record.
8. Approver sign-off	Residual risk points.	Approve procedure, HS, value, tax, origin and licences under internal authority rules.	Internal “Approved to transmit” status; it does not replace customs acceptance for registration.
9. Submit and archive	Approved data and digital signature.	Transmit the data, read the acceptance or rejection response and act on the actual status.	If accepted: archive the registered declaration, routing and audit trail. If rejected: retain the reason and return to the draft for correction.

RISKS AND COMMON ERRORS

Error	Cause	Potential effect	Control
Copying an old declaration	Route, model or policy changed.	Wrong office, procedure, HS, tax or licence.	Reconfirm all shipment-dependent fields.
Checking only invoice total	Line data and off-invoice payments ignored.	Wrong quantity, line value, adjustment or tax.	Reconcile every line and the total.
Generic description	Material, function or specifications missing.	Weak HS and policy evidence.	Technical description template.
Relying on software tax	No independent calculation.	Rate or basis error remains hidden.	Double calculation.
Origin proof not reconciled	Only existence is checked.	Preference denied or verification requested.	Reconcile origin proof with invoice, PL, transport and filing.
Maker self-approves	No independent challenge.	Systemic errors repeat.	Maker–checker and risk approver.
Treating green channel as quality approval	Routing confused with compliance conclusion.	Errors accumulate until audit.	Sample-audit green-channel declarations.
No frozen final version	Email/chat files change after submission.	Cannot prove the filing basis.	Lock the declaration evidence folder and version history.

LEGAL BASIS AND OFFICIAL SOURCES

Instrument/source	Authority/status	Relevant point	Use
Consolidated Customs Law 54/VBHN-VPQH dated 23 March 2026	Office of the National Assembly; current consolidated text at update date.	Articles 18, 24, 29, 30 and 32.	Core legal basis for pre-registration controls.
Decree 167/2025/ND-CP	Government; effective 15 August 2025.	Amends Decree 08/2015 on customs procedures and supervision.	Read together with Decree 08 and any consolidation.
Circular 121/2025/TT-BTC	Ministry of Finance; effective 1 February 2026.	Amends customs-procedure rules and data appendices.	Check current filing indicators, documents and electronic procedures.
Decision 1357/QD-TCHQ procedure-code guidance	Customs authority; procedure-code guidance published in 2021, subject to checking for later amendment or replacement at filing time.	Export/import procedure-code table and use.	Use as operational guidance; classify by transaction substance and check newer specialised rules.
Vietnam Customs portal	Official operational and systems source.	System notices, policy guidance and public services.	Check updates for time-sensitive or sector-regulated shipments.

Translation note: English wording is for operational reference only and is not an official legal translation.

FREQUENTLY ASKED QUESTIONS

Can a software-validated draft be submitted immediately?

No. Technical validation does not prove the procedure code, HS, value, origin or regulatory treatment is correct.

Who should give final approval?

The law does not prescribe Maker–Checker–Approver job titles. A business should authorise someone independent from data entry and competent to approve material procedure, tax and regulatory risks.

Should green-channel declarations be reviewed?

Yes. Green routing does not remove declarant responsibility or post-clearance powers.

May an old declaration be used as a template?

Yes as a reference, but all shipment-, date-, model-, route-, policy- and tax-dependent fields must be reconfirmed.

Can a small B/L versus Packing List weight difference be ignored?

Only after the reason, unit and final authoritative data are documented. Do not select one figure and plan to explain later.

Who is responsible when a customs broker files?

The broker performs declarant duties within the law and authorisation; the cargo owner must still provide accurate data and maintain approval controls.

Can one checklist cover all industries?

Only as a baseline. Food, chemicals, used machinery, radio equipment, pharmaceuticals, animals/plants and trade-remedy goods need additional sector controls.

APPLICATION NOTE: Configure the checklist by procedure and product group, linking each critical field to evidence, an owner and a “do not submit” condition. A tick-box checklist without evidence provides little value during explanation or post-clearance audit.

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B

MACHINERY

HOUSEHOLD GOODS

COSMETICS – PERSONAL CARE