Vietnam E-Invoice Adjustment vs Replacement Guide

If you are deciding between an adjustment invoice and a replacement invoice in Vietnam, start with the error type. Under Vietnam's post-Decree 70 Article 19 rules, an issued e-invoice that is wrong only in the buyer's name or address is usually handled by notifying the buyer and the tax authority, not by issuing a new invoice. If the error affects the tax code, amounts, tax, goods or services, or other substantive invoice details, you move into a correction path that requires either an adjustment or a replacement. When the same incorrect information appears on multiple invoices issued in the same month to the same buyer, one correction document may cover all of them. For business buyers, the parties must prepare a written agreement before an adjustment or replacement. For individual buyers, the seller must notify the buyer or publish the notice on its website if the site is available.

That is the short answer to the Vietnam e-invoice adjustment vs replacement question. The harder part is turning that answer into a workflow your team can follow under time pressure, especially when billing, tax, and ERP teams all need the same correction file to make sense.

The fastest way to work through a Vietnam adjustment and replacement e-invoice guide is to sort every issued invoice error into three buckets:

• Notify only when the mistake is limited to the buyer's name or address and the tax code plus the transactional details remain correct.
• Adjust when the original invoice should remain part of the record but specific figures or details need to be corrected through a linked follow-on document.
• Replace when it is cleaner to supersede the incorrect invoice with a corrected invoice that still points back to the original.

This article is written as a finance-team decision guide, not a general Decree 70 summary. The goal is to help you classify a wrong issued invoice quickly, decide whether Vietnam e-invoice error correction should be handled through notice, adjustment, or replacement, and keep the resulting audit trail defensible for accounting and tax review.

---

What Decree 70 Changed in Article 19

The biggest reason this topic causes confusion is that many teams still think in terms of the older cancellation logic. Decree 70/2025/ND-CP changed that mindset. In practice, the post-Decree 70 reading of Article 19 in Decree 123/2020/ND-CP shifts the operator's question away from "Can I cancel this invoice?" and toward "Does this error only need notice, or does it require an adjusted or replacement invoice?"

That sounds like a small wording change, but it changes how finance teams build correction workflows. A broad regulatory summary may mention the amendment, yet still leave AP or AR teams without a usable decision path. Your process has to start with the status of the issued invoice, the nature of the error, and the documentary consequences of correcting it.

This is why the topic should be separated from the broader Vietnam e-invoicing framework and Decree 70 changes. The national regime explains who issues e-invoices and under what rules. A Vietnam Article 19 e-invoice correction workflow deals with a narrower operational problem: the invoice already exists, it is wrong, and you need the correct remedy without breaking the audit trail.

One practical summary from Acclime Vietnam's April 2025 Decree 70 update captures the operational shift well: Decree 70 removed the cancellation rule for incorrect e-invoices, allows one adjustment or replacement invoice to cover multiple incorrect invoices issued in the same month to the same buyer, and requires a written agreement before B2B adjustments or replacements. For finance teams, that means your correction model now revolves around classification, supporting documentation, and traceable links between the original invoice and the correcting document.

If you keep that shift in mind, the rest of the decision becomes much clearer. First determine whether the issue is trivial enough for notice only. If it is not, decide whether the original invoice should stay in place and be adjusted, or whether it should be superseded by a replacement.

---

When You Only Notify Instead of Issuing a New Invoice

The cleanest branch in the workflow is the notify-only case. If the issued invoice is wrong only in the buyer's name or address, while the buyer tax code and the commercial and tax substance of the invoice remain correct, the seller generally does not need to issue a new invoice. Instead, the seller notifies the buyer and the Vietnam tax authority.

That distinction matters because it prevents unnecessary reissuance. A team that treats every typo as a full correction event creates avoidable downstream work in ledgers, reconciliations, and document archives. The first question should therefore be: does this mistake change who was taxed, what was supplied, or how much was invoiced? If the answer is no, and the problem is limited to buyer name or address details, you are usually still in the notice branch rather than the reissue branch.

This is also the point where finance teams should classify the incorrect issued invoice carefully. A wrong buyer name looks minor, but a wrong buyer tax code does not belong in the same category. Likewise, a goods description error that changes the commercial meaning of the invoice is not just an administrative typo. Once the error affects tax identity, values, tax amounts, or the substance of the transaction, you have moved beyond a Vietnam buyer notice for invoice errors and into adjustment-or-replacement territory.

From a control perspective, the notice step should be documented, not treated as a casual email fix. Teams should preserve the buyer communication, the internal classification of the error, and any relevant notification form such as Form No. 04/SS-HDDT where the correction process requires a formal notice path. That way, if the file is reviewed later, you can show why no new invoice was issued and why the issue was treated as a limited-data correction rather than a substantive invoice rewrite.

---

When an Adjustment Invoice Is the Better Fix

An adjusted e-invoice is usually the better tool when the original invoice should remain part of the record, but one or more details need to be corrected through a linked follow-on document. In other words, you are not pretending the first invoice never existed. You are preserving it, then recording the correction against it in a traceable way.

That logic is especially useful when values need to move up or down. A Vietnam adjustment invoice for positive negative amounts should make the change explicit, not leave reviewers guessing whether the corrected figures replace the original values or represent only the delta. Finance teams often prefer adjustment where the audit question is "what changed?" rather than "what is the entirely restated invoice?"

In practice, the adjusted invoice should clearly identify the original incorrect invoice and state that it is an adjustment to that invoice, so the file makes sense on its own without extra explanation. This notation matters because the documentary chain has to be understandable to tax reviewers, auditors, and anyone reconciling the correction in an ERP or spreadsheet export. If your team cannot see the reference back to the original invoice immediately, the file will be harder to defend later.

Adjustment also fits well when the business wants to preserve the original commercial document sequence but fix amounts, tax elements, or other data points through a controlled follow-up entry. Where Article 19 permits value corrections, teams should be disciplined about how increases and decreases are shown. If a value rises, the adjustment should show the upward correction clearly. If a value falls, the adjustment should reflect the negative change clearly. Ambiguous wording creates avoidable confusion in later VAT reporting and ledger review.

This is also where the downstream declaration file matters. If the correction affects reportable values, your records may need to tie into supporting schedules such as Form No. 01/BK-DCTT. The exact filing consequences depend on the scenario, but operationally the point is straightforward: adjustment works best when you need a visible, linked correction that preserves the original invoice history and makes the numerical change easy to trace.

---

When a Replacement Invoice Is Better, Including Same-Month Batch Corrections

A replacement e-invoice is often the cleaner option when the original issued invoice should be superseded by a corrected version rather than adjusted through separate positive or negative changes. Operationally, replacement is useful when the team wants one corrected invoice record to stand in place of the wrong one, while still maintaining a reference back to the original.

That reference is not optional housekeeping. Vietnam replacement invoice notation needs to make the relationship to the incorrect invoice obvious and state that the new invoice replaces it. A reviewer should be able to identify which invoice is being replaced without reconstructing the story from email threads or internal notes. The replacement invoice therefore needs clear linkage to the original incorrect invoice so the documentary trail remains intact.

Replacement becomes especially powerful under the same-month rule. For a Vietnam same-month e-invoice correction, one replacement invoice may cover multiple incorrect invoices issued in the same month to the same buyer when the incorrect information is the same. This is useful when a recurring data issue, such as the same wrong tax detail or repeated product-field mistake, affected a batch of invoices before the error was discovered.

Even so, batching should be used with care. If the invoices have different error patterns, different commercial facts, or different correction logic, separate correction documents may be safer. The goal is not to compress paperwork at any cost. The goal is to create a file that clearly shows what was wrong, what replaced it, and why the grouped correction makes sense.

The simplest way to distinguish replacement from adjustment is this: replacement restates the corrected invoice record, while adjustment preserves the original and records the change against it. If your team needs a fully corrected substitute document, replacement is often the better fit. If your team needs to preserve the original and highlight the delta, adjustment is usually more natural.

---

Documentation, Declaration Timing, and a Clean Audit Trail

Once you know whether the invoice should be notified, adjusted, or replaced, the last job is to make the correction defensible. For B2B cases, that means preparing the required buyer written agreement before issuing an adjustment or replacement invoice. For B2C cases, it means notifying the buyer or publishing the notice on the seller's website if the website is available. Those steps are not side paperwork. They are part of the correction file itself.

Tax declaration timing also needs separate attention. The correction decision tells you which document to issue. It does not automatically answer when the seller and buyer should reflect the change in VAT reporting. If the error affects declared values, teams should map the declaration date to the specific Article 19 correction scenario they used, instead of assuming every correction follows the original invoice period. Preserve records showing how that conclusion moved into the tax file. That is where operational evidence, not just the invoice PDF, becomes important.

A defensible correction file usually contains four things: the original invoice reference, the notice or written agreement that supports the correction path, the adjustment or replacement invoice itself, and the downstream accounting record showing how the correction was reflected. If a correction touches amounts, tax, or timing, your ERP and VAT workpapers should tell the same story as the invoice trail.

This is also a good point to remind teams that correction logic is jurisdiction-specific. The mechanics discussed here differ from how VAT credit note corrections work under UK rules and from how Italy handles credit and debit note corrections in e-invoicing, even though all three topics deal with post-issuance invoice fixes. Borrowing the wrong country's pattern is a common source of avoidable compliance mistakes.

Before closing a Vietnam correction file, run a short checklist:

• Confirm whether the error qualified for notice only, adjustment, or replacement.
• Confirm the original invoice reference appears in the notice or correcting invoice.
• Confirm the buyer agreement or buyer notice requirement was satisfied for the correct buyer type.
• Confirm same-month batching was used only where the incorrect information was the same.
• Confirm any VAT declaration impact was reflected in the supporting records.

If your team can answer those five points clearly, the correction is much more likely to stand up in accounting review, tax review, and later audit work.