Invoice numbering rules in Belgium

Belgian continuous invoice numbering, separate credit-note sequences, Peppol immutability after send, and the gaps that break auditors.

Updated

  • Belgium

Numbers are audit trail, not decoration

Belgian VAT practice expects unique, continuous invoice numbers within a defined series. The number identifies the document for the buyer, your ledger, and FPS Finance. On Peppol the same ID travels in structured form and is matched automatically. Gaps, reuse, and silent renumbering start audits and AP disputes.

For document roles, see Invoice, credit note, and quote. For field completeness, see Mandatory legal mentions.

Continuous invoice sequences

Use one clear scheme per issuing entity (and per series if you run several justified books). Within a series:

RuleGood practiceBad practice
UniquenessOne number, one documentReusing a voided number
ContinuityNext = previous + 1Skipping “to look tidy”
ChronologyIssue order follows the sequenceBackdating into an old gap
Entity scopeSeparate counters per KBO companyShared counter across subsidiaries

Typical shapes: 2026/0042, F2026-0042. Prefixes are fine if the sequence stays continuous. Quotes must never consume invoice numbers; keep a commercial series such as Q-2026-0042 (Quote to invoice).

If you void a draft before legal issue, do not leave a hole in an issued series: allocate the number only at issue, or document the void as your accountant accepts.

Credit notes: own sequence, clear reference

Credit notes need their own continuous sequence (for example CN-2026-0017). They must not take the next invoice number.

DocumentNumberingMust reference
InvoiceInvoice seriesSupply / commercial trail as needed
Credit noteCredit-note seriesOriginal invoice number (and date where required)
QuoteQuote seriesNever Peppol; never the invoice counter

On Peppol, send a structured CreditNote with a billing reference to the invoice you correct. Partial credits still get a new credit-note number.

Continuous numbering

A gap-free sequence of unique document IDs within a series so each issued invoice or credit note can be traced without unexplained skips or duplicates.

Peppol immutability after send

Once a structured invoice is delivered on Peppol, treat number, parties, lines, and totals as frozen.

TemptationWhy it breaksCorrect move
Fix a typo and resend same IDTwo versions of one numberCredit note, then new invoice if needed
Delete and re-issue with a new numberBuyer still holds the first Peppol documentCredit the first; issue the replacement
Renumber year-end “for cleanliness”Sequence history destroyedLeave issued numbers; fix the process

Network rejection before successful delivery differs from post-delivery correction. If nothing was accepted as the invoice of record, reissue the draft. If the buyer received it, correct with a credit note (Fix a rejected Peppol invoice).

What breaks auditors

  1. Unexplained gaps in an issued series without void documentation
  2. Duplicate numbers across PDF and Peppol or across entities
  3. Invoice numbers on quotes, or credit notes mixed into the invoice counter
  4. Peppol vs PDF mismatch after editing only one channel
  5. Missing credit-note link back to the original invoice
  6. Shared numbering across several KBO entities in a group

Keep issue logs, Peppol delivery proofs, and credit-note references with the archive. Under the Belgian e-invoicing obligation, the structured trail is what counterparties and controls rely on.

Invoice numbering rules in Belgium · OrdoGrid