E-invoicing mandates are arriving across Europe, the UK and South Africa, and they'll make the invoices you receive far cleaner. They won't tell you whether your ledger agrees with your supplier's. You still need the statement for that.
We keep hearing the same question from finance teams planning an e-invoicing go-live. If every invoice arrives as structured data, why would we still reconcile supplier statements?
Fair enough. Plenty of statement work today really is cleanup after bad capture: an invoice keyed with the wrong number, or a total that doesn't add up. E-invoicing gets rid of most of that, and nobody will miss it.
The gap comes from having two sets of books. Your ERP holds what your team posted. Your supplier's ledger holds what they billed, what they credited and what they think you've paid. E-invoicing tidies up your side. The statement gives you their account-level view for comparison.
Where the mandates stand
Overview checked on 18 November 2026. Scope, exceptions and transition rules vary by country.
| Country | Who and when |
|---|---|
| Belgium | Structured e-invoicing for in-scope domestic B2B transactions from 1 January 2026. |
| Poland | KSeF issuing phased from February and April 2026; the smallest taxpayers have a temporary exemption until January 2027, subject to the monthly PLN 10,000 threshold. |
| France | Receiving obligations from September 2026; issuing for large and mid-sized businesses from September 2026, with SMEs and micro-businesses following in September 2027. |
| Germany | In-scope domestic businesses must be able to receive e-invoices from January 2025. Issuing requirements phase in during 2027 and 2028, subject to transitional rules and exceptions. |
| United Kingdom | VAT e-invoicing requirements from 1 April 2029. Digital reporting is being consulted on separately. |
| South Africa | Proposed digital VAT model, with phased implementation indicated from 2030, subject to consultation, approvals and readiness. |
| EU cross-border | ViDA digital reporting based on e-invoicing for in-scope intra-EU B2B transactions from 1 July 2030. |
All of these are phased, so most AP teams will be running a mixed estate for years. You'll get e-invoices from suppliers in one country and PDFs from another. The long tail will carry on sending whatever it sends now, and overseas suppliers often fall outside every mandate.
What an e-invoice can't tell you
The invoice that never arrived
E-invoicing controls the format of an invoice once it's sent. Whether it gets sent, and where it lands, is another matter.
During a transition, invoices can still be rejected, sent to an incorrect destination or left waiting for a corrected submission. Validating invoice data does not remove the need to monitor delivery and resolve failures.
Meanwhile the supplier counts that invoice as owed and the due date keeps running. Your ERP has never heard of it, so your ageing report hasn't either. It turns up on the statement, or in an angry email.
Credits and disputes
A credit note can arrive as perfectly valid structured data and still sit unapplied. You might reject a disputed invoice on your side while the supplier keeps it open on theirs. Then there's the credit the supplier raised and never sent you at all.
Every one of these changes what you owe, and you won't find any of them by looking at your invoices.
What happens after receipt
An e-invoice only gets you as far as the inbox. From there it's people and workflows. Invoices get posted to the wrong vendor. Others sit in an approval queue until they miss cut-off. Sometimes a PDF copy turns up alongside the e-invoice and both get entered.
Your ERP holds what was posted, and that is not always the same as what was received. Regular reconciliation helps identify differences that need investigation.
Payments, and how the supplier allocated them
E-invoicing covers the invoice. It has nothing to say about the payment. If a supplier put your payment against the wrong invoice, or never matched your remittance, you find out when they chase you for something you paid weeks ago. The statement puts their allocation next to yours, so you can sort it out before that call.
GRNI
Goods received not invoiced comes down to understanding which receipts still need an invoice and why. Supplier statements provide additional evidence about what has been billed, alongside purchase orders, goods receipts and supplier follow-up.
If the supplier has billed something you have not posted, investigate whether it is already covered by a GRNI accrual before making an adjustment. An old receipt missing from a supplier statement is a reason to investigate, rather than proof that the liability can be reversed. Any release needs supporting evidence and the appropriate approval.
When the tax authority holds a copy
Some countries are going further than e-invoicing. Under clearance and real-time reporting models, like Poland's KSeF or the near real-time reporting SARS has proposed, the tax authority sees invoices as they're issued.
That makes completeness an important part of the control design. Differences between invoice records and your ledger need investigation, with any tax consequences assessed under the relevant local rules.
The UK has gone the other way, with a decentralised model and no real-time reporting at launch. So nobody outside the business checks completeness for you there. Either way, proving your payables are complete stays with you.
What does change: recons get easier
For statement reconciliation, e-invoicing is good news. With structured invoice data you lose most of the false differences that come from capture errors, so what's left are the real ones. Matching gets quicker, and more of it runs without anyone touching it.
That shifts what a recon is for. Most teams today reconcile their top suppliers once a quarter, because anything more takes too long. Once matching is fast, you can run recons every month across the whole supplier base, and they start working as a control.
Where 360° AP fits
We spent years in recovery audit before building 360° AP. Missing invoices, unapplied credits and duplicates were the bread and butter of that work, and none of them depended on what format the invoice came in.
AP Accurate runs autonomous recons. It requests statements from every supplier in scope, reconciles them line by line against your ERP and chases what's missing. It highlights differences that may indicate incorrect postings or missing documents, and it tests open GRNI against what each supplier has actually billed. It works the same way whether the invoice arrived as a UBL file, a PDF or a piece of paper.
On the invoice side, AP Automate takes in the e-invoice, enriches it and passes it to your ERP, and handles capture for suppliers who haven't moved to e-invoicing yet. AP Assure keeps checking for duplicates. Classic keying duplicates fade once documents are electronic, but a supplier can still bill the same service twice under two invoice numbers.
Where to start
If you're planning an e-invoicing go-live, keep statement reconciliation in the design. For the first few months, watch two groups of suppliers closely: the ones moving to e-invoicing first, and the ones who won't move at all.
Then look at where your statement differences come from today. Some will be capture errors, and that share should shrink after go-live. The rest will be missing invoices, unapplied credits and misallocated payments. That second group is why the recon stays.