Vietnam Cash Register E-Invoice Requirements

Vietnam cash register e-invoice requirements now matter to any business in Vietnam that sells directly to consumers through high-volume retail-style workflows. From June 1, 2025, Decree 70/2025/ND-CP brought sharper operational focus to e-invoices generated from cash registers connected to the tax authority. The practical headline is straightforward: certain business households, business individuals, and consumer-facing businesses in sectors such as retail, food and beverage, restaurants, hotels, passenger transport, and personal services are expected to use this model. In the same discussion, advisers commonly point to the VND 1 billion annual revenue threshold for business households and business individuals. This invoice type also does not require a digital signature.

That short answer matters because the question behind most searches is not purely legal. If you run stores, restaurants, hotels, or passenger services, the real issue is whether your point-of-sale flow now has to create invoice records in a way that is visible to the tax authority at the point of transaction, not later as a back-office clean-up exercise. A Vietnam POS e-invoice requirements review therefore affects more than invoice wording. It reaches into issuance timing, cashier workflow, transaction capture, exception handling, and the records finance teams rely on after the sale is complete.

This is why the topic should be treated as an operational compliance workflow, not just a decree summary. An e-invoice generated from cash register equipment sits inside the broader invoice regime, but it is designed for a specific kind of selling environment: fast, repeated, direct-to-consumer transactions where the document trail has to keep pace with front-line sales activity. That makes it especially relevant for businesses with many low-value transactions and a constant need to keep sales evidence, accounting support, and tax-facing records aligned.

The rest of this guide stays current-law first. It starts by mapping who is in scope and how the threshold is usually interpreted, then separates invoice-content and digital-signature rules from the back-office records teams still need for bookkeeping and reconciliation. It closes by showing how to monitor the February 23, 2026 proposal without treating it as current law.

Which Businesses Are in Scope and How the VND 1 Billion Threshold Works

The first scoping question is not "Do we use a cash register?" It is "Are we part of the consumer-facing sales activity this rule is aimed at?" Current guidance around Decree 70 usually centers on direct sale to consumers in sectors such as retail, food and beverage, restaurants, hotels, passenger transport, and personal services. Those are the operating environments where cash-register-generated e-invoices are most often discussed because the sales pattern is frequent, front-line, and often low in individual transaction value.

For business households and business individuals, the VND 1 billion annual revenue threshold is commonly presented as a key practical trigger. That threshold matters, but it should not be read in isolation. The safer interpretation is to read the threshold together with the seller's status and the nature of the business activity. In other words, the threshold is part of the scoping analysis, not a substitute for it.

This working table is a useful way to organize the issue internally:

Business profile	Why it is commonly treated as in scope	Threshold takeaway
Business household or business individual selling direct to consumers in listed sectors	This is the core fact pattern discussed in Decree 70 explainers and implementation commentary	The VND 1 billion annual revenue threshold is often the first number to test
Retail, restaurant, hotel, transport, or personal-service operation with high-volume B2C sales	The rule is designed around immediate consumer transaction documentation, not occasional invoice issuance	Do not assume a threshold reference removes the need for review
Mixed-model seller serving both consumers and business customers	Different transaction flows may need different invoice handling rules	Review the consumer-facing branch separately from ordinary B2B invoicing
Business using POS tools outside the listed sectors or in edge cases	The technology alone does not decide scope	Confirm how current guidance applies before treating the cash-register model as optional

The key discipline is to classify the business model before changing procedures. A Vietnam Decree 70 cash register invoice workflow is aimed at a specific transaction pattern, not every sale that happens to pass through a terminal. If your operation includes both counter sales and ordinary business invoicing, it is worth separating those channels clearly so staff do not apply consumer-transaction rules to every invoice by default.

For finance teams, that means the scoping exercise should end with a decision tree, not just a legal note. Identify whether the seller is a business household or business individual, confirm whether the activity falls into the listed consumer-facing sectors, test how the VND 1 billion threshold is relevant, and then document which sales channels should follow the cash-register e-invoice path.

What a Cash-Register E-Invoice Must Include and Why No Digital Signature Is Required

Once scope is clear, the next question is mechanical: what has to appear on the invoice, and what does the digital-signature exemption actually change? A Vietnam cash register e-invoice still has to identify the seller, the transaction, the goods or services sold, the amounts involved, and the tax treatment well enough for the document to function as a real invoice rather than a casual till slip. In practice, teams should review the current field set against the decree and implementation guidance, including the framework discussed alongside Circular 32/2025/TT-BTC, before they finalize templates or system settings.

From an operating perspective, the content review usually comes down to five checks:

• Seller identification and tax details are present and consistent with the registered business.
• The transaction can be traced by date, time, and reference data generated through the cash-register flow.
• The goods or services sold are described clearly enough for later review.
• The monetary fields are complete, including totals and any tax amounts or tax treatment information that the workflow requires.
• The invoice carries the data needed for the buyer or reviewer to verify it through the tax authority environment where applicable.

The digital-signature point is important because many teams assume "electronic invoice" automatically means "digitally signed invoice." That is not how this branch works. According to Vietnam's decree text on cash-register e-invoices and digital signatures, e-invoices generated by cash registers that are connected to the tax authority do not require a digital signature, and buyers may still use them to support deductible expenses when the invoice information can be checked on the tax authority's electronic portal. For high-frequency consumer sales, that removes one step from issuance without turning the invoice into an informal record.

That distinction matters in practice. The exemption changes how the invoice is executed, but it does not remove the need for proper contents, reliable transmission, or later lookup. A finance team should therefore treat the digital signature exemption as a workflow feature, not a reduction in documentary discipline.

It also helps to separate two related questions. The first is whether the invoice itself contains the information required for compliant issuance. The second is whether the business retains enough supporting material for bookkeeping, tax review, refunds, corrections, and reconciliation later. The invoice answers the first question. Your internal record trail has to answer the second.

Cash-Register E-Invoices vs Standard Vietnam E-Invoice Workflows

Many teams misread this topic by treating cash-register e-invoices as the same workflow as an ordinary Vietnam e-invoice, just issued from different hardware. They sit inside the same national framework, but they are built for a different operating pattern. If you need the wider baseline first, our guide to Vietnam's wider Decree 123 and Decree 70 e-invoice framework explains how the broader regime fits together under Decree 123/2020/ND-CP and the 2025 amendment cycle.

For day-to-day operations, the comparison usually looks like this:

Question	Cash-register-generated e-invoice	Standard Vietnam e-invoice workflow
Typical sales pattern	High-volume, direct-to-consumer transactions	Broader B2B or non-counter invoice scenarios
Issuance rhythm	Closely tied to point-of-sale activity	Often tied to the ordinary invoicing step in the commercial process
Signature handling	No digital signature required for this invoice type	Signature expectations depend on the specific workflow and rule set in use
Operational focus	Immediate transaction capture, transmission, and lookup	Wider invoice classification, timing, and correction controls
Finance-team concern	Making sure front-line sales data stays usable for review and reconciliation	Making sure the right invoice type and timing logic were applied overall

A reader comparing the two should take away one core point: this is not just a naming issue. A Vietnam cash register vs standard e-invoice decision changes the control environment. Cash-register issuance is aimed at consumer-facing sales where the invoice process has to keep pace with front-line transactions. Standard e-invoicing analysis is broader and often starts with invoice classification, timing, and correction rules across different types of sellers and transactions.

That difference is exactly why businesses should not copy an existing B2B invoice procedure and assume it will cover a retail or hospitality counter flow. The accounting questions remain familiar, but the operational trigger is different. The cash-register model expects the issuance path, the transaction data, and the tax-authority connection to behave like part of the sale itself, not like a document that can be reconstructed later from summary reports alone.

---

What "Connected to the Tax Authority" Means in Daily Retail and Hospitality Operations

For most businesses, "connected to the tax authority" is the phrase that sounds technical but causes the most operational uncertainty. In practice, it means the cash-register workflow is not just producing a customer-facing sales record. It is part of a tax-facing issuance chain, so the business needs the transaction data, invoice creation step, and later lookup path to stay aligned from the moment of sale onward.

That does not mean every business has to solve the same implementation problem in the same way. What it does mean is that stores, restaurants, hotels, and passenger-service operators should think in terms of control points:

• when the invoice is created in relation to the sale
• how corrections, cancellations, or refunds are recorded
• what end-of-day reports support the issued invoices
• which records accounting keeps for audit trail and reconciliation
• how staff confirm that invoice data can still be retrieved and reviewed later

For finance teams, this is where the rule turns into daily work. A compliant front-line issuance flow still needs back-office evidence. Retain the invoice outputs themselves, the related POS or sales summaries, payment-settlement support, correction logs, and any archived exports used to reconcile totals into bookkeeping. That record set is what lets a reviewer trace the path from an individual consumer transaction to a day-end total and then into accounting records.

The comparison with other consumer-transaction systems is useful here. You can see some of the same workflow pressure in how Egypt's retail e-receipt regime handles POS-linked receipt compliance, in cash receipt rules in South Korea for consumer-facing transactions, and in Colombia's POS electronic receipt rules for deciding between a POS document and a full invoice. The legal systems are different, but the operational lesson is similar: once transaction reporting moves closer to the point of sale, finance teams need stronger retrieval, exception-handling, and reconciliation habits.

This is also the point where a downstream processing tool can help without pretending to be the issuance system. If your business exports invoice PDFs, image files, or archived transaction documents after issuance, AI invoice data extraction for high-volume retail records can help turn those records into structured Excel, CSV, or JSON files for bookkeeping and reconciliation. Invoice Data Extraction supports PDF, JPG, and PNG inputs, can handle large batches, and preserves source references for review. That is useful after compliant issuance has already happened. It is not a substitute for the Vietnam tax-authority connection itself.

How to Plan Around the February 23, 2026 Proposal Without Treating It as Current Law

A common planning mistake is to read proposal coverage as if it had already changed the live rule. The February 23, 2026 consolidated-invoice proposal should be treated as a development to monitor, not as a current-law rollback of the existing cash-register e-invoice requirement. If your business is already in scope today, the proposal is not a reason to delay compliance work that the current framework expects you to complete.

Why does the proposal still matter? Because it speaks to a real operational pressure point: businesses with very high volumes of low-value consumer transactions want to know whether some form of later consolidation might become available again for specific scenarios. That is a legitimate planning question. It is not the same as saying the current connected cash-register workflow has been suspended or replaced.

The safest approach is to separate current-law actions from proposal monitoring:

• Current law tells you how your business should issue invoices now.
• Proposal monitoring tells you what future flexibility might emerge, and what process changes you might want to model in advance.
• Internal project plans should show those as different workstreams so staff do not assume a proposal has already changed the live operating rule.

For a practical implementation checklist, confirm these points in order:

1. Decide whether the business falls into an in-scope sector and whether it sells directly to consumers.
2. Test how the VND 1 billion threshold is relevant for the seller's status rather than treating it as a universal shortcut.
3. Verify the invoice content requirements and the no-digital-signature rule for the live workflow.
4. Map how connected cash-register issuance fits into cashier procedures, exceptions, corrections, and end-of-day control routines.
5. Define which supporting records accounting must retain for bookkeeping, tax review, and reconciliation.
6. Track the February 23, 2026 proposal separately so management can plan for possible future changes without confusing them with the rule in force today.

That checklist keeps the article's core distinction intact: the live compliance burden is operational and immediate, while the proposal is something to watch carefully, not something to rely on yet.