`BR-DEC-09`Sum of line amounts 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-09.

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-09]-The allowed maximum number of decimals for the Sum of Invoice line net amount (BT-106) 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.

Sum of line amounts is written with more than two decimal places

Reported asmore_than_two_decimalsmore than two decimal places

What is wrong

The cbc:LineExtensionAmount in the document totals block - BT-106, the sum of the invoice lines before document level allowances, charges and VAT - carries more than two characters after its first full stop, and ZATCA flags it under EN 16931 rule BR-DEC-09 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 is one of six checks on cac:LegalMonetaryTotal: the allowance total (BT-107), the amount without VAT (BT-109), the amount with VAT (BT-112), the paid amount (BT-113) and the amount due for payment (BT-115) each have a two-decimal rule of their own, so a totals block serialised at one precision setting usually draws several of these at once. Note also that the element with the same name on an invoice line is a different figure and a different rule, BR-DEC-23.

What to check in your ERP

A long figure here rarely means this field was formatted wrongly - it means the sum was taken over line amounts that carry more precision internally than they print. Round each line net amount to two decimals first, then add the rounded values and write that total here. Summing first and rounding afterwards gives a figure that can differ from the printed lines by a halalah or two, and BR-CO-10 requires this element to equal the sum of the cbc:LineExtensionAmount values the lines actually carry, so the two rules have to be satisfied by the same rounding order. Look at the order of operations in your totals routine, and at whether a report writer formats the lines for display while the XML export reads the unformatted ones.

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

string-length(substring-after(cbc:LineExtensionAmount,'.')) > 2

Reported test

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

Evaluated against: cac:LegalMonetaryTotal
Source: vendor/zatca/schematron/CEN-EN16931-UBL.xsl:498
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-87-sum-line-net-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