Free tier

← All guides · EN 16931 & validation

What is EN 16931 and why does your invoice need to follow it?

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

EN 16931 is the European standard for electronic invoicing: it defines the data an invoice must carry (the semantic data model), the syntaxes it can be written in — including UBL 2.1 — and the business rules totals and fields must satisfy. An invoice that follows EN 16931 can be read automatically by your client's accounting system; a plain PDF cannot, and in a growing list of EU countries a PDF alone is now rejected.

What is EN 16931?

EN 16931 is a European standard (EN 16931-1) that specifies the core invoice model: the business terms (BT) and business groups (BG) every electronic invoice must be able to express, plus business rules (BR) that valid invoices satisfy. EInvoice Translator validates invoices against the EN 16931 core business rules implemented in its engine and outputs UBL 2.1 XML and Factur-X PDF.

Why a standard was needed at all

Before EN 16931, every country, platform and accounting package described an invoice differently. A supplier in one country sent a PDF, a portal upload or a home-grown XML file, and the buyer retyped or re-mapped it by hand. The European Commission's answer was a single core model: one list of invoice data elements that every compliant syntax must support, so a structured invoice created in one member state can be processed automatically in another.

The practical consequence for a freelancer or small firm is simple. Your client's system no longer reads your invoice the way a person reads a PDF. It parses fields — seller name, VAT identifiers, line amounts, tax breakdowns — and checks them against rules. If a required field is missing or a total does not reconcile, the file is rejected before a human ever sees it. EN 16931 is the rulebook that tells you, in advance, exactly what will be checked.

The pieces: business terms, groups and rules

The standard names every piece of invoice data. Business terms are individual fields, each with an identifier: BT-1 is the invoice number, BT-2 the issue date, BT-27 the seller's name, BT-44 the buyer's name, BT-151 the VAT category of a line and BT-152 its VAT rate. Business groups bundle related fields: BG-25 is the set of invoice lines, and each party's name and address form their own groups.

On top of the data model sit the business rules, numbered BR-01, BR-02 and so on. Some rules require a field to be present — BR-01 requires an invoice number, BR-16 requires at least one invoice line. Others govern the arithmetic: the BR-CO rules require the document totals to equal the sums computed from the lines. EInvoice Translator implements these core rules in code and names the exact rule whenever an invoice fails, so a rejection here tells you precisely what to fix.

Syntaxes: the same invoice, written as UBL or embedded in PDF

EN 16931 defines what an invoice means, not the file format that carries it. The standard allows a small number of syntax bindings, and the one this product produces is UBL 2.1 — an XML format your client's system can import directly. The same invoice also leaves here as a Factur-X PDF: a readable PDF document with the identical XML embedded inside it as factur-x.xml.

That pairing solves a real workflow problem. The human at your client's firm can open and read the PDF; their system parses the embedded XML. Because the XML is embedded byte-for-byte, what the person reads and what the machine books are the same invoice — there is no second, diverging copy. When you convert an invoice on this site you download both files, so you can send whichever your client asks for.

How validation actually works on your invoice

Validation runs in two passes here. First, the invoice data you enter is checked against the implemented EN 16931 core rules: required fields, valid invoice type codes (380, 381, 384, 389), supported currency codes, VAT category and rate combinations, and the cross-border rules — for example, a reverse-charge invoice across borders requires the buyer's VAT identifier. If anything fails, conversion stops and you get the rule and the reason.

Second, the generated UBL XML is parsed back and re-checked, so the file you download is verified as a file, not just as form data. The totals are computed from your lines — line extensions, the tax breakdown per VAT category and rate, allowances, charges and the final payable amount — and the BR-CO arithmetic rules compare those computed totals against the document totals. A mismatch is an error, not a warning you can ignore.

Who has to care, and from when

EN 16931 matters to you when your client's country makes structured e-invoicing mandatory for B2B invoices, or when a large client simply refuses PDFs. In this product's mandate table, Italy has required structured invoices through SdI since 2019, Belgium's Peppol B2B mandate runs from January 2026, Poland's KSeF phases in during 2026, France requires receiving from September 2026 and issuing for SMEs from September 2027, Germany phases issuing in across 2027 and 2028, and Spain follows in 2027 and 2028. The EU-wide ViDA backstop makes intra-EU B2B structured invoicing mandatory from 1 July 2030.

You do not need a mandate in force to benefit. A structured invoice is booked faster, queried less and paid sooner than a PDF that someone must retype. The acceptance checker on the home page answers the country question for a specific invoice date, buyer country and buyer size, using the same mandate table as the converter.

What EN 16931 does not do

The standard does not deliver your invoice. It defines the invoice, not the envelope: sending happens through channels such as the Peppol network, a national platform like Italy's SdI or Poland's KSeF, or simply by sending the file to your client. Here, Peppol sending is guided: the product builds and validates your Peppol invoice, and you send it free from your own Qvalia Connect Free account, under your own Peppol ID.

The standard also does not set your prices, your VAT rates or your payment terms. It requires that whatever you charge is expressed completely and consistently — every line with a name, quantity, net price, VAT category and rate, and totals that reconcile. Getting those mechanics right is exactly the part a converter can do for you, and it is the part that decides whether your client's system accepts the invoice or bounces it.

Your 5-step EN 16931 readiness checklist

  1. List every field your current invoice template carries and match it against the EN 16931 business terms — number, dates, both parties' names, addresses and VAT identifiers.
  2. Give every invoice line a name, a positive quantity, a net unit price, a VAT category and the matching VAT rate.
  3. Check your totals the BR-CO way: line sums, tax per category and rate, allowances and charges, and the payable amount must reconcile exactly.
  4. Convert one real invoice to UBL 2.1 and Factur-X and confirm both files validate with no rule failures.
  5. Run the acceptance checker for each client's country and note the date structured invoicing becomes mandatory for them.

Worked example: a design invoice that passes first time

Take a freelance brand designer invoicing a Belgian client: invoice INV-2026-014, issued 27 October 2026, one line — 'Brand identity design', quantity 1, net price EUR 2,400.00, VAT category AE (reverse charge) at 0%, because the service is cross-border B2B and the buyer supplies their VAT identifier. That is the exact shape of the demonstration invoice on this site's home page.

Run through the converter, the line extension is EUR 2,400.00, the tax breakdown shows category AE with a taxable amount of EUR 2,400.00 and tax of EUR 0.00, and the payable amount is EUR 2,400.00. The reverse-charge rule is satisfied because the buyer's VAT identifier is present; the totals reconcile under the BR-CO rules; and the acceptance checker reports that Belgium requires a structured invoice — so the UBL file, not a PDF, is the one to send.

Frequently asked questions

Is a PDF invoice EN 16931 compliant?

A plain PDF is not. A Factur-X PDF is different: it carries the EN 16931 invoice as embedded XML (factur-x.xml), so the file is both human-readable and machine-readable. That is the PDF this product produces.

Which EN 16931 rules does the validator check?

The core business rules implemented in the engine: required fields (for example BR-01 invoice number, BR-16 at least one line), type and currency codes, VAT category and rate consistency, cross-border VAT identifier rules, and the BR-CO totals arithmetic. Failures name the rule.

Do I need EN 16931 if my country has no mandate yet?

Not legally, until a mandate or the 1 July 2030 ViDA backstop applies — but clients in mandate countries may still require structured invoices from you as their supplier, and structured invoices are processed faster everywhere.

What is the difference between EN 16931 and UBL 2.1?

EN 16931 is the data model and rulebook; UBL 2.1 is one of the syntaxes that can carry it. This product outputs your EN 16931 invoice as UBL 2.1 XML, and embedded in a Factur-X PDF.

How much does it cost to convert an invoice?

The first conversion and the acceptance checker are free. Pro ($19/month) adds bulk conversion of up to 200 invoices per job, country rule packs, monitored clients and accounting exports; Team is $49/month.

Keep going

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

Related guides

← Back