MPS A05 Administrative Procedures Decision 778

The Vietnam Personal Data Protection Law (Law 91/2025/QH15) establishes the filing obligations – when organizations must interact with MPS. Decree 356/2025/ND-CP specifies the forms and data structures for those interactions. Decision 778/QD-BCA-A05 specifies the procedural mechanics within the MPS A05 unit for handling those interactions. For a full view of the statutory obligations that trigger these procedures, see the Vietnam PDPL (Law 91/2025/QH15) compliance page. For the complete Decree 356 form catalog, see the Decree 356 PDPL Implementation page.

Decision 778 sits at the most granular level of the PDPL compliance instrument hierarchy: Law 91 (statutory obligations) – Decree 356 (administrative forms and data structures) – Decision 778 (MPS A05 procedural mechanics). A practitioner implementing PDPL compliance must understand all three levels to execute MPS interactions correctly. Decision 778 is specifically relevant for the A05 unit interactions and does not govern all MPS interactions – only the six procedure types it explicitly operationalizes.

For organizations that rely on a compliance platform to manage PDPL filings, Decision 778 is the instrument that determines whether the platform's filing workflow matches what MPS A05 actually expects to receive. A platform that implements Decree 356 forms but does not model the Decision 778 procedural steps will produce correctly formatted documents that may still follow the wrong procedure sequence when submitted.

ComplianceOne models the Decision 778 A05 procedural sequence as a named filing workflow state machine, separate from but integrated with the Decree 356 form preparation workflow. When a practitioner initiates a filing that falls within one of the six Decision 778 procedures, the platform configures the filing lifecycle to track the A05 procedural steps – not just the generic filing states – ensuring that the 30-day review clock, 15-day supplement response window, and 10-day resubmission timeline are all tracked against the MPS procedure timeline rather than an internal deadline only.

The DLCN-HC procedure code for the applicable procedure is pre-configured within each relevant form template in the Compliance Forms module. When a practitioner generates a Mau so 02a (DPIA Dossier – Controller), the form is pre-labeled with both the Decree 356 template ID and the corresponding DLCN-HC procedure code. This removes a common error mode where the form content is correct but the procedure reference is missing or mismatched. The filing workflow routes the completed dossier through internal review and approval before submission, with the approval record captured in the audit trail.

For supplement request management, the platform creates a linked supplement response task when an MPS A05 supplement request is logged. The task is pre-assigned to the practitioner responsible for the original filing, pre-populated with the supplement deadline (15 working days from the supplement request date), and linked to the original filing record so that the complete interaction history – initial submission, supplement request, supplement response, and final determination – is captured in a single, navigable evidence record. This complete procedural record is available for export as an audit-grade evidence pack at any point in the lifecycle.