Credit notes on Peppol — structured corrections

When an invoice needs to be undone or reduced

In Belgian B2B trade, a credit note is the formal way to reverse or reduce amounts on a previously issued invoice. Returns, pricing errors, partial cancellations, goodwill adjustments that affect VAT, and agreed rebates after invoicing all belong here — not in a revised PDF or a casual email.

Under the structured e-invoicing mandate, many of these corrections must travel as Peppol billing documents, not only as human-readable attachments. The commercial meaning of a credit note is unchanged from paper practice; what changes is that accounting software on both sides expects machine-readable data with strict validation rules.

If you are new to the distinction between quotes, invoices, and credit notes in Belgian practice, start with Invoice, credit note, and quote — Belgian practice.

BIS CreditNote: the Peppol billing document type

Peppol does not treat a credit note as a special case of email workflow. It defines a dedicated document type in the Peppol BIS Billing 3.0 family, conceptually aligned with EN 16931 and typically encoded as UBL CreditNote XML.

At a high level, a BIS CreditNote carries the same kind of structured payload as an invoice:

• Seller and buyer party identifiers (including Belgian enterprise numbers where required)
• Document number and issue date in a dedicated credit-note sequence
• Line items with quantities, amounts, and VAT categories
• Tax totals and document totals that must reconcile mathematically
• Payment and delivery references where applicable

The root element differs (CreditNote instead of Invoice), and the document type identifier on the Peppol network signals to receivers that this message reduces receivables rather than creating a new charge. Access Points route it through the same transport layer as invoices, but downstream ERP and AP automation apply credit logic: open item matching, VAT adjustment, and ledger posting.

Validation is as strict as for invoices. Missing mandatory fields, inconsistent VAT breakdowns, or totals that do not add up cause rejection before the counterparty's system ever books the correction. That strictness protects both parties from silent mismatches that used to surface only at year-end reconciliation.

Referencing the original invoice

A credit note is not a standalone discount voucher. Belgian VAT practice and Peppol BIS both expect a clear link to the invoice being corrected.

In UBL terms, this appears through billing references (BillingReference / InvoiceDocumentReference): the credit note points to the original invoice number and, where required, its issue date. Some scenarios allow multiple references or line-level links, but the principle is constant: auditors and software must know which supply is being adjusted.

Why this matters in structured e-invoicing:

Never "edit and resend" an invoice that already left your system on Peppol. The original structured invoice remains the legal and technical baseline; the credit note is the controlled amendment.

VAT adjustments in structured form

For VAT-liable businesses, a valid credit note reduces VAT in the same proportions as the original invoice, subject to the underlying supply rules. The structured file makes those adjustments explicit:

• Each line carries a VAT category code and rate consistent with the corrected supply
• TaxTotal and LegalMonetaryTotal reflect negative or reducing amounts as defined by the profile
• Intra-community, reverse charge, or exempt treatments must mirror the logic of the original transaction where applicable

Belgian tax administration expects coherent VAT reporting. When your customer receives a Peppol credit note, their system posts a VAT reduction that should align with your VAT declaration. Informal shortcuts break that symmetry.

Partial credits are common: one line returned, a percentage rebate on a project milestone, or a freight charge waived after dispatch. Structured lines make partial corrections precise. A lump-sum "€500 off" email gives the receiver no line-level VAT detail and forces manual intervention — exactly what the mandate aims to eliminate.

Why an informal email discount is not enough

It is tempting, after sending a Peppol invoice, to agree a discount by email and ask the customer to "pay less". Under structured B2B e-invoicing, that approach creates operational and compliance gaps:

1. No authoritative document — The Peppol invoice still shows the full amount in both parties' systems. Payment files, dunning, and credit limits remain wrong until someone manually overrides them.
2. VAT mismatch — If you reduce the commercial price but do not issue a credit note, your VAT declared on the original invoice may not match economic reality, and your customer's deductible VAT may be overstated unless they adjust manually with weak evidence.
3. No network delivery proof — Email agreements lack Peppol delivery status and structured archiving expected in audits.
4. Automation failure — Accounts payable tools ingest Peppol invoices automatically. They do not ingest informal mail as credit documents. Finance teams reintroduce manual work you adopted e-invoicing to remove.
5. Audit trail weakness — Continuous numbering and chronological sequences for invoices and credit notes are standard Belgian practice. An off-ledger discount bypasses those controls.

A PDF credit note attached to email is slightly better for human reading but still insufficient when the mandate requires structured exchange: the receiver's platform needs the XML CreditNote to book automatically.

A practical Peppol credit-note workflow

A robust process mirrors invoice issuance:

1. Identify the invoice to correct (Peppol ID and your internal number)
2. Issue a credit note in your billing tool with line-level detail and billing reference to the original invoice
3. Validate against EN 16931 / BIS rules before send
4. Transmit via your Peppol Access Point with the CreditNote document type identifier
5. Confirm network delivery status and retain the structured original
6. Match customer remittance against the reduced open balance

For full cancellations, a credit note covering the entire invoice amount is usual. For price corrections, issue the credit for the delta only, then invoice again if a new charge replaces it — do not mutate the sent invoice.

Separate numbering sequences for credit notes remain best practice in Belgium. Structured validation makes duplicate or out-of-sequence numbers easier for systems and reviewers to flag.

Credit notes and the wider e-invoicing stack

Credit notes sit on the same technical baseline as invoices: EN 16931 semantics, UBL syntax, Peppol BIS Billing profile, delivery through an Access Point. If invoices in your organisation already comply with the Belgian structured e-invoicing obligation (2026), credit notes should be enabled in the same platform — not handled as an offline exception.

Receivers must be able to process inbound CreditNote messages as reliably as invoices. That includes mapping references, posting negative amounts, and adjusting VAT boxes in their periodic returns.

BIS CreditNote

A Peppol billing document type, based on EN 16931 and usually UBL CreditNote XML, used to structurally reduce or cancel amounts on a previously issued invoice.