E-invoicing
A mandate standardises the invoice. It never checks it against your order
No. An e-invoicing mandate standardises an invoice's format and its transport, and never checks it against your purchase order. Italy is the proof: SdI has cleared invoice format for years and AP teams there still reconcile by hand. Structured data makes matching possible. It does not do the matching.
What a mandate actually standardises
Three things: format (EN 16931, XRechnung and ZUGFeRD, UBL, FatturaPA, PINT-SG), transport (Peppol, SdI, the French PPF and PDP model, NemHandel, the UAE five-corner model) and tax reporting.
Three things it never touches
- Agreement with the purchase order
- Agreement with the goods receipt
- Agreement with the contracted price
Italy is the proof
Italy is the control group. Fatturazione elettronica through SdI has been mandatory for years, and 2026 changed almost nothing — FatturaPA XML 1.2.2 still valid, technical specifications materially unchanged since 1.7.1.
Italian AP teams still reconcile by hand. SdI clears an invoice's format, never its agreement with the order. If a mandate were going to remove reconciliation anywhere, it would have removed it there first.
What structured invoices change, and what they do not
They remove OCR error and make automated matching possible for the first time. That is a real gain and it is the reason to want the mandate.
They also raise exception volume, because more invoices arrive machine-readable and arrive faster. Singapore's five-corner model is the clearest case: structured invoice data arriving at scale increases reconciliation and exception work rather than reducing it. The UK's 2029 framework makes the mirror point — PDFs, Word files, HTML invoices and OCR images are expressly outside the definition, so the clean-up is data quality, not scanning.
What still has to be matched, whatever the mandate says
A structured invoice changes none of these. From the note the matching workflow reads:
- Match on SKU, never on line position
- Unit price: ±2%
- Quantity: exact, no tolerance
- Freight: ignored, reconciled separately in freight-accrual
- Anything outside tolerance to escalation-queue — never auto-approved, regardless of confidence score
Two vendors send consolidated invoices covering several POs. Current behaviour splits them, which is wrong about a third of the time. Not yet solved — tracked in consolidated-invoice-handling.
ops/vendor-onboarding.md
The full rule set as accounts-payable mechanics is on purchase-order matching, rule by rule; the tolerance rules written down in plain text are the file they live in.
Do you need to replace your ERP for e-invoicing compliance?
No. It sits above your CRM, ERP and management software and reads them where they are — no migration, no replacement, no data-warehouse project that has to finish first — no migration, no replacement, no data-warehouse project that has to finish first. 0 systems replaced.
One honest qualification in the same breath: appointing an access point, a PDP or an accredited service provider is a separate obligation, and we are not one of those. The layer reads what the ERP already holds and writes results back. Compliance deadlines without an ERP migration covers the rest.
What this page does not claim
No accreditation, no ASP, PDP or access-point status, no Peppol certification, and no tax advice. Dates and rules are stated as published by the sources linked, not as advice about your obligations.
The nine-jurisdiction deadline table this page was scoped to carry is deliberately absent. Sixteen dates across nine jurisdictions rot within a year, and two of them have already moved once. It publishes when somebody owns a quarterly re-check and a visible last-reviewed date — not before.
Questions
Straight answers.
Does e-invoicing remove the need for invoice reconciliation?
No. A mandate standardises an invoice's format and how it travels, and never checks it against your purchase order. Italy has cleared invoice format through SdI for years and its AP teams still reconcile by hand. Structured data makes matching possible; it does not do the matching.
Do we need to replace our ERP for e-invoicing compliance?
No. The layer reads what the ERP already holds and writes results back into it — nothing migrated, nothing replaced. Appointing an access point or an accredited service provider is a separate obligation, and we are not one of those and do not claim to be.
Does structured invoice data reduce exception volume?
Usually the opposite, at first. More invoices arrive machine-readable and arrive faster, so more of them reach the matching step and more mismatches surface. What it removes is OCR error. What it exposes is every disagreement that was previously invisible.
What does a mandate not standardise?
Three things, and they are the three that matter to accounts payable: agreement with the purchase order, agreement with the goods receipt, and agreement with the contracted price. Format, transport and tax reporting are standardised. Whether the invoice is correct is not.
Where do the matching rules live?
In plain markdown notes in your own storage, not in code and not in a console. Match on SKU rather than line position, unit price within two per cent, quantity exact, freight reconciled separately, and everything outside tolerance held for a person to decide.
Start here
Bring us one workflow.
Tell us the process that crosses the most systems. You get a scope, a measure and a delivery plan back — and a straight answer if we think it is not worth building.
Get in touch