E-invoicing mandates in Europe: which AI tools read structured invoices (September 2026)

Why structured e-invoices change what AI does in finance

German law now separates two kinds of invoices. An electronic invoice is issued, sent and received in a structured electronic format that allows electronic processing, and the format has to follow the European standard under Directive 2014/55/EU or be agreed between the parties. Everything else, including a PDF attached to an email, counts as an other invoice.

Belgium puts it plainly: since January 1, 2026, sending a PDF invoice by email or through a platform is no longer enough between Belgian VAT registered companies. The invoice itself carries the data, so there is nothing left for optical character recognition to guess.

That shifts the work AI does. Pennylane states that it reads incoming e-invoices automatically and turns them into a booking proposal. Candis describes automatic pre-coding for e-invoices and other invoices alike. The value moves from capture to the decisions after it: which account, which cost center and who approves.

Paper and PDF will not vanish overnight. Foreign suppliers, small senders in transition periods and receipts from travel still arrive as images, so most finance teams will run both paths for years. A useful tool handles both in one process rather than splitting the inbox in two.

Sources: [1][2][3][4]

E-invoicing mandates in Europe: the dates that matter

Italy moved first: all VAT registered businesses there have issued and received e-invoices through the SdI exchange system since January 1, 2019. Germany followed with a receiving obligation for domestic business to business invoices from January 1, 2025, with a transition for senders.

Under Section 27 (38) of the German VAT Act, senders may still use paper or, with the recipient's consent, other electronic formats for supplies until December 31, 2026. Companies whose total turnover in the previous year did not exceed 800,000 euros get one more year, until December 31, 2027, and the same end date applies to existing EDI procedures. Small invoices up to 250 euros stay exempt.

Belgium made structured invoices mandatory between Belgian VAT registered companies on January 1, 2026, sent through the Peppol network. Poland's national system KSeF became mandatory on February 1, 2026 for companies whose 2024 sales exceeded 200 million zloty and on April 1, 2026 for everyone else. France started on September 1, 2026: all companies must be able to receive e-invoices, and large and midsize companies must issue them. Small and micro companies follow on September 1, 2027.

At EU level, the VAT in the Digital Age package was adopted on March 11, 2025. It lets member states introduce mandatory domestic e-invoicing, starts digital reporting for cross-border business to business supplies on July 1, 2030 and asks existing national reporting systems to align by January 1, 2035.

Sources: [5][6][7][2][8][9][10]

Our check: 32 AI invoice tools and what they publish on XRechnung, ZUGFeRD and Peppol

On September 26, 2026 we took every tool in our directory whose main category is accounts payable or bookkeeping, 32 in total, and read the vendor's public pages: website, e-invoicing page, pricing and help articles where available. We recorded three things. Does the vendor name XRechnung or ZUGFeRD? Does it describe receiving or reading incoming structured e-invoices, not only sending them? Does it name a Peppol connection or access point?

The result is thinner than the marketing around e-invoicing suggests. 17 of the 32 tools describe receiving structured e-invoices. 10 name XRechnung or ZUGFeRD, 10 name Peppol, and 6 name all three. 15 tools say nothing about receiving e-invoices on the pages we checked. Our directory currently lists 92 tools for accounts payable automation, counting secondary categories, so the picture will move as we add tools.

Accounts payable specialists do better than bookkeeping tools. Of the 17 tools built mainly for invoice processing, 12 describe receiving e-invoices and 8 name Peppol. Of the 15 bookkeeping tools, 5 describe receiving and 2 name Peppol, although the German bookkeeping tools in this group are among the clearest about XRechnung and ZUGFeRD.

Use the explorer below to filter by headquarters and category. One caution: one German vendor's e-invoicing page returned an error during our check, and several US vendors simply do not market to German buyers. Treat a missing entry as a question for the sales call.

Sources: [11][12]

Where the vendor is based predicts e-invoice coverage

The clearest pattern in our check is geography. Of the 8 tools headquartered in Germany, 5 name XRechnung or ZUGFeRD. Of the 12 headquartered in the United States, none does, and only 2 describe receiving structured e-invoices at all. The 12 tools from other countries sit in between, with 5 naming a German format and 6 naming Peppol.

European accounts payable vendors that sell across several mandates document the most. Esker states that it is a Peppol access point and has implemented XRechnung and ZUGFeRD in customer projects. Rossum validates invoices against country formats such as FatturaPA, XRechnung, ZUGFeRD and Peppol BIS 3 and ingests them from Peppol, KSeF and other channels.

Some tools for small companies are just as explicit. Zoho Books says its German edition receives e-invoices from suppliers over Peppol and supports XRechnung and ZUGFeRD. GetMyInvoices registers a Peppol ID for its customers and reads incoming e-invoices from email, portals and Peppol.

US vendors such as Vic.ai, Stampli and BILL focus their pages on AI capture, coding and payments for American customers. Tipalti mentions global e-invoicing and links to European e-invoicing networks without naming formats. If you run German entities on a US platform, ask for a written statement on XRechnung, ZUGFeRD and Peppol before you sign.

Sources: [13][5][14][15][16]

What AI still does when the invoice is already data

A structured invoice removes the reading step, not the judgment. Somebody still has to decide whether the supplier is genuine, whether the VAT treatment is right, which general ledger account applies and whether the invoice matches a purchase order and a delivery. That is where current AI features concentrate.

Hypatos describes a set of AI agents that capture, classify, extract and validate invoice data, resolve the supplier, check for duplicates and prepare a posting in the ERP, applying tax and e-invoicing rules per line. Its e-invoicing skill lists formats from Peppol BIS Billing 3.0 to FA(3) KSeF, XRechnung and ZUGFeRD.

Mixed inboxes are the practical challenge. Medius says its capture handles PDF, XML, EDI and other formats in one flow, and Basware runs its own Peppol access point and codes invoices without a purchase order with a machine learning feature called SmartCoding. For a buyer, the question is less whether a tool has AI and more whether PDF invoices and e-invoices end up in the same approval, coding and archive process.

One risk grows during the transition: the same invoice arriving twice, once as a PDF by email and once as an e-invoice through another channel. Hypatos names this directly and says its agents manage e-invoices without creating duplicate payment risk. Whatever tool you pick, ask how it recognizes a second copy of an invoice it has already posted, and whether that check runs across both channels.

Sources: [17][18][19][20]

How to test e-invoice support before you buy

Ask for a trial and send real files. At minimum, test a pure XML XRechnung, a ZUGFeRD hybrid invoice (a PDF with embedded XML) and, if you trade in Belgium or other Peppol countries, an invoice through Peppol. Check that the tool reads the XML rather than the visible PDF layer and that validation errors are shown in plain language.

Then follow the invoice to the end. Where does it land in approval, how does it reach your accounting system or ERP, and which file is archived? Under German rules the structured data is the invoice, so the archive has to keep the XML, not only a rendered image of it.

Finally, ask the vendor to name the formats and networks in the contract or order form. For a wider comparison of what AI does across the invoice process, from capture to payment, see our guide to AI accounts payable automation.

Sources: [7][21][6][2]