Businesses often assume that entering data, transmitting IDA/EDA or seeing a declaration number means the declaration has been officially registered. That can trigger truck dispatch, cargo delivery or tax decisions too early. Under the VNACCS workflow, a declaration number may be allocated at the IDA/EDA information stage; legal effect for customs formalities arises only after IDC/EDC is accepted as registered. Errors found after registration must be handled through formal amendment, cancellation or a new declaration, depending on the affected field and procedural stage. This article separates an internal draft, IDA/EDA information filing, IDB/EDB correction and IDC/EDC official registration.

QUICK FACTS

“Draft declaration” is an operational term

It may mean a local file not yet transmitted or a pre-declaration step sent to the customs system.

Official registration creates legal effect

Legal effect arises when IDC/EDC is accepted as registered, not merely when a declaration number appears.

A number does not prove registration

VNACCS may allocate a number at IDA/EDA; verify registration date, registered status and the IDC/EDC response.

Post-registration errors require formal handling

Data can no longer be edited like a draft; amendment, cancellation or a new declaration may be required.

Illustration for Draft and Official Customs Declarations: What Is the Difference? — Illustration of the logistics topic, document or operation discussed in the article.

SCOPE

This article covers electronic import and export declarations submitted through VNACCS/VCIS or authorised connected software. It does not replace procedures for passenger baggage, postal/express shipments, transit cargo or specialised declaration types.

Software labels may differ. The correct distinction must be based on the procedural status, not merely on buttons labelled “draft”, “pre-declare” or “register”.

KEY TERMS

Term	Meaning	Operational role
Internal draft	Data stored locally or on the company’s server and not sent to Customs.	Used for data entry, internal review and approval; no declaration number or routing result.
Pre-declaration	Information transmitted before official registration, commonly associated with IDA/EDA.	The system may validate data and allocate a declaration number, but this does not by itself establish registered status.
IDA / EDA	Import/export declaration information messages sent before official registration.	May produce a declaration number and an information-stage status; the number alone does not prove registration.
IDB / EDB	System messages used to call up and correct import/export declaration information after IDA/EDA and before IDC/EDC.	Allow pre-registration correction; they do not replace formal amendment after registration.
IDC / EDC	Official import/export declaration registration messages.	When accepted, the declaration obtains registered status and registration date and proceeds to customs processing.
Amendment	A formal procedure to correct a registered declaration within permitted scope and timing.	Replaces free editing after registration and may affect tax or compliance.
Cancellation	A procedure terminating a registered declaration in eligible cases.	Used where the old declaration cannot continue or cannot be corrected by amendment.

HOW THE PROCESS WORKS

1. Internal draft

Data from the commercial invoice, packing list, transport document, contract, certificate of origin, technical documents and permits is entered into the software. The company may revise or delete the file without changing the legal status of the shipment.

2. IDA/EDA information filing: a number may be allocated before registration

The customs system may return structural errors, tax-calculation information or items requiring review. The official VNACCS user manual shows that the information-stage record may have a “declaration number allocated” status while the “official filing” action remains available. Therefore, a number or an IDA/EDA response does not by itself mean the declaration is registered.

3. IDB/EDB correction: revise data before registration

After IDA/EDA, the declarant may call up and correct information through the appropriate pre-registration message before IDC/EDC. System responses and approved versions should be retained, especially for high-risk fields.

4. IDC/EDC official registration: legal effect for customs formalities

Under the Customs Law, an electronic declaration is registered after Customs accepts the filing, and the registration time is recorded. From that point the registered declaration is valid for customs formalities. The applicable goods-control, tax and correction rules must still be checked against the specific regime, timing and shipment documents; they cannot be inferred from the declaration number alone.

Control point: “Message transmitted” is not enough. Verify system acceptance, declaration number, registration date and processing status.

COMPARISON TABLE

Criterion	Internal draft	IDA/EDA pre-declaration	IDC/EDC official registration
Data status	Stored internally.	Sent for validation, number allocation and correction before registration.	Accepted and registered by Customs.
Declaration number	None.	May be allocated at the information stage; not proof of registration.	The allocated number is associated with a registered status and registration date once IDC/EDC is accepted.
Validity for customs formalities	No.	Not equivalent to a registered declaration.	Yes.
Risk routing	None.	Not the final processing result.	Processed under the customs risk-management mechanism.
Editing	Freely editable internally.	May be corrected through messages such as IDB/EDB before registration.	Requires amendment, cancellation or a new declaration as applicable.
Tax/policy impact	Internal estimate only.	Pre-registration review.	The legally relevant timing must be checked under the rules applicable to the specific case; the number alone is insufficient.
Responsibility	Internal data-control responsibility.	Further review is required.	The declarant is responsible for completeness and accuracy.

DATA TO LOCK BEFORE OFFICIAL REGISTRATION

Data group	Source	Items to lock	Risk
Parties and customs regime	Tax ID, contract, transaction purpose	Importer/exporter, regime code, customs office	Cancellation/re-registration or wrong compliance treatment
Transport	B/L, AWB, booking, arrival notice	Mode, document number, port/border gate, dates	Manifest mismatch and customs-supervision issues
Goods	Invoice, packing list, catalogue, datasheet	Description, model, function, material, quantity, weight	Wrong HS code or specialised-control policy
HS, origin and tax	Tariff, C/O, technical documents	HS code, origin, customs value, tax and preference codes	Tax shortfall, denied preference, reassessment
Specialised control	Licence, registration, test report	Document number, model and scope	Delayed clearance or additional document requests
Containers/packages	Packing list and loading records	Container, seal, packages and gross/net weight	Customs-supervision mismatch

CONTROL WORKFLOW

Confirm the final version of all commercial, transport and regulatory documents.
Create an internal draft with version history and preparer identity.
Review three layers: commercial; technical/regulatory; customs/tax.
Send IDA/EDA, review the allocated number and system response, and do not mistake that stage for registration.
Use IDB/EDB or the relevant pre-registration function to correct data and retain the approved version.
Obtain approval for high-risk fields: regime, HS, value, origin, customs office and licences.
Digitally sign and submit IDC/EDC, then verify the registered/accepted response.
Verify registration date, registered status, routing and tax requirements; do not rely on the declaration number alone.
Handle errors through amendment, cancellation or re-registration as legally appropriate.

COMMON RISKS

Error	Cause	Impact	Control
Confusing “number allocated” with “registered”	Relying on the number or the “number allocated” status	Dispatching cargo before IDC/EDC is accepted	Verify registration date, registered status and the system response
Submitting before documents are final	Invoice/packing list still changing	Amendment, explanation or cancellation	Freeze document versions before IDC/EDC
Wrong foundational fields	Incorrect regime, customs office or declarant	May not be fixable through ordinary amendment	Two-person approval for red-flag fields
Ignoring pre-declaration feedback	Focusing only on successful transmission	Tax or logical errors remain	Review IDA/EDA, correct through IDB/EDB and recheck before IDC/EDC
No approval trail	Fragmented chat-based communication	Difficult accountability and audit trail	Maintain shipment-level approval records

LEGAL BASIS AND SOURCES

Source	Authority	Date/status	Role
Consolidated Customs Law No. 54/VBHN-VPQH	Office of the National Assembly	23 March 2026	Articles 29–30 on customs declaration and registration.
Decree 167/2025/ND-CP	Government	Effective 15 August 2025	Amends detailed Customs Law implementation rules.
Circular 121/2025/TT-BTC	Ministry of Finance	Effective 1 February 2026	Updates customs procedures, supervision and import/export tax administration.
VNACCS User Manual	Vietnam Customs	System reference	Confirms the system sequence: IDA/EDA may show “declaration number allocated” while official filing remains available; IDC/EDC is the registration step.

FAQ

Does saving a declaration in the software count as filing?

No. A local file has no customs effect, and even a number allocated at IDA/EDA is insufficient without successful registration.

Can IDA/EDA alone be used to dispatch a truck?

It should not be the sole basis. IDA/EDA may only have allocated a number; verify accepted IDC/EDC registration and port/customs-supervision requirements.

Can an official declaration be edited like a draft?

No. Formal amendment, cancellation or re-registration rules apply.

Does a declaration number mean registration or customs clearance?

No. A number may be allocated before registration. After successful registration, routing, checks, taxes and specialised-control conditions still remain.

Must a wrong HS code always lead to cancellation?

Not necessarily. The answer depends on timing, processing status, amendment rules and policy impact.

Who should approve the declaration before official registration?

At minimum, use a preparer and an independent reviewer. Higher-risk shipments should also involve tax, compliance or specialised-control personnel.

APPLICATION NOTE: “Draft declaration” is an operational expression. In VNACCS, a declaration number may be allocated before official registration. Operational decisions should be based on the number, registration date, registered status, system response and actual documents. This English version is for operational reference and is not an official legal translation.

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