How to fix aligned-ibrp-ae-09-ae in UAE e-invoicing
What is aligned-ibrp-ae-09-ae?
aligned-ibrp-ae-09-ae is a fatal validation rule in the UAE's Peppol PINT-AE e-invoicing specification — one of the UAE-specific rules. It is checked against the VAT totals and belongs to the VAT categories & rates rule group. An e-invoice that fails aligned-ibrp-ae-09-ae is rejected by the Accredited Service Provider gateway before it reaches the FTA.
What the official rule says
Where it applies
This rule is checked against the VAT totals of your UBL 2.1 invoice:
/*/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[normalize-space(cbc:ID) = 'AE'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']
Business terms referenced
| Term ID | Field | Other rules |
|---|---|---|
| IBG-23 | VAT breakdown | view → |
| IBT-118 | VAT category code | view → |
| IBT-117 | VAT category tax amount | view → |
Field names are derived automatically from the official rule corpus.
Why this happens
In a reverse-charge VAT breakdown (category AE), the VAT category tax amount must be zero — under the reverse-charge mechanism the buyer self-accounts the VAT, so the invoice itself shows no VAT amount. Stating a rate is fine; stating a non-zero VAT amount is a fatal error.
How to fix it
1. Set the VAT amount for the reverse-charge breakdown to 0. 2. Keep the taxable amount and (optionally) the rate. 3. Ensure the buyer's TRN is present — reverse charge requires an identified, VAT-registered buyer (rule ibr-103-ae).
Technical test condition (Schematron)
xs:decimal(../cbc:TaxAmount) = 0
Worried your invoices fail aligned-ibrp-ae-09-ae?
Upload your UBL XML — qmetrics runs 40+ core PINT-AE pre-submission checks (TRN, VAT math, addresses, totals and more) in one second. Your file is validated in memory and never stored.
Related rules
Rule text sourced from the official OpenPeppol PINT-AE validation artifacts (version 2026.5), refreshed weekly. Explanations are qmetrics' own guidance, not official FTA/MoF text.