Free tier

← All guides · EN 16931 & validation

How to validate an e-invoice before you send it (and read the errors)

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

To validate an e-invoice, run its data against the EN 16931 business rules: required fields present, codes from the allowed lists, VAT category and rate in agreement, cross-border identifiers in place, and totals that reconcile under the BR-CO arithmetic — then parse the generated XML back and check the file itself. Validating before you send turns a client-side rejection into a two-minute fix at your desk.

What does e-invoice validation mean?

Validation is the automated checking of an invoice against the EN 16931 core business rules (BR), producing either a pass or a list of named rule failures. EInvoice Translator validates the invoice data, generates the UBL 2.1 XML only on a pass, then re-validates by parsing the XML back — and records any failures in an exception workspace for correction.

Why validate before sending, not after

Every structured invoice gets validated — the only question is where. If your client's system is the first to check, a failure becomes a rejected invoice, a stalled payment and a conversation you did not want. If you validate at creation, the same failure is a form field highlighted while the invoice is still yours to edit. The checks are identical; the cost of the finding differs by weeks.

Validation also protects the relationship. Clients in mandate countries run payables processes tuned for clean data; suppliers whose invoices pass first time are, visibly, the easy ones to pay. A supplier whose invoices routinely bounce generates exception work, and exception queues are where invoices go to be paid last. Pre-validation is a small discipline with a cash-flow return.

The five families of checks

First, presence: invoice number, issue date, seller and buyer names, countries, cities and postal codes, and at least one line. Second, codes: the invoice type code must be 380, 381, 384 or 389, and the currency a supported ISO code. Third, line integrity: each line needs a name, a positive quantity, a non-negative net price, a valid VAT category and a rate that agrees with the category.

Fourth, cross-border identifiers: seller's VAT identifier on cross-border B2B invoices, and the buyer's VAT identifier when a line uses reverse charge (AE). Fifth, arithmetic: the BR-CO rules compare stated totals against totals computed from the lines — line extensions, tax breakdown per category and rate, allowances, charges and the payable amount. An invoice that passes all five families is an invoice a receiving system can book without a human question.

The second pass: checking the file, not just the form

Data that validates can still become a bad file if generation goes wrong — a field mapped to the wrong element, a total written from a stale value. That is why this product parses the generated UBL XML back and validates what the file actually contains. The file, not the form, is what your client receives, so the file is what gets the final verdict.

The same paranoia applies to the Factur-X PDF: its embedded XML is extracted in testing to prove the attachment is really present and identical. When you download the pair — XML and PDF — both have been checked as artefacts. If you ever build your own pipeline, copy that pattern: validate inputs, generate, then validate outputs as if you did not trust yourself, because the receiving system will not.

Fixing failures in the right order

Work the list top-down, in dependency order. Presence first: a missing line or party field makes downstream checks meaningless. Codes next, because a wrong type code can misrepresent the whole document — a credit note coded 380 is not a small error. Then line-level VAT agreement, then identifiers, then totals last, because totals failures often evaporate once the lines are right.

The exception workspace built into a failed conversion here follows that logic: each failure is an item with its field, rule and message, and corrections re-validate the invoice rather than restarting it. Keep the same order when you fix your template afterwards — validation failures are usually template failures repeated, and fixing the source ends the series.

What validation cannot tell you

Validation proves the invoice is well-formed and rule-consistent; it does not prove the invoice is commercially right. It will not notice that you billed the wrong client, charged the wrong price, or described work you did not do. It also does not prove channel acceptance: a Peppol send, an SdI submission or a KSeF filing each adds platform-specific checks on top of the EN 16931 core.

And validation does not deliver anything. The validated file still has to travel — by portal, platform, Peppol through your own Qvalia account, or email where the client accepts files. Treat validation as the gate before dispatch: necessary, mechanical, and most valuable exactly because it is boring. Passing it quietly, every time, is the goal.

Making validation a habit, not an event

The end state is not 'we validated the big invoice' — it is a billing run where validation is simply a step, like numbering. Convert through a tool that validates by construction, keep totals computed rather than typed, and fix templates at the first repeated failure. Pro's bulk conversion applies the same checks across up to 200 invoices in one job, so a whole run either passes as a batch or shows you its exceptions as a list.

Monitored clients close the loop over time: their acceptance status is re-checked as mandate dates approach and pass, so the invoice that was fine as a PDF last year gets flagged before the client starts requiring the structured file. Validation is a moment; readiness is the habit of never being surprised by that moment.

Validate before you send: 5 steps

  1. Enter the invoice data and run the conversion — validation happens before any file is generated.
  2. Read failures by rule code and fix in order: presence, codes, VAT agreement, identifiers, totals.
  3. Use the exception workspace to correct values and re-validate instead of re-entering the invoice.
  4. Confirm the generated XML passed the parse-back check and the Factur-X PDF embeds the identical XML.
  5. Record the validated files with the invoice number — they are the operative copies your client books.

Worked example: catching a totals failure at your own desk

A bookkeeper converts a EUR 5,000.00 services invoice: two lines, EUR 3,000.00 and EUR 2,000.00, both category S at 20%. The computed tax is EUR 1,000.00 and the payable amount EUR 6,000.00 — but the form carries a payable figure of EUR 5,950.00 copied from a quote that included a discount the lines no longer show. BR-CO-15 fires: stated 5,950.00, computed 6,000.00.

Two honest fixes exist: put the EUR 50.00 discount in the allowance field where the arithmetic can see it (making the payable EUR 5,940.00 after tax is recomputed on the reduced base), or remove it if the quote changed. Either way the correction happens before sending — not three weeks later as a client query with the payment clock stopped.

Frequently asked questions

What is checked first when validation fails?

Presence rules — invoice number, dates, party names and addresses, and at least one line (BR-16). Fix those first; later checks depend on the data existing.

Does validation check my prices?

No. It checks that quantities, prices, VAT categories and totals are consistent and rule-compliant — not that the price is the one you agreed with your client.

What is the exception workspace?

When a conversion fails here, the failures are stored as an exception list for that conversion: each with its field, rule and message, so you correct and re-validate rather than starting over.

Is a validated invoice guaranteed to be accepted?

It is guaranteed to satisfy the EN 16931 core rules this engine implements, as data and as a generated file. Channels and national platforms add their own checks on top.

Can I validate a whole billing run?

Yes — Pro's bulk conversion validates and converts up to 200 invoices per job, reporting exceptions per invoice.

Keep going

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

Related guides

← Back