Your customers now demand structured invoices, and every country has its own format, network and deadline.
Your system prints PDFs; the mandate wants validated XML through Peppol or a national platform.
XRechnung, ZUGFeRD and UBL files arrive and someone still opens them in a viewer and retypes the numbers.
One process per country, one provider per network, and nobody sees the whole picture.
Numbers from the European Commission, Billentis and 2025–2026 readiness surveys — mandates are arriving country by country, and most companies are not finished.
VAT compliance gap in the EU in 2023 — 9.5% of the VAT due. Closing it is why governments are making e-invoicing mandatory.
of roughly 300 billion B2B invoices a year worldwide are electronic; the rest are still paper or PDF.
of ~870 companies surveyed by RSM Ebner Stolz in Germany had a fully working e-invoicing solution for sending and receiving in mid-2026 — with the sending mandate due in 2027.
of large and mid-sized French companies expect their e-invoicing project to cost more than €1 million.
growth in Peppol registrations in just 30 days, to 6.16 million in August 2026 — your customers are joining the network.
VAT compliance gap in Germany alone in 2023 — 9.7% of the VAT due, the largest amount of any EU country.
Put your monthly volume into the calculator and see hours and dollars.
Outbound and inbound in one workflow. Every invoice runs on its own; anything that fails validation or a match stops and goes to a person with the error spelled out.
A finalised invoice in your ERP, billing tool or shop starts a run — by webhook, API poll or a dropped file.
OutboundLooks up the buyer: Peppol ID, country, public or private customer — and picks XRechnung, ZUGFeRD, Factur-X, Peppol BIS or FatturaPA.
OutboundMaps your invoice data to the EN 16931 semantic model and writes the XML, or the hybrid PDF with embedded XML.
OutboundRuns the EN 16931 and country Schematron rules plus your own checks — VAT IDs, tax categories, totals, mandatory references.
OutboundOnly clean files go out. Errors stop the run and go to finance with the failing rule and field named.
OutboundDelivers through your Peppol access point, or to KSeF, SDI or a French approved platform, and stores the delivery receipt.
OutboundFollows delivery, acceptance and rejection messages and updates the invoice status in the ERP.
OutboundAn XML or hybrid PDF arrives from the access point, a platform or the invoice mailbox.
InboundReads vendor, number, dates, lines, tax and totals directly from the structured data — no OCR, no retyping.
InboundChecks number, amount and vendor against the books and flags changed bank details before anything is posted.
InboundLooks up the purchase order and goods receipt in the ERP and compares line by line within your tolerances.
InboundMismatches and new vendors go to the approver in Slack or Teams with the readable invoice attached.
InboundPosts the bill to the ERP or accounting system and archives the original file unchanged for the legal retention period.
Post & archiveWeekly summary: invoices sent and received per country, rejections, open exceptions and upcoming mandate dates.
Post & archiveE-invoicing automation replaces the manual work that electronic invoicing mandates create — converting invoices into the right structured format, fixing validation errors, uploading files to portals and opening received XML to retype it — with a workflow that does it on every invoice, in both directions. Mandates are now live or coming in Germany, Belgium, Poland, France and, since 2019, Italy, and the EU’s VAT in the Digital Age package makes cross-border e-invoicing mandatory from 1 July 2030. A PDF attached to an e-mail is no longer enough.
We build electronic invoicing automation around your existing ERP or billing system rather than replacing it. Outgoing invoices are mapped to the EN 16931 model and written as XRechnung, ZUGFeRD, Factur-X, Peppol BIS or FatturaPA, validated against the European and national rules, and sent through your Peppol access point or the national platform, with delivery and rejection messages tracked back into the ERP. Incoming e-invoices are read straight from the XML, checked for duplicates and bank-detail changes, matched to purchase orders and posted, with the original archived unchanged for audit.
Compliance stops being a project per country and becomes one process: invoices are valid before they leave, rejections fall to almost zero and received invoices are posted without anyone retyping a number. Finance keeps every decision on tax treatment, disputes and payments, while the workflow handles formats, networks and deadlines.
Typical minutes per invoice for a small finance team handling both outgoing and incoming e-invoices. Your own numbers go into the calculator below.
Based on 18.5 min by hand and 30 sec with the flow per item, from the table above.
The workflow builds, validates, sends, receives and posts. People keep the decisions about money, customers and tax treatment.
Reverse charge, exemptions and unusual VAT cases are set up and reviewed with your tax adviser.
When an invoice fails a rule, a person fixes the master data — the flow never forces a file through.
Rejected invoices, corrections and credit notes are decided by finance.
Price or quantity mismatches and unknown vendors go to the approver.
Verified by a phone call on a known number, never by an e-mail or an invoice field.
Which Peppol access point or platform you contract with stays your decision; we connect to it.
Flip a switch to hand a step to the flow or take it back.
Benchmarks from the European Commission’s ViDA package, Billentis and the Generix 2025 survey: every invoice structured and validated before it leaves, inbound XML posted without retyping, and one process across every country you sell into.
We map the process as it runs today, count the minutes and agree what the flow must never do on its own.
A working flow on your real data, in a sandbox. You see every run and every exception.
Edge cases, approvals and alerts, then the switch-over — with the old way kept as a fallback.
Monitoring, fixes when a vendor changes a format, and a monthly report of hours saved.
It depends on where you and your customers are. Germany requires every business to receive e-invoices since 1 January 2025, with sending phased in from 2027 and 2028. Belgium has required structured B2B e-invoices since 1 January 2026, Poland’s KSeF since February and April 2026, and France starts on 1 September 2026 for large and mid-sized companies, with smaller ones from 1 September 2027. Italy has run B2B e-invoicing through SDI since 2019, and cross-border EU e-invoicing follows from 1 July 2030 under ViDA.
All are built on the European standard EN 16931. XRechnung and Peppol BIS are pure XML; ZUGFeRD and Factur-X are a readable PDF with the same XML embedded. Peppol is the network that carries the file between access points, not a format of its own.
No. Under the EU mandates an e-invoice is a structured, machine-readable file. A plain PDF is a different type of invoice, accepted in Germany only during the transition years and not accepted in Italy, Poland’s KSeF or Belgium’s B2B mandate.
Usually not. The workflow takes the invoice data your ERP already produces, builds and validates the structured file and hands it to a Peppol access point or the national platform. You keep your ERP and choose the provider; we connect the two.
Every file is validated against EN 16931, the country Schematron rules and your own checks before it is sent. Errors stop the run and go to a person with the failing rule named, so master data is fixed once instead of the same invoice bouncing back.
They are read directly from the XML, checked for duplicates and changed bank details, matched to purchase orders and posted to your ERP with the original archived unchanged — no viewer, no retyping.
A first country with outbound and inbound flows typically goes live in a few weeks, depending on ERP access and the provider. Additional countries reuse the same validation and posting steps.
Describe it in two sentences — we reply within a day with a workflow sketch.
hello@wireclad.com →