IMPORTING ENTITY
Importer · Tax ID · Type · ResponsibilityCompany name, tax ID, import type and the role of the named entity should match the actual transaction structure.
An import shipment does not end at the status “cleared through the border”. Declaration data, HS classification, customs value, origin, tax obligations, VAT and the post-clearance document set should be locked within one consistent data structure so the business can receive the goods, account for the shipment and reconcile the file.

Before registering the declaration, five data groups should be cross-checked together to prevent mismatches between the transaction, the actual goods and the declaration file.
Company name, tax ID, import type and the role of the named entity should match the actual transaction structure.
Product name, model, function, construction, material and technical documents should provide sufficient basis for classification review.
Invoice, currency, trade terms and value-related data should be reconciled before declaration registration.
If preferential treatment is claimed, origin and C/O should be reviewed together with HS, product description, commercial documents and the applicable origin rules.
Permits, specialized inspections and technical documents should be determined from the actual product category, not merely the trade name.
A declaration is reliable only when commercial, technical, origin, valuation and tax data are locked to the same source information set.
Commercial, technical, origin and tax data must be reconcilable before entering the declaration.
Import VAT should be read across the full chain HS → customs value → import duty → VAT → documents, rather than treated as an isolated rate.
Importer and the VAT status of the imported goods.
Customs taxable value and relevant taxes, where applicable.
Determined by product group and the policy in effect at the time of import.
Declaration · tax evidence · invoice · file.
The current VAT framework includes Law 48/2024/QH15, Law 149/2025/QH15, Decree 181/2025/ND-CP and amendments/supplements effective in 2026.
Each step is a data handoff point. Move to the next step only after the previous step’s input file has been checked and recorded.
Product name · model · function · reference HS · taxes · specialized control.
Invoice · Packing List · Contract · transport document · C/O · catalogue.
Submit reconciled data into the customs declaration system under the appropriate import type.
Handle document review, physical goods inspection or supplementary requests based on the actual customs result.
Import duty · VAT · other obligations depending on the goods.
Confirm status, deliver the goods and close the shipment output file.
The checklist is divided into two groups: transaction/transport documents and goods/compliance documents, helping identify missing items before declaration.
NOTE: Not every document in this checklist is mandatory for every customs file. The actual list must be determined by import type, goods and the specialized policy applicable to the specific shipment.
Each product group requires a different data layer. Model, composition, function, labeling or technical documents determine how HS and applicable policy should be reviewed.
Model · function · year of manufacture · new/used · serial · catalogue.
Model · function · specifications · component or complete equipment.
Composition · CAS · SDS/TDS · intended use · physical form.
Finished product/raw material · use · label · specialized file where applicable.
Ingredients · packing format · label · food-safety/inspection requirements if applicable.
Equipment list · shipment split · model/serial · system configuration · timeline.
Declaration data and final processing status.
Calculation basis and obligations arising from the shipment.
Tax amount and supporting evidence based on the actual shipment.
Origin documents used in the file, if any.
Permits, inspection results or other arising documents.
Invoice · PL · transport document · declaration · tax · documents within scope.
Legal sources cross-checked through 14/08/2026; click each row to open the official document on the Government Portal. Application must still be reviewed against the actual goods and the date of the specific shipment.
No. Clearance and file completion are not the same. After clearance, the handover documents, tax data and specialized-control file should still be checked against the shipment scope.
No. A C/O alone is not sufficient. HS, origin, product description, documents and the preferential conditions of the specific shipment must be reconciled.
No. The VAT base for imported goods must be determined under the VAT law and the relevant tax components of the actual shipment.
Tax obligations, C/O treatment and policy should not be locked before there is sufficient classification basis. The scope may be prepared in advance, but declaration data should be fully reviewed before registration.
It may be necessary in some cases, but operational risk is higher. Review should preferably be completed beforehand to allow time for document corrections and file preparation.
No. The actual file depends on the import type, goods, specialized policy and shipment-specific requirements.
This page structures data and control workflow only; it does not replace an official classification conclusion, tax determination or the opinion of the competent authority for a specific file.
Product name · Model · Catalogue · Invoice · Packing List · C/O · Customs value · Incoterms · Packages · Kg/CBM · Delivery point