Convert PDF invoices to XRechnung automatically – without replacing your ERP

With PEDIF you convert PDF invoices to XRechnung and create XRechnung from PDF – automated, validated and straight from your existing ERP. PEDIF converts recurring PDF invoices from ERP, billing and legacy systems into structured, validated XRechnung data. Keep your existing invoice process while PEDIF adds XRechnung output, validation and handoff to the required target workflow.

PDF remains the starting point
Validation before handoff
ERP & EDI stay in the architecture
Ambu
Blue Alpha
Bosch
Leipziger
Metro
Phoenix
Seeburger
Societe
Tamoil
Dimmel

Create XRechnung from PDF: how the automation works

Not "upload a PDF and hope", but a defined workflow for recognition, structure, validation and controlled handoff.

1

Keep creating PDF invoices

Your ERP, billing or specialist application continues generating the familiar PDF invoice.

2

Recognize and map invoice data

PEDIF processes recurring invoice layouts configured and tested for automation, including header, line-item, tax, total and reference data.

3

Create XRechnung automatically

The identified invoice data is mapped into the structured fields required for the agreed XRechnung output.

4

Validate the XRechnung automatically

The generated output is checked for format, mandatory fields, calculations and agreed recipient/process rules before release.

5

Deliver to the target process

The validated XRechnung is passed to the agreed ERP, EDI, portal, interface or transmission workflow.

Automated XRechnung: not every e-invoice is an XRechnung

E-Invoice is the broader category for structured electronic invoices. XRechnung is a German structured invoice specification based on EN 16931. A recipient may specifically require XRechnung, while another workflow may use a suitable ZUGFeRD/Factur-X profile or another compliant structured format. PEDIF first clarifies the required format, recipient requirements, validation rules and transmission process before the PDF workflow is automated.

What data does an automated XRechnung need?

Missing mandatory data cannot be invented by conversion. It must come from the PDF, the source system or another reliable data source. Typical data includes:

  • Invoice number
  • Invoice date
  • Seller and buyer data
  • Invoice line items
  • Quantities and units
  • Prices and discounts
  • Tax information
  • Net, tax and gross totals
  • Payment information
  • Purchase-order or contract references
  • Delivery or service references
  • Recipient-specific references

Business meaning matters

OCR can read visible characters, but XRechnung needs their business meaning. A value such as 1,250.00 may be a unit price, net total, tax amount or gross total. A date may mean invoice date, delivery date, service date or due date.

PEDIF therefore combines document recognition with field logic, mapping rules, validation and exception handling instead of treating the PDF as plain text.

Leitweg-ID in automated XRechnung

The Leitweg-ID is primarily used to identify and address invoice recipients in German public administration and route an e-invoice to the responsible downstream authority system. It is particularly relevant in workflows for the German federal administration.

Not every B2B XRechnung automatically requires a Leitweg-ID. The exact requirement depends on the recipient, transmission route and process rules. Before conversion, the target workflow therefore needs to define which recipient references are mandatory.

What PEDIF checks first

technical format and structure

required version/profile

mandatory invoice fields

mathematical consistency and totals

tax logic

buyer, seller, order and contract references

recipient-specific requirements

exception handling before release

XRechnung generator or automation? PDF to XRechnung without one-off conversion

For a single invoice, a manual online converter may be enough. If your systems generate tens, hundreds or thousands of recurring PDFs, the real question is different: how do you turn conversion into a repeatable, controlled workflow?

Manual one-off converter

A typical flow is: upload PDF, review extracted fields, add missing information and download XML. For occasional invoices, this can be the simplest and most economical option.

Single or rare invoices

Manual review for each document

Download as the endpoint

Automated PEDIF workflow

Relevant when ERP, billing or specialist systems continuously generate PDFs and a defined structured target output is required.

Recurring approved layouts

Defined field and validation rules

Validation before handoff

Review path for exceptions

Handoff to ERP, EDI, portal, interface or other target process

Create XRechnung automatically – without replacing your ERP or invoicing system

If your ERP, billing or legacy application reliably creates PDF invoices but cannot generate the required XRechnung output, you do not necessarily need to replace the source system.

PEDIF can add a structured output layer to the existing process: the PDF remains the familiar source document, relevant invoice data is mapped into XRechnung, the result is validated and the structured output is passed to the agreed downstream process.

This is particularly relevant for legacy applications, subsidiaries, specialist billing systems and EDI exceptions that continue to produce recurring PDFs.

Typical starting point

ERP reliably creates PDF, but not the required XRechnung output

Multiple invoice sources or subsidiaries

Existing EDI does not cover every partner or exception

Customers require different formats and references

Finance wants to avoid manual re-entry

IT wants to avoid an unnecessary migration project

Automate XRechnung or ZUGFeRD?

The right choice depends on the recipient, B2B/B2G context, required profile/version, target systems, submission route and human-readability needs.

XRechnung

A structured XML-based invoice standard. It is especially relevant where the recipient explicitly requires XRechnung, public-sector rules apply, or the target process expects a pure structured dataset.

ZUGFeRD / Factur-X

A hybrid format that combines a readable PDF/A-3 representation with embedded structured XML invoice data. It can be useful when people still need a familiar invoice view while systems also need structured data.

Automated XRechnung in practice: versions, delivery and validation

Generating an XRechnung file is only part of the job. The invoice also has to match the current specification, reach the right portal or recipient and pass validation there. The following sections explain what matters in day-to-day operation.

What XRechnung is technically

XRechnung is the German specification for electronic invoices based on the European standard EN 16931. It defines which fields are mandatory, which codes may be used and which additional German rules apply. The specification is maintained by the Coordination Office for IT Standards (KoSIT) and is updated in regular releases.

An XRechnung can be written in two XML syntaxes: UBL and UN/CEFACT CII. Both carry the same business content. Which syntax is used usually depends on the recipient's platform or on what the sender's processes already support.

How XRechnungen reach public-sector recipients

Public-sector clients in Germany receive e-invoices through dedicated channels. At federal level these are the central invoice receipt platforms; many federal states and municipalities operate their own portals. Depending on the recipient, invoices are uploaded, sent via the Peppol network or, in some cases, transmitted by email.

For a supplier with several public-sector customers, this means different delivery routes for the same type of invoice. PEDIF prepares the validated XRechnung and hands it to the delivery route agreed for each recipient, so the billing system does not need a separate export for every portal.

The Leitweg-ID in practice

The Leitweg-ID identifies the receiving public authority and is required by most public-sector recipients. It is issued by the authority itself and is usually communicated with the order or contract. In the XRechnung it is carried in the buyer reference field.

Many PDF invoices do not print the Leitweg-ID, because it was never needed on paper. In such cases PEDIF can add it from rules or master data, for example as a fixed value per customer or derived from a contract number on the invoice. If no valid Leitweg-ID can be determined, the invoice is routed for review instead of being sent without it.

XRechnung in B2B: automated from 2027

XRechnung is best known from the public sector, but it is also a valid e-invoice format between companies under the German e-invoicing rules. Some business customers ask for XRechnung because their accounting systems already process it. Others prefer ZUGFeRD, because it keeps a readable PDF view. PEDIF can produce either format from the same recurring PDF invoice, depending on what each recipient requires.

Validation: schema and business rules

An XRechnung is checked on two levels. The XML must match the schema of the chosen syntax, and the content must comply with the business rules of EN 16931 and the additional German rules of XRechnung. Public-sector portals typically run these checks on receipt and reject invoices that fail them.

PEDIF runs the validation before the invoice leaves your process. Invoices with findings are held back with a clear message, so they can be corrected before they reach the portal.

Credit notes and corrections

Credit notes and corrected invoices also have to be issued as XRechnung where the recipient requires it. A credit note is marked with its own document type, and a corrected invoice should refer to the invoice it replaces. Because these documents often come from the same billing system as regular invoices but with slightly different layouts, PEDIF handles them as separate cases with their own recognition, mapping and validation.

Making XRechnung readable for people

An XRechnung is a pure XML file without a visual layout. Accounting systems process it directly, but people who need to check or approve an invoice usually need a readable view. Many receiving systems generate one automatically. Where that is not the case, structured files can be turned into a readable PDF, for example with X to PDF, without changing the XRechnung itself.

Archiving XRechnungen

E-invoices have to be stored in the format in which they were issued or received and must remain unchanged for the statutory retention period. For XRechnung this means archiving the XML file itself; a printout or a generated PDF view is not enough on its own. Because the invoice data is structured, archive systems can index XRechnungen by invoice number, date, recipient or amount, which makes later searches and audits easier.

Typical reasons for rejected XRechnungen

  • Missing or invalid Leitweg-ID in the buyer reference
  • Missing seller contact details, which XRechnung requires
  • Payment instructions missing or incomplete, for example no IBAN for a credit transfer
  • VAT category codes that do not match the tax rates and amounts
  • Rounding differences between line totals, tax totals and the invoice total
  • An outdated specification version that the receiving portal no longer accepts

From the first XRechnung to steady operation

  • Identify the invoices that must be issued as XRechnung and the recipients and portals involved
  • Collect sample invoices for each recurring layout, including credit notes
  • Clarify where the Leitweg-ID and other references come from
  • Configure mapping, rules and validation, then test against the recipients' requirements
  • Start with selected recipients and extend once the results are stable

More questions about XRechnung in daily operation

Which XRechnung version should we use?
Recipients usually accept the versions that are currently valid according to the published schedule of the specification. Older versions are phased out over time. PEDIF produces the version required for the target workflow and is updated when new versions become mandatory.
UBL or CII: which syntax is better?
Neither is better in general. Both carry the same business content. The choice depends on what the receiving platform or customer prefers and what your downstream processes already support.
Can we send XRechnung by email?
Some recipients accept XRechnungen by email, while many public-sector recipients require upload to their portal or delivery via Peppol. The delivery route is clarified per recipient before the first invoice is sent.
What if the recipient rejects an XRechnung?
The rejection message usually names the rule that failed, for example a missing reference. The invoice is corrected and sent again. Validating before sending avoids most rejections in the first place.
Do we need a separate process for each public authority?
No. The invoice process stays the same. Only recipient-specific details such as the Leitweg-ID and the delivery route differ, and these are maintained as rules per recipient.

FAQ: creating XRechnung automatically

Yes. In a defined workflow, a PDF invoice can serve as the starting point for XRechnung. The required invoice data must be reliably available from the PDF or an additional trusted source, mapped to the correct structured invoice fields and validated against the agreed target rules. Simply renaming a .pdf file to .xml is not a conversion. PEDIF therefore starts with a fit check covering layout, required data, target profile and downstream workflow.
No. A standard PDF usually contains a visual representation designed for people. Under Germany's B2B e-invoicing rules, an e-invoice generally needs to be issued in a structured electronic format that enables electronic processing. XRechnung is a structured XML-based invoice standard. A PDF may still be permitted as an 'other invoice' in certain transitional cases, but that does not turn the PDF itself into XRechnung.
The conversion needs the invoice information required for the specific invoice scenario and recipient workflow. This may include invoice number and date, seller and buyer data, line items, quantities, prices, tax information, payment details, order or contract references and recipient-specific information. The key requirement is not only that a value appears on the PDF, but that its business meaning is unambiguous. Missing mandatory data must be supplied from a reliable source.
No. The Leitweg-ID is especially relevant for addressing recipients in German public administration and routing an e-invoice to the responsible authority system. It is an important part of invoicing workflows for the German federal administration. This does not mean that every B2B XRechnung needs a Leitweg-ID. The exact requirement depends on the recipient, the transmission route and the applicable process rules.
Yes, when the specific workflow is suitable for automation. PEDIF is designed for recurring PDF invoice layouts and clearly defined downstream processes. The existing ERP or billing application can continue producing its PDF; PEDIF recognizes approved layouts, structures relevant data, validates the target output and hands validated results to the agreed downstream process. New, ambiguous or invalid cases should follow a review path instead of being silently released.
Public-sector / B2G invoices: XRechnung is particularly important when invoicing German public-sector recipients. The exact buyer reference, mandatory fields and submission route depend on the recipient and platform. Business-to-business / B2B invoices: Germany’s B2B E-Invoice rules do not mean that every business invoice must specifically use XRechnung. XRechnung is one structured option. The required format depends on the transaction, recipient requirements and agreed technical process.

Fit check, not a blanket promise

Is your PDF workflow suitable for XRechnung?

Show PEDIF representative PDF invoices and the intended target workflow. The important factors are recurring layout, available mandatory data, recipient requirements, validation and the desired downstream handoff.

Check your e-invoice gap

Contact Us

Questions, need help choosing the right setup?

Book a Meeting

Prefer to talk directly? Pick a time that works for you.

The calendar is provided by Microsoft Bookings and loads when you click.

For information on how we process your data, see our Privacy Policy.