`BR-DEC-18`Payable amount 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-18.

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-18]-The allowed maximum number of decimals for the Amount due for payment (BT-115) 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.

Payable amount is written with more than two decimal places

Reported asmore_than_two_decimalsmore than two decimal places

What is wrong

The cbc:PayableAmount in the document totals block - BT-115, the amount the buyer actually has to pay - carries more than two characters after its first full stop, and ZATCA flags it under EN 16931 rule BR-DEC-18 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. Of the six amounts in this block, this is the one a human reads first and the one a payment is made against, so a fraction of a halalah in it is a practical problem as much as a validation one. BR-CO-16 requires it to be the total with VAT less the prepaid amount, plus the rounding amount where one is stated.

What to check in your ERP

Do not truncate this figure to make the rule pass, because BR-CO-16 checks the same number against its inputs and will report the difference. If the arithmetic genuinely produces a fraction, round the inputs - the tax-inclusive total and the prepaid amount - and let this be their difference. If the intention is to round what the customer pays, for instance to a whole riyal at a cash till, the standard provides an element for exactly that: put the difference in cbc:PayableRoundingAmount in this same block and let this element carry the rounded figure, which keeps the arithmetic rule satisfied and shows the reader where the adjustment came from. Check also for a payable amount taken from a payment request or a statement rather than from this invoice's own totals, since a figure with a different rounding history is the other 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:PayableAmount,'.'))<=2)

Reported test

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

Evaluated against: cac:LegalMonetaryTotal
Source: vendor/zatca/schematron/CEN-EN16931-UBL.xsl:556
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-92-payable-amount-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