# PDF to UBL XML: workflow, validation, and review before sending - Date: 2026-05-17 - Reading time: 7 min read Convert PDF invoices to UBL XML with validation, review steps, and practical checks before sending e-invoices. ## Article overview This article explains PDF to UBL XML: workflow, validation, and review before sending as a practical reference for European e-invoicing. It defines the topic in plain language, places it in the compliance context, and connects the explanation to invoice formats such as XRechnung, ZUGFeRD/Factur-X, UBL, and CII. Use the article as a starting point before changing a finance or ERP workflow: identify the applicable country rule or standard, decide which structured format is expected, validate the generated XML, and keep a documented exception process for invoices that require manual review. Searching for PDF to UBL usually means one of two things: you have invoice PDFs from an existing billing process, or you receive supplier PDFs and need structured UBL XML for compliance, exchange, or archiving. The practical answer is not to pretend that every PDF can become a perfect e-invoice automatically. A good workflow extracts invoice data, maps it to UBL, validates it against the right rules, and gives people a clear review step before the invoice is sent. ## How to use this guide Use the article as a starting point before changing a finance or ERP workflow: identify the applicable country rule or standard, decide which structured format is expected, validate the generated XML, and keep a documented exception process for invoices that require manual review. ## Why PDF to UBL matters UBL XML is structured invoice data. Unlike a PDF, it is designed for software to read, validate, route, and archive. That is why many e-invoicing networks and public-sector workflows depend on UBL-based formats. For many teams, the source invoice is still a PDF. Replacing the ERP or billing system just to produce UBL can be expensive and disruptive. A conversion workflow lets the existing process stay in place while adding the structured output needed for e-invoicing. - Keep the current billing or supplier intake process where it already works. - Create UBL XML from invoice PDFs for systems that require structured data. - Validate the result before it reaches a customer, portal, or Peppol access point. - Flag uncertain fields for manual review instead of hiding risk. ## A practical PDF to UBL workflow A dependable workflow has distinct steps. Each step should make the invoice more machine-readable and more reliable, without claiming that source quality no longer matters. - Upload or ingest the source PDF invoice. - Extract header data, parties, totals, tax details, payment terms, references, and line items. - Normalize the data into the business terms expected by UBL and EN 16931-based profiles. - Generate UBL XML with the correct identifiers, currencies, tax categories, dates, and totals. - Run validation against the target format and business rules. - Review warnings, uncertain fields, and validation errors before sending. - Export or send the approved UBL XML through the required channel. ## What needs review Review is not a weakness in the process. It is the control that prevents bad source data, unusual layouts, OCR mistakes, or missing legal fields from becoming rejected e-invoices. The highest-risk areas are usually fields that affect tax, routing, payment, or legal validity. - Buyer and seller identifiers, including VAT IDs, registration numbers, and Peppol IDs. - Invoice number, issue date, due date, delivery date, and service period. - Line descriptions, quantities, unit prices, discounts, charges, and tax categories. - VAT rates, taxable amounts, tax totals, and payable amount. - Purchase order references, contract references, project references, and buyer references. - Bank details, payment means, payment terms, and remittance information. ## Validation before sending UBL XML can be well-formed but still wrong for the receiving workflow. Validation should check XML syntax, schema rules, profile rules, and business rules that decide whether the invoice can be accepted. For European e-invoicing, many UBL invoices are checked against EN 16931-based rules and Peppol BIS Billing 3.0 rules. The exact target depends on where the invoice is going and what the receiver requires. - XML must be well-formed and use the expected UBL namespaces. - Mandatory business terms must be present. - Totals must add up across lines, allowances, charges, VAT, and payable amount. - Codes must come from accepted code lists. - Buyer, seller, tax, and payment data must meet the selected profile rules. - Warnings should be visible to reviewers, not buried in logs. ## PDF to UBL and UBL to PDF are different jobs PDF to UBL turns visual invoice content into structured invoice data. UBL to PDF does the reverse: it renders structured invoice data into a human-readable document. Both can be useful, but they solve different problems. If compliance, routing, or Peppol exchange is the goal, the UBL XML is the critical artifact. The PDF is useful for people, but the structured XML is what systems validate and process. ## Official sources for UBL and Peppol UBL is maintained by OASIS. The UBL 2.1 specification is available at [OASIS UBL 2.1](https://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html). Peppol BIS Billing 3.0 defines the Peppol billing rules used by many European e-invoicing workflows. The official documentation is available at [Peppol BIS Billing 3.0](https://docs.peppol.eu/poacc/billing/3.0/bis/). Use these sources to understand the target rules. Use conversion and validation software to apply them consistently to real invoices. ## How Invoice Converter fits Invoice Converter is built for teams that need e-invoicing compliance without replacing the systems that already create or receive invoices. The workflow focuses on conversion plus validation, with review where source data is incomplete or uncertain. That means PDF invoices can become UBL XML, but the process still treats edge cases seriously. Low-quality scans, unusual invoice layouts, missing references, or unclear tax data should be flagged before the invoice is sent. - Convert invoice PDFs into structured e-invoice data. - Validate outputs before sending. - Review extracted fields and exceptions. - Use one workflow for manual checks and API-based automation. ## Convert PDF invoices to UBL XML with validation Use Invoice Converter to create structured UBL XML from PDF invoices, check the result, and review issues before sending. [Try PDF to UBL](/en/pdf-to-ubl)