Source: PINT-AE BIS Invoice v1.0.2 Schematron

Rule at a Glance

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

Classification

Transaction Data — The invoice total amount with tax (IBT-112) is the gross invoice value inclusive of all taxes. It is one of three mandatory totals in cac:LegalMonetaryTotal and is the figure most visible to the buyer as the amount they owe before any prepayments are netted off.

What the Rule Is Checking

BR-14 fires when the cac:LegalMonetaryTotal block does not contain a cbc:TaxInclusiveAmount element. This element holds IBT-112: the sum of IBT-109 (net total) plus IBT-110 (total VAT amount), adjusted for any document-level rounding (IBT-114). The schematron validates presence, not arithmetic correctness — separate calculation rules (BR-CO series) verify the mathematical relationships.

In the UAE context, IBT-112 represents the total amount a buyer must settle before the network of prepayments and credit adjustments is applied to arrive at IBT-115 (the amount actually due).

Why This Rule Exists

IBT-112 is required by both the UBL specification and the PINT-AE mandatory field list. The FTA uses it as the primary audit anchor for verifying that the invoice has correctly added VAT to the net amount. It also drives the buyer's accounts payable posting: without IBT-112, an ERP system cannot determine the total liability to record against the supplier.

For the ASP's clearance engine, IBT-112 is a cross-reference point: the system checks that IBT-112 equals IBT-109 plus the sum of cac:TaxTotal/cbc:TaxAmount values (within the permitted rounding tolerance). A missing IBT-112 makes this check impossible and triggers a fatal rejection.

Standard / Code List

No code list applies. The value is a decimal amount in the invoice currency (IBT-005, ISO 4217). Negative values are permitted only on credit notes where the total credit exceeds the taxable base. See ISO 4217 currency codes in PINT-AE.

UAE Data Example

PASSES ✓
<cac:LegalMonetaryTotal>
  <cbc:TaxExclusiveAmount currencyID="AED">20000.00</cbc:TaxExclusiveAmount>
  <cbc:TaxInclusiveAmount currencyID="AED">21000.00</cbc:TaxInclusiveAmount>
  <cbc:PayableAmount currencyID="AED">21000.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
(AED 20,000 net + AED 1,000 VAT at 5%)

FAILS ✗
<cac:LegalMonetaryTotal>
  <cbc:TaxExclusiveAmount currencyID="AED">20000.00</cbc:TaxExclusiveAmount>
  <!-- TaxInclusiveAmount omitted — BR-14 fires as fatal -->
  <cbc:PayableAmount currencyID="AED">21000.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>

What Your ERP / IT Team Must Ensure

  • Map cbc:TaxInclusiveAmount from the gross invoice total field in your ERP billing document — this is the post-tax, pre-payment-adjustment figure.
  • In SAP SD/FI, this is the WMWST (tax amount) plus NETWR (net value) from the billing document header; in Oracle AR, it is the TOTAL_TAX plus AMOUNT field on the transaction.
  • Verify that your UBL builder does not confuse IBT-112 with the line-extension amount (IBT-109 equivalent at line level); they are structurally different fields.
  • Where rounding differences exist between the sum of line-level taxes and the document total, IBT-114 (rounding adjustment) must absorb the difference — do not silently adjust IBT-112.
  • Include IBT-112 in your pre-submission validation checklist; its absence causes a fatal rejection at the ASP gateway before the invoice reaches the buyer.

Related Rules

BR-13 (IBT-109 — net total without tax), BR-15 (IBT-115 — amount due for payment), BR-CO-15 (mathematical relationship between IBT-112, IBT-109, and IBT-110). See also 51 mandatory fields in PINT-AE.