DPO Radio

Circular 08/2026/TT-BNV sets how eContract providers and information systems connect to the Electronic Labour Contract Platform, how platform data is accessed, and how services are reported. It has been in force since 1 July 2026.
It covers:
Confirm how it applies to you, and how to read it, with qualified advisers.

Circular 08 sits under the Vietnam Electronic Labor Contracts Overlay. The parent decree, Decree 337/2025/NĐ-CP, sets when an electronic labor contract has the same legal validity as a paper one. Circular 08 adds the narrower procedures for connecting, using data, working with the Platform and reporting.
In ComplianceOne, your Circular 08 evidence links to your Decree 337 evidence without repeating it. Each instrument keeps its own status and its own role.
| Operational Area | ComplianceOne Support |
|---|---|
| Applicability | Track each provider's connection request and platform-synchronization status before contract data flows through the Platform |
| Operational work | Record each e-contract's lifecycle stage and identifier, linked to its Decree 337 signature and identity evidence |
| Official forms | Four verified official forms are included: Form No. 01 (Mẫu số 01), Form No. 02 (Mẫu số 02), the data-access request and the service report. The data catalog that accompanies them is a reference, not a form |
| Audit readiness | Keep the Form No. 01 and Form No. 02 connection-request trail beside the data-access log and the service report |

Circular 08 is available in the Enterprise Unlimited package, through the Sector Overlays module, whether installed directly or for reference.
Two kinds of evidence, kept apart and linked. Connection requests and platform-synchronization status are tracked separately from contract identifiers and lifecycle evidence. Both link to the Decree 337 signature and identity records behind them.
Official forms, clearly labelled. The four official forms from the circular's appendices keep their official numbers and source labels. The nine internal lifecycle, synchronization and cross-reference templates are marked as ComplianceOne working documents.
Ready for an audit or an authority. You can package the filings Circular 08 covers for an audit or for the authority. ComplianceOne does not guarantee compliance, certification or acceptance by an authority.
Connecting to the Platform. Circular 08 opens access to the Electronic Labour Contract Platform. A user signs in with a national electronic identification account. An eContract provider files a connection request before any contract data flows. ComplianceOne records each connection-request dossier against the channel that actually carried it, not a generic label.
Agreements and their synchronisation. Each agreement signed electronically links its parties to the people and organizations already in ComplianceOne. It holds the signature evidence that verified each signer, and the synchronisation records that show whether it reached the Platform. Each attempt carries its outcome. If the most recent attempt failed, ComplianceOne flags it in your evidence pack.
Filings on the record. Each dossier filed under Circular 08 is recorded as an electronic submission with:
Who does what. ComplianceOne records that a filing was made; it does not transmit it. Sending a contract to the Platform within 24 hours is the eContract provider's duty under the parent decree. The Platform assigns the contract identification code.
The procedures Decree 337 leaves out. Circular 08 adds provider and information-system connection requests, platform data-access requests and service-provision reporting, with four official forms from its appendices behind them.
Two evidence streams, as the circular has them. Connection and synchronization evidence stays apart from contract-identifier and lifecycle evidence, matching the circular's two groups of requirements rather than one merged HR record.
One employee record, two laws. Employee-data evidence links to your PDPL records rather than being copied, so one employee record supports both the labor-contract and the personal-data duties.
Failed synchronisations flagged early. Every attempt to synchronise with the Ministry of Home Affairs platform is recorded with its outcome, so you see a failed one in the evidence pack, not during an inspection.
Maintains Records of Processing Activities aligned with Phu luc I data structure requirements.
Explore Data MappingProvides all 13 Mau so and 8 Phu luc templates with official IDs and prescribed data fields.
Explore Compliance FormsCaptures tamper-evident records of every form preparation, state transition, submission, and supplement action.
Explore Audit Trailownership and recurring review across the decree and circular layers of this overlay.
Explore Program GovernanceSee how ComplianceOne helps structure evidence, ownership, and review for this framework.

Yes. It has been in force since 1 July 2026. ComplianceOne keeps it separate from draft, roadmap and related instruments.
Decree 337 sets when an electronic labor contract has the same legal validity as a paper one. Circular 08 adds the procedures that put it into practice: connection, data use, the Platform and reporting. In ComplianceOne it keeps its own status, evidence and review history.
The four official forms keep their official numbers and source labels:
Form No. 01 and Form No. 02, the provider and information-system connection requests in Appendix I;
the data-access request in Appendix III;
the service report in Appendix IV.
The nine internal lifecycle, synchronization and cross-reference templates behind them are labelled as ComplianceOne working documents.
No. Under the parent decree, the eContract provider must send an electronic labour contract to the Platform within 24 hours of the last party signing. ComplianceOne records each synchronisation attempt and its outcome, and flags a failed latest attempt in an evidence pack. It concludes no contract, transmits nothing, and does not assign the contract identification code, which the Platform issues.
No. It organizes evidence, ownership, workflow and review. Your organization remains responsible for legal interpretation.
Yes. Contract identifier, synchronization and connection-request records link to your Decree 337 signature and identity evidence and to your PDPL employee-data record. Each keeps its own ownership and audit history.

Test scoped workflows, evidence, and review with your compliance team.

Review applicability, evidence sources, and operating-model requirements.