E-Invoicing Compliance for CFOs: Checklist, Dashboard KPIs and Mandate Deadlines
The Belgian mandate went live on 1 January 2026 and the tolerance period ended on 31 March 2026. The project phase is over. What finance owns now is a running process that can fail quietly, every day, in ways an annual audit will not catch. This guide covers the numbers to put on a compliance dashboard, what non-compliance actually costs, and which deadlines still sit ahead of you.

How we know this
e-invoice.be is a certified Peppol Access Point. The failure modes and the metrics below come from traffic we move on the network for Belgian companies, not from a survey. Where a number comes from a law or a regulator, we say which one.
In this article
1. What e-invoicing compliance actually means
Compliance is not one obligation. It is four, and companies usually pass the first and fail one of the others.
Issue. Sales invoices leave your system in a structured format that meets the legal standard. In Belgium that is Peppol BIS 3.0 UBL, built on the European standard EN 16931.
Transmit. The invoice travels over an accepted channel and reaches the buyer's Access Point. An invoice that was generated correctly but never delivered is not a compliant invoice. It is an unpaid one.
Receive and retain. You can accept structured invoices from every supplier, and you keep the original structured file. A PDF rendering of an e-invoice is not the invoice. The XML is.
Report. Belgium does not require transaction reporting yet. It will from January 2028. Design your data now for the version of the rules that arrives then.
The one distinction that matters
A PDF sent by email is not an e-invoice, even if it is digital, signed, and archived. An e-invoice carries the invoice data as fields a machine can read and validate before it is sent. That is the whole point: the check happens at issuance, not three weeks later in a dispute.
2. The Belgian compliance clock
Four dates matter for a Belgian company. Two are behind you.
| Date | What happened or happens | What finance has to do about it |
|---|---|---|
| 1 January 2026 | Structured B2B e-invoicing becomes mandatory between Belgian VAT-registered businesses, with Peppol as the default network. | Be able to issue and to accept Peppol invoices. Both directions, not just sending. |
| 31 March 2026 | The tolerance period ended. | No further grace on missing technical means. |
| 1 April 2026 | The progressive fine regime applies: €1,500, then €3,000, then €5,000. | Monitor continuously. A gap you find in month nine is already an exposure. |
| January 2028 | Near real-time e-reporting to the FPS Finance on a dual-sided model, running on a five-corner Peppol setup. It replaces the annual client listing. | Both you and your customer report the same transaction. Data quality stops being a private problem. |
The 2028 change is the one most Belgian finance teams have not budgeted for. Dual-sided reporting means the administration reconciles what you declared you sent against what your customer declared it received. Mismatches in VAT amounts, dates, or identifiers become visible automatically. The fix is not a 2027 project. It is clean master data and a low error rate now.
3. Penalties and the real financial exposure
The fine schedule since 1 April 2026
A non-proportional administrative fine applies when a business does not have the technical means to send and receive structured e-invoices. It rises with repetition: €1,500 for a first offence, €3,000 for a second, and €5,000 for further offences. A three-month window runs between offences before the next tier applies.
Separately, ordinary VAT fines under article 70 of the VAT Code still apply to invoice content problems such as missing mandatory fields or incorrect VAT treatment.
For most companies the fine is not the real number. Three other exposures are larger and they arrive sooner.
Your customer's VAT deduction. If the invoice you issued does not meet the formal requirements, the input VAT deduction on the buyer's side can be challenged. That is your customer's money, which makes it your commercial problem. Expect the invoice back.
Days sales outstanding. A rejected or undelivered invoice does not age as a dispute. It ages silently as an invoice nobody received. Track undelivered documents daily or they surface in the DSO report a month later.
Procurement gates. Larger buyers now screen suppliers on structured invoicing capability. Failing that check removes you from a vendor list before any fine is ever assessed.
4. What it costs, and what the 120% deduction is worth
Build the cost model on documents, not on users or seats. The unit that drives spend is a document that crosses the network, and both directions count. A company sending 250 and receiving 250 invoices per month handles 6,000 documents per year, not 3,000.
| Documents per year (sent + received) | At €0.25 (Pro) | At €0.18 (Enterprise) |
|---|---|---|
| 1,200 (about 100 per month) | €300 per year | €216 per year |
| 6,000 (about 500 per month) | €1,500 per year | €1,080 per year |
| 24,000 (about 2,000 per month) | €6,000 per year | €4,320 per year |
| 120,000 (about 10,000 per month) | €30,000 per year | €21,600 per year |
The account and the Peppol ID registration are free. There is no setup fee and no monthly minimum. Every invoice is billed per document, on sending and on receiving. Enterprise pricing applies at volume. See the full cost breakdown for Peppol e-invoicing.
The 120% deduction, calculated honestly
Belgium allows small companies an increased cost deduction of 120% on subscription costs for invoicing software that supports structured e-invoicing, and on related advice costs. It is often presented as a 20% discount. It is not.
It is an extra 20% of deduction. Spend €1,500 and you deduct €1,800. At the standard 25% corporate rate, that extra €300 of deduction is worth about €75 of tax. Roughly five cents on every euro spent, not twenty.
It applies to small companies only, judged on the usual size criteria (about €11.25 million turnover, €6 million balance sheet total, 50 employees on average, of which no more than one may be exceeded). It covers subscriptions and advice, not one-off software purchases, and it is a temporary measure. Confirm the current position with your accountant before you put it in a business case.
5. Your e-invoicing compliance dashboard: 12 metrics
Most compliance failures are not decisions. They are drift. A customer changes its Peppol registration, an ERP update rounds VAT differently, a new entity starts invoicing outside the flow. None of that shows up in a yearly review. It shows up in these twelve numbers, all of which can be pulled from an Access Point API and reported monthly.
| Metric | How to calculate it | Target |
|---|---|---|
| Customer reachability | Active Belgian B2B customers with a resolvable Peppol ID, divided by all active Belgian B2B customers. | 100% |
| Structured send rate | In-scope sales invoices sent as structured e-invoices, divided by all in-scope sales invoices issued. | 100% |
| First-pass validation rate | Invoices accepted without a validation error on the first submission, divided by all submissions. | Above 98% |
| Top three error codes | Rank validation failures by rule code each week. The same three codes usually cause most of the volume. | Falling week on week |
| Undelivered after 24 hours | Invoices sent with no confirmed transport acknowledgement from the receiving Access Point after one day. | 0 |
| Buyer rejection rate | Invoices rejected by the customer through an invoice response message, divided by invoices delivered. | Below 1% |
| Inbound structured share | Supplier invoices received over Peppol, divided by all supplier invoices booked. The rest is your migration backlog. | Rising every month |
| Days from receipt to posting | Average days between an inbound invoice arriving and the entry being booked. Split Peppol against everything else. | Peppol clearly faster |
| Master data completeness | Customer and supplier records carrying a valid VAT number and a Peppol endpoint identifier with the correct scheme. | 100% |
| Archive coverage | Sent and received invoices for which the original structured file is retained, not just a rendered PDF. | 100% |
| Cross-border exposure | Revenue invoiced into countries with a live or announced mandate, divided by total revenue. | Reviewed each quarter |
| Cost per document | Total e-invoicing spend divided by documents sent plus documents received. Both directions are billed. | Flat or falling per document |
If you only track four
Customer reachability, structured send rate, first-pass validation rate, and undelivered after 24 hours. Those four catch the majority of real problems. You can query them directly through the e-invoice.be API and push them into whatever your finance team already uses.
6. Where compliance breaks in practice
These are the recurring failures we see on the network. None of them is exotic. All of them stop an invoice from being delivered or booked.
The customer is not reachable on Peppol. The company exists, the VAT number is valid, but no participant is registered. You cannot deliver until they register. Read what to do in what to do when a customer is not on Peppol.
Wrong identifier scheme. A Belgian enterprise number sent under the wrong scheme resolves to nothing. See Peppol participant identifiers in Belgium.
VAT totals that do not add up to the cent. The classic is rule EN16931-R004, where the sum of line VAT does not match the document VAT after rounding. Your ERP rounds one way, the standard expects another. See fixing EN16931-R004 tax calculation errors.
Credit notes with negative amounts. Peppol expects positive amounts on a credit note document type. Sending a negative invoice instead is a common accounting habit that fails validation. See credit notes and negative amounts.
Nobody watches the responses. Delivery acknowledgements and validation errors arrive back on the channel and go unread, so a batch of invoices sits undelivered for weeks. See the common Peppol UBL errors and assign an owner to the error queue.
Invoices issued outside the flow. A subsidiary, a project team, or a spreadsheet keeps issuing PDFs. Your structured send rate is the metric that exposes it. Close the gap through ERP and accounting integration.
7. What changes in O2C, P2P and R2R
The structural change is that validation moves to the front. Errors that used to be corrected during collection now block issuance.
Order-to-Cash
An invoice must be valid before it can leave. Credit control now depends on a delivery status, not on a sent folder. Add undelivered documents to the AR review, next to overdue ones.
Procure-to-Pay
Inbound data arrives already structured, so three-way matching can run without OCR. The bottleneck shifts to supplier master data and to approving what the match could not resolve.
Record-to-Report
Close work moves from correcting entries to reconciling your records against what was transmitted. From 2028 the tax authority holds the other half of that reconciliation.
8. Mandate deadlines for the countries you invoice
Read this table by customer base, not by curiosity. The column that usually gets missed is the receiving obligation, because it lands earlier than the issuing obligation in several countries. Dates change, so confirm before you commit a budget.
| Country | Already binding | What comes next |
|---|---|---|
| Belgium | Structured B2B e-invoicing via Peppol since 1 January 2026. Progressive fines since 1 April 2026. | Near real-time dual-sided e-reporting from January 2028, replacing the annual client listing. |
| Germany | Every German-established business must be able to receive EN 16931 e-invoices since 1 January 2025. No grace period on receiving. | Issuing mandatory from 1 January 2027 above €800,000 prior-year turnover, and from 1 January 2028 for everyone else. |
| France | B2G e-invoicing since 2020. | From September 2026 every French-established VAT business must be able to receive, with no size threshold. Issuing starts September 2026 for large and mid-size companies and September 2027 for SMEs and micro businesses. |
| Italy | Clearance through the SdI platform since 2019, covering B2B and B2C. | Alignment work toward the EU standard. The domestic model is stable. |
| Poland | KSeF is live in 2026, phased by company size during the first months of the year. | Full coverage of domestic B2B, with invoice data flowing straight to the tax administration. |
| Netherlands | B2G e-invoicing only. No domestic B2B mandate. | Peppol is already widely used voluntarily. The binding date for Dutch counterparties is the EU one in 2030. |
| Ireland | B2G e-invoicing. | Domestic B2B e-invoicing announced for 2028, starting with larger businesses. |
| United Kingdom | Nothing binding yet. Peppol confirmed as the core interoperability network. | B2B and B2G e-invoicing announced from April 2029, with the implementation roadmap due at Budget 2026. |
| EU (ViDA) | Member states may impose domestic e-invoicing mandates without an EU derogation. | From 1 July 2030, digital reporting for intra-EU B2B transactions on EN 16931, with invoices to be issued within ten days of the chargeable event. |
9. E-invoicing readiness checklist
Use this to find the gaps before an auditor or a customer does. It covers six areas: regulatory scope, invoice data and formats, transmission and timing, systems and integrations, controls and audit readiness, and operational readiness. Progress is saved in your browser.
Regulatory scope
Invoice data and formats
Transmission and timing
Systems and integrations
Controls and audit readiness
Operational readiness
This checklist is a starting point. Requirements vary by country and by sector.
Take this checklist to your next meeting
Download the printable PDF version. Share it with your finance team, IT department, or accountant.
10. How to get started
Registration is instant and free. Company verification takes 24 to 48 hours through a wire transfer check, which is why everyone on the network is a real business.
For SMEs
No technical integration needed. Register, send invoices from the dashboard, or upload PDFs for automatic conversion to Peppol format.
Register nowFor developers and ERP vendors
Send, receive, and pull the dashboard metrics above over a REST API with JSON. Full API integration guide available.
Explore the API11. Frequently asked questions
What is e-invoicing compliance?
E-invoicing compliance means four things at once. You issue invoices in a structured format that meets the legal standard (in Belgium, Peppol BIS 3.0 based on EN 16931). You transmit them over an accepted channel. You are able to receive and archive structured invoices from your suppliers. And you report transaction data to the tax authority where the law requires it. A PDF sent by email meets none of these.
Is e-invoicing mandatory in Belgium?
Yes. Since 1 January 2026, invoices between Belgian VAT-registered businesses must be issued as structured e-invoices, with Peppol as the default network. B2C invoices are out of scope. So are invoices from businesses that only carry out VAT-exempt transactions under article 44 of the VAT Code.
What are the penalties for non-compliance in Belgium?
The tolerance period ended on 31 March 2026. Since 1 April 2026 a progressive non-proportional fine applies for not having the technical means to send and receive structured e-invoices: 1,500 euro for a first offence, 3,000 euro for a second, and 5,000 euro for further offences. A three-month window runs between offences before the next tier applies. The larger exposure is usually not the fine. It is your customer's input VAT deduction being questioned, and your customer refusing the invoice as a result.
How do I monitor e-invoicing compliance?
Track a small set of numbers monthly rather than auditing once a year. The four that catch the most problems are: the share of your active Belgian B2B customers with a resolvable Peppol ID, the share of in-scope sales invoices actually sent as structured e-invoices, the first-pass validation rate, and the number of invoices with no confirmed delivery after 24 hours. Every one of these can be pulled from an Access Point API and put on a finance dashboard.
What changes for Belgian companies in 2028?
From January 2028 Belgium adds near real-time e-reporting. Invoice data goes to the FPS Finance on a dual-sided model, meaning the supplier reports what it issued and the customer reports what it received, so the administration can reconcile both sides. It runs on a five-corner Peppol model and replaces the annual client listing. If your invoice data is wrong today, the reporting layer will surface it in 2028.
How much does e-invoicing compliance cost?
With e-invoice.be the account and the Peppol ID registration are free, with no setup fee and no monthly minimum. Every document is billed per invoice, on sending and on receiving, from 0.25 euro on Pro and 0.18 euro on Enterprise. A company that sends 250 and receives 250 invoices per month handles 6,000 documents per year, which is 1,500 euro per year at 0.25 euro per document.
Is the Belgian 120% deduction worth as much as it sounds?
Less than most people assume. It is an extra 20% of deduction, not an extra 20% of cash back. At the standard 25% corporate rate, an extra 20% deduction is worth about 5% of what you spend. On 1,500 euro of subscription cost that is roughly 75 euro of tax saved. It applies to small companies only, covers subscription and advice costs rather than one-off software purchases, and it is temporary. Confirm the details with your accountant.
Do I need to replace my ERP or accounting software?
Usually not. Most ERP and accounting systems either support Peppol already or can connect to a certified Access Point over an API. The work is rarely the connection. It is the master data behind it: VAT numbers, Peppol endpoint identifiers, and unit codes that have to be correct on every customer and supplier record.
Put the numbers on a dashboard
Free account, free Peppol ID, no setup fee and no monthly minimum. You pay per invoice, on sending and on receiving.
Want these twelve metrics running against your own invoice flow?
Fifteen minutes on where your data breaks, which deadlines actually apply to your customer base, and what a compliance dashboard needs to show. Built for the finance leadership conversation.

Vendor-neutral. No obligation to switch platforms.