`BR-DEC-14`Tax-inclusive 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-14.

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-14]-The allowed maximum number of decimals for the Invoice total amount with VAT (BT-112) 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.

Tax-inclusive total is written with more than two decimal places

Reported asmore_than_two_decimalsmore than two decimal places

What is wrong

The cbc:TaxInclusiveAmount in the document totals block - BT-112, the invoice total including VAT - carries more than two characters after its first full stop, and ZATCA flags it under EN 16931 rule BR-DEC-14 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 total is not a figure of its own: BR-CO-15 requires it to be the tax-exclusive total plus the invoice total VAT amount, so it inherits whatever precision those two carry. It is also the figure the QR code's fourth field states, and the one the payable amount is derived from, which is why a fraction here tends to appear again further down the document.

What to check in your ERP

Do not format this element on its own. It is a sum of two numbers, so if it prints three decimals then at least one of its inputs does too, and rounding only the printed copy will put it a fraction away from that sum and draw BR-CO-15 instead of this. Round the tax-exclusive total and each VAT amount to two decimals first, add the rounded figures, and let this element be their sum. Where the difference is genuinely a rounding one - cash collection to a whole riyal, for instance - the element for it is cbc:PayableRoundingAmount further down the same block, applied to the payable amount and not to this one.

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:TaxInclusiveAmount,'.'))<=2)

Reported test

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

Evaluated against: cac:LegalMonetaryTotal
Source: vendor/zatca/schematron/CEN-EN16931-UBL.xsl:532
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-90-tax-inclusive-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