Tool · Office
E-invoice validation rules
What does BR-DE-15, BR-CO-10 or PEPPOL-EN16931-R010 mean? This page lists all 2,588 rules that the xmoo e-invoice viewer uses to validate an XRechnung or ZUGFeRD/Factur-X invoice – with the official wording, the severity and the rule sets each rule belongs to. Search for the rule ID from your validation report or for a word.
What it is for
An e-invoice is checked by software against fixed rules, not by a person. If a recipient or a portal rejects your invoice, the validation report usually shows little more than a rule ID and one sentence. This page gives the full wording for every rule ID, its group and the rule sets in which it applies, with their severity. It covers the European standard EN 16931, the German XRechnung and the Franco-German ZUGFeRD/Factur-X profiles.
How to read a message
- Rule ID – such as BR-CO-15. The part before the number tells you where the rule comes from
(list below). The search also finds it without hyphens (
brco15) or when you paste the whole message. - Fields – BT-112, BG-23 and so on are the numbers of the information elements in EN 16931: BT for a single business term, BG for a business group of terms. They appear in the rule text.
- Severity – an error (
fatalin the rules) means the invoice is invalid under that rule set. A warning leaves the invoice valid but points to something that should not be there. The same rule can have a different severity in different rule sets: BR-51 is an error in CII and a warning in UBL. Rules of the ZUGFeRD profiles without a severity count as errors, as in the viewer. - Rule set – which set applies depends on the invoice: an XRechnung is checked against EN 16931 and XRechnung, a ZUGFeRD/Factur-X invoice against the rules of its profile.
What the rule IDs mean
- BR-01 to BR-65, BR-CO-…, BR-DEC-… and BR-S-…, BR-AE-… etc. (222 rules) – the business rules of EN 16931. BR-CO rules link fields to each other, among them the calculation rules for totals and VAT (BR-CO-10 to BR-CO-17); BR-DEC rules set the allowed number of decimals. BR-S, BR-Z, BR-E, BR-AE, BR-IC, BR-G, BR-O and the others each apply to one VAT category; the rule text names it.
- BR-CL-… (23) – a code is not in the allowed code list.
- CII-SR, CII-DT, UBL-SR, UBL-DT, UBL-CR (1,347) – syntax rules for the two formats CII and UBL: what may appear in the XML and how often. The 678 UBL-CR rules name elements a UBL invoice should not contain; 676 of them are warnings.
- BR-DE-… (31) – the national rules of the German XRechnung, worded in German in the original. Plus BR-DEX-… (15) for the XRechnung extension, BR-DE-CVD-… and BR-TMP-CVD-01 (8) for vehicle categories and BR-TMP-… with BR-DE-TMP-32 (7) as temporary rules – according to the changelog, KoSIT uses some of them until an error in the EN 16931 rules is fixed.
- PEPPOL-EN16931-R… (23) – rules from Peppol BIS Billing 3.0 that XRechnung also checks, such as R010 (buyer electronic address).
- BR-FXEXT-… (62) and FX-SCH-A-… (850) – rules of the ZUGFeRD/Factur-X profiles. FX-SCH-A is an internal number; where the rule carries its own ID in the text, the viewer shows that one, and the search finds both.
Example: two errors in one invoice
The sample invoice of the viewer has a net total of 308.90 (BT-109) and VAT of 55.70 (BT-110), so 308.90 + 55.70 = 364.60 including VAT (BT-112). If the invoice says 364.61 instead, the official validation reports:
- BR-CO-15 (error, EN 16931): Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110). 364.61 is not 364.60.
- BR-CO-16 (error, EN 16931): the amount due BT-115 (364.60) has to equal BT-112 minus the amount already paid plus rounding, which would be 364.61 – so this rule fails as well.
Both are fixed by correcting BT-112 back to 364.60. If the buyer reference (BT-10) is missing as well, an XRechnung also fails BR-DE-15.
Where the rules come from
A script reads the rules from exactly the nine rule sets the viewer validates with: EN 16931 Validation Artefacts 1.3.17 for CII and UBL, XRechnung Schematron 2.6.0 for CII and UBL and Factur-X 1.09.2 (= ZUGFeRD 2.5.2) for the profiles MINIMUM, BASIC WL, BASIC, EN 16931 and EXTENDED. Nothing is typed in by hand or translated; the national XRechnung rules therefore appear in German. Where a rule inserts a value only during validation, such as the name of the element, the text shows “…”.
If the same rule is worded differently in two rule sets, both versions are shown. For BR-51, the CII set names the field BT-97, the UBL set BT-87.
Limits
- The page explains what a rule requires, not why your invoice breaks it. The validation itself tells you that: the viewer shows the location in the XML for every message.
- 872 checks in the ZUGFeRD profiles (50 different texts) have no rule ID, for example “Attribute @schemeID' marked as not used in the given context.” They are not listed; their text explains itself.
- XML schema errors (wrong order, unknown element) are not rules with an ID; the viewer reports them as XSD.
- Other validators may use other versions of the rules. Newer rules appear here once the viewer adopts them.
- The viewer itself is available in German and French so far.
Privacy: the search runs entirely in your browser. Nothing you type is sent to xmoo.app or anyone else.
Sources
- EN 16931 Validation Artefacts 1.3.17 by the European Commission (CII and UBL, licence EUPL 1.2)
- XRechnung Schematron 2.6.0 by KoSIT, with changelog on BR-TMP and Peppol BIS Billing 3.0.21 (licence Apache 2.0)
- Factur-X 1.09.2 / ZUGFeRD 2.5.2 by FNFE-MPE and FeRD, from the Python package factur-x 7.7 (BSD)
- Licence texts: EUPL 1.2, Apache License 2.0, factur-x
Page last updated: 15 November 2026