Your bookkeeping probably still runs on PDF invoices, yet a growing share of your customers can only accept structured e-invoices. Belgium's B2B mandate, France's phased rollout, and similar rules across Europe all point the same way: invoices need to travel as structured UBL over the Peppol network. Retyping every PDF by hand is slow and invites errors. Peppolio closes that gap: upload a PDF, download a validated Peppol invoice.
How the PDF to UBL conversion works
Three things happen automatically after you upload:
Reading the invoice. AI extraction handles native PDFs and scans alike, in most European languages and any layout. It picks out the seller, the buyer, every line item, the tax breakdown, the totals, and the payment details. There are no templates to set up and nothing to train.
Building the UBL. The extracted data is written into UBL 2.1, the XML format the Peppol network runs on, using the elements and code lists the EN 16931 European standard defines: unit codes, VAT categories, and the full document and tax structure.
Checking before download. The finished file is verified against the UBL 2.1 schema, the EN 16931 business rules, and the Peppol BIS Billing 3.0 specification. What you download is not just well-formed XML, it is an invoice any Peppol participant can accept.
You stay in control
AI is quick, but it is not perfect. Whenever the engine is unsure about a value, or the PDF simply lacks something Peppol requires (the buyer's electronic address is a common example), Peppolio highlights that field for review. You correct it before sending instead of finding out through a rejection.
Your documents stay yours. Uploads and the generated UBL are held in memory only and discarded the moment your file is ready. Nothing is stored on our servers, passed to third parties, or used to train models.
Where to next
Want to write the invoice yourself instead? Create a Peppol invoice with the guided wizard. Already have UBL XML? Check it against Peppol BIS 3.0 before you send it.