Belgium's mandatory B2B e-invoicing rollout (phased from 2025) requires structured invoice exchange via the Peppol network. For energy, this changes more than how you receive the document: it tightens approval windows and exposes gaps in control. Many SMEs still validate energy bills with PDF review and spreadsheets-a slow but forgiving process. With Peppol, invoices can reach your system and approval workflow before anyone has verified that billed logic (indexation, capacity, periods) matches your contract. Preparing now means defining which fields must be checked before posting or payment.
1. What changes in practice for finance and operations
A Peppol-structured invoice carries explicit fields for supplier ID, billing period, tax blocks, and line-level charge components (energy, capacity, distribution, taxes). That supports automation and audit trails but also exposes weak internal setup. Without a clear mapping between your contract (e.g. fixed vs variable, indexation clause, capacity tariff) and these fields, the format change does not prevent overpayment-it only delivers incorrect values in a standardised structure.
The real shift is from "does this PDF look right?" to rule-based validation: billing period aligned with meter reading dates, indexation parameter and reference period matching the contract, and network/capacity components consistent with your EAN and metering context. Energy invoices are especially complex because they combine commodity, grid, and capacity elements that must each be validated.
2. Why energy invoices need a dedicated control model
Energy invoices are not simple recurring subscriptions. They include variable usage, network elements, taxes, and contract-specific calculations. Even when the document is technically compliant, these components can still be economically wrong for your site. This is why compliance and financial control should be treated as separate tracks.
A useful baseline is to review invoices on three layers: structural validity, tariff/indexation correctness, and anomaly detection versus historical behavior. Teams that separate those layers can escalate supplier questions with precise evidence instead of broad assumptions.
3. Minimum readiness checklist before 2026
Readiness checklist
- 1. Define which structured fields are mandatory for approval (e.g. period, EAN, unit prices, indexation reference).
- 2. Build exception rules for missing, inconsistent, or outlier values and route them to a single owner.
- 3. Assign clear ownership for validation decisions before posting or payment-avoid shared, unowned checks.
- 4. Prepare a dispute template with traceable field-level references so escalations are evidence-ready.
- 5. Track recurring supplier anomalies (wrong period, wrong EAN, indexation drift) month over month to spot systemic issues.
Treat the Peppol transition as a control upgrade: use the new structure to enforce consistent checks and faster dispute evidence, not only to comply with transport rules.
4. How to work with accounting and ERP when Peppol lands
Structured invoices will flow into your systems earlier and in a format that accounting or ERP can consume directly. That is an advantage for automation but a risk if the "mandatory for approval" checks are not defined. Agree with finance and operations which fields must be validated before the invoice is posted or paid: typically supplier ID, EAN, billing period, and a sanity check on total amount vs expected range. If your ERP or approval tool can run rule-based checks (e.g. period continuity, EAN in allowed list), design those rules now so they are ready when the first Peppol invoices arrive.
Keep a single point of contact for exceptions-invoices that fail a mandatory check or fall outside tolerance. Without that, structured invoices can still slip through with wrong EAN or period, and correcting after posting is costly and confusing for audits.
5. What to do in the first 90 days
Month 1: Map your process
Document who opens the invoice, who checks what, and who approves. Turn "by eye" checks into explicit rules or checklist items.
Month 2: Define mandatory fields
Agree with the approval owner on mandatory fields and the exception workflow.
Month 3: Dry run
Take one or two recent energy invoices and simulate the structured flow. Fill the dispute template with field-level references.
By the time Peppol becomes mandatory for your segment, you will have a repeatable control instead of a last-minute scramble.
If you use or plan to use an invoice validation tool, ensure it can ingest the structured format and flag the same dimensions you care about: period, EAN, indexation, capacity. Tools that only "read PDFs" will not be enough once the primary channel is structured.
6. Common pitfalls when moving to structured invoicing
Pitfall 1: Compliant does not mean correct
The first pitfall is assuming that "compliant" means "correct". A Peppol invoice can be fully compliant with format and transport rules and still contain wrong amounts, wrong periods, or wrong EANs. Compliance checks that the document is well-formed and reaches the right recipient; it does not check that the values match your contract. Your control layer must do that.
Pitfall 2: Vague validation ownership
A second pitfall is leaving validation to "whoever opens the invoice" without clear rules. When PDFs were slow and manual, that person might have developed an informal checklist. With structured flow, invoices can arrive in bulk or be auto-imported-so the validator may see many more documents and have less time per document. Without explicit mandatory checks and exception routing, errors will slip through.
Pitfall 3: Untested dispute path
A third pitfall is not testing the dispute path. When you need to contest a structured invoice, you will need to refer to specific field names, values, and document IDs. If your dispute template and escalation process are still built for "see attached PDF, page 2", you will lose time and clarity. Run a test dispute (e.g. on a known small error) to ensure your template and evidence pack work with the new format.
7. How to test your control process before go-live
Before the first live Peppol invoice, run a walkthrough with a sample. Take a recent energy invoice (PDF or a test structured file if your supplier or tooling can provide one) and simulate the full flow: invoice received, mandatory fields checked, exception (or approval) decision, and if applicable dispute pack prepared. Time the steps and note where information is missing or ambiguous. Fix those gaps-e.g. add the missing field to your checklist, or get the contract excerpt that defines the expected indexation reference.
Involve the same people who will own the process in production: the person who will open or import invoices, the person who will perform the 12-point or mandatory check, and the person who will approve or escalate. If they cannot complete the walkthrough without confusion, the process is not ready. Repeat until the path is clear and the dispute template is filled with real field names and examples.
Final takeaway
The best-performing SMEs treat Peppol adoption as a finance-control project with clear operational ownership. When structured invoices are combined with automated checks, billing errors surface faster, disputes become easier to evidence, and approval decisions are less dependent on manual hero work. Start by defining mandatory fields and exception ownership; then align accounting and operations on a single control model before the mandate applies to you.