Convert PDF invoices to ZUGFeRD – automated and validated
With PEDIF you convert PDF invoices to ZUGFeRD and create ZUGFeRD from PDF – automated, with a readable PDF and structured XML in one file. Your ERP can keep producing the PDF invoices your team already uses.
PEDIF turns the required invoice data into the appropriate ZUGFeRD structure, creates the hybrid e-invoice and validates the result before it moves downstream.
From €49 per monthSetup from €349 incl. pilotNo lock-in
E-invoicing mandate in Germany: issuing from 1 Jan 2027 – find out now which format your customers need.
Partners & integrations










What does automated PDF to ZUGFeRD conversion mean?
A standard PDF invoice is designed mainly for people to read. A ZUGFeRD invoice keeps a readable PDF view and adds structured XML data that accounting and ERP systems can process automatically.
Normal PDF invoice
The PDF shows invoice numbers, line items, taxes, totals and payment details in a layout people can read. Automated ERP, EDI and e-invoice workflows need those values in a predictable data structure.
ZUGFeRD hybrid e-invoice
A ZUGFeRD invoice uses a PDF/A-3 document with embedded structured XML. People can read the PDF while software processes the XML. Select the ZUGFeRD / Factur-X version and profile required for the recipient and workflow.
Why companies convert PDF invoices to ZUGFeRD automatically
Many ERP, billing and industry systems already produce reliable PDF invoices. The gap appears when a customer or downstream process requires ZUGFeRD and the source system cannot generate it.
Keep a stable ERP
If the source system already works, you should not need a major ERP upgrade just to add a ZUGFeRD output path.
Meet different recipient requirements
One billing process may need to support ZUGFeRD, XRechnung, EDI or customer portals, depending on the recipient.
Keep the familiar invoice view
Finance teams and customers are used to the existing invoice design. ZUGFeRD can combine that human-readable view with machine-readable invoice data.
Support multiple billing systems
Subsidiaries, sites and specialist tools can keep their recurring PDF layouts while the required invoice data is structured centrally.
Avoid rebuilding every source system
Instead of modifying each invoice-generating application, use the recurring PDF as the starting point for a controlled ZUGFeRD process.
Build validation into the workflow
Generating XML is only one step. The workflow should also check required data, business rules and the selected ZUGFeRD profile before delivery.
Create ZUGFeRD from PDF: how the automation works
PEDIF is built for repeatable invoice workflows, not mainly for one-off manual conversion. We first check the recurring layout, required fields, target profile, recipient requirements and downstream system.
Keep creating the PDF
Your ERP or billing system continues producing the invoice as it does today.
Map the recurring layout
PEDIF identifies the approved invoice layout and maps the fields needed for the e-invoice.
Structure the invoice data
Invoice number, seller and buyer data, line items, taxes, totals and other required values are prepared in a consistent structure.
Map to the required profile
The structured data is mapped to the ZUGFeRD / Factur-X profile required for the workflow.
Create the ZUGFeRD invoice automatically
The PDF/A-3 document and structured XML are combined into the required hybrid e-invoice.
Validate and deliver automatically
PEDIF checks the output before approved invoices continue to the downstream process. Exceptions are routed for review.
No-touch does not mean no-control. Reliable automation requires defined rules, validation and a clear exception path for missing or contradictory data.
See it with your own invoice.
ZUGFeRD converter: PDF invoice to ZUGFeRD
A classic ZUGFeRD converter turns single files into e-invoices: upload the invoice, check it, download it. That works for the occasional invoice. With PDF invoices from your ERP or billing system, every manual conversion becomes a bottleneck.
PEDIF works as an automated converter inside the running process: your PDF invoice is recognised, the invoice data is structured, mapped to the required ZUGFeRD profile and created as a hybrid e-invoice of PDF/A-3 and embedded XML. Before handover, PEDIF checks both the format and the business data. The result: a readable invoice for people and structured data for the recipient's system – in one file.
Automation with your existing PDF invoice design?
In many cases, the familiar invoice view can remain part of the ZUGFeRD file. That makes the format well suited to PDF-first invoice workflows.
What can remain
The existing invoice appearance – including branding, line items, totals and customer-specific presentation – can potentially remain the visual component if it is technically suitable.
What must be checked
PDF/A-3 requirements, the selected ZUGFeRD profile, mandatory data, data quality and consistency between the visible PDF and structured XML. Under Germany's current e-invoice rules, the structured part is especially important in hybrid invoices.
Automated ZUGFeRD invoice vs. a standard PDF invoice
← swipe →
| Criterion | Normal PDF | ZUGFeRD |
|---|---|---|
| Readable by people | Yes | Yes, through the PDF visual component |
| Structured invoice data | Not automatically | Yes, as embedded XML |
| Machine processing | Needs an additional recognition/structuring step | Designed for software processing through the structured part |
| German e-invoice requirements | A simple PDF alone does not meet the new definition | Suitable ZUGFeRD versions/profiles can meet the requirements |
| Validation | No EN 16931 format validation | XML and business rules can be validated against the target profile |
| Existing invoice design | Yes | Can remain as the PDF/A-3 visual component |
Automate PDF to ZUGFeRD or XRechnung?
Both formats make invoice data machine-readable. The main difference is whether the invoice includes a readable PDF view and which format the recipient requires.
ZUGFeRD: readable PDF + structured XML
Use ZUGFeRD when a readable invoice view should remain available and the recipient accepts the required profile.
XRechnung: structured XML
XRechnung is an XML-based e-invoice format without an integrated PDF invoice view. Use it when the recipient or process explicitly requires XRechnung.
The right format depends on the recipient, required profile, downstream system and delivery channel.
When does automation with PEDIF beat an ERP rebuild?
If your ERP already creates the right ZUGFeRD output cleanly and validates it, the native route is often the logical first choice. PEDIF is relevant where the operational reality remains PDF-first across multiple source systems or recurring special cases.
Existing PDF generation can remain in scope.
Recurring invoice layouts can be structured in a controlled way.
ERP, DMS, EDI and accounting systems do not need to be replaced wholesale.
Target profile and mandatory fields are clarified before implementation.
Validation becomes part of technical handoff.
Missing or contradictory values do not silently pass into the target system.
A focused rollout can start with a limited set of recurring layouts.
Additional structured target paths can be assessed separately by workflow.
PDF remains the starting point. Structured data is the target. That reflects PEDIF's current positioning for document-based e-invoice, ERP and EDI workflows.
See it with your own invoice.
Is automation a good fit for your PDF-to-ZUGFeRD workflow?
Good fit
Companies with recurring B2B invoices
Finance, Accounting, ERP, IT and EDI teams
Multiple billing or legacy systems
Stable PDF layouts but missing structured exports
Recipients with different invoice requirements
Processes where validation and exception handling matter
Automated validation: creating the XML is not enough
A reliable ZUGFeRD workflow must validate both the technical format and the business data before the invoice is delivered downstream.
Profile and version
Which ZUGFeRD / Factur-X version and profile does the recipient or workflow require?
Required data
Are all mandatory invoice values available in the PDF, or must some come from ERP master data or customer records?
Calculation checks
Do line items, net totals, taxes, charges, discounts and invoice totals reconcile?
PDF and XML consistency
Does the visible invoice match the structured XML? Any differences must be detected and resolved.
Recipient requirements
Does the recipient require a buyer reference, purchase order reference, payment details or other process-specific data?
Exception handling
If required data is missing or a value fails a validation rule, route the invoice for review instead of passing it downstream silently.
E-invoicing mandate 2027: create ZUGFeRD invoices automatically
Under Germany’s e-invoice rules, a simple PDF alone does not meet the structured e-invoice definition. Transitional rules still apply to invoice issuance.
What matters in 2026
According to the German Federal Ministry of Finance FAQ, invoice issuers can generally continue using "other invoices" through 31 December 2026. Where the previous year's turnover does not exceed €800,000, the transition can extend through the end of 2027 under the stated conditions. German businesses have needed to be able to receive e-invoices since 1 January 2025.
ZUGFeRD as a possible target path
The Ministry lists ZUGFeRD from version 2.0.1 – excluding the MINIMUM and BASIC-WL profiles – among the common German formats that can meet the VAT requirements for an e-invoice. The correct version and profile still need to be assessed for the specific workflow.
Mandatory from 1 Jan 2027 – find out in 15 minutes what you need.
ZUGFeRD automation in practice: profiles, data and rollout
Creating a ZUGFeRD file is a technical step. Making it work reliably for every invoice, every recipient and every month-end run is a process question. The following sections explain what matters when recurring PDF invoices become validated ZUGFeRD e-invoices.
ZUGFeRD profiles explained: which one do you need?
ZUGFeRD is not a single format but a family of profiles that differ in how much structured data they carry. ZUGFeRD 2.x and the French Factur-X standard are technically aligned, so the same profile names appear in both.
Which profile is right depends on the recipient and the invoice content. Many B2B workflows use the EN 16931 profile because it covers the European core invoice model. Invoices with more complex content may need EXTENDED, while some public-sector recipients expect the XRECHNUNG profile or a pure XRechnung file instead.
- MINIMUM and BASIC WL: contain header data only, without invoice lines. Under the German e-invoice rules they are not considered e-invoices and are mainly relevant as accounting aids.
- BASIC: adds invoice lines with a reduced set of fields for simple invoices.
- EN 16931 (formerly COMFORT): maps the European standard for electronic invoices and is the usual target for B2B invoices in Germany.
- EXTENDED: extends EN 16931 with additional fields for complex scenarios, for example more detailed delivery or allowance information.
- XRECHNUNG: embeds data that follows the German XRechnung specification, for recipients that require it.
Which invoice data a ZUGFeRD e-invoice needs
A ZUGFeRD e-invoice is only as good as the data behind it. Most of the required values are already printed on the PDF invoice, but some are not visible in a form that software can use directly.
- Seller and buyer: names, addresses and VAT identification numbers or tax numbers
- Invoice identification: invoice number, invoice date, invoice type (invoice or credit note) and currency
- Delivery or service date or period
- Invoice lines: description, quantity, unit, net price and line total
- Tax information: VAT category and rate per line, taxable amounts and tax totals per rate
- Totals, allowances and charges, prepaid amounts and the amount due
- Payment terms and payment details such as the IBAN
- References the recipient requires, for example a buyer reference or purchase order number
Where the PDF alone is not enough
A PDF invoice is designed to be read by people. Some values that are obvious to a reader have to be translated into defined codes for the structured part. Units written as "pcs" or "Stk." must be mapped to standard unit codes, VAT categories must be expressed as codes rather than text, and countries and currencies need their standard identifiers.
Other values are not on the PDF at all, such as a buyer reference that a particular customer requires. In these cases PEDIF can add information from rules or master data, for example a fixed reference per customer. Where a value cannot be determined reliably, the invoice is routed for review instead of being completed by guesswork.
Typical issues when switching from PDF to ZUGFeRD
Most problems in ZUGFeRD projects are not caused by the XML format itself, but by details that a PDF tolerates and a structured invoice does not.
- Rounding differences between line totals, tax amounts and the invoice total
- Discounts or surcharges written as free text instead of defined allowances and charges
- Several VAT rates on one invoice without a clean breakdown per rate
- Credit notes and corrections that must be marked with the correct invoice type
- Missing references that the recipient needs to assign the invoice automatically
- Differences between the visible PDF and the embedded XML after manual edits
Credit notes, corrections and cancellations
Not every document in the billing process is a regular invoice. Credit notes, corrected invoices and cancellations also have to be issued as e-invoices once the obligation applies, and they have their own rules in the structured data.
A credit note is marked with its own invoice type and usually refers to the original invoice. A corrected invoice must make clear which invoice it replaces. If these documents come from the same billing system as the invoices, their layouts are often similar but not identical. PEDIF treats them as separate cases with their own recognition, mapping and validation, so that a credit note is never delivered as if it were an invoice.
- Set the correct document type for invoices, credit notes and corrections
- Carry over the reference to the original invoice where the recipient needs it
- Check signs and totals, because credit amounts are easy to invert by mistake
- Include these document types in testing before go-live, not only standard invoices
What happens on the recipient's side
The recipient's accounting or ERP system reads the embedded XML and can process the invoice without typing it in. The PDF view stays available for people who want to look at the invoice in its familiar layout.
German tax guidance treats the structured XML data as the authoritative part of a hybrid invoice. That is why PEDIF checks that the visible invoice and the XML match before an invoice is released. A mismatch is treated as an exception, not as a detail.
Archiving ZUGFeRD invoices
E-invoices have to be stored in the format in which they were issued or received, including the structured data, and must remain unchanged for the statutory retention period. For ZUGFeRD this means keeping the complete hybrid file, not only a printout or an image of the PDF view.
Because the XML carries the invoice data, archive and document management systems can also index ZUGFeRD invoices by invoice number, date, supplier or amount, which makes later searches and audits easier.
From the first invoice to steady operation
A PDF-to-ZUGFeRD workflow is usually introduced in stages, starting with the invoice layouts that occur most often.
- Collect sample invoices for each recurring layout, including credit notes and special cases
- Define the target profile and required references for each group of recipients
- Configure the layout recognition, field mapping and business rules
- Validate test invoices technically and check them against the original PDFs
- Start with selected recipients and review exceptions closely
- Extend the workflow to further layouts, sites and recipients once results are stable
One billing system, different recipient requirements
In practice, one billing run rarely goes to recipients with identical requirements. Business customers may accept ZUGFeRD, public-sector clients may require XRechnung with a Leitweg-ID, some customers expect invoices over the Peppol network and others upload them to their own supplier portal.
Instead of building a separate export for every case in the source system, PEDIF can create the required format per recipient from the same recurring PDF invoice. The recipient-specific rules, such as the target format, profile, mandatory references and delivery channel, are maintained once and applied automatically to every invoice for that recipient.
How to check a ZUGFeRD invoice
A ZUGFeRD invoice looks like a normal PDF in any viewer, so the structured part is easy to overlook. A few checks show whether an invoice is really a valid e-invoice:
- The PDF contains an embedded XML attachment, which PDF viewers usually list under attachments
- The file is a PDF/A-3 document, the archive format that allows the embedded XML
- The XML declares a profile that the recipient accepts, and not MINIMUM or BASIC WL for German e-invoices
- The XML passes validation against the schema and the business rules of that profile
- Invoice number, dates, totals and tax amounts in the XML match the visible PDF
FAQ: creating ZUGFeRD invoices automatically
Can a PDF invoice be converted to ZUGFeRD?
Is a normal PDF invoice already a ZUGFeRD invoice?
Can the existing PDF invoice layout be retained with ZUGFeRD?
What is the difference between PDF to ZUGFeRD and PDF to XRechnung?
What data does PEDIF need to turn PDF invoices into ZUGFeRD?
Next step
Check a PDF invoice
We review the recurring layout, mandatory data, intended ZUGFeRD target path and downstream workflow. The first step is a technical process and document check – not legal advice and not a blanket promise that every invoice can be automated.
Check a PDF invoiceContact 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.