Electronic Labour Contracts Vietnam: Employer Guide 2026
Vietnam's electronic labour contract framework moved into its operational phase on 1 July 2026, when the National Electronic Labour Contract Platform and the Contract ID system came into use. For employers, however, the change is not simply a matter of replacing paper with electronic documents. Paper labour contracts remain valid, so the more important question is whether an employer's HR workflow is ready to meet the requirements that apply when the electronic route is chosen.
That means looking beyond the contract itself. Employers need to consider how employees and authorised signatories are identified, how digital signatures and timestamps are applied, whether their eContract provider meets the applicable requirements, how contract data reaches the national platform, and how employee information is retained and protected. This guide focuses on those operational questions and what employers should review before integrating electronic labour contracts into their HR processes.
Is an Electronic Labour Contract Mandatory in Vietnam?
No. Employers are not generally required to replace paper labour contracts with electronic labour contracts.
Vietnamese law recognises labour contracts concluded electronically in the form of data messages, but the electronic format does not eliminate conventional written contracts. Decree 337/2025/NĐ-CP established the specific framework for electronic labour contracts and took effect on 1 January 2026, while Circular 08/2026/TT-BNV introduced detailed implementation rules effective from 1 July 2026, including the National Electronic Labour Contract Platform and Contract ID mechanism.
An employer can therefore continue using paper contracts, adopt electronic contracts, or operate both formats where appropriate. The compliance issue begins when the employer chooses the electronic route. At that point, simply uploading a PDF or placing an electronic image of a signature on a document should not be treated as equivalent to completing the regulated eContract process.
The Three Layers Behind a Valid Electronic Labour Contract
A practical way for employers to review the process is to separate it into three operational layers: identification, signing and authentication, and platform submission. Each layer performs a different function, involves different responsibilities, and creates different compliance risks.
Layer | What needs to happen | Who is responsible | What can go wrong |
1. Identification | The employee and the employer's legal or duly authorised representative must be properly identified and authenticated using an accepted method. | Employer, employee and supporting identification system | The person signing cannot be reliably linked to the identity or authority claimed. |
2. Signing & authentication | The contract is executed through an appropriate eContract system using compliant digital signatures, timestamps and data-message authentication. | Employer, employee and eContract provider | A signature, timestamp or authentication requirement is missing, or the signatory lacks authority. |
3. Platform submission | Prescribed contract information is transmitted to the National Electronic Labour Contract Platform and processed for a Contract ID. | eContract provider, with employer oversight | Submission is late, incomplete or rejected because required information does not pass platform checks. |
These stages should not be treated as one technical event. Confirming an employee's identity does not by itself mean that the electronic contract has been properly executed, while receiving a Contract ID does not retrospectively determine whether the person signing on behalf of the employer had the necessary authority. HR teams should therefore establish separate controls for identity, signing authority, execution and submission.
Signing authority deserves particular attention. Before moving employment documentation online, employers should map which individuals are legally or internally authorised to execute labour contracts and whether any delegation of authority is properly documented. Digitalising an unclear approval structure does not solve the underlying governance issue; it can simply make an incorrect signature happen faster.
How to Choose a Licensed eContract Provider
Provider selection is one of the most important implementation decisions because the provider sits between the employer's internal HR process and the national electronic contract infrastructure. Employers should therefore not select a provider simply because it offers electronic signatures or document-signing functionality. The relevant question is whether the provider can support the specific legal, technical and data requirements associated with electronic labour contracts in Vietnam.
Before onboarding a provider, employers should review the following areas:
Due-diligence area | What the employer should verify |
Regulatory eligibility | Whether the provider meets applicable requirements for electronic labour contract services and can connect to the national platform. |
Platform connectivity | How contracts and required information are transmitted to the National Electronic Labour Contract Platform. |
Digital signatures | Which signature methods are supported and how their validity is checked. |
Timestamping | How timestamps are generated, attached and preserved. |
Authentication | How the completed data message is authenticated. |
Submission controls | How failed, delayed or rejected submissions are detected and resolved. |
Contract ID handling | How Contract IDs are received, stored and reconciled with HR records. |
Audit trail | Whether HR can retrieve evidence of identification, signatures, timestamps, authentication and submission history. |
Data protection | Where employee data is stored, who can access it and whether processing occurs outside Vietnam. |
Data portability | How contracts, audit records and employee data can be transferred if the employer changes providers. |
Incident management | How security incidents, platform failures and service interruptions are reported and handled. |
The agreement with the provider should also allocate responsibilities clearly. If a submission fails, for example, HR should know who identifies the failure, who corrects the information, how quickly the employer will be notified and what evidence will be retained. Employers should also confirm the provider's current regulatory and platform-connection status against official information available from the competent authority before signing a long-term service agreement.
When Does the Contract Take Effect — and Why Doesn't the Contract ID Change It?
One of the easiest mistakes is to treat the Contract ID as the point at which an electronic labour contract becomes effective. It is not. Under the electronic labour contract framework, effectiveness is tied to completion of the applicable signing and authentication process, unless the parties agree on another effective time.
The Contract ID is an administrative identifier used by the national platform. Circular 08/2026/TT-BNV provides that issuing the ID does not change the time of conclusion, content or effective date of the contract. In practice, HR teams should therefore avoid designing onboarding workflows that automatically wait for a Contract ID before treating an otherwise properly concluded contract as effective.
What Do the A, B and C Prefixes Mean?
Each electronic labour contract receives an ID containing a letter followed by numerical characters. The first letter indicates how the contract entered the national system.
Prefix | Contract category |
A | Electronic labour contract concluded from 1 July 2026 through the prescribed electronic process |
B | Paper labour contract subsequently converted into electronic form |
C | Electronic labour contract concluded before 1 July 2026 and processed under the transitional mechanism |
The practical distinction is important: the Contract ID identifies and classifies the contract; it does not create the employment relationship or independently determine when that relationship begins.
Contracts Signed Before 1 July 2026
Employers should not assume that contracts signed before the national platform became operational suddenly became invalid. Electronic labour contracts concluded before 1 July 2026 may enter the transitional mechanism and receive a Contract ID beginning with C where the applicable requirements are satisfied.
This makes a historical contract review useful for employers that had already adopted electronic signing. HR teams should identify electronic labour contracts signed before 1 July 2026, determine which signature and authentication methods were originally used, establish whether additional technical steps are required for the transitional process, and confirm which provider will manage any necessary submission.
The absence of a Contract ID alone should therefore not be treated as evidence that a pre-July contract is invalid. The underlying contract and the way it was concluded need to be reviewed according to the rules applicable to it.
What About Existing Paper Contracts?
Existing paper contracts do not need to be re-signed simply because an employer decides to introduce an electronic HR system. Paper contracts may be converted into electronic form subject to the applicable conversion requirements, and a qualifying converted contract can receive a Contract ID beginning with B.
For implementation purposes, employers should first classify their contract population into three groups: existing paper contracts, electronic contracts concluded before 1 July 2026, and new electronic contracts concluded under the current framework. A separate process can then be established for each category instead of attempting to migrate every employee through the same workflow.
Foreign Employees and the Work Permit Overlap
Foreign employees add another compliance layer because an electronic labour contract does not replace immigration or work-authorisation requirements. For identification purposes, the electronic contract framework accommodates foreign individuals through relevant identity documentation, including passport and immigration information where applicable. However, employers should not treat successful eContract execution as confirmation that an employee is legally authorised to work in Vietnam.
The HR file should remain consistent across the electronic labour contract, work permit or exemption, passport, immigration documentation, payroll and tax records. Before releasing an electronic contract for signature, HR should compare the employee's identity, job title, employer and other relevant employment details against the work-authorisation documents already held. A technically compliant electronic signing process cannot cure a separate work-permit problem.
This is particularly important when an employment term changes. A change that appears straightforward within the eContract system may also affect the employee's work-authorisation or immigration documentation. Employers hiring foreign personnel should therefore integrate electronic contracting into their wider Vietnam work permit and immigration compliance process, rather than operate it as an isolated HR tool.
Employee Data, Retention and the Personal Data Protection Issue
Electronic labour contracting is also a data-governance project. Contract information can include employee identification details, contact information, position, salary, allowances, benefits and other employment data. Employers therefore need to consider not only whether a contract can be signed electronically, but also where that information travels, who can access it and how long different copies are retained.
Circular 08/2026/TT-BNV provides for electronic labour contract data, appendices and related electronic documents on the National Electronic Labour Contract Platform to be stored for 10 years from termination of the labour contract, subject to the detailed rules applying to the relevant records. At the same time, employers must comply with Vietnam's personal data protection requirements concerning the lawful processing, retention and deletion of employee information.
The practical response should not be to apply a blanket ten-year retention period to every item in an employee's HR file. Employers should instead distinguish between records subject to specific statutory retention requirements and other employee data held for separate HR, legal or operational purposes.
Data category | Retention approach |
Electronic contract records subject to statutory platform retention | Follow the applicable statutory retention period |
Supporting HR records | Identify the applicable legal and operational basis for retention |
Provider audit logs | Define retention requirements contractually and legally |
Duplicate employee data | Review whether continued retention remains necessary |
Data held when a provider relationship ends | Establish migration, return and deletion procedures |
This distinction becomes particularly important when an eContract provider processes information on the employer's behalf. Provider agreements should address access controls, information security, incident response, data export, deletion, subcontractors and cross-border processing where relevant. Employers should obtain appropriate legal review before implementing a company-wide retention schedule where labour, statutory eContract and personal data requirements overlap.
A 30-Day Readiness Checklist for HR
Employers do not need to digitise their entire employment contracting process at once. A controlled 30-day implementation period can expose legal, technical and operational gaps before electronic contracting becomes the default workflow.
Days 1–5: Map the Current Contract Process
Document how a labour contract currently moves from employment approval to onboarding. Identify who prepares contracts, who approves employment terms, who has authority to sign, how employee identity is checked, where executed contracts are stored and which internal systems receive employee information. The objective is to understand the existing workflow before adding another technology layer.
Days 6–10: Classify Existing Contracts
Separate the current workforce into existing paper contracts, electronic contracts concluded before 1 July 2026, and contracts that will be signed electronically under the current framework. This exercise helps determine which records may need conversion or transitional processing and which require no immediate action.
Days 11–15: Review Provider Capability
Assess potential providers against regulatory, technical and data-protection requirements. Employers should request evidence of national-platform connectivity, digital signature and authentication controls, audit-trail functionality, data-hosting arrangements, security measures and incident procedures rather than relying only on product demonstrations or marketing claims.
Days 16–20: Fix Signing Authority and Internal Controls
Create or review the employer's signing-authority matrix, then map responsibility across the electronic process: identity → authority → contract approval → digital signature → authentication → platform submission → Contract ID reconciliation. Each stage should have a clear owner and an escalation process when something fails.
Days 21–25: Review Employee Data Governance
Map what information leaves the HR system, what the provider receives, what is transmitted to the national platform, where copies are stored and how long each dataset is retained. Privacy documentation and internal policies should be updated where necessary, with particular attention to third-party access, cross-border processing and what happens to employee data when the provider relationship ends.
Days 26–30: Pilot Before Full Rollout
Test the process using a controlled group of contracts before expanding it across the workforce. HR should be able to retrieve the executed contract, signatures and timestamps, authentication evidence, submission status, Contract ID and relevant audit history. Failed or delayed steps should be documented and corrected before electronic contracting becomes the standard process.
At the end of the 30-day review, management should be able to answer four basic questions: Who is authorised to sign? Is the provider properly equipped to process the contract? Who confirms successful submission? Where is employee data going? If any of those answers remains unclear, the process is not yet ready for a full rollout
How Vinex Can Help
Moving to electronic labour contracts is not only an HR technology project. It involves labour compliance, signing authority, employee data, foreign-worker documentation and the internal controls connecting these areas. Vinex can support employers in reviewing electronic labour contract templates and signing arrangements, assessing signing authority and approval workflows, reviewing eContract provider requirements and contractual responsibilities, and assessing existing paper and pre-July 2026 electronic contracts.
For companies employing foreign personnel, Vinex can also help align employment documentation with work permit and immigration requirements. More broadly, our team can assist with employee-data considerations and ongoing HR and labour compliance in Vietnam, helping businesses identify legal and operational gaps before rolling electronic contracting out across their workforce.
Are electronic labour contracts mandatory in Vietnam?
No. Employers are not generally required to replace paper labour contracts with electronic labour contracts. Paper contracts remain available, while employers choosing the electronic format must follow the legal and technical requirements applicable to that process.
Do paper labour contracts remain valid?
Yes. The introduction of the electronic labour contract framework does not generally invalidate properly executed paper labour contracts. Employers may continue using paper contracts or convert eligible existing contracts into electronic form where appropriate.
When does an electronic labour contract take effect?
The Contract ID itself does not determine when the contract takes effect. The applicable signing, timestamping and authentication requirements must be completed, subject to any different effective time agreed by the parties.
What Is a Contract ID and What Do the A, B and C Prefixes Mean?
A Contract ID is an identifier assigned through the National Electronic Labour Contract Platform. A identifies qualifying electronic contracts concluded from 1 July 2026, B identifies qualifying paper contracts converted into electronic form, and C applies to qualifying electronic contracts concluded before 1 July 2026 under the transitional mechanism.
Comments