Check PINT AE validation rules
Find the UAE invoice and credit-note rules that apply to your document and correct a rejected submission. You need its document type and any validation errors returned by Unify.
The applicable rules depend on the document type. An ordinary invoice uses PINT AE Billing invoice rules; a credit note uses its own rules. Self-billed documents use the separate PINT AE Self-Billing rules. Do not apply invoice rules indiscriminately to a credit note.
What to check before sending
| Check | Example of an applicable rule | Correction |
|---|---|---|
| Seller and buyer addresses | IBR-143-AE requires the seller’s address line 1, city and country subdivision. IBR-144-AE does the same for the buyer. | Add the missing address parts. For UAE addresses, use an allowed emirate subdivision code from the UAE code lists. |
| VAT and totals | IBR-190-AE requires a 5% rate for lines classified as standard rated. IBR-147-AE checks a line’s net amount against its quantity, price, charges and allowances. | Match the VAT category and rate; recalculate affected amounts from the lines. |
| Conditional credit-note fields | IBR-055-AE requires a preceding invoice reference for ordinary credit notes except when the credit-note reason is volume discount. | Add the preceding invoice reference or check that the selected reason is correct. |
| Coded values | IBR-139-AE checks VAT category codes against the allowed list. | Choose a code from the UAE code lists instead of free text. |
These are examples, not a complete rule catalogue. In the UAE field reference, Requirement covers all document types and modifiers; Description explains conditional requirements, and Business term identifies the PINT AE term. Choose List with sample request to select your document type and modifiers and see the applicable fields beside a sample request. For the full public rules, use the PINT AE invoice or credit-note rule index, as appropriate.
Correct a 422 response
If Unify returns HTTP 422, the document failed validation. Each entry in errors identifies the problem; code may be a published rule ID, while getsPath and payloadPath locate the affected values. For example, the Unify API example shows IBR-015 for a missing totals.amountDue. Correct the data in the named field, then resubmit the complete document. A change may expose another conditional requirement. Unify errors describes the response and the other status codes.
An HTTP 200 means validation passed and the document was stored, not that the buyer has received it. Use the returned documentId to follow delivery. For missing or incorrect values, start with the UAE field reference.
Last updated