qmetrics
Fatal — invoice rejected Currency & exchange UAE-specific rule PINT-AE 2026.5

How to fix ibr-140-ae in UAE e-invoicing

What is ibr-140-ae?

ibr-140-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 invoice document and belongs to the Currency & exchange rule group. An e-invoice that fails ibr-140-ae is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

When VAT accounting currency (IBT-006) is present, it shall be AED.
UAE impact: this is a fatal rule specific to the UAE PINT-AE profile — an invoice failing it is rejected at the Accredited Service Provider gateway before it ever reaches the FTA. A rejected invoice means resubmission delays, and late transmission risks the AED 100-per-invoice penalty under Cabinet Decision No. 106 of 2025.

Where it applies

This rule is checked against the invoice document of your UBL 2.1 invoice: 

/ubl:Invoice | /cn:CreditNote

Business terms referenced

Term ID Field Other rules
IBT-006 Tax accounting currency view →

Field names are derived automatically from the official rule corpus.

Why this happens

If the invoice states a VAT accounting currency (IBT-006 / TaxCurrencyCode), it must be AED — UAE VAT is always accounted in dirhams, even when the invoice itself is issued in USD, EUR or any other currency.

How to fix it

1. If your invoice currency is AED, you can usually omit TaxCurrencyCode entirely. 2. If you invoice in a foreign currency, set <cbc:TaxCurrencyCode>AED</cbc:TaxCurrencyCode> and provide the AED-converted VAT total.

Compliant XML

<cbc:DocumentCurrencyCode>USD</cbc:DocumentCurrencyCode>
<cbc:TaxCurrencyCode>AED</cbc:TaxCurrencyCode>
Technical test condition (Schematron) 
not(cbc:TaxCurrencyCode) or cbc:TaxCurrencyCode = "AED"

Worried your invoices fail ibr-140-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

aligned-ibrp-001-ae Specification identifier (ibt-024) MUST start with the value 'urn:peppol:pint:billing-1@ae-1' or 'ur aligned-ibrp-002-ae Business process (ibt-023) MUST be in the format 'urn:peppol:bis:billing' or 'urn:peppol:bis:selfbil aligned-ibrp-ae-01-ae An Invoice that contains an Invoice line (ibg-25), a Document level allowance (ibg-20) or a Document aligned-ibrp-e-01 An Invoice that contains an Invoice line (ibg-25), a Document level allowance (ibg-20) or a Document aligned-ibrp-o-01 An Invoice that contains an Invoice line (ibg-25), a Document level allowance (ibg-20) or a Document aligned-ibrp-s-01 An Invoice that contains an Invoice line (ibg-25), a Document level allowance (ibg-20) or a Document aligned-ibrp-sr-12 Seller tax identifier (ibt-031) MUST occur maximum once aligned-ibrp-z-01 An Invoice that contains an Invoice line (ibg-25), a Document level allowance (ibg-20) or a Document

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.