Can You Void or Delete an Invoice in Belgium? A Practical 2026 Guide

If your team creates an invoice by mistake, the first instinct is often: can we just delete it?
In Belgium, that answer depends on a key distinction: draft invoice vs finalized/numbered invoice.

The short version: once an invoice is finalized and part of your legal/accounting trail, the safest approach is usually not deletion, but voiding and/or issuing a credit note with clear references.

This guide explains the practical workflow finance teams can apply in 2026, including Stripe-specific operations.

This article is informational and operational in nature. It is not legal advice.

Quick answer

For most Belgian businesses:

• Draft, unnumbered invoice: deleting is usually acceptable.
• Finalized or numbered invoice: avoid deleting; preserve the record and correct via void and/or credit note.
• If VAT was impacted: correction should follow a traceable document chain and VAT return correction process.

Why this matters in Belgium

Belgian invoicing and VAT compliance are built around traceability. In practice, auditors and tax authorities expect to see:

• coherent sequential numbering,
• complete journal evidence,
• records retained for the required retention period,
• integrity and readability of invoice documents over time.

A hard delete of a finalized invoice can create unexplained sequence gaps and weaken the audit trail. Even if the commercial transaction did not proceed, the document history still needs to be explainable.

The decision framework: delete vs void vs credit note

Use this practical rule set.

1) Draft invoice (not finalized, no legal number assigned)

If the invoice is still a draft and has not been used in accounting/VAT workflows:

• delete it,
• ensure no booking was posted,
• keep an internal log entry if your policy requires it.

This is the lowest-risk scenario.

2) Finalized/numbered invoice, not sent to customer

If the invoice already has a number or appears in your invoicing sequence:

• do not hard-delete,
• mark as void/cancelled in your billing platform,
• keep a reason in your internal notes,
• if it hit accounting, post reversing entries.

Even if the customer never received it, your internal trail may already treat it as an issued accounting document.

3) Finalized/numbered invoice, sent or made available

If the invoice reached the customer (email, portal, Peppol, etc.):

• preserve the original,
• issue a credit note that explicitly references the original invoice,
• issue a corrected replacement invoice if the transaction still needs billing.

This gives you a complete and auditable chain: original -> correction -> replacement.

Stripe workflow that aligns with Belgian expectations

Stripe’s lifecycle makes this practical if your team uses it consistently.

Draft state

• Delete draft invoice.
• No accounting or VAT effect should exist.

Finalized/open state

• Prefer void over delete to preserve traceability.
• If amounts must be corrected formally, issue a credit note.
• Never renumber old invoices to “fill a hole”.

Team policy to reduce risk

• Assign invoice numbers as late as possible (finalization point).
• Limit who can finalize invoices.
• Reconcile invoice number sequences monthly.
• Require reason codes for voids and credits.

Accounting treatment: reverse, do not erase

If an erroneous invoice was posted, use reversible entries tied to supporting documents.

Typical pattern (illustrative values):

(1) Original invoice
Dr Accounts Receivable.................... 121.00
   Cr Revenue............................. 100.00
   Cr VAT Payable.........................  21.00

(2) Full credit / reversal
Dr Revenue (or Sales Returns)............. 100.00
Dr VAT Payable............................  21.00
   Cr Accounts Receivable................. 121.00

In your journal memo/reference fields, include both document IDs, for example:

• INV-2026-000456 corrected by CN-2026-000123

That simple cross-reference is valuable during audits.

VAT return implications

Invoice mistakes can create VAT consequences depending on timing and issuance status. Operationally:

• If the mistake is caught before filing, ensure the period reflects the corrected chain.
• If already filed, correct according to the Belgian VAT return correction path (Intervat process), supported by the corrective document.
• Treat invoice-level corrections as document-led corrections, not just spreadsheet adjustments.

The principle is consistency: your VAT return, invoice register, and general ledger should tell the same story.

What a compliant correction chain looks like

For an erroneous finalized invoice, this is usually the strongest pattern:

1. Original invoice exists with unique number.
2. Invoice is voided/cancelled (if platform supports explicit status).
3. Credit note references original invoice number and date.
4. Replacement invoice (if needed) gets a new number.
5. Accounting entries mirror those documents.
6. VAT reporting mirrors those documents.
7. All records are archived for retention and auditability.

Option comparison

Option	Compliance risk in Belgium	When to use
Delete draft	Low	Draft only, not finalized, not posted
Void finalized invoice	Low to moderate	Finalized by mistake, preserve audit trail
Issue credit note	Low	Finalized invoice needs formal correction
Renumber past invoices	High	Avoid
Leave numbering gaps unexplained	Moderate to high	Avoid

Credit note template (practical starting point)

CREDIT NOTE
Credit Note No.: CN-2026-000123
Issue date: 2026-03-02

Supplier: [Legal entity], [Address], VAT BE[...]
Customer: [Customer legal name], [Address], VAT [...]

Reference:
This credit note modifies and cancels Invoice INV-2026-000456 dated 2026-02-28.
Reason: Invoice issued in error.

Tax base: -[amount]
VAT rate: [e.g. 21%]
VAT amount: -[amount]
Total incl. VAT: -[amount]

Adjust language, fields, and bilingual formatting to your legal/document standards.

Internal control checklist for finance teams

Use this checklist in your monthly close.

• Identify whether erroneous invoices were draft or finalized.
• Confirm every missing number has a documented status (void/cancelled/credited).
• Ensure every correction document references the original invoice clearly.
• Verify accounting entries reference document IDs.
• Verify VAT return treatment matches correction documents.
• Confirm retention and archive integrity rules are met.

Common failure modes to avoid

1. Deleting finalized invoices directly in tooling and losing traceability.
2. Posting manual GL reversals without issuing correction documents where needed.
3. Fixing VAT return totals without matching invoice-level evidence.
4. Renumbering invoices retroactively to hide sequence gaps.
5. No owner for invoice sequence controls between finance and ops.

2026 note: structured B2B e-invoicing in Belgium

From 2026 onward, Belgian B2B environments increasingly require structured e-invoicing workflows (including Peppol contexts). That makes document integrity and correction traceability even more central.

If your billing stack uses multiple systems, make sure number assignment and correction authority are clearly owned in one source-of-truth process.

Final takeaway

For Belgian operations, the safest policy is straightforward:

• Delete only true drafts.
• Void or credit finalized invoices.
• Keep the chain explicit from invoice to correction to reporting.

If your team follows that policy consistently, invoice mistakes become routine operational events instead of audit-risk events.