Sending an electronic invoice is only one part of the invoicing process. What happens when the amount is incorrect, a customer disputes a charge, or an invoice reaches the wrong recipient? For businesses operating in Belgium, correcting these mistakes now requires just as much attention as issuing the original invoice.
Since January 1, 2026, Belgium has required structured e-invoicing for most domestic B2B transactions between VAT-liable businesses. While much of the conversation has focused on sending invoices through the Peppol network, the mandate also affects the documents businesses use to correct them.
Credit notes, debit notes, and other corrective documents play an important role in this process. When a structured electronic invoice needs to be amended, businesses must use the appropriate format and clearly link the correction to the original transaction. For finance teams, this means compliance doesn’t end when an invoice is delivered. It also covers how errors are identified, corrections are communicated, and financial records are kept consistent across accounting systems and VAT reporting.
How Are Credit Notes Handled Under Belgium E-Invoicing?
Under Belgium's e-invoicing requirements, credit notes are more than administrative documents used to adjust an outstanding balance. They form part of the structured electronic invoicing process and must be handled accordingly.
Belgium's Federal Public Service Finance has clarified that documents modifying an original structured electronic invoice and referring to it specifically and unambiguously are also treated as structured electronic invoices. This means that credit notes and debit notes correcting those invoices must follow the same structured format and be exchanged through Peppol.
Consider a supplier that issues an invoice for €5,000 but later discovers that the customer was overcharged by €500. Rather than modifying the original invoice in its accounting system and emailing an updated PDF, the supplier should issue an appropriate structured credit note referencing the original invoice. This creates a clear record of the original transaction and the subsequent adjustment, allowing both businesses to maintain consistent financial information.
A credit note may be necessary when goods are returned, services are partially canceled, pricing is adjusted, or an invoice needs to be reversed. Depending on the circumstances, a debit note or another appropriate corrective document may be used to record an additional amount. The important principle is that a correction must remain traceable to the invoice it changes. This supports accurate accounting, reduces confusion between trading partners, and helps preserve the documentation needed for VAT compliance.
When Does a Corrective Document Need to Be Sent Through Peppol?
One of the most important distinctions in Belgium's e-invoicing rules is the relationship between the original invoice and its correction.
If an original invoice was issued as a structured electronic invoice, a document that modifies it and specifically references it must also be issued in the same structured format. For transactions subject to Belgium's Peppol-based requirements, this means the corrective document must follow the applicable electronic exchange process.
However, not every credit note issued in 2026 automatically falls under the same requirement. Belgium's official guidance addresses a particularly relevant example: a credit note issued in 2026 that relates to an invoice originally issued in 2025.
If the original invoice was a PDF rather than a structured electronic invoice, the new requirement does not automatically force the credit note into a structured format solely because it is issued in 2026. The format of the original invoice matters. This difference is extremely important for businesses managing transactions that cross accounting periods or involve older invoices issued before Belgium's mandate took effect.
For finance teams, the key questions are whether the original transaction falls within the e-invoicing requirements, how the original invoice was issued, and whether the new document modifies that invoice. By checking these details before creating a correction, businesses can avoid unnecessary rework and maintain a clearer audit trail.
How Should Businesses Correct an Invoice Sent to the Wrong Recipient?
Sending an invoice to the wrong customer is one of the more complicated mistakes businesses can encounter. Unlike a simple pricing error, the issue affects the identity of the parties involved in the transaction. Belgium's tax authorities have provided specific guidance for both the sender and the unintended recipient.
If a business receives an invoice for goods or services it never purchased, the invoice should be rejected. The unintended recipient should not claim a VAT deduction based on that invoice or record it as a legitimate purchase in its accounts.
Where the appropriate functionality is available, the recipient can communicate the rejection through a Peppol Invoice Response using the status code RE, indicating that the invoice has been rejected.
For the supplier, the process requires additional attention. Where VAT is chargeable, Belgium's guidance explains that an invoice sent to the wrong recipient must still be accounted for in the outgoing invoice records and reflected in the relevant VAT return. The incorrectly invoiced amounts must then be addressed through a corrective document, generally a credit note.
The supplier can subsequently issue a correctly addressed invoice to the intended customer. This process helps preserve a traceable record of what was originally issued, how the mistake was corrected, and which customer ultimately received the valid invoice.
For businesses processing large numbers of transactions, accurate customer identifiers and recipient validation are particularly important. Confirming these details before sending an invoice can reduce the risk of corrections that affect both accounting records and VAT reporting.
How Can Finance Teams Handle Rejected E-Invoices in Belgium?
Not every rejected invoice requires the same corrective action. An invoice might fail technical validation before reaching the recipient, or it might be successfully delivered and later disputed by the customer. Understanding the difference is absolutely essential for maintaining accurate records.
A technical rejection may occur because the invoice contains invalid structured data, missing mandatory information, or formatting errors that prevent it from being processed. In these circumstances, the sending system may need to correct the underlying data and submit a valid invoice.
A business rejection is different. The invoice may have reached the customer's system successfully, but the customer identifies a problem with the transaction, such as an incorrect amount, missing required information, or a charge that does not correspond to an agreed purchase.
In these situations, finance teams should establish a consistent process for investigating and resolving the issue.
- Identify the reason for rejection: Determine whether the invoice failed technical validation or was rejected by the customer after delivery.
- Review the original transaction: Check customer information, invoice references, VAT details, purchase orders, and any supporting documentation.
- Determine the appropriate correction: Depending on the circumstances, the business may need to resubmit a technically invalid invoice, issue a structured credit note, or provide another legally appropriate correction.
- Maintain a clear audit trail: Preserve the original invoice, relevant transmission or response information, and any subsequent corrective documents.
- Reconcile the financial records: Ensure that accounts receivable, accounts payable, and VAT records reflect the final transaction accurately.
It is also important to distinguish a Peppol transport acknowledgment from a customer's business acceptance of an invoice. Successful delivery does not necessarily mean that the customer agrees with the invoice's contents.
By treating invoice rejection as a defined financial workflow rather than an isolated technical problem, businesses can reduce the risk of duplicate invoices, unresolved balances, and inconsistent records.
How Should ERP Systems Track Invoice Corrections and Credit Notes?
For businesses processing hundreds or thousands of invoices, manually tracking corrections can quickly become difficult. An invoice might be issued in one accounting period, disputed in another, and corrected after the original transaction has already been included in financial reporting.
This makes ERP integration particularly important under Belgium's e-invoicing requirements. When an invoice is corrected, the original document should remain identifiable in the financial system. The corrective document should contain the appropriate references so that the relationship between the two transactions can be understood and reconciled.
For example, if a supplier issues an invoice for €10,000 and later provides a €2,000 credit note, the ERP system should preserve both documents and reflect the resulting financial adjustment. Simply replacing the original invoice amount with €8,000 could obscure the history of the transaction.
Businesses should therefore consider several capabilities when designing their invoice correction workflows:
- Document referencing: Link credit notes and other corrective documents to the original invoice using the relevant invoice identifiers.
- Status tracking: Distinguish invoices that have been created, transmitted, rejected, disputed, corrected, or otherwise resolved.
- VAT consistency: Ensure that applicable corrections are reflected in the appropriate VAT records and reporting periods.
- Duplicate prevention: Use invoice identifiers and validation controls to reduce the risk of processing the same invoice or correction more than once.
- System reconciliation: Keep invoice and correction information consistent between procurement, accounts payable, accounts receivable, and ERP systems.
- Auditability: Retain the original documents, corrective records, and relevant processing history to support internal reviews and compliance requirements.
These capabilities are especially valuable for multinational enterprises managing Belgian transactions alongside other national e-invoicing requirements. A centralized approach to document exchange and financial integration can help organizations apply consistent controls while accommodating the specific requirements of each market.
Manage Belgium E-Invoicing Corrections With Storecove
Belgium's e-invoicing mandate has made structured invoice exchange an essential part of financial operations for businesses within its scope. However, successful implementation involves more than sending compliant invoices. Organizations must also consider what happens when transactions need to be corrected, disputed, or reversed. Credit notes, invoice references, recipient information, and ERP records all play an important role in maintaining accurate financial data.
At Storecove, we help businesses simplify electronic invoicing through API-based connectivity to supported networks and services, including Peppol.
For enterprises and software providers managing high transaction volumes, integrating electronic document exchange with existing financial systems can reduce manual intervention and support more consistent invoicing processes. By building invoice correction workflows around structured documents, accurate references, and appropriate validation, businesses can improve their ability to manage exceptions without losing visibility into the original transaction.
Belgium's e-invoicing requirements demonstrate why the full invoice lifecycle matters. Sending an invoice correctly is important, but knowing how to handle it when something goes wrong is just as essential.
Looking to simplify Belgium e-invoicing and Peppol connectivity?
Read More
Lauren Kelly
Lauren Kelly
Lauren Kelly
Comments