Free tier

← All guides · Formats & conversion

How to convert a PDF invoice to XML (UBL) that validates

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Convert an invoice free

Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.

Short answer

You cannot truly convert a plain PDF invoice to XML by transformation — a PDF holds a picture of the data, not the data. The reliable method is re-expression: enter the invoice's data (parties, lines, VAT treatment) into a converter, let it compute totals and validate against the EN 16931 rules, and generate the UBL 2.1 XML plus a Factur-X PDF. What you get is not a transcription of the PDF but a structured invoice that receiving systems accept.

What does PDF-to-XML conversion really mean?

In this product, conversion means building the structured invoice from the invoice's data: 'You fill in the invoice — seller, buyer, lines, VAT categories — and the product computes the totals, validates the invoice against the real EN 16931 business rules, and produces two downloads: a UBL 2.1 XML file and a Factur-X PDF.' A plain PDF contains no structured data to extract; the invoice is re-created in structured form and proven by validation.

Why the PDF itself cannot be converted

A PDF invoice stores glyphs and positions: characters that look like 'EUR 2,400.00' to a reader, with no marker saying this is the payable amount, that is a VAT rate, those are the buyer's identifiers. Tools that promise one-click PDF-to-XML are guessing at your invoice's semantics with OCR and layout heuristics — and a guessed VAT category or a misread total is worse than no XML, because the receiving system will act on the guess.

The honest conversion therefore starts from the invoice's meaning, which the issuer knows: who sold, who bought, what lines, under what VAT treatment. Entering that data takes minutes for a typical invoice, and unlike OCR output, every value is one you chose. Validation then proves the assembled invoice — something no transcription can offer, because validation checks the invoice, not the handwriting.

The workflow, step by step

Open the converter and work its sections. The invoice: number, issue date, due date, type code (380 for a normal invoice), currency. The seller: your name, address, city, postal code, country, VAT identifier. The buyer: the same for your client. The lines: one per item, each with a name, quantity, net unit price, VAT category and rate. Allowances, charges and prepaid amounts if the invoice has them — in their fields, not buried in line prices.

Submit, and validation runs before any file exists. If it passes, download the UBL XML and the Factur-X PDF. If it fails, the errors name the rules and fields; the exception workspace holds the failed conversion so you correct values and re-validate instead of re-entering everything. Either way, the PDF you started from is fully replaced: the new Factur-X PDF is the readable copy now, generated from the same data as the XML.

The traps a PDF hides

PDFs conceal exactly the defects structured validation exposes. Totals typed in a spreadsheet that no longer match the lines — BR-CO failures waiting to happen. A reverse-charge invoice with the buyer's VAT identifier nowhere on the document, because the PDF era never asked. Lines that merge two VAT treatments into one row with a blended rate. 'VAT included' prices with no category stated at all.

Expect your first conversion of an old template to fail somewhere; almost everyone's does. That failure is the conversion doing its real job — auditing the invoice you have been sending and showing you, rule by rule, why receiving systems struggle with it. Fix the template, not just the invoice, and the second conversion is the start of a clean series.

What you send afterwards

Send the pair. The UBL XML is the structured invoice: for Peppol clients it is the file you upload in your Qvalia account for the guided send; for platform and portal clients it is the ingestible artefact; for email-based clients it rides alongside. The Factur-X PDF is the human copy — and unlike your old PDF, it carries the identical XML embedded, so the readable document and the structured data can never part company.

Archive the pair together, under the invoice number, and retire the old PDF as the operative copy. In mandate countries the structured file is the invoice; keeping the relic as your primary record invites someone — a colleague, an auditor, your future self — to work from the wrong artefact.

Converting at volume: billing runs, not singles

One invoice converts in minutes; a month-end run of two hundred needs machinery. That is Pro's bulk conversion: up to 200 invoices per job, each validated with the same rules, exceptions reported per invoice. The discipline does not change — complete data in, reconciled totals out — but the unit of work becomes the run, and the exception list becomes your corrections queue.

Bulk also changes the PDF question: you are no longer converting documents one by one but re-founding the billing process on structured data. From that point, 'conversion' is a misnomer — invoices are born structured, the PDF is generated as the readable view, and the XML was never an afterthought. That inversion is the whole destination of the mandate era, reached one converted invoice at a time.

Convert a PDF invoice to XML in 5 steps

  1. Gather the invoice's data from the PDF: number, dates, both parties in full, VAT identifiers, every line with its VAT treatment.
  2. Enter it in the converter's sections — one line per item, allowances and charges in their own fields.
  3. Run the conversion and fix any named rule failures in the exception workspace; re-validate until clean.
  4. Download both outputs: the UBL XML (the structured invoice) and the Factur-X PDF (the new readable copy).
  5. Send the pair, archive them together, and retire the old PDF as the operative record.

Worked example: a legacy PDF becomes a valid invoice

A designer's PDF invoice 2026-014 shows one line — 'Brand identity design — EUR 2,400.00' — 'VAT: reverse charge' as a note, and no VAT identifiers anywhere. Entered into the converter, validation stops it: the reverse-charge line (category AE) requires the buyer's VAT identifier, and cross-border B2B requires the seller's too. Both are added from the client file.

Second pass: clean. Line extension EUR 2,400.00, AE subtotal tax EUR 0.00, payable EUR 2,400.00 — computed, not transcribed. The downloads replace the PDF: the UBL for the client's system (and a later Peppol send), the Factur-X PDF for the humans. The conversion took one correction — the exact correction the client's system would have demanded, delivered a month early and without the rejection letter.

Frequently asked questions

Can software extract the XML straight from my PDF?

Not reliably: a plain PDF has no structured data to extract, so extraction is OCR guesswork. This converter rebuilds the invoice from its data and validates it — the output is a proven structured invoice, not a guess.

Is the Factur-X PDF the same as my old PDF?

It looks like an invoice and reads like one, but it is generated from the structured data and embeds the identical XML. Your old PDF had no data layer at all.

What if my PDF invoice has many lines?

Enter them one per row — or, for whole billing runs, use Pro's bulk conversion (up to 200 invoices per job) with per-invoice exception reporting.

Why did my first conversion fail?

Because PDFs hide defects: unmatched totals, missing VAT identifiers, merged VAT treatments. Each failure names its rule; fixing the template makes later conversions pass first time.

What do I send the client — XML or PDF?

Both: the UBL XML for their system, the Factur-X PDF for their people. They are generated together from the same validated data.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back