PDF to Peppol automation – turn recurring PDF invoices into structured invoice workflows
Does your ERP or billing system still create PDF invoices? PEDIF recognizes approved recurring layouts, structures the required invoice data, validates the agreed target output and hands approved results to your defined Peppol workflow.
What does “PDF to Peppol” actually mean?
Peppol is not a file format. It is a network and interoperability framework for exchanging structured electronic business documents. A normal PDF invoice cannot simply be “sent through Peppol” and become a structured e-invoice. Its business data first needs to be structured, mapped to the required invoice specification and validated. Only then should the result be handed to the configured Peppol transport process.
PDF as the source
Your existing ERP, billing or legacy system keeps creating the familiar invoice PDF.
Structured invoice output
PEDIF maps relevant fields into the agreed structured target profile, based on recipient, country and workflow.
Peppol transport
The validated output is handed to the Peppol Access Point or downstream integration defined in your architecture.
Clear roles: PEDIF is described here as a PDF-to-structured output layer. A Peppol Access Point provides network connectivity and transport. This page does not claim that PEDIF itself is a certified Peppol Access Point.
How PDF to Peppol automation works with PEDIF
Not “upload a PDF and hope”, but a defined automation workflow with layout recognition, mapping, validation and a visible review path for exceptions.
1. Keep generating PDFs
The existing source system creates invoices as before.
2. Recognize the layout
PEDIF processes approved, recurring invoice layouts.
3. Structure invoice data
Header, line-item, tax, total and reference data is mapped by business meaning.
4. Map the target profile
Data is mapped to the agreed Peppol/e-invoice target structure.
5. Validate the output
Format, mandatory fields, calculations and agreed business rules are checked.
6. Hand off or review
Approved results move downstream; unclear cases enter review.
Peppol is the transport network – not the PDF file
Peppol uses a four-corner model. Sender and receiver can use different service providers or Access Points. The business document and the network transport are separate layers. For a PDF-first process, that separation is important: PEDIF prepares structured invoice data; the configured Access Point handles transmission through the Peppol network.
Peppol BIS Billing 3.0, UBL and EN 16931 – how do they fit together?
EN 16931
The European standard provides the shared semantic core model for structured e-invoice data.
Peppol BIS Billing 3.0
The Peppol invoice specification builds on EN 16931 and is used for invoice exchange in Peppol environments. The current technical documentation uses UBL syntax for invoices.
XRechnung in Germany
XRechnung is a German CIUS of EN 16931. In a Peppol context, recipient requirements, the current national ruleset and the actual document type determine the correct target.
For PEDIF, this means the target has to be clear before automation starts: which structured output the recipient accepts, which version and rules apply, and how the invoice will be transported afterward.
What invoice data is needed for a PDF-to-Peppol workflow?
Conversion cannot invent missing mandatory information. Required data needs to be reliably available in the PDF, ERP, master data or another trusted source.
Typical invoice data
- Invoice number and invoice date
- Seller and buyer information
- Invoice lines, quantities and units
- Prices, discounts, charges and allowances
- Tax categories and tax amounts
- Net, tax and gross totals
- Payment information and payment terms
Process and recipient data
- Purchase-order, contract or project references
- Delivery or service references
- Electronic addresses and recipient identifiers
- Peppol ID or required identifier scheme
- Country-specific mandatory data
- Recipient-specific business rules
- Target Access Point and handoff method
Important: if a Peppol ID, purchase-order reference or other required value is not present on the PDF, it should only be added from a predefined trusted data source. It should not be guessed.
Peppol ID and Access Point: what must be clear before sending?
Peppol ID
Organizations are addressed in the Peppol network through defined electronic identifier schemes. The exact scheme and identifier depend on the recipient and national requirements. For German public-sector recipients, Leitweg-ID-related requirements may be relevant.
Peppol Access Point
The Access Point connects a sender or receiver to the Peppol network. In a PEDIF workflow, the target Access Point or technical interface for the validated invoice output should be defined before production automation begins.
PDF to Peppol without replacing your ERP
If your ERP reliably creates PDF invoices but cannot provide the structured Peppol target output you need, you do not automatically need to replace the entire source system. PEDIF can act as an additional output layer between PDF generation and your e-invoicing/Peppol process.
Legacy and specialist systems
Useful when existing applications create stable PDFs but do not provide the required structured invoice output.
Multiple invoice layouts
Different sites or subsidiaries can activate recurring layouts in a controlled, testable scope.
Peppol as an additional channel
An existing EDI, portal or email flow does not automatically have to disappear. The target channel can be defined by recipient group.
Peppol for international invoice workflows
Peppol is used across Europe and increasingly internationally. For cross-border invoicing, a generic “Peppol-compatible” claim is not enough. Destination country, recipient, accepted document type, national rules, tax requirements and electronic addressing all need to be checked for the specific workflow.
What PEDIF can standardize
Recurring PDF recognition, field mapping, structured target output, technical validation and controlled handoff can be standardized within a defined scope.
What must be checked by country or recipient
Invoice profile, mandatory fields, national rules, recipient ID, network onboarding, tax and archiving requirements, and the permitted transmission method.
When is PDF to Peppol with PEDIF a good fit?
Good fit
- Your ERP regularly generates PDF invoices.
- Layouts are recurring and can be tested.
- Required data is present or can be supplied from trusted sources.
- The Peppol target workflow and Access Point are defined or can be defined.
- You want validation and review before handoff.
Needs a closer check first
- •PDF layouts constantly change or are difficult to read.
- •Mandatory invoice data is systematically missing.
- •The recipient format or destination-country rules are unclear.
- •No Access Point or downstream process has been defined.
- •A blanket legal compliance guarantee is expected without domain review.
Peppol, XRechnung or ZUGFeRD?
These terms solve different parts of the problem. Peppol mainly describes network interoperability and transmission; XRechnung and ZUGFeRD describe structured invoice formats or profiles. The right path depends on the recipient.
| Term | Purpose | Typical question | PEDIF role |
|---|---|---|---|
| Peppol | Network / exchange route | How does the structured invoice reach the recipient? | Prepare and hand off the structured output for the defined target process. |
| XRechnung | Structured e-invoice / German CIUS | Which structured invoice dataset is required? | Automate PDF to XRechnung |
| ZUGFeRD | Hybrid PDF/XML e-invoice | Should a readable PDF view be combined with structured XML? | Automate PDF to ZUGFeRD |
Frequently asked questions about PDF to Peppol
Is your PDF invoice workflow a fit for Peppol?
Check layout, mandatory data, recipient requirements, target profile, Access Point and validation path before automating the workflow.
Contact Us
Questions, need help choosing the right setup?
Book a Meeting
Prefer to talk directly? Pick a time that works for you.