E-invoicing is spreading across Europe. Where does an AP agent fit for a German manufacturer?
Belgium, France and the EU's 2030 cross-border rules change how invoices arrive. What an accounts payable agent still does once the PDF goes away.
The short answer
Structured e-invoices remove the reading problem, not the matching problem. For a German manufacturer receiving invoices from Belgian, French and domestic suppliers, an AP agent's job moves from extracting fields out of PDFs to matching, coding and routing exceptions. Scope it for the mixed inbox you will have until 2030, not the clean one regulators describe.
Key takeaways
- Mandatory B2B e-invoicing applies in Belgium from 1 January 2026 and starts in France in September 2026, according to Grant Thornton's August 2026 summary.
- Germany already requires businesses to be able to receive e-invoices, with further obligations from 2027.
- EU cross-border B2B e-invoicing under ViDA begins on 1 July 2030, so most manufacturers will run a mixed inbox of structured files and PDFs for years.
- A structured invoice removes extraction work but leaves three-way matching, cost coding and exceptions, which is where an AP agent earns its place.
- Measure your own cost per invoice and exception rate before scoping an agent; published benchmarks do not state their samples or periods.
In this article
What the mandates change, and when
The mandates change the format in which invoices arrive, country by country, on fixed dates. Grant Thornton Netherlands' summary of August 2026 sets out the sequence.1 Italy has required B2B e-invoicing since 2019. Belgium made it mandatory from 1 January 2026, and Poland is phasing in its national system from February 2026. France begins mandatory e-invoicing and e-reporting in September 2026.
Germany sits in the middle. German businesses have had to be able to receive structured e-invoices since January 2025, and Grant Thornton notes that issuing obligations expand from 2027 and apply more broadly from 2028.1 Across the EU, the VAT in the Digital Age package (ViDA) brings mandatory cross-border B2B e-invoicing from 1 July 2030, with domestic systems expected to align by 2035.
For a German manufacturer that buys from suppliers across Europe, that means a long transition. Some invoices arrive as structured files today. Many still arrive as PDFs attached to emails, and some will keep arriving that way until the cross-border rules bite.
B2B e-invoicing dates that touch a German manufacturer
Germany: businesses must be able to receive e-invoices.
Belgium: mandatory B2B e-invoicing.
Poland: national system phased in.
France: e-invoicing and e-reporting begin.
Germany: issuing obligations expand, then apply more broadly.
EU: cross-border B2B e-invoicing under ViDA.
Why a German exporter feels other countries' rules
A German manufacturer feels Belgian and French rules on both sides of the ledger. On the sales side, customers in those countries need invoices they can process in their own mandated systems. On the purchasing side, suppliers who have already built e-invoicing for their home market start sending structured files to everyone, including you.
That second effect is the one AP teams notice first. A supplier switches format without much warning, the files land in a shared inbox, and someone has to work out how they reach the ERP. Grant Thornton points to the European standard EN 16931 as the common data model, and to Peppol as the network Belgium's planned e-reporting and Luxembourg's mandate build on.1 Ask your ERP partner which formats and networks your system already accepts.
Our view: treat the mandates as an intake project first and an automation project second. Decide where structured files arrive, how they are validated and how they reach the ERP before you ask an agent to do anything with them.
Structured invoices and PDFs: what changes for an agent
A structured invoice removes the reading problem and leaves the matching problem. With a PDF, an agent or an OCR tool must first find the supplier, the invoice number, the lines, the VAT and the totals, and it can misread any of them. With an EN 16931 file, those fields arrive labelled.
What does not change is the work after the fields are known. The invoice still has to match a purchase order and a goods receipt. Prices and quantities still drift outside tolerance. Freight lines still appear that nobody ordered, and cost centres still need coding. Those are the steps where an AP clerk spends judgement, and they are the steps where an agent can help.
Where the agent's work sits, by invoice format
PDF by email
- Read the document and extract fields
- Check the extraction against the supplier master
- Match to order and receipt
- Code, route exceptions, draft for approval
Structured e-invoice
- Validate the file against the standard
- Match to order and receipt
- Explain mismatches in plain language
- Code, route exceptions, draft for approval
Does an e-invoicing mandate make an AP agent unnecessary?
No, but it makes the agent narrower and easier to test. When extraction errors disappear, the agent's mistakes are easier to see: it either matched correctly or it did not. That is a better place to start than a pilot where nobody can tell whether a wrong total came from the OCR or the logic.
Narrower also means the business case shifts. Part of what PDF-capture vendors sold was reading. If most of your volume becomes structured, that saving belongs to the mandate, not to any tool. The agent's saving then comes from fewer exceptions handled by hand and faster answers to suppliers who ask why they have not been paid.
Our view: a manufacturer with a high share of PO-backed invoices from a stable supplier base gains most. A business with many non-PO invoices, such as services, utilities and one-off purchases, gains less from matching and more from coding suggestions that a person approves.
What does an invoice cost you today?
Know your own number before you scope anything, because published benchmarks are thin on method. Ardent Partners' State of ePayables 2025 (published January 2026; sample, period and geography not stated) puts the average cost to process an invoice at $9.84.2 It reports best-in-class organisations at 79% lower cost per invoice (period again not stated).2
APQC's benchmarks put accounts payable cost at about $0.38 per $1,000 of revenue for top performers and about $0.92 for bottom performers (published March 2026; sample and period not stated).3 Neither source splits manufacturers out or reports German data.
Use them as a sanity check on a figure you measure: time a normal week of invoices, multiply by loaded hourly cost and add the time spent on supplier queries and corrections. Our guide to invoice agents in the ERP walks through that calculation and the controls around it.
Scoping the agent for a mixed inbox
Scope for the inbox you will actually have between now and 2030: some structured files, many PDFs, and a long tail of odd formats. A sound first scope has four parts.
- Intake. One channel for structured files and one for PDFs, both landing as drafts in the ERP. The agent never posts or submits.
- Matching. Two-way or three-way match against orders and receipts, with tolerances agreed by finance in writing.
- Exceptions. Every mismatch goes to a queue with the agent's explanation attached, so the clerk starts from a reason, not a blank screen.
- Supplier questions. A drafted reply on payment status, grounded in ERP data and sent only after a person approves it.
Permissions matter more than models here. The agent's ERP user should create and save drafts and nothing else, as our least-privilege checklist sets out. Every action it takes should land in a log your auditors can read; our audit log field list covers what to record.
Where to start this quarter
Start with a count, not a tool. Pull three months of supplier invoices and mark each one by format, country of the supplier, whether it carried a purchase order and whether it needed a person. That sheet tells you how much of your volume is already structured, how much will be by 2027 and where exceptions cluster.
Then decide the order. If exceptions are concentrated in a few suppliers, fix the master data and tolerances first. If they are spread across many PO-backed invoices, an agent drafting matches and explanations is a good first build. Our view: if more than a third of invoices carry no purchase order, start with coding suggestions rather than matching.
Running costs belong in the plan from day one. Our breakdown of monthly agent costs covers platform, usage, people and exceptions. The manufacturers page and our AI automation page describe how we scope one workflow on the ERP you already run.
