BT-92Document level allowance amount
Official rule text
[BR-DEC-01] The allowed maximum number of decimals for the Document level allowance amount (BT-92) is 2.
Why this error occurs
The document level allowance amount must have at most two decimal places. The rule is a string check: it counts the characters after the decimal point in cbc:Amount of /Invoice/cac:AllowanceCharge with ChargeIndicator false (UBL) or ram:SpecifiedTradeAllowanceCharge/ram:ActualAmount (CII). It fires when a percentage discount is written unrounded (12.345) or when the formatter emits three decimals (10.500), even if the value is mathematically a two-decimal amount.
How to fix it
Round the allowance amount to two decimals before writing it and format it with at most two fraction digits, e.g. 12.35 or 10.5. Do the rounding in the export layer, not only in the display layer. Recompute cbc:AllowanceTotalAmount / ram:AllowanceTotalAmount (BT-107) from the rounded values so BR-CO-11 and BR-CO-13 still hold. Use a point as decimal separator, never a comma.
Example (valid)
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:AllowanceChargeReason>Volume discount</cbc:AllowanceChargeReason>
<cbc:Amount currencyID="EUR">12.35</cbc:Amount>
<cac:TaxCategory><cbc:ID>S</cbc:ID><cbc:Percent>19</cbc:Percent><cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme></cac:TaxCategory>
</cac:AllowanceCharge>What the validator checks
Checked element (context):
UBL
/ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator = false()] | /cn:CreditNote/cac:AllowanceCharge[cbc:ChargeIndicator = false()]Test (XPath):
string-length(substring-after(cbc:Amount,'.'))<=2CII
//ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator[udt:Indicator='false']Test (XPath):
string-length(substring-after(../ram:ActualAmount,'.'))<=2Check your invoice
Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.
Same check via API:
curl -F file=@invoice.xml https://einvoicechecker.com/v1/validateRelated rules
BR-31Each Document level allowance shall have a Document level allowance amountBR-AE-08In a VAT breakdown where the VAT category code is "Reverse charge" the VAT category…BR-AF-08For each different value of VAT category rate where the VAT category code is "IGIC",…BR-AG-08For each different value of VAT category rate where the VAT category code is "IPSI",…BR-CO-11Sum of document level allowances (BT-107) is wrongBR-E-08In a VAT breakdown where the VAT category code is "Exempt from VAT" the VAT category…BR-G-08In a VAT breakdown where the VAT category code is "Export outside the EU" the VAT…BR-IC-08In a VAT breakdown where the VAT category code is "Intra-community supply" the VAT…
Frequently asked questions
What does BR-DEC-01 mean?
BR-DEC-01 is a en 16931 core rule: The allowed maximum number of decimals for the Document level allowance amount (BT-92) is 2.
Will my invoice be rejected because of BR-DEC-01?
Yes. BR-DEC-01 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.
Which formats does BR-DEC-01 apply to?
Every EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles. Syntax: UBL and CII.
Source: EN 16931-1:2017 schematron (CEN TC434, via Peppol BIS 3.0.20). Catalogue generated from the official schematron on 2026-10-14.