EU e-invoicing API

Any invoice in.
Valid EU e-invoice out.

Developer-first API that validates and converts invoices to Peppol BIS 3.0, XRechnung and Factur-X — the EN 16931 formats that EU mandates require from 2026 onward. Pay per invoice. No subscription.

Validate an invoice free → Read the docs

186/186 official KoSIT & OpenPeppol sample invoices pass the official rules after conversion — re-tested daily.

What happens to an invoice

One real invoice to a German public-sector buyer, from your data to a valid XRechnung.

  1. You send the invoiceAs simple JSON from your software, an XML you already have, or a PDF.

    {
      "number": "RE-2026-100",
      "issueDate": "2026-11-02",
      "currency": "EUR",
      "seller": { "name": "Muster GmbH", … },
      "buyer": { "name": "Stadt Köln", … },
      "lines": [{
        "name": "Beratung",
        "quantity": 10,
        "unitPrice": 100,
        "vat": { "categoryCode": "S",
                 "rate": 19 }
      }]
    }
  2. We check it against the rulesEvery problem comes back with what to change. Nothing is converted, or charged, until it passes.

    BR-DE-15 BuyerReference (BT-10) is mandatory in XRechnung — for B2G this is the Leitweg-ID.

    Add the buyer’s Leitweg-ID

    + "buyerReference":
    +   "04011000-12345-67"

    Valid. Official KoSIT rules passed.

  3. You get a valid e-invoiceXRechnung, Peppol BIS 3.0 or Factur-X — also as a hybrid PDF/A-3 — checked once more with the official rules before you get it.

    <Invoice …>
      <cbc:CustomizationID>
        urn:cen.eu:en16931:2017
        #compliant#urn:xeinkauf.de
        :kosit:xrechnung_3.0
      </cbc:CustomizationID>
      <cbc:ID>RE-2026-100</cbc:ID>
      <cbc:BuyerReference>
        04011000-12345-67
      </cbc:BuyerReference>
      …
      <cbc:PayableAmount
        currencyID="EUR">1190.00
      </cbc:PayableAmount>
    </Invoice>

Three ways in

No developer on the team

Sign in, drop a PDF or paste an XML in the dashboard, check it, and download the XRechnung. No code.

Start with 50 free credits

You build the software

One POST request from your invoicing code, with SDKs for Node, PHP, .NET and Python. Errors tell you exactly what to fix.

See the XRechnung API

You receive e-invoices

Got an XRechnung or ZUGFeRD file you can’t read? Open it as a normal invoice in the free viewer.

Open the free viewer

Mandatory e-invoicing is rolling across Europe

Belgium already requires structured B2B e-invoices. France, Greece, Germany and Slovakia follow in 2026–2028. Your invoices will need to be machine-readable XML — not PDFs. See every country deadline →

Built for developers

One POST request. Clear errors. Honest pay-per-use pricing.

# Convert JSON → XRechnung in one call
curl -X POST https://fakturwire.com/v1/convert \
  -H "authorization: Bearer $FW_KEY" \
  -H "content-type: application/json" \
  -d '{"target":"xrechnung-ubl","invoice":{"number":"INV-42", ...}}'
1 credit

per validation — full rule report

2 credits

per conversion — validation included

50 free

credits on signup, no card required

Why teams pick FakturWire

Fail fast, not at the tax office

Invalid invoices are rejected before conversion with a full findings list — you never deliver a non-compliant document.

Credits never expire

Buy a pack, use it whenever — see pricing. No monthly minimum, no seat licences, no "contact sales".

EU-hosted, GDPR-native

Invoice payloads are processed in the EU and never stored after the request completes.

Explore the rule reference, the free developer tools, or — if you run a practice — the accounting-firm plan.