`BR-DEC-10`Allowance total is written with more than two decimal places

Mutabiq checks Saudi ZATCA Phase 2 e-invoice XML before you submit it: pre-validation against published ZATCA requirements, not an approval by the authority. This page explains one rule, BR-DEC-10.

Validate 5 invoices free

Five checks a month on the Free plan. The file is checked in memory and is never stored.

The message ZATCA prints

[BR-DEC-10]-The allowed maximum number of decimals for the Sum of allowanced on document level (BT-107) is 2.

What Mutabiq reports

One entry for each way this rule can be reported.

Reported as: What kind of value was found — empty, not_15_digits and the like — never the value itself.

Allowance total is written with more than two decimal places

Reported asmore_than_two_decimalsmore than two decimal places

What is wrong

The cbc:AllowanceTotalAmount in the document totals block - BT-107, the sum of the document level discounts - carries more than two characters after its first full stop, and ZATCA flags it under EN 16931 rule BR-DEC-10 as a warning, which does not by itself reject the document. The rule counts the characters after the first full stop in the element's text rather than judging the value, so a third digit fails even when it is a nought, and a value written with no full stop at all passes however large it is. An absent or empty element passes as well. This element sums the document level allowances only; the discounts on individual lines are already inside the line amounts and are not counted again here. It sits in cac:LegalMonetaryTotal beside five other amounts with two-decimal rules of their own, so it is common to see this finding together with BR-DEC-09, BR-DEC-12 or BR-DEC-14.

What to check in your ERP

There are two shapes to look for and they need different fixes. If your totals routine adds the document allowances up, the fraction has come in from the individual discount amounts - round each cbc:Amount to two decimals first, then sum the rounded values, which is also what BR-CO-11 requires, since it compares this total against the allowances the document actually carries. If instead this total is derived by subtraction, calculated as the line sum minus the tax-exclusive total, then it is inheriting a fraction from whichever of those two is itself unrounded, and the fix belongs there rather than here. A discount converted from another currency is the third common source.

The clause that runs

Quoted from the validation-rule stylesheet ZATCA publishes, at the file and line named below. The executed guard is what the check runs; the reported test is what it prints when it fails, and the two are not always the same.

Executed guard

not(string-length(substring-after(cbc:AllowanceTotalAmount,'.'))<=2)

Reported test

string-length(substring-after(cbc:AllowanceTotalAmount,'.'))<=2

Evaluated against: cac:LegalMonetaryTotal
Source: vendor/zatca/schematron/CEN-EN16931-UBL.xsl:506
As shipped in ZATCA SDK 3.4.8: the copy quoted here is, byte for byte, the file that release ships. The date in the file name is the name ZATCA gives the file; the rules in it are those of SDK 3.4.8.

A worked example

A synthetic document from the measured test corpus that trips this rule, shown where it differs from one that passed. Mutabiq's report names the class of the value, never the value itself.

Document: bad-88-allowance-total-decimals.xml
Mutabiq's verdict: Passed
Reported as: more_than_two_decimalsmore than two decimal places

Download this example (.xml)Check it in Mutabiq

This page's example, checked by the same rules your own upload goes through. No upload and no sign-in.

Rules evaluated against the same part of the document. One wrong value often reports several of them at once.

Check an invoice

Check your own invoice