PDF to XRechnung – automate the bridge from existing invoice workflows
Does your ERP or billing application still generate PDF invoices? PEDIF can use recurring, approved PDF layouts as a starting point, structure relevant invoice data, validate the generated target output and hand it off to a defined XRechnung workflow.
Can you convert a PDF into XRechnung?
A PDF invoice is primarily a visual representation. It may be perfectly readable for a person while still providing no structured invoice dataset that a downstream system can process automatically. XRechnung, by contrast, describes structured invoice information in XML. That means PDF to XRechnung is not a file-extension conversion. It is a data and workflow transformation.
For PEDIF, the first step is a fit check: recurring layouts, required data, recipient requirements, target structure, validation and downstream handoff need to be clear. Only then does it make sense to automate the PDF-first route.
How PDF to XRechnung works with PEDIF
Not "upload a PDF and hope", but a defined workflow for recognition, structure, validation and controlled handoff.
PDF is created
Your existing ERP, billing or specialist application continues generating the familiar PDF invoice.
Recognize data
PEDIF recognizes approved recurring layouts and assigns relevant header, line-item, tax and total information.
Structure
The captured information is converted into clearly defined machine-readable invoice fields for the target workflow.
Validate
The generated target output is checked against the technical and business rules agreed for the project.
Hand off
Validated results move to the defined e-invoice, ERP, EDI, DMS or other downstream process.
What data does XRechnung need?
The exact information depends on the invoice scenario, recipient and target workflow. 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
“1,250.00” might be a unit price, net total, tax amount or gross total. A date might mean invoice date, delivery date, service date or due date. For XRechnung, the process needs to understand not only the visible text, but also its business meaning.
OCR reads characters. A robust e-invoice workflow needs field logic, rules and validation.
Leitweg-ID and 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
Which recipient requires XRechnung?
Which references are required?
Is the data available in the PDF or another reliable source?
Which profile and validation rules apply?
Where should the validated result be handed off?
Automate PDF to XRechnung instead of converting every invoice manually
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
Connection to existing downstream processes
Keep existing systems
PDF to XRechnung without replacing your ERP
Many organizations run ERP, billing or specialist applications that work reliably for the business but cannot produce the required XRechnung output for every recipient workflow. Replacing the entire system just to satisfy a target format can be disproportionate.
PEDIF therefore starts where the invoice already exists: the recurring PDF output. When layout and data quality are suitable, PEDIF can act as a bridge between the existing PDF-first process and the structured target workflow.
The goal is not to replace a working ERP or EDI architecture. PEDIF complements it where residual, legacy or exception processes still depend on PDF.
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
XRechnung or ZUGFeRD?
XRechnung
A structured XML-based invoice standard. It is especially relevant where the recipient expects a pure structured dataset or explicitly requires XRechnung.
ZUGFeRD
A hybrid approach that can combine a readable PDF representation with embedded structured XML invoice data. This can be useful when people still need a PDF view while systems also need structured data.
Close the PDF gap while keeping ERP and EDI in place
PEDIF is not positioned as a generic “every PDF in, everything finished” black box. The strength is a defined scope: recognize recurring document layouts, structure relevant fields, validate target outputs, expose exceptions and hand validated data to the intended downstream workflow.
That directly addresses the long tail that classic EDI connections often do not cover: partners, legacy applications and exception processes that still use PDF.
PEDIF principle
PDF remains the input. Structured, validated data becomes the target.
The project starts with a fit check covering layout, data quality, target structure, validation rules and handoff. New or ambiguous cases are handled deliberately instead of being silently counted as successful automation.
FAQ
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 gapContact Us
Questions, need help choosing the right setup?
Book a Meeting
Prefer to talk directly? Pick a time that works for you.