UAE electronic invoicing

Use this guide to configure and validate UAE invoices and credit notes in Complyance. It covers ordinary, out-of-scope, and self-billed documents using the customer-facing labels shown in your integration or mapping experience.

Generate a UAE document

1. Compose the Document Type. Start with UAE document type composition. Combine Tax Invoice or Tax Credit Note with Ordinary, Out of Scope, or Self-Billed. The complete selection determines the official document type code and validation profile.
2. Map your source data. Use the labels in UAE field requirements to map the information from your source system.
3. Choose allowed values. Apply the route-specific options in UAE allowed values and code lists.
4. Validate the document. Complyance applies the correct PINT AE validation profile for the selected route.
5. Correct validation findings. Use the affected field label, explanation, and correction guidance in UAE validation and troubleshooting, then validate again.
6. Submit the validated document. Submit only after the document passes validation.

Supported Document Type selections

• Tax Invoice + Ordinary
• Tax Credit Note + Ordinary
• Tax Invoice + Out of Scope
• Tax Credit Note + Out of Scope
• Tax Invoice + Self-Billed
• Tax Credit Note + Self-Billed

Debit notes and separate UAE document variants are not included in this guide.

Publication boundary

This guide documents the business information clients need to configure and validate UAE documents. Internal schema paths, enum tokens, transformation mappings, validation payload structures, and generated XML mechanics are intentionally excluded.

Reference pages

• UAE document type composition
• UAE field requirements
• UAE allowed values and code lists
• UAE validation and troubleshooting
• UAE official sources

The guide is based on MoF Electronic Invoice Mandatory Fields V1.0, MoF E-Invoicing Guidelines V1.1, PINT AE Billing 1.0.4, and PINT AE Self-Billing 1.0.4.