Skip to main content
Convert PDF to XRechnung: practical workflow and paid plans
Blog

Convert PDF to XRechnung: practical workflow and paid plans

3 min readReviewed: July 14, 2026
Markdown export

Official references

Use these sources to verify dates, formats, and official rule changes.

Related Technical Wiki

Explore deep-dive developer documentation and regulatory guidelines matching this article.

XRechnung Standard

How XRechnung applies EN 16931 in Germany, including XML syntax, validation, buyer references, and delivery channels.

XRechnung Field Guide

XRechnung Business Terms and Groups (BT and BG), with field requirements, validation rules, and examples.

KoSIT BR-DE Validation Errors

German XRechnung BR-DE validation errors, with the related business rules and practical fixes.

This guide is for finance teams, suppliers, and ERP owners who still receive or create PDF invoices but now need a compliant XRechnung workflow for Germany.

Convert PDF to XRechnung – tutorial with validation

When you play it, YouTube (youtube-nocookie.com) loads the video, and data is transferred to Google.

Watch on YouTube · Chapters and transcript

As of April 20, 2026, businesses in Germany must already be able to receive e-invoices. For domestic B2B transactions, the issuing transition period runs until December 31, 2026, and until December 31, 2027 for issuers whose previous-year turnover did not exceed EUR 800,000. From January 1, 2027, the transition no longer covers issuers above that threshold; from January 1, 2028, the e-invoice obligation applies more broadly. If your source process is still PDF-first, conversion can be a practical bridge, but only if the output is reviewed and validated.

When PDF-to-XRechnung conversion is the right approach

Use conversion when the upstream ERP or billing system still produces PDFs, while the recipient expects structured XML. It is especially useful during a phased rollout, pilot project, or ERP migration.

Do not treat conversion as a magic replacement for process design. If buyer identifiers, tax logic, payment terms, or line data are missing in the source invoice, those issues still need human review before the XML is sent.

What an acceptable XRechnung output must contain

Interactive map

Tap a part of the invoice to list its required fields and the rule that makes each one mandatory.

fields on every invoice

of them only by XRechnung rules

more in certain cases

8 always required · +7 in certain cases

XRechnung ruleEN 16931 ruleOnly in certain cases
An XRechnung needs 37 business terms on every invoice: Header 7, Seller 8, Buyer 5, Lines 7, Totals and tax 9, Payment 1. 13 of them are required only by XRechnung rules (BR-DE, plus the PEPPOL-EN16931 rules that XRechnung applies), for example the buyer reference BT-10 and the seller contact BT-41 to BT-43; the others by EN 16931 rules. Another 40 become required in certain cases, for example with a deliver-to address, direct debit, an allowance or a VAT exemption. Source: XRechnung 3.0.2 in the KoSIT configuration of 31 Aug 2026; same field list as our XRechnung required fields guide.
  • A supported XRechnung syntax and rule set, such as XRechnung 3.0.2.
  • Required seller, buyer, invoice, tax, and payment information in the correct structured positions.
  • Recipient-specific identifiers such as Buyer Reference or Leitweg-ID where required.
  • A validation pass against EN 16931 and the applicable German rule set before submission.

Recommended conversion workflow

Interactive pipeline

Click a stage to see what it checks, or type a rule ID to light up the stage that reports it.

Try:

Stage 1 · What it checks

  • The file is well-formed XML. If it cannot be parsed, no rule can run.
  • Root element, namespaces, element order and data types follow the UBL 2.1 or CII D16B schema.

Example codes

Typical fix

Correct the generator: a misplaced element, a wrong namespace or a value in the wrong data type.

A validator checks an e-invoice in stages. First the file must be well-formed XML that matches the UBL or CII schema (XSD). Then the EN 16931 business rules run: BR core rules, BR-CO calculations, BR-CL code lists, BR-DEC decimals and VAT-category rules such as BR-S. Next come the national or network rules that BT-24 selects: BR-DE for XRechnung, PEPPOL-EN16931 for Peppol BIS Billing. The report lists every failed rule: one error means reject, warnings alone still mean accept. Rule sets: KoSIT validator 1.6.3 with the XRechnung configuration of 31 Aug 2026 (EN 16931 artefacts 1.3.16), Peppol BIS Billing 3.0.21.
  1. Upload the PDF and check that header data, dates, totals, VAT rates, and line items were extracted correctly.
  2. Add or correct missing identifiers, especially buyer reference, Leitweg-ID, tax IDs, and payment references.
  3. Generate the XRechnung XML and run validation before the file leaves your team.
  4. Review warnings or failed rules, correct the source data, and regenerate instead of patching the XML manually where possible.
  5. Only then send the invoice through the correct recipient channel, portal, or Peppol setup.

Common failure points

  • Treating the PDF layout as proof that the structured data is complete.
  • Missing buyer reference or Leitweg-ID for German public-sector workflows.
  • VAT category mismatches between line-level and document-level totals.
  • Assuming the XML is ready to send without a validator report and exception handling process.

Frequently asked questions

Is a PDF alone compliant for German e-invoicing in 2026?

No. A plain PDF is not a structured e-invoice. It may still appear in legacy workflows during transition periods, but the compliance target is structured invoice data such as XRechnung or another accepted EN 16931 format.

When should I choose XRechnung instead of ZUGFeRD?

Choose XRechnung when the recipient, channel, or validation process expects the German XRechnung ruleset in structured XML. ZUGFeRD is usually better when you need a hybrid PDF plus XML invoice, provided the profile and recipient requirements allow it.

Can conversion remove the need for manual review?

No. Conversion reduces manual effort, but teams still need review steps for low-quality PDFs, missing identifiers, VAT edge cases, and invoices that fail validation.

Ready to convert your invoices?

Convert PDF invoices to XRechnung, ZUGFeRD, and other formats. Subscriptions from €10/month with annual billing (excl. taxes), with a 3-day trial on your first subscription. Or without a subscription: €5 per conversion (excl. taxes).

PDF to XRechnung

Try it free without an account, up to 6 PDF pages per conversion, attachments included. Only the download costs: it needs an account and one credit or a subscription.

Related articles