E-invoicing compliance software: what compliance requires and how to check a tool

Short answer: e-invoicing compliance is five separate obligations: the right structured format, the right delivery channel, any tax reporting, valid content and a proper archive of the original file. No single country asks for all five in the same way, so "compliance software" usually means a network or platform provider for the channel and reporting, plus a processing tool that reads, checks and books the invoices. Check which of the five a vendor actually covers before you buy.

This article is an overview, not tax advice. Rules are as published on 4 November 2026; see our e-invoicing deadlines tracker for changes by country.

What does e-invoicing compliance actually mean?

Vendors use "compliant" loosely. For an accounting firm it helps to split it into five questions:

A tool that "supports XRechnung" covers part of the first row. A Peppol access point covers the second row for Peppol countries. Neither, on its own, makes a client compliant.

How do the rules differ by country?

The model a country picks decides which software your client needs first.

France is the clearest case of a channel rule. The tax administration says taxable businesses must use an approved platform from 1 September 2026, and that only an approved platform can carry out every function the reform requires: issuing, transmitting and receiving invoices, and sending transaction and payment data to the administration. A "compatible solution" can still prepare invoices, but it cannot deliver them to the client's platform or report to the tax authority. See France.

Belgium shows what non-compliance costs. Deloitte Belgium reports administrative fines from 1,500 euros for a first offence to 5,000 euros for repeated non-compliance, after a tolerance period from January to March 2026. Domestic PDFs by email are on their way out; for cross-border invoices, PDFs remain permitted. See Belgium and what Peppol is.

The EU direction is set by VAT in the Digital Age (ViDA), adopted on 11 March 2025. The Commission says member states can now introduce mandatory e-invoicing under specific conditions, and digital reporting for cross-border B2B transactions starts on 1 July 2030. More countries will move from "PDF is fine" to one of the models above; our ViDA guide covers the timeline.

Format: what "EN 16931 compliant" means

EN 16931 is the European e-invoicing standard. The Commission describes its first part as a semantic data model that lists the business terms of a core invoice and defines what they mean. Two syntaxes meet the criteria: UBL and CII. National formats such as XRechnung are a CIUS (core invoice usage specification), which the Commission notes is a compliant use of the standard, while an extension is not.

For a firm this has two practical consequences:

1. A PDF is not an e-invoice where a mandate applies. A ZUGFeRD or Factur-X file is a PDF with XML inside, and it is the XML that counts.
2. Reading the header is not enough. A compliant file carries every line, with quantity, unit price and the VAT rate per line. Software that only extracts the supplier and total throws away the data the format was built to carry.

Validation: what a failed check means

E-invoices are machine-checked against the standard's rules, and most tools will show red errors on some incoming files. That does not always mean the invoice must be rejected.

As summarised by IHK Köln, Germany's Ministry of Finance distinguishes three kinds of problem: format errors, business-rule errors and VAT content errors. A technical business-rule error does not automatically mean the invoice stops counting as an e-invoice, and a negative technical validation does not necessarily rule out input VAT deduction. The guidance is not to reject incoming e-invoices across the board because of technical error messages, but to check whether the format and the mandatory invoice details are correct.

So good compliance software tells you which kind of error it found, and lets a person decide, rather than bouncing every file that fails a rule.

Archive: keep the original

Where the structured file is the legal invoice, it is the structured file that has to be archived, in its original form, for the full retention period. Converting the XML to a PDF, booking the PDF and deleting the file leaves the archive without the actual invoice. The same logic applies wherever the structured file is the legal invoice. Our guide to e-invoice receiving software covers the receiving side in more detail.

What to check before you buy

Questions to put to any vendor that calls itself e-invoicing compliance software:

1. Which of the five obligations do you cover? Ask for a plain answer per row of the first table.
2. Which channels? Peppol access point, approved platform in France, KSeF in Poland, accredited provider in the UAE. Name the countries.
3. Which formats, read in full? UBL, CII, XRechnung, ZUGFeRD, Factur-X, with every line and the VAT rate per line.
4. How are validation errors shown? By type, with the decision left to a person.
5. Where is the original stored, and is it linked to the booked bill?
6. What about non-e-invoices? PDFs, scans and photos keep arriving from small and foreign suppliers for years.
7. One view for many clients, rather than a portal login per client.
8. Where is data processed? Get it in writing.

For the wider buying picture, including sending, see our overview of e-invoicing software.

A worked example

A firm in the Netherlands looks after 30 clients. Four have Belgian entities, three trade with German customers, two have French subsidiaries.

• The Belgian entities need a Peppol provider to send and receive domestic invoices, or they risk fines.
• The French subsidiaries need an approved platform to receive since September 2026, and to issue from September 2027 if they are SMEs.
• The clients selling to Germany may be asked for XRechnung or ZUGFeRD, because German businesses have had to be able to receive e-invoices since 2025. The German issuing duty itself applies to German suppliers.
• The Dutch clients have no domestic B2B mandate yet, but receive a growing share of XML invoices from abroad.

That is three different channel answers. The processing answer can be one: every received invoice, XML or PDF, goes into a single queue, is read line by line, checked, coded, approved and booked, with the original file kept.

Where Invoreg fits

Invoreg covers the processing part of compliance for received invoices. It reads XML e-invoices (XRechnung, ZUGFeRD/Factur-X, Peppol UBL) alongside PDFs, scans and phone photos, reads every line including the VAT rate per line, suggests coding from each client's history, flags duplicates against bills already in the accounting software and registers nothing until a person approves it. Firms see all client organisations in one queue, and invoice content is processed and stored in EU regions only.

It is not a Peppol access point, an approved French platform or a KSeF connector, and it does not send or report invoices to tax authorities, so your clients still need a provider for the channel. If processing received invoices is where your team loses time, try it on your own invoices: the first 20 invoices are free.