Vietnam E-Invoicing: SAP Readiness Guide

Vietnam’s current electronic-invoicing framework is set out in Government Decree No. 254/2026/NĐ-CP, issued on 30 June 2026 and effective from 1 July 2026. The decree details the implementation of Tax Administration Law No. 108/2025/QH15 for electronic invoices and electronic documents. For SAP teams, the central design question is which invoice route applies to each legal entity and transaction: an invoice with a tax-authority code, an invoice without a tax-authority code, an invoice generated from a connected cash register, or an eligible export invoice type.

Executive Summary

Current status	Decree 254/2026/NĐ-CP is in force from 1 July 2026.
Who is affected	Economic and other organizations, business households and individual businesses are covered through route-specific rules, with defined exceptions and special cases.
Invoice models	Electronic invoices with a tax-authority code, invoices without a tax-authority code, and invoices generated from cash registers connected to the tax authority.
Exports	Eligible exporters may use an electronic commercial invoice, electronic VAT invoice or electronic sales invoice, depending on the transaction.
SAP impact	Legal-entity and branch scope, billing-event timing, master data, tax data, output generation, authority or provider communication, response handling and audit evidence.
Recommended next step	Classify each Vietnam company code, branch and invoice scenario before selecting the SAP and integration design.

Who Uses Which Electronic-Invoice Route?

Decree 254/2026 does not place every taxpayer on a single technical route. The applicable model depends on the taxpayer type, business activity, tax-risk classification and technical capability.

• Invoices with a tax-authority code: These apply to the broad group identified by the decree, including economic organizations, other organizations, business households, individual businesses and specified high-tax-risk cases, unless a different route applies.
• Invoices without a tax-authority code: Qualifying businesses in listed sectors may use this route where they meet the decree’s conditions for electronic tax interaction, IT infrastructure, accounting and e-invoice software, data storage and transmission to buyers and the tax authority. High-tax-risk cases are excluded from this route.
• Cash-register-generated invoices: Listed consumer-facing activities may use electronic invoices generated from cash registers connected to the tax authority. The decree includes sectors such as retail, hospitality, food service, passenger transport and certain entertainment or personal services.
• Business households and individuals: Those with annual revenue above VND 1 billion, or selling assets for which ownership or usage rights must be registered, must use a coded electronic invoice or a qualifying connected cash-register invoice.

A taxpayer already registered for an applicable coded or non-coded electronic-invoice route may not be required to register separately for the cash-register route. Exact registration and applicability should nevertheless be confirmed for each taxpayer with the Vietnamese tax authority.

Exports and Scenario-Specific Treatment

For exports of goods or services, including processing activities, the decree permits an electronic commercial invoice, an electronic VAT invoice or an electronic sales invoice, depending on the transaction. It also contains specific treatments for areas such as entrusted imports and exports, goods movements, dependent branches, agency arrangements and mobile sales. These scenarios should not inherit a generic domestic billing profile without a local tax review.

Invoice timing is addressed separately in Article 9 of the decree. SAP design should therefore map the legally relevant billing event and invoice date for each scenario instead of hard-coding one timing rule across goods, services, exports and consumer transactions.

What This Means for an SAP Environment

• Organizational scope: Map Vietnam legal entities, company codes, branches, tax registrations and sales locations to the correct taxpayer and invoice route.
• Scenario classification: Separate domestic sales, exports, consumer sales, returns, corrections, branch movements and other special processes before designing output.
• Source data: Confirm that SD and FI processes can provide the required seller, buyer, tax, line-item, amount and transaction data for the relevant invoice type.
• Routing and integration: Determine whether the scenario requires a tax-authority code, non-coded transmission, a connected POS flow or an export invoice route. The detailed provider and interface design must be validated against current local technical specifications.
• Status and exception handling: Store authority or provider responses and give finance teams a controlled process for validation errors, rejected submissions, changes and reprocessing.
• Retention and retrieval: Preserve the electronic document, relevant identifiers, processing evidence and a link to the originating SAP transaction in a retrievable audit trail.

A Practical SAP Workflow

1. Determine the taxpayer, branch, business activity and invoice scenario.
2. Select the legally applicable invoice route and timing rule.
3. Extract and validate the required billing, tax and master-data fields from SAP or the relevant POS system.
4. Generate the correct electronic-invoice payload and transmit it through the approved local route.
5. Capture the tax-authority code or processing status where applicable and make errors visible to the responsible finance team.
6. Deliver the invoice to the buyer, retain the electronic record and reconcile the final status with the SAP source document.

SAP Readiness Checklist

• Inventory all Vietnam company codes, branches, billing systems and POS systems.
• Classify coded, non-coded, cash-register and export invoice scenarios.
• Validate invoice timing by transaction type under the current decree.
• Check customer, branch, tax and line-item master data for completeness.
• Confirm the current Vietnamese technical specification and provider interface before development.
• Define ownership for errors, corrections, monitoring and reconciliation.
• Test both successful and failed responses and preserve the resulting audit evidence.

How S4FN Can Help

S4FN can review Vietnam invoice scenarios, SAP source-data readiness, routing decisions, validation requirements, exception handling and integration prerequisites. The technical design should be finalized only after the taxpayer’s legal scope and the current Vietnamese authority or provider specifications have been confirmed.

Official Sources and Verification

• Government of Vietnam — Decree 254/2026/NĐ-CP, official document page
• Government information portal — electronic-invoice users under Article 6

Content verified: 10 July 2026. This page provides general implementation information and is not legal or tax advice. Confirm the official Vietnamese text, current Ministry of Finance and tax-authority guidance, taxpayer registration status and applicable technical specifications before implementation.

Verified on: 10 July 2026. Confirm the current legal scope, authority technical package and SAP-supported scenario before implementation.