`BR-DEC-23`Line net 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-23.

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

Line net amount is written with more than two decimal places

Reported asmore_than_two_decimalsmore than two decimal places

What is wrong

The cbc:LineExtensionAmount of an invoice line - BT-131, the net amount of that line after its own discounts and before VAT - carries more than two characters after its first full stop, and ZATCA flags it under EN 16931 rule BR-DEC-23 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. The element with the same name in cac:LegalMonetaryTotal is a different figure - the sum of all the lines - and has its own rule, BR-DEC-09, which is why a single mis-set precision can produce both findings at once. This is the number everything above it is built from: the document totals, the VAT breakdown and the line's own VAT amount are all derived from it, so it is worth fixing here first.

What to check in your ERP

The line net is a quantity multiplied by a net price and then reduced by the line's discounts, and each of those three can introduce a fraction: a quantity that is a weight, a duration or a volume rather than a whole number, a price held at more decimals than it prints, and a percentage discount applied to the product. Round the result to two decimals at the line, and do it before the line is used anywhere else. Where a genuine unit price needs more precision, state it against a larger base quantity in cbc:BaseQuantity rather than lengthening the price: rule packs before 2.0.0 held the price itself to two decimals under BR-KSA-DEC-05, which SDK 3.4.8 removed, and a longer price still has to produce a two-decimal line net. Check as well for a line net imported from a source document - an order line or a delivery note - at that system's precision rather than recomputed here.

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

Reported test

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

Evaluated against: cac:InvoiceLine | cac:CreditNoteLine
Source: vendor/zatca/schematron/CEN-EN16931-UBL.xsl:953
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-95-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.

ERP guides

Product names identify the systems only. Mutabiq is independent of their vendors and is not affiliated with or endorsed by any of them.

Dynamics 365 Business Central: checking the ZATCA e-invoice XML

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