IBR-038

PINT AE validation rule for UAE e-invoices

What it means

Every charge on the whole invoice must have a reason, given as text or as a reason code.

How to fix it

Add a reason or a reason code to each document level charge.

The official wording of this rule is in the PINT AE specification published by OpenPeppol.

In Alya Books

Alya Books builds the invoice XML so this holds; the official rule files confirm it on our sample documents.

بالعربية

يجب أن يكون لكل رسم على مستوى الفاتورة سبب، يُذكر نصاً أو برمز سبب.

أضف سبباً أو رمز سبب إلى كل رسم على مستوى الفاتورة.

See this rule in the interactive reference, or pre-check an invoice file.

Create compliant e-invoices with Alya Books

Explanations are Alya Books's own. The PINT AE specification is published and owned by OpenPeppol. This page is a reading aid, not legal or tax advice. Checked against Schematron release 2026.5.