One invoice format converter API: any format in, a compliant e-invoice out
Every country wants a different e-invoice format, but your ERP still exports the same CSV. Here is how one invoice format converter API fixes that.
You built your ERP export once. It spits out a CSV, or maybe a UBL file, and for years that was fine. Then France mandated Factur-X. Germany wants XRechnung. Italy has FatturaPA and its SdI clearance. Poland is rolling out KSeF with its FA(3) schema. Spain expects Facturae. Norway runs on EHF over Peppol. The UAE, Oman and Singapore are standardising on PINT.
Your ERP did not change. The world around it did. And now every new customer or country your business touches comes with a different technical demand, while your finance team is stuck exporting the exact same file it always did.
Why invoice formats fragmented in the first place
There is a European standard, EN 16931, that defines a common semantic model for an electronic invoice. In theory, everyone agrees on what a "net amount" or a "buyer VAT identifier" means. In practice, each country wraps that model in its own syntax, its own required fields and its own validation rules.
XRechnung and Factur-X are both based on EN 16931, but they are not interchangeable files. FatturaPA predates the standard and uses its own Italian schema entirely. KSeF FA(3) is Polish-specific. So "we support e-invoicing" is never one job. It is a dozen jobs that all start from the same source data and end in incompatible files. That is the gap an invoice format converter API is built to close: you keep exporting what you already export, and something else handles the translation into whatever each destination demands.
What "any format in" actually means
The messy part is usually the input, not the output. Real accounting systems export legacy and inconsistent data: a flat CSV with 40 columns, an Excel sheet a controller maintains by hand, EDIFACT from an old EDI setup, or structured UBL and CII from a newer stack. Some send a ZUGFeRD or Factur-X PDF with the XML embedded inside it.
A converter API worth using reads all of that. MyInvoice takes CSV, Excel, EDIFACT, UBL, CII and ZUGFeRD/Factur-X PDF as inputs — and when a supplier sends you a hybrid PDF, it pulls the XML out of the file and normalises it into the same clean model. That last part matters more than it sounds: an e-invoice you receive becomes a valid input, not just something you file. You can take an inbound Factur-X or ZUGFeRD document and re-emit it as Peppol BIS or XRechnung without rebuilding your pipeline.
One API, every compliant output
Once your data is parsed into the common model, the output is a choice, not a rebuild. The same source invoice can come out as:
- Peppol BIS 3.0 for the Peppol network
- XRechnung for German public-sector buyers
- Factur-X / ZUGFeRD for France and Germany
- FatturaPA for Italy
- KSeF FA(3) for Poland
- EHF for Norway
- PINT for the UAE, Oman and Singapore
You send data once and pick the format at the end. When a new country goes live, you change a parameter, not your ERP.
Keep your system, fix the last mile
The point is not to replace your software. It is to stop wiring one-off format projects every time a mandate lands. Your ERP keeps exporting its CSV. The API handles the last mile, turning that export into the exact file a country or the Peppol network will accept, and it validates the result before you send it.
If your team is staring down a new mandate with the same old export file, that is exactly the gap this closes. Take a look at MyInvoice and try converting one of your real exports into the format you actually need.
Convert one of your exports in the browserRead the API docs