EN16931 / XRechnung / Peppol BIS 3 Validator

UBL-DT-01: Amounts shall be decimal up to two fraction digits

fatal UBL auto-fix

What this error means and how to fix it

A UBL data type rule: an attribute or value format is not allowed in EN 16931 (for example a scheme attribute or the number of decimals). This is an error: the invoice is rejected until it is fixed.

Check your invoice against UBL-DT-01 — free

Runs the KoSIT validator 1.6.3, unmodified · result in seconds · the file is not stored · No file at hand? Try a sample invoice

Automatic fix: 9 € per file (excl. VAT where applicable). Amounts with more than 2 decimals are rounded to 2 decimals. Unit prices (BT-146) and price allowance base amounts keep their precision, as the rule allows. The result page shows which errors the repair removes and whether the corrected file then passes — before you pay. Many files? Pilot and Repair API.

Rule text

[UBL-DT-01]-Amounts shall be decimal up to two fraction digits

Automatic repair

Amounts with more than 2 decimals are rounded to 2 decimals. Unit prices (BT-146) and price allowance base amounts keep their precision, as the rule allows.

This rule is in the deterministic set of our repair engine (UBL 2.1; measured 2026-10-23: XRechnung 15 broken test invoices accepted after repair, 45 valid invoices unchanged; Peppol BIS Billing 3: 10 official examples unchanged, 40 mutated invoices: 36 accepted after repair, 4 rejected as expected — one documented limit, two with the repair parameter switched off, one where no address could be derived; profile conversion of 33 XRechnung test invoices to Peppol: 30 accepted). For UN/CEFACT CII (Factur-X / ZUGFeRD EN 16931 XML, XRechnung CII) the engine repairs the totals chain, VAT breakdown, rounding, decimals and element order (measured 2026-10-24: 53 valid CEN and XRechnung CII invoices unchanged; 28 broken invoices: 27 accepted after repair, 1 rejected as expected because a VAT exemption reason cannot be derived). Single files: 9 € on the result page; many files: the Repair API — see Pricing.

Where the rule is checked (XPath context and test)
SyntaxSeverityContext (XPath)Test (XPath)
EN16931-UBLfatal//*[ends-with(name(), 'Amount') and not(ends-with(name(),'PriceAmount')) and not(ancestor::cac:Price/cac:AllowanceCharge)]string-length(substring-after(.,'.'))<=2

Source: EN 16931-1 Schematron, UBL syntax binding (ConnectingEurope/eInvoicing-EN16931, EUPL-1.2).

Check your invoice against this rule