Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| Series ref. BR-41 | Fatal (error) | cac:LegalMonetaryTotal |
Schematron ID: ibr-012 | Field: cbc:LineExtensionAmount (Sum of Invoice line net amount, IBT-106) |
||
Classification
Transaction Data — this is a calculated total generated at invoice creation, not a stored master data value, and it changes on every document.
What the Rule Is Checking
The rule requires that cac:LegalMonetaryTotal carries a cbc:LineExtensionAmount element — the sum of every invoice line's net amount before document-level allowances, charges, or VAT. This is one of six monetary totals PINT-AE expects in the LegalMonetaryTotal block, and it is the one every other total in that block is arithmetically anchored to. An invoice can carry a payable amount and a tax-inclusive total and still fail this rule if the underlying line-sum figure is missing.
Why This Rule Exists
The sum of line net amounts is the bridge between line-level detail and document-level totals. Tax authorities and buyers' accounts payable systems both use it as the reconciliation point: line items add up to this figure, this figure plus allowances, charges, and VAT produces the payable amount. Omit it, and there is no single verifiable number connecting the line detail to the summary — an auditor or an ASP validating the invoice has nothing to check the line arithmetic against.
UAE Data Example
PASSES ✓: cac:LegalMonetaryTotal includes <cbc:LineExtensionAmount currencyID="AED">12500.00</cbc:LineExtensionAmount>, matching the sum of the individual invoice lines.
FAILS ✗: The LegalMonetaryTotal block contains TaxExclusiveAmount, TaxInclusiveAmount, and PayableAmount, but no LineExtensionAmount — an outcome seen when an ERP's tax engine populates only the totals it treats as customer-facing and drops the intermediate calculation field.
What Your ERP / IT Team Must Ensure
Confirm the invoice generation logic writes all six LegalMonetaryTotal fields, not just the ones visible on a printed invoice layout. Test this specifically against invoices with document-level allowances or charges, since these are the cases most likely to expose a mapping that only populates the final payable figure. Reconcile LineExtensionAmount against the sum of line net amounts in every test batch before go-live — a mismatch here usually means a rounding or currency-conversion fault upstream.
Related Rules
ibr-147-ae governs how each individual invoice line's net amount must be calculated. ibr-104-ae requires the line amount in AED for lines carrying VAT information.