PEDIF can generate a configured, human-readable PDF representation from structured input data.
Structured files such as XML or EDI messages are often difficult for people to read and may need an appropriate visual representation for review or communication.
Legal or manual approval steps often require a PDF format that humans can easily read and understand.
Structured file (XRechnung, XML, EDIFACT, ZUGFeRD, etc.)
PEDIF reads the data and checks it against defined structure and required-field rules
The data is rendered into the configured, readable PDF layout
Sends PDF via email, API, or archive system
XRechnung, EDIFACT, UBL, ZUGFeRD, XML, JSON
Processing time and throughput converting files to PDF often in seconds, not minutes
Structured input data and variants are specified for the target workflow
Input data and output can be checked against selected rules and required fields
A readable PDF output is generated using the agreed layout
Hosted in Germany, GDPR-compliant. Read more: https://www.pedif.digital/en/security.
Flexible delivery: Email, SFTP, AS2, or direct API integration
Status, validation and exceptions can be made visible for operations.
Structured files are made for systems, not for people. As soon as someone has to check, approve, archive or forward such a file, a readable representation is needed. The following sections describe when X to PDF is useful and what to consider.
The PDF shows the information that people need to understand the document: parties, document number and dates, references, line items with quantities and prices, taxes, totals and payment terms. Which fields are shown, in which order and with which labels is agreed for each document type.
The layout can follow your corporate design, for example with your logo, fonts and colours, so the generated documents look consistent with the rest of your communication.
For e-invoices, the structured file remains the legally relevant original. The generated PDF is a readable representation of its content. It is useful for review, approval and communication, but it does not replace archiving the original XML file. Keeping this distinction clear avoids problems in audits.
Because the PDF is generated directly from the structured data, it shows exactly what the file contains. Values are not retyped or reinterpreted along the way.
Structured files come in many variants. XRechnung exists in two syntaxes, ZUGFeRD carries its data as embedded XML, EDIFACT messages use their own segment structure, and many systems export their own XML or JSON formats. PEDIF reads the agreed input formats and maps them to one consistent representation, so the resulting PDFs look the same regardless of the source format.
Before a PDF is generated, the input file is checked against the expected structure and required fields. A file with missing or contradictory data is not silently turned into a document that looks complete. It is flagged, so the problem can be clarified with the sender.
In many companies, invoices are approved by people outside accounting, for example project managers, purchasers or department heads. They need to see what is being charged, but they should not have to deal with XML. A readable PDF that is generated automatically and delivered into the approval workflow keeps the process fast and avoids queries about what an invoice actually contains.
E-invoice viewers display the content of a single file on screen. That helps for occasional checks. X to PDF is designed for recurring processes: files are converted automatically as they arrive, the layout follows your design, and the PDFs are delivered to the right place, such as an archive, a mailbox or an approval system, without anyone opening a viewer.
A new layout starts with the document type and its most important fields. Together with you, it is defined which information appears in the header, how line items are shown, which totals and tax details are listed and where references such as order or delivery note numbers are placed. The layout is then tested with real files from your process, including special cases such as credit notes or invoices with many lines, before it goes live.
Moving to structured formats does not mean that people stop needing documents they can read. Approvals, queries and audits still rely on a clear view of what was ordered, delivered or invoiced. X to PDF bridges this gap: systems keep working with the structured data, while people get a consistent, readable document whenever they need one.
Archive and document management systems often display PDFs better than XML files. Storing a readable PDF next to the original structured file makes documents easier to find and view later, for example during an audit or when a customer asks about an old invoice. The structured original remains the authoritative record, and the PDF serves as the convenient view of it.
Generated PDFs can be delivered by email, via SFTP or AS2, through an API or directly into an archive or document management system. The delivery route is agreed per use case, so the PDF arrives where it is actually needed, for example in an approval workflow or a customer service mailbox.
