How to fix ibr-136-ae in UAE e-invoicing
What is ibr-136-ae?
ibr-136-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 TRN & registration rule group. An e-invoice that fails ibr-136-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 invoice document of your UBL 2.1 invoice:
/ubl:Invoice | /cn:CreditNote
Business terms referenced
| Term ID | Field | Other rules |
|---|---|---|
| IBT-047 | Buyer legal registration identifier | view → |
| IBT-003 | Invoice type code | view → |
Field names are derived automatically from the official rule corpus.
Technical test condition (Schematron)
not(cbc:InvoiceTypeCode = "480" or cbc:CreditNoteTypeCode = "81") or exists(cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID)
Test your invoice against ibr-136-ae now
Upload your UBL XML — we check all 302 PINT-AE rules including this one, 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.