Convert a PDF to XRechnung: step‑by‑step to valid e‑invoice XML

If you only have an invoice as a PDF but your customer requires XRechnung, you need more than a visual document. XRechnung is structured invoice data in XML designed for automated processing. E‑Rechnungs‑Studio helps you upload a PDF, extract the invoice details, validate them, request edits in plain language, and finally download XRechnung XML.

Upload PDF now →

Quick summary (TL;DR)

XRechnung is XML, built for systems, not humans.
A standard PDF is not an e‑invoice even if it looks complete.
E‑Rechnungs‑Studio generates EN‑16931‑based CII XML and validates it.

What is XRechnung—and when do you need it?

XRechnung is a German e‑invoice specification based on EN 16931. It’s commonly required in public sector procurement and in automated B2B invoice workflows.

In practice, recipients may require a specific technical variant (XML syntax/profile). If in doubt, confirm what your recipient accepts.

PDF vs XRechnung: the key difference

A PDF is mainly for people to read. XRechnung contains invoice data in a structured form so software can reliably import and verify line items, VAT, totals, payment terms, references, and more.

So “PDF invoice as XRechnung” means: convert PDF content into structured XML.

How to convert PDF → XRechnung with E‑Rechnungs‑Studio

1) Upload your PDF

Upload your existing invoice PDF. The tool extracts invoice fields and generates structured XML.

2) Review the result

Compare the original source PDF, the preview PDF rendered from extracted data, and the XML that represents the actual e‑invoice.

3) Read validation results (errors first)

Validation helps you catch missing required fields, inconsistent totals/VAT calculations, and incomplete or ambiguous line item data.

4) Fix issues in plain language

Instead of editing XML manually, type changes like “Correct the seller email address”, “Add a description to line item 2”, or “Payment term is 14 days”.

5) Download the XML

When everything looks right and validation is clean, download the XML and deliver it through your process (portal, email, API, etc.).

Tip: If you also need a human‑readable PDF in the same file, export a hybrid invoice (ZUGFeRD) instead.

Pre‑send checklist

Invoice number & issue date
Delivery/service date (if applicable)
Seller/buyer name, address, contact details
VAT IDs/tax identifiers (as needed)
Payment terms, due date, IBAN/BIC, discounts
Line items: quantity, unit, net price, VAT rate/category, description
Totals: net/VAT/gross—do calculations match?
References: PO number, project reference, recipient requirements

FAQ

Can every PDF be converted to XRechnung?

Often yes, but scanned PDFs and complex layouts typically require more review and corrections. Always verify preview + XML.

Do I need to know XML?

No. You work via preview, validation hints, and change requests in natural language.

How do I know the XRechnung is valid?

In practice, you want zero validation errors. Warnings should be reviewed and fixed when relevant.

Can I send a PDF alongside the XML?

Yes, many workflows include a visual copy. For system processing, the structured invoice data matters.

Get started

Upload your PDF and generate a verifiable XRechnung XML—with validation and an easy correction loop.