qmetrics
Fatal — invoice rejected TRN & registration UAE-specific rule PINT-AE 2026.5

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

What is ibr-149-ae?

ibr-149-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 buyer (customer) party block and belongs to the TRN & registration rule group. An e-invoice that fails ibr-149-ae is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

The buyer legal registration identifier (IBT-047) MUST be provided when the scheme identifier (IBT-049-1) is '0235' and buyer electronic address (IBT-049) is not '1XXXXXXXXX' or '9XXXXXXXXX'
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 buyer (customer) party block of your UBL 2.1 invoice: 

cac:AccountingCustomerParty/cac:Party

Business terms referenced

Term ID Field Other rules
IBT-047 Buyer legal registration identifier view →
IBT-049-1 scheme identifier view →
IBT-049 Buyer electronic address view →

Field names are derived automatically from the official rule corpus.

Why this happens

The buyer-side twin of ibr-150-ae: when the buyer's electronic address uses UAE scheme 0235 (and the endpoint doesn't match the exempt patterns), the buyer's legal registration identifier is mandatory. Simplified B2C invoices are the usual exception path — but standard B2B invoices between UAE businesses must identify the buyer.

How to fix it

1. For B2B invoices, populate the buyer's PartyLegalEntity/CompanyID with type TL, EID, PAS or CD. 2. If this is genuinely a B2C/simplified invoice, check with your ASP which transaction-type flags (BTAE-02) apply instead.

Technical test condition (Schematron) 
cbc:EndpointID/@schemeID != "0235" or matches(normalize-space(cbc:EndpointID), "^[19]") or exists(cac:PartyTaxScheme/cbc:CompanyID)

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

ibr-010-ae Passport issuing country code (BTAE-19) MUST be there when Buyer legal registration identifier type ibr-080 The Buyer electronic address (ibt-049) MUST be provided. ibr-101-ae Authority name (BTAE-11) MUST be there when Buyer legal registration identifier type (BTAE-16) is Co ibr-135-ae Either Buyer identifier (IBT-046) or Buyer VAT identifier (IBT-048 ) MUST be present when the Invoic ibr-179-ae Buyer VAT identifier (IBT-048) MUST occur maximum once ibr-180-ae When scheme identifier (IBT-049-1) is '0235' and Buyer legal registration identifier (ibt-047) is pr ibr-183-ae The value in Buyer legal registration identifier type [BTAE-16] should either be 'Commercial/Trade l ibr-063 The Buyer electronic address (ibt-049) MUST have a Scheme identifier.

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.