Source: PINT-AE BIS Invoice v1.0.2 Schematron

Rule at a Glance

ID Severity Context (XPath)
BR-13 Fatal (error) ubl:Invoice/cac:LegalMonetaryTotal
Series reference: BR-13  |  Schematron ID: ibr-013

Classification

Transaction Data — The invoice total amount without tax (IBT-109) is one of three mandatory monetary totals that every invoice must carry. Together with the total with tax (IBT-112) and the amount due for payment (IBT-115), it forms the minimum set of financial summary fields required under PINT-AE.

What the Rule Is Checking

BR-13 fires when the cac:LegalMonetaryTotal block does not contain a cbc:TaxExclusiveAmount element. This element carries IBT-109: the net payable total after all line-level deductions and allowances but before any VAT or other tax is added. The schematron checks for the element's existence; it does not validate the arithmetic at this rule level.

The cac:LegalMonetaryTotal block is the primary financial summary section of a PINT-AE invoice. BR-13, BR-14, and BR-15 collectively mandate that this block must always contain the three key monetary figures: net total, gross total, and amount due.

Why This Rule Exists

IBT-109 is the baseline against which the tax authority verifies that the declared VAT (IBT-110) has been correctly applied. In the UAE context, the FTA and the receiving ASP (Accredited Service Provider) use this figure to cross-check that the VAT amount equals IBT-109 multiplied by the applicable rate. Without IBT-109, automated VAT validation at the clearing layer cannot be performed.

This field is also the figure that feeds directly into the supplier's VAT return output tax calculation and the buyer's input tax claim. Omitting it would break the audit chain between the invoice and the periodic VAT filing.

Standard / Code List

No code list applies. The value must be a non-negative decimal amount in the invoice currency (IBT-005, ISO 4217). See the related post on ISO 4217 currency codes in PINT-AE.

UAE Data Example

PASSES ✓
<cac:LegalMonetaryTotal>
  <cbc:LineExtensionAmount currencyID="AED">10000.00</cbc:LineExtensionAmount>
  <cbc:TaxExclusiveAmount currencyID="AED">10000.00</cbc:TaxExclusiveAmount>
  <cbc:TaxInclusiveAmount currencyID="AED">10500.00</cbc:TaxInclusiveAmount>
  <cbc:PayableAmount currencyID="AED">10500.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>

FAILS ✗
<cac:LegalMonetaryTotal>
  <cbc:LineExtensionAmount currencyID="AED">10000.00</cbc:LineExtensionAmount>
  <!-- TaxExclusiveAmount missing — BR-13 fires as fatal -->
  <cbc:TaxInclusiveAmount currencyID="AED">10500.00</cbc:TaxInclusiveAmount>
  <cbc:PayableAmount currencyID="AED">10500.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>

What Your ERP / IT Team Must Ensure

  • The UBL mapper always populates cac:LegalMonetaryTotal/cbc:TaxExclusiveAmount from the invoice subtotal field before tax is applied.
  • In SAP, this typically maps from the NETWR (net value) field in the billing document; in Oracle, from the EXTENDED_AMOUNT on the invoice header.
  • The value must use the same currency code as IBT-005 (document currency) — mixed-currency totals are not permitted.
  • Do not confuse this with line-level net amounts (IBT-131); IBT-109 is the document-level sum across all lines after document-level allowances and charges.
  • Validate this field in your pre-clearance check before submitting to the ASP, as a missing IBT-109 will cause a fatal rejection at the network layer.

Related Rules

BR-14 (IBT-112 — Invoice total with Tax), BR-15 (IBT-115 — Amount due for payment), BR-08 (seller postal address country), BR-09 (VAT breakdown mandatory). See also 51 mandatory fields in PINT-AE.