A Belgian company can receive a Peppol invoice and still book it by hand. The file arrives with the supplier, the lines and the tax already structured. Someone opens a viewer, pastes the lines into a sheet, asks a manager by email, and the external accountant keys the entry again. Peppol invoice automation Belgium is that later work: intake, coding, approval and a booking the accounts agree with. This is an operating guide for finance leads in Belgium, not a tax opinion on one company.
What the 2026 mandate already requires
From 1 January 2026, structured electronic invoicing is compulsory for nearly all transactions between Belgian enterprises liable to VAT. Supplies to private individuals are outside it. Invoicing to public authorities is a separate regime. An in-scope invoice drawn up, issued or sent from that date must be structured, whether the supply itself came before or after 1 January. The note on the start date and the B2B FAQ are the references.
In principle the invoice uses Peppol BIS and travels on the Peppol network, so the company needs connected software to send, receive and process it. Another format is allowed only if both parties agree and it still meets the European standard. A customer cannot force its own portal without an explicit agreement. A PDF sent alongside does not replace the structured invoice. The electronic invoicing FAQ and the B2B FAQ set this out.
FPS Finance tolerated the first three months of 2026 for offences specific to the new duty, and only where the enterprise could show timely, reasonable steps. It said this was not a general postponement. A narrower window for self-billing, where the software could not yet send or receive those invoices and the provider was still building them, ran to 30 June 2026. Both windows are closed. The tolerance notice and B2B FAQ question 23 record the conditions.
Lacking the technical means to issue and receive a structured electronic invoice draws a fine of €1,500, then €3,000, then €5,000. A later breach counts only if the administration establishes it at least three months after the previous breach that led to a fine. Fines for a missing, late or incomplete invoice remain. Deducting VAT on an in-scope purchase generally requires the structured invoice, with a narrow exception where the material conditions are met. A buyer who cannot receive it may still face that fine. The sanctions FAQ states the amounts.
What the 2028 draft would add
On 27 October 2026 the government sent Parliament a draft law for near-real-time VAT e-reporting from 1 January 2028. EY Belgium's alert of 5 November 2026 summarises it. The text is not in force. A royal decree would still set the working deadline, the exact data and how the message is sent.
For taxpayers inside the new duty, the annual customer listing would become a report of each transaction. The periodic VAT return would stay. Supplier and customer would generally each send the mandatory data from the structured invoice, or from an equivalent structured document. The draft caps the period at five calendar days, except in force majeure the King designates, and EY says not to treat five days as the deadline in every case. Transmission would use Peppol. The administration does not plan a separate API.
Reporting will often happen before the review EY calls business validation, and a report does not mean the recipient accepts the invoice. A correction goes out on a corrective document. A gap between the two sides is not by itself an irregularity or an automatic VAT adjustment, though it can lead to further checks.
The scopes differ. A Belgian supplier may have to report a qualifying sale to a non-established customer using a Belgian VAT number, even where no structured invoice is required. Non-established taxpayers would not themselves face mandatory e-reporting. They would generally keep the annual listing through 30 June 2030 unless they opt in for that whole scope. The listing for 2027 would still be due by 31 March 2028. An invoice of €250 or less would still be reported.
Why is a compliant inbox still manual?
The 2026 rules require the means to issue and receive a structured invoice. They do not pick a cost centre, accept a price or post the entry the accountant uses. Many Belgian SMEs now have Peppol in the tool their fiduciary chose. The owner in Brussels still approves a variance by email, and the bookkeeper still waits for a PDF because the analytical accounts live elsewhere. Line text arrives in French, Dutch or both, and a supplier code does not turn that sentence into the buyer's chart of accounts.
If the 2028 draft passes in this form, the received file and the approved booking are different states on purpose. The administration may already hold the data before the budget owner has agreed the line. Storing the XML is a compliant pipe and an undocumented decision.
The finance invoice automation case follows the same shape from email attachments and scanned PDFs: read the page, match the order, and hold a mismatch for a person. A Peppol invoice already carries the identity, the lines, the tax and the totals. Coding, the exception and the booking remain. Raising an invoice from a field job is a different flow, described in AI for field service from booking to invoice.
From Peppol receipt to an approved booking
This path is an illustration for a fictional Brussels facilities company, not a client result. A Belgian supplier sends a Peppol invoice with a buyer reference, a French line and an amount above the monthly contract.
- Intake. The access point writes one record: VAT number, invoice number, date, currency, lines, tax, amount, buyer reference and the Peppol document id. A repeat updates that record.
- Checks. Rules, not a model, test a known supplier, a new invoice number, totals that agree and a buyer reference on an open order or contract. A missing required reference stops the flow.
- Wrong recipient. A person rejects an invoice that is not for this company. The official FAQ allows a Peppol Invoice Response with status RE where that function exists. The model does not send it.
- Coding. A rule proposes the account and the Brussels cost centre when a person has already approved that pattern for this supplier and contract. The French line stays visible. An AI suggestion for a new line must show the invoices it used, and a person confirms the first use.
- Exception. Past the written tolerance, the rule stops. The model may compare the line with the contract and the last invoice. The owner approves, asks for a credit note or rejects the difference.
- Booking. Only the approved decision is written once, with the Peppol document id, so a retry cannot double the entry. The accountant sees that booking and the structured invoice. Payment stays separate. A report is not an instruction to pay.
Keep received, decided and booked as three states. A rejection still depends on the supplier's corrective document.
Where a person still decides
Rules clear the repeats. A person stays accountable for a new supplier, changed identity data, a missing or mismatched order, an amount outside the written tolerance, and an unclear VAT category, including reverse charge or mixed use. Anything above the company's own threshold waits, even when the match is clean. Self-billing still needs a prior agreement and an acceptance step by the supplier. Do not let a model accept it because the file parsed.
AI can read a French or Dutch line, propose a coding and draft the approver's note. It should not post, change a supplier record, release a payment or tell the administration the invoice is accepted. Low confidence, a new pattern and any clash with the contract go to a named owner, with a time limit so the queue does not sit over a weekend.
Measure the flow before you widen it
Count one supplier group against its own baseline before you extend the rules:
- hours from Peppol receipt to an approved booking, as a median and as a slow tail;
- the share of in-scope invoices posted without retyping the structured fields;
- the share of proposed codings kept unchanged, for known patterns and for new ones;
- exceptions by cause: unknown supplier, missing reference, price or quantity, tax category, duplicate;
- invoices still waiting past the approval time the company set;
- duplicate bookings, and corrections after the entry was posted.
Do not publish a saving from a handful of invoices, or treat a clean test file as the live exception rate. If the draft proceeds, check that reportable data matches the received file and that a correction reaches both the ledger and the report.
Book an invoice-flow audit
Start with a map, not a new inbox. An invoice-flow audit follows one supplier family from Peppol receipt to the booking: where the file lands, who codes it, which variances stop, who approves, and how the entry reaches the package and the external accountant. Intyb's operational workflow work with Belgian companies starts there. Book an invoice-flow audit and bring the access point, the approval rules and the accounting package you already use.
Key takeaways
- A person still codes, approves and books the structured invoice.
- The October 2026 draft is not law, and a report is not acceptance.
- Measure one supplier group before widening the rules.
