Free tier

← All guides · EN 16931 & validation

EN 16931 business rules explained: what BR codes mean when validation fails

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

When an EN 16931 validator rejects an invoice it names a business rule: BR-01 means the invoice number is missing, BR-16 means there are no invoice lines, and the BR-CO rules mean your totals do not add up. This guide explains the rule families this product checks — presence rules, code rules, VAT category rules and totals arithmetic — so a failure message becomes a specific, fixable instruction.

What is an EN 16931 business rule?

A business rule (BR) is a numbered, testable requirement in EN 16931: a field that must be present, a code that must come from an allowed list, or a calculation that must reconcile. EInvoice Translator implements the core BR rules in its validation engine and returns the rule identifier with every error, for example BR-16 when an invoice contains no lines (BG-25).

Presence rules: the fields an invoice may not omit

The most common validation failures are the simplest: something required is absent. BR-01 requires an invoice number (BT-1). BR-02 requires an issue date (BT-2) and that it be a real ISO date. BR-06 requires the seller's name (BT-27), BR-07 the buyer's name (BT-44), and the seller and buyer country, city and postal code fields each have their own rules, because a structured invoice is routed and booked by systems that need a complete address.

BR-16 is the structural one: an invoice must contain at least one invoice line. An invoice with totals but no lines is not an invoice under the standard — the lines are where the money is explained. In the exception workspace that this product creates for a failed conversion, each presence failure is listed with its field, so you correct the data rather than guessing. Fix presence errors first, because several later checks — totals, VAT breakdowns — only make sense once the lines exist.

Code rules: values must come from the allowed lists

Structured invoices replace free text with codes wherever a system must act on the value. BR-03 requires the invoice type code (BT-3) to be one of 380 (commercial invoice), 381 (credit note), 384 (corrected invoice) or 389 (self-billed invoice). BR-04 requires the currency (BT-5) to be a supported ISO 4217 code — this product supports EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK and NOK.

Codes fail quietly in spreadsheets and loudly in validators: a currency typed as 'Euro' or a type code of 'INV' reads fine to a person and means nothing to the receiving system. When you convert here, these checks run before any XML is generated, and the error tells you which value was rejected and why. Choosing the right type code matters beyond validation — a credit note coded as an invoice will be booked as money owed in the wrong direction.

VAT category rules: category and rate must agree

Every line carries a VAT category (BT-151) and a VAT rate (BT-152), and the rules bind the two together. The categories this product accepts are S (standard), Z (zero rated), E (exempt), AE (reverse charge), K (intra-EU supply), G (export), O (outside scope), L and M. BR-22 rejects a category outside that list. BR-S-08 requires a standard-rated line to carry a rate above zero; the zero-family rules require categories Z, E and AE to carry exactly 0.

Cross-border lines add identifier rules. If seller and buyer are in different countries and a line uses category AE, the buyer's VAT identifier is required — that is the reverse-charge evidence the buyer's tax accounting relies on. Cross-border B2B invoices also require the seller's VAT identifier. These are the failures most likely to surprise a freelancer who has sent PDFs for years: the PDF never asked, but the receiving system checks before it books anything.

Totals rules: the BR-CO arithmetic must reconcile

The BR-CO rules are the standard's arithmetic conscience. The validator computes totals from your lines: each line extension is quantity times unit price, rounded to two decimals; the tax breakdown groups taxable amounts by VAT category and rate; document allowances reduce and charges increase the tax-exclusive amount; and the payable amount is the tax-exclusive amount plus tax, minus anything prepaid.

BR-CO-13, BR-CO-14 and BR-CO-15 compare the computed tax-exclusive amount, tax total and payable amount against the totals stated on the invoice. If you typed totals by hand in a spreadsheet and one line changed afterwards, this is where the invoice dies. Converting here removes the whole class of error: totals are computed from the lines, never typed, and the generated XML is parsed back and re-checked so the file itself satisfies the same arithmetic.

Line rules: every line must stand on its own

Rules also apply line by line. Each line needs an item name (BT-153), a quantity greater than zero (BT-129) and a net price that is not negative (BT-146). A line with a zero quantity usually means a service was described but never quantified — give it quantity 1 and the agreed price. A negative line is not how you discount: discounts belong in the allowance fields, where the totals rules can see them.

Line-level thinking is the habit structured invoicing rewards. One line per distinct thing sold, each with its own VAT category and rate, produces a tax breakdown your client's system can book without queries. Mixed lines — goods and services, two VAT rates, a discount buried in a price — are where both validation failures and slow payments are born. Splitting lines costs a minute and removes both risks.

Reading a failure like an instruction, not a verdict

A validation report is a work list. Each entry gives you the rule, the field and the reason; work top to bottom, because presence fixes often clear code and totals failures that depended on the missing data. This product's exception workspace exists for exactly that loop: a failed conversion lists its exceptions, you correct values, and the invoice is re-validated rather than rebuilt from scratch.

It is also worth fixing your source template, not just the single invoice. If BR-S-08 fires because your standard lines carry no rate, the template is wrong and every future invoice will fail the same way. The rules are stable and public; once your invoice data satisfies them, conversions become routine — which is the point of a standard. Your client's system runs the same checks, so passing here means passing there.

Fixing a failed invoice in 5 steps

  1. Read the first error and note its rule code — fix presence failures (BR-01, BR-02, BR-06, BR-07, BR-16) before anything else.
  2. Check the codes: type code 380/381/384/389 and an ISO currency code your client's system supports.
  3. Match every line's VAT category to its rate — S needs a rate above 0; Z, E and AE need exactly 0.
  4. For cross-border reverse charge, add the buyer's VAT identifier, and confirm your own VAT identifier is on the invoice.
  5. Re-run the conversion and confirm the totals pass the BR-CO checks with no stated-versus-computed mismatch.

Worked example: three failures, three fixes

A consultant converts an invoice to a German client and gets three errors. BR-16 does not fire — there are two lines — but BR-S-08 fires on line 2: category S with a VAT rate of 0. The line is a standard-rated service, so the fix is the real rate, not a category change. BR-CO-15 also fires: the payable amount typed into the form is EUR 1,190.00, while the lines compute EUR 1,428.00 — an old total left over from an earlier draft.

The third failure is the cross-border identifier rule: the seller's VAT identifier is blank. Adding it, correcting the rate to 20% on the EUR 1,200.00 line (tax EUR 240.00, recomputed by the engine from the line), and letting the converter compute totals produces a clean validation: line total EUR 1,200.00, tax EUR 240.00, payable EUR 1,440.00 — every figure derived from the lines, so the BR-CO comparison passes exactly.

Frequently asked questions

What does BR-16 mean?

The invoice contains no invoice lines (BG-25 is empty). Add at least one line with a name, quantity, net price, VAT category and rate.

Why did my totals fail BR-CO-15?

The stated payable amount does not equal the computed amount: tax-exclusive total plus tax minus prepaid. Let the converter compute totals from the lines instead of typing them.

Can I use a negative line for a discount?

No — line net prices must not be negative. Use the document allowance fields so the discount appears in the totals arithmetic correctly.

Which VAT categories are supported?

S, Z, E, AE, K, G, O, L and M. Category and rate must agree: S requires a rate above zero; Z, E and AE require a rate of exactly 0.

Does passing validation here guarantee my client accepts the invoice?

It guarantees the invoice satisfies the EN 16931 core rules this engine implements and that the XML re-checks cleanly — the same checks receiving systems run. Acceptance also depends on the channel and mandate timing, which the acceptance checker covers.

Keep going

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

Related guides

← Back