PINT-AE: UAE E-Invoicing Standard
The complete technical guide to PINT-AE, the UAE's national e-invoicing XML format based on UBL 2.1 and PEPPOL specifications.
What is PINT-AE?
PINT-AE stands for PEPPOL International Invoice, UAE (Arabi Emirates). It is the structured XML data format that defines exactly how a UAE e-invoice must be formatted, what mandatory fields it must contain, and how it must be transmitted over the PEPPOL network. PINT-AE is the UAE Data Dictionary built on the PEPPOL International (PINT) specification, with UBL 2.1 as the underlying ISO standard.
Key Technical Features
UBL 2.1 Foundation
Built on Universal Business Language 2.1, the ISO standard for electronic business documents.
51 Mandatory Fields
The UAE Electronic Invoice Mandatory Fields specification defines 51 required data elements for compliance.
PEPPOL Network
Transmitted through the PEPPOL network using the five-corner DCTCE model.
XML Format
Machine-readable structured XML, not PDFs or scanned invoices.
Digital Signatures
Requires qualified digital signatures from the issuing ASP for authenticity and integrity.
Arabic Support
Full support for Arabic language fields and RTL document requirements.
51 Mandatory Fields Overview
The UAE Ministry of Finance published the official UAE Electronic Invoice Mandatory Fields document (Version 1.0, February 2026). These fields are organized into categories:
Invoice Identification
Invoice number, issue date, invoice type code, document currency code
Seller Information
Seller name, TRN/TIN, address, trade license details, PEPPOL identifier
Buyer Information
Buyer name, TRN/TIN, address, PEPPOL identifier
Line Items
Item description, quantity, unit price, VAT rate, VAT amount, discounts, charges
Tax Details
VAT category codes (S/Z/E/O/AE), tax amounts, exemption reasons
Payment Information
Payment terms, due date, bank details, payment method
Document Totals
Line extension amount, tax exclusive amount, tax inclusive amount, payable amount
XML Structure Example
PINT-AE invoices follow the UBL 2.1 XML schema. Here's a simplified structure:
<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
<cbc:ID>INV-2024-001</cbc:ID>
<cbc:IssueDate>2024-08-05</cbc:IssueDate>
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<cac:AccountingSupplierParty>
<cbc:ID schemeID="0235">1234567890</cbc:ID>
<cac:Party>
<cbc:Name>Seller Company LLC</cbc:Name>
<!-- Additional seller details -->
</cac:Party>
</cac:AccountingSupplierParty>
<cac:AccountingCustomerParty>
<cbc:ID schemeID="0235">0987654321</cbc:ID>
<cac:Party>
<cbc:Name>Buyer Company LLC</cbc:Name>
<!-- Additional buyer details -->
</cac:Party>
</cac:AccountingCustomerParty>
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<cbc:Quantity unitCode="EA">10</cbc:Quantity>
<cbc:LineExtensionAmount currencyID="AED">1000.00</cbc:LineExtensionAmount>
<cac:Item>
<cbc:Description>Product description</cbc:Description>
</cac:Item>
<cac:Price>
<cbc:PriceAmount currencyID="AED">100.00</cbc:PriceAmount>
</cac:Price>
</cac:InvoiceLine>
<!-- Additional invoice lines -->
</Invoice>Validation Rules
PINT-AE invoices must pass multiple validation layers before transmission:
Schema Validation
XML must conform to the UBL 2.1 schema and PINT-AE data dictionary constraints.
Business Rule Validation
Business logic checks such as invoice totals matching line item sums, valid VAT rates, and correct tax calculations.
Field Completeness
All 51 mandatory fields must be present and populated with valid data.
Format Validation
Dates, numbers, currency codes, and country codes must follow ISO standards.
TRN/TIN Validation
Tax identification numbers must be valid UAE TRNs (10 digits) or TINs.
PEPPOL Identifier
PEPPOL participant identifiers must follow the 0235 + TIN format.
VAT Category Codes
PINT-AE uses specific VAT category codes to indicate the tax treatment of goods and services:
PEPPOL Integration
PINT-AE is transmitted through the PEPPOL network using the Decentralised Continuous Transaction Control and Exchange (DCTCE) five-corner model. This model connects the supplier, supplier's ASP, buyer's ASP, buyer, and Federal Tax Authority. The supplier's ASP validates the invoice, applies digital signatures, and transmits it to the buyer's ASP while simultaneously reporting tax data to the FTA.
Implementation Steps
Review Mandatory Fields
Study the 51 mandatory fields and ensure your ERP can capture all required data.
Map ERP Fields
Map your ERP's invoice fields to PINT-AE XML structure and data dictionary.
Generate XML
Implement XML generation logic following UBL 2.1 schema and PINT-AE specifications.
Validate Locally
Perform local validation against PINT-AE schema and business rules before transmission.
Test with ASP
Connect with your Accredited Service Provider and test invoice transmission in sandbox.
Go Live
After successful testing, move to production transmission before your deadline.
Validation Tools
Use these tools to validate your PINT-AE invoices:
UBL 2.1 Schema Validator
Official UBL schema validation tools for XML structure compliance.
PINT-AE Data Dictionary
UAE Ministry of Finance published data dictionary for field specifications.
ASP Sandbox
Most Accredited Service Providers offer sandbox testing environments.
PEPPOL Validator
PEPPOL network validation tools for participant identifiers and routing.
Frequently Asked Questions
Is PINT-AE the same as PEPPOL?
No. PEPPOL is the network infrastructure for transmitting documents. PINT-AE is the UAE-specific invoice format (data dictionary) that runs on the PEPPOL network. Think of PEPPOL as the postal service and PINT-AE as the letter format.
Can I use PDF invoices instead of XML?
No. The UAE Electronic Invoicing System explicitly requires structured XML invoices in PINT-AE format. PDFs, scanned invoices, and paper invoices are not valid e-invoices under the mandate.
What happens if my invoice fails validation?
Your ASP will reject the invoice and return an error message explaining the validation failure. You must correct the issue and resubmit. Common failures include missing mandatory fields, invalid TRNs, incorrect VAT calculations, or schema violations.
Do I need to implement PINT-AE myself?
Most businesses work with an Accredited Service Provider who handles PINT-AE conversion, validation, and transmission. However, you must ensure your ERP can provide all 51 mandatory data fields to your ASP.
How do I get the official PINT-AE specification?
The UAE Ministry of Finance publishes the official UAE Electronic Invoicing Guidelines and Mandatory Fields specification on their website. Version 1.0 was published in February 2026, with Version 1.1 released in June 2026.
What is the PEPPOL identifier format?
The PEPPOL participant identifier for UAE businesses follows the format: 0235 + 10-digit TIN. For example, if your TIN is 1234567890, your PEPPOL identifier is 02351234567890.