E-invoice converter

Turn an invoice in one EN 16931 format into another: XRechnung UBL into CII, a Peppol BIS invoice into a ZUGFeRD PDF, a Factur-X PDF into XRechnung. The result is checked against the schema and business rules of its format before you save it, and the converter says what it could not carry over. Everything runs in your browser

Invoice to convert

Examples

From and to

It reads the invoices of the EN 16931 model, as XML or inside a PDF:

  • UBL 2.1 Invoice and CreditNote: XRechnung UBL, Peppol BIS Billing 3.0 and the national profiles on EN 16931.
  • CII D16B: XRechnung CII, ZUGFeRD 2 and Factur-X, the XML on its own or the PDF that carries it.

And writes them as XRechnung 3.0 in UBL or CII, Peppol BIS Billing 3.0, ZUGFeRD / Factur-X in the EN 16931 profile as XML or as a PDF/A-3 with the XML inside, or XRechnung inside a ZUGFeRD PDF (the XRECHNUNG profile). A credit note stays a credit note.

How it converts

The invoice is read into the terms of EN 16931, the model every one of these formats writes in its own syntax: the parties, the lines, the VAT breakdown, the totals, the payment details and attached files. Then it is written in the format chosen, by the same code as the e-invoice generator, and checked with the validator's engine against that format's XML Schema and Schematron rules, the KoSIT, Peppol and Factur-X ones.

Before anything is offered, the converter compares the total without VAT, the VAT and the amount due of the result with the amounts the file states. When they differ, because the file has something the conversion leaves out that changes them, such as allowances on lines or a rounding amount, it converts nothing: an invoice written again must ask for the same money.

What does not carry over

The formats share a model, not every field. What the converter can't write, it names under the result: a payee, a delivery address, item classifications, line notes, a second address line and the like. What it has to change is named too: a document type other than an invoice or credit note is written as one of them, a payment means other than a transfer or a direct debit as a SEPA transfer.

A format also asks for things the others don't. An XRechnung needs the buyer reference (BT-10, the Leitweg-ID for German public buyers) and the seller's contact; Peppol needs electronic addresses for both parties (BT-34, BT-49) in a scheme other than email. When the file lacks them, the result fails those rules and the converter lists them, each linked to its rule. Fill them in with the e-invoice generator, which opens the same file.

A ZUGFeRD PDF made here is laid out by xmlvalid, A4 with the invoice's own data, not a copy of the seller's PDF.

Who should convert

The seller. An invoice is the document the seller issued: a buyer whose system can't read the format it arrived in can convert it to look at or import it, but the file received is the one to archive. A seller who has to send XRechnung to one customer and Peppol BIS to another, or whose software writes only one format, can write the others here and check them in the same step.

Questions

Is my invoice uploaded?

No. The file is read, converted, checked and laid out as a PDF in your browser. Nothing is sent to the server.

Is the converted invoice valid?

It is checked against the schema and the business rules of its format before you save it, as the validator would check it. A result that fails is shown with its findings; most often the file lacks something the new format requires.

Can the amounts change?

No. The converter compares the totals of the result with those of the file and converts nothing when they differ.

Which formats can it not read?

FatturaPA, KSeF, ZUGFeRD 1.0 (CrossIndustryDocument) and other formats outside the EN 16931 UBL and CII syntaxes. The e-invoice viewer shows FatturaPA and KSeF invoices.

Other tools

  • XML formatter: Pretty-print or minify XML, keeping text, CDATA and comments as written.
  • XML viewer: Read a document as a tree you can fold, search and copy XPaths from.
  • XPath tester: Evaluate XPath 3.1 against a document and see each match with its line.
  • XSD generator: Infer an XML Schema from sample documents, checked against them.
  • XML from XSD: Generate a sample XML document from a schema, validated against it.
  • XSLT transformer: Run XSLT 1.0, 2.0 or 3.0 on a document and see the result, the messages and the files it writes.
  • XML diff: Compare two XML documents as trees: changed, added and removed elements, attributes and text.
  • XML to JSON converter: Convert XML to JSON, with arrays where an element repeats or wherever its XSD allows.
  • JSON to XML converter: Convert JSON to XML: @keys become attributes, arrays repeated elements.
  • XML to CSV converter: Turn a repeating element into CSV rows: invoice lines, products, records.
  • XML to PDF converter: Save any XML as a PDF to read, print or attach: indented, coloured, with line numbers.
  • E-invoice viewer: Read an XRechnung, ZUGFeRD, Factur-X or Peppol invoice as a document, and save it as a PDF.
  • ZUGFeRD validator: Check a ZUGFeRD or Factur-X PDF: the XML inside against its profile's rules, and the PDF around it.
  • XRechnung validator: Check an XRechnung in UBL or CII against EN 16931 and KoSIT's XRechnung rules before you send it.
  • UBL validator: Check a UBL invoice, order or any other UBL 2.1 document against its OASIS schema, and the business rules of the profile it names.
  • Peppol validator: Check a Peppol BIS Billing 3.0 or PINT invoice against the OpenPeppol rules before your access point sends it.
  • P7M viewer: open a .p7m file: Open a signed .p7m file: the PDF, invoice or document inside it, and who signed it.
  • XRechnung examples to download: Example XRechnung and ZUGFeRD invoices to download, one for each common case.
  • E-invoicing mandate in Germany: do I have to?: Find out whether your invoices in Germany must be e-invoices in 2026, 2027 and from 2028.
  • Factur-X examples: Example Factur-X invoices of every profile and of the French reform, as XML and as PDF.
  • Leitweg-ID check: Check the form and the check digits of a Leitweg-ID, the address of a German public buyer.
  • Peppol lookup: Check whether a company is registered in Peppol, under which ID, and which invoices it can receive.
  • XML validator: check a document against XSD, DTD, RelaxNG or Schematron, up to 1 GB.