One cent is enough for an XRechnung to be rejected. The result is rarely "wrong"; almost always the order of calculation differs: the validation rules calculate differently from many ERP and shop systems.
The calculation the check expects
KoSIT writes in its XRechnung FAQ (in German) that EN 16931-1 assumes net + VAT = gross on document level; the reverse way (gross − VAT = net) or a calculation on line level is not supported by the model. So the check goes in this order:
- Line: quantity × net price − allowances + charges = line net amount (BT-131), rounded to the cent.
- Sum of lines (BT-106) = sum of the rounded BT-131.
- Total without VAT (BT-109) = BT-106 − document allowances (BT-107) + document charges (BT-108).
- VAT per rate: taxable amount (BT-116) × rate (BT-119), rounded once — not the sum of VAT amounts rounded per line.
- Total VAT (BT-110) = sum of the VAT amounts per rate (BT-117).
- Total with VAT (BT-112) = BT-109 + BT-110; amount due (BT-115) = BT-112 − paid (BT-113) + rounding (BT-114).
According to KoSIT (answer in the configuration repository, December 2025), EN 16931-1 section 6.5.13 sets three principles: document level totals are rounded to two decimals; the final result is rounded, not intermediate results; the VAT amount per category is rounded on document level and not summed from rounded line VAT amounts.
How to round
EN 16931 does not fix the rounding mode. For VAT, the German Ministry of Finance refers to the VAT application decree (UStAE) section 14.5 (20): the tax is calculated to the cent; if the next digit is 4 or less, round down, otherwise up — commercial rounding.
How strict each rule is
The rules have different tolerances. As in KoSIT's XRechnung 3.0.2 configuration (31 Aug 2026):
| Rule | What | Tolerance |
|---|---|---|
| BR-CO-10 | sum of lines | none: sum rounded to the cent, then exactly equal |
| BR-CO-13 | total without VAT | none |
| BR-CO-14 | total VAT | none |
| BR-CO-15 | total with VAT | none |
| BR-CO-16 | amount due | none |
| BR-S-08 | taxable amount per rate | CII: none; UBL: below 1.00 |
| BR-CO-17 | VAT per rate | up to 1.00 (UBL: below 1.00) |
| BR-S-09 | VAT per rate (standard rated) | below 1.00 |
| PEPPOL-EN16931-R120 | line net amount | 0.02 (HUF: 0.50); warning only |
So one cent off in the totals means rejection. For the VAT of a category, BR-CO-17 and BR-S-09 only fire from about one euro — then it is usually not rounding but the calculation or the rate that is wrong.
Why another validator says something else
- UBL and CII are two syntaxes of the same standard. KoSIT itself writes that the calculation rules may be implemented differently, so validation results may differ by syntax. Example: BR-S-08 is exact in CII and has a tolerance below 1.00 in UBL.
- Configuration version: older validators check with older rules.
- Other rule sets: ZUGFeRD validators check the FeRD profile rules, not KoSIT's XRechnung configuration.
What our check adds
The official validator only says "the sum does not match". Our recalculation follows the EN 16931 calculation for every line and total and shows where the difference comes from: a certain line, a sum of unrounded amounts, VAT rounded per line, a price including VAT.
Sources
- KoSIT, XRechnung FAQ, section "Rundung" (German): xeinkauf.de/xrechnung/xrechnung
- KoSIT, validator configuration XRechnung 3.0.2 (31 Aug 2026): github.com/itplr-kosit/validator-configuration-xrechnung
- KoSIT on EN 16931-1 section 6.5.13: issue #128; on UStAE 14.5 (20): issue #125