qmetrics
Fatal — invoice rejected Document structure Shared Peppol rule PINT-AE 2026.5

How to fix ibr-018 in UAE e-invoicing

What is ibr-018?

ibr-018 is a fatal validation rule in the UAE's Peppol PINT-AE e-invoicing specification, inherited from the shared Peppol layer. It is checked against the invoice document and belongs to the Document structure rule group. An e-invoice that fails ibr-018 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

The Seller tax representative name (ibt-062) MUST be provided in the Invoice, if the Seller (ibg-04) has a Seller tax representative party (ibg-11)
UAE impact: this is a fatal rule from the shared Peppol layer, enforced in the UAE 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:

cac:TaxRepresentativeParty

Business terms referenced

Term ID Field Other rules
IBT-062 Seller tax representative name view →
IBG-04 Seller view →
IBG-11 Seller tax representative party view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
normalize-space(cac:PartyName/cbc:Name) != ''

Worried your invoices fail ibr-018?

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.