Every customs declaration in Vietnam currently runs on the VNACCS/VCIS system — the electronic declaration platform modelled on Japan’s NACCS, operating since 2014. This system is entering the final phase of its life cycle: the customs service has determined to build a new digital customs system to replace it, and although the official cutover date belongs to the regulator’s decision, a wise import-export enterprise prepares from now — because in every customs system transition worldwide, enterprises get stuck not on the new software, but on their own old data.
Context: why must VNACCS/VCIS be replaced?
VNACCS/VCIS took Vietnamese customs from paper files to electronic declaration and automatic channeling, but its architecture belongs to the declaration-centric generation of systems. The digital customs direction the General Department of Customs pursues places data and risk management at the centre: data connectivity between customs and licensing ministries, seaports, carriers and the national single window system; pre-arrival processing; and big data analytics to select inspection targets instead of blanket inspection. The new system is therefore not merely a rewritten VNACCS — it is a management model change the enterprise will feel at three points: declared data must be standardised and consistent at field level, with little room left for “approximately right” declarations; the enterprise’s compliance history is accumulated by the system and used directly in channeling; and machine-to-machine integration between the enterprise’s software and the customs system becomes the main channel in place of manual interface entry.
What the enterprise must prepare: four data assets to clean from now
The first asset is goods master data: HS codes, goods names, technical descriptions, units of measure — in many enterprises this master set has fragmented over years, with the same item carrying multiple descriptions and sometimes multiple HS codes; the new system with automatic consistency checks will flag exactly those fragmentations. The second asset is partner data: tax codes, names and addresses of foreign suppliers and customers must match across the accounting system, the customs declaration software and commercial documents. The third asset is the declaration history repository: the enterprise must store and be able to retrieve all of its own past declarations, channeling results, amendments and assessments, because this history is both an input to future channeling and evidence in post-clearance audits within the five-year window. The fourth asset is signing and integration infrastructure: a valid digital signature of the correct subject, declaration software with an upgrade path to the new connectivity standard, and a fallback operating plan for the transition — an enterprise with large declaration volumes should agree the cutover scenario with its software vendor and customs broker in advance, including any period when the two systems coexist.
Governing the transition: do not let one cutover day break the supply chain
International experience shows the greatest risk of a customs system transition sits in the cutover window: declarations in progress on the old system, goods already shipped but documents not yet synchronised, declaration teams unfamiliar with new data fields. An enterprise governs this phase well with four principles. First, follow the General Department of Customs’ official notices on the roadmap and pilot runs, appointing a fixed technical-business focal point to join trial programmes if invited. Second, do not concentrate time-sensitive shipments exactly in the cutover window once the schedule is published — coordinate import-export timing around the cutover milestone the way one coordinates around a long holiday. Third, retrain the declaration team on the new data standard before the application date, with an internal review round of sample declarations. Fourth, keep a direct contact channel with the managing customs sub-department and the software vendor during the first weeks of the new system’s operation, because on-the-ground support in this phase decides incident resolution speed more than any guidance document. An enterprise treating the system transition as “customs’ and the vendor’s business” will discover, on cutover day, that its own ten-year master data was the largest part of the work.
Frequently Asked Questions
What is the official transition roadmap for the new digital customs system replacing VNACCS/VCIS?
There is as yet no single officially published cutover date that an enterprise can lock into its calendar. The customs service is deploying the programme to build a digital customs system replacing VNACCS/VCIS under the sector’s digital transformation strategy, with preparation and pilot steps preceding a full cutover. The enterprise should follow the General Department of Customs’ official notices and do the work that does not depend on the cutover date — cleaning master data, partner data and declaration history — because that work is necessary under every timeline scenario.
How should an enterprise prepare declaration data, digital signatures and system connectivity before the transition?
Four preparation layers. One, declaration data: unify the goods master data — HS code, goods name, technical description and unit of measurement for each item, eliminating the state where the same goods carry different declaration styles across years; partner data (tax code, name, address) consistent across accounting, declaration software and documents; and a complete declaration history repository serving future channeling as well as post-clearance audit within five years. Two, digital signatures: ensure the enterprise’s digital certificate is valid, belongs to the correct entity and is properly registered with customs for the declarant. Three, system connectivity: the declaration software must have an upgrade roadmap to the digital customs system’s new connection standards and data fields — the enterprise should agree in advance with its software vendor and customs broker on the cutover scenario, including a phase where both systems coexist. Four, people: appoint a fixed technical–professional contact and retrain the declaration team on the new data standards before the real application date.
During the transition phase, are declarations on the old system still accepted?
Under the transition scenario the General Department of Customs publishes for each cutover wave, not under the enterprise’s own assumptions. The governing principle for this phase is that declarations already opened on VNACCS/VCIS before the cutover point are closed out under the transition guidance — completed on the old system or migrated to the new system under the published rehearsal scenario — and the enterprise must not unilaterally cancel an old declaration to re-declare on the new system, because duplicate declaration across both systems is the error creating the most serious data discrepancies in the transition window. The real risk sits in in-flight declarations: goods already shipped with documents not yet synchronised, declarations opened but not yet cleared when the old system stops receiving. A high-volume enterprise should reconcile its list of open declarations in advance with the managing customs branch and its software vendor, and avoid opening new declarations right against the cutover point for time-sensitive shipments.
When an enterprise hits a technical error declaring on the new system, through which channels is it handled and complained about?
Handle it on two levels: technical incident and administrative complaint. When a technical error arises on the new system — a declaration cannot be transmitted, a data field error, no system response — the enterprise contacts immediately the customs authority’s official support channels (the support unit at the managing customs branch and the system’s user support channel) in parallel with its own declaration software vendor, and records full incident evidence: the time, the error message, the affected declaration codes — because this is the basis for customs to handle consequences on declaration deadlines and to keep the enterprise from being charged a late-declaration fault caused by a system incident. In the first operating weeks, on-site support through a fixed contact with the branch decides handling speed more than any guidance document. If the incident leads to a specific adverse administrative decision — an assessment, a penalty for late declaration — the enterprise exercises its complaint right against that decision under the Law on Complaints and customs law, with the saved incident evidence attached.
Clean your customs data before cutover day with FLAT Law Firm
FLAT Law Firm audits the enterprise’s goods master data and declaration history against the digital customs risk management standard, and builds the system transition plan for the declaration team and customs broker — so the day VNACCS/VCIS stops is an ordinary working day.
This article has been quality-reviewed by the FLAW AI Legal Council