E-Invoice Reader & Converter — XRechnung, ZUGFeRD, Factur-X, Peppol

Turn European e-invoices into clean JSON or a readable page, convert between formats, and generate compliant XML from JSON.

E-invoicing is becoming mandatory across Europe: Germany requires businesses to receive XRechnung / ZUGFeRD since 2025 and to issue them from 2027–2028; Belgium, Poland and France follow. Many small businesses now get XML invoices they cannot read, and many apps need to produce XRechnung, Peppol or Factur-X without building a compliance stack. This Actor does both.

What it does

Mode	Input	Output
parse	URL of an XML invoice or a ZUGFeRD / Factur-X PDF	Structured JSON: parties, lines, VAT, totals, payment details, plus a validation report
render	Same as above	A clean, printable HTML page in the key-value store
transform	Same as above + targetFormat	The invoice rewritten in another format (e.g. ZUGFeRD → Peppol BIS), stored as XML
convert	Invoice JSON + targetFormat	XRechnung / Peppol BIS / Factur-X XML. Line amounts, VAT breakdown and totals are calculated for you

Formats: XRechnung 3.0 (UBL and CII), Peppol BIS Billing 3.0, Factur-X / ZUGFeRD 2.x profile EN 16931 (XML, and reading the XML embedded in a hybrid PDF), EN 16931 UBL. Invoices and credit notes.

Tested on official reference data: all 86 documents of the KoSIT XRechnung test suite are read and converted to XRechnung UBL and CII, and the official KoSIT validator accepts the result for 85 of them (the remaining one uses the XRechnung Extension, which is not supported yet). The embedded invoice is found in every one of the 61 official FeRD ZUGFeRD 2.5.2 sample PDFs.

Try it

Press Start: the input is prefilled with two public reference invoices — an XRechnung test invoice published by KoSIT and a ZUGFeRD sample PDF published by FeRD. Switch the mode to convert to generate XML from the prefilled JSON invoice.

Example input

{
  "mode": "parse",
  "documentUrls": ["https://example.com/invoices/RE-2026-001.xml"],
  "includeHtml": true
}

Example output (one dataset item per document)

{
  "source": "https://example.com/invoices/RE-2026-001.xml",
  "ok": true,
  "number": "RE-2026-001",
  "format": "XRechnung (UBL)",
  "fromPdf": false,
  "invoice": { "number": "RE-2026-001", "issueDate": "2026-11-01", "currency": "EUR", "seller": { "name": "..." }, "totals": { "payableAmount": 1190.00 } },
  "validation": { "isValid": true, "errorCount": 0, "warningCount": 0, "issues": [] },
  "htmlUrl": "https://api.apify.com/v2/key-value-stores/.../records/RE-2026-001-a1b2c3.html"
}

A document that cannot be read gives an item with "ok": false and an error that says why — for example a PDF without an embedded invoice, or a ZUGFeRD 1.0 invoice (not supported).

Validation

Every result carries a fast built-in check of the most common EN 16931, XRechnung (BR-DE) and Peppol rules: mandatory fields, totals, VAT arithmetic, code lists. Rule ids are the official ones (BR-…, BR-DE-…, PEPPOL-…) where the check matches the official rule, IB-… for our own checks. It is a pre-check, not the official schematron validation. The official validation (KoSIT validator with the XRechnung, EN 16931 and Peppol BIS rules) is part of the InvoiceBridge REST API.

No silent data loss: when a source invoice contains data the JSON model does not carry (for example a delivery period or an attached document), the report lists each of them as an IB-DROPPED warning with the EN 16931 term, so you know exactly what a conversion leaves out.

Pricing

Pay per event: you pay per successfully processed document (event document-processed). Documents that fail are not charged. The run stops before it would exceed your maximum charge per run.

Privacy

Documents are processed in memory during the run and are not stored by us. Results are written only to your own Apify storage (dataset and key-value store).