Every invoice your business issues under the UAE’s e-invoicing mandate will be validated field by field before it reaches the buyer or the Federal Tax Authority (FTA). That validation runs against a single specification: PINT-AE (Peppol International Invoice, UAE Profile). One missing data element, one misformatted code, and the invoice is rejected automatically. No exceptions, no manual workaround. For finance teams, IT departments, and compliance leads preparing for the mandatory rollout, understanding the PINT-AE XML format, mandatory fields, and data structure rules is the first step toward a system that passes validation consistently.
PINT-AE is the UAE’s localized version of the global Peppol BIS Billing 3.0 standard, built on Universal Business Language (UBL) 2.1. The UAE Ministry of Finance (MoF) and the FTA developed it to define how e-invoice data must be structured, labelled, and validated before entering the national e-invoicing network. OpenPeppol released the current specification, PINT AE v1.0.1, in July 2025, refining validation rules, code lists, and syntax bindings ahead of the July 2026 mandate.
The PINT-AE format UAE businesses must follow governs every data field on an invoice, from seller identifiers to VAT category codes and line-item breakdowns. Compliance is not about issuing invoices electronically. It is about issuing them in the exact structure the FTA’s system accepts. A PDF attached to an email is not an e-invoice. Only a structured XML message aligned to PINT-AE qualifies.
Every e-invoice must be issued in XML (Extensible Markup Language), the only file type the national system will process. Unlike PDFs or Word documents, XML is machine-readable, with each data field inside a defined tag that allows automated validation at every stage.
Your Accredited Service Provider (ASP) validates the XML against the UAE Data Dictionary before transmitting it through the Peppol network. If mandatory fields are missing or incorrectly formatted, the invoice is rejected with no manual override.
For IT and ERP managers, this means your billing system must generate compliant XML output. If your software produces invoices only as print-ready documents, it will need configuration changes, middleware, or API-based integration.
PINT-AE is built in three layers, each serving a different purpose within the Peppol framework.
Shared Core Content contains universally required invoice elements found across all Peppol PINT implementations: invoice identifiers, issue dates, supplier and buyer details, and invoice totals. This ensures baseline interoperability across the global Peppol network.
Aligned Content covers internationally standardized fields mapped to UAE-specific classifications, including VAT categories, tax calculation logic, and payment terms. This layer ensures tax data is interpreted consistently while remaining compatible with international standards.
Distinct UAE Content is where PINT-AE diverges from global Peppol PINT. It includes the mandatory 10-digit Tax Registration Number (TRN) format, UAE-specific transaction type codes, VAT treatment rules for free zone operations, and the requirement to report VAT line amounts in AED. These fields do not exist in European or Asia-Pacific PINT specifications, which means your ASP must be configured specifically for PINT-AE, not generic Peppol.
The PINT-AE Data Dictionary defines over 135 data elements across mandatory, conditional, and optional fields. For a standard tax invoice, 51 mandatory fields must be populated before the invoice can pass ASP validation. The MoF published the formal mandatory fields specification (Version 1.0) in February 2026, grouping them into six categories: invoice details (9 fields), seller details (11 fields), buyer details (9 fields), document totals (5 fields), tax breakdown (4 fields), and invoice line items (13 fields).
Seller and buyer sections require business names, TRNs, electronic addresses, and structured address fields. Invoice line items must include descriptions, quantities, unit prices, gross prices, and VAT amounts. Tax totals must reconcile with line-level data, and VAT amounts must be reported in AED even when the invoice currency differs.
Two fields within the invoice line category are UAE-specific additions not found in standard European or Asia-Pacific PINT: VAT line amount in AED and invoice line amount in AED. These are mandatory for every line item regardless of transaction type. Missing even one mandatory field causes the invoice to fail ASP validation. It will not reach the buyer and will not be reported to the FTA.
Conditional fields add further requirements depending on transaction type. Reverse charge supplies, zero-rated exports, free zone transactions, and multi-currency invoices each trigger additional fields. For example, the exchange rate field becomes mandatory whenever the invoice currency is not AED.
The UAE operates a Decentralized Continuous Transaction Control and Exchange (DCTCE) model, known as the 5-corner model. Your ERP sends invoice data to your ASP (Corner 2), which validates the XML and transmits it through the Peppol network to the buyer’s ASP (Corner 3). The buyer receives the invoice (Corner 4), and both ASPs report the relevant Tax Data Document (TDD) to the FTA’s central platform (Corner 5).
Tax data flows to the FTA automatically with every invoice exchanged. There is no separate VAT reporting step. Errors are flagged in near real-time, so businesses that rely on end-of-month invoice cleanup will need to shift to invoice-level accuracy at the point of creation.
Data mapping gaps. Most ERP systems store invoice data, but not in the structure PINT-AE requires. Fields like VAT category codes, country codes (ISO 3166-1 Alpha-2), unit-of-measure codes (UNECE Recommendation 20), and the 10-digit TRN may not exist in your master data. Date fields must follow YYYY-MM-DD strictly.
Legacy system limitations. Businesses running older accounting software or custom-built billing tools often lack native XML generation. Bridging this gap requires software upgrades, API connectors, or middleware. This is common among businesses using Tally, QuickBooks, or custom solutions that predate structured data requirements.
Multi-entity complexity. Companies operating across multiple emirates or free zones face additional conditional field requirements. Each entity may need separate ASP configurations and VAT treatment logic. Without a structured readiness assessment, these complexities surface late and delay compliance.
Cabinet Decision No. 106 of 2025 establishes a clear penalty framework. Businesses that fail to implement the e-invoicing system or appoint an ASP face AED 5,000 per month. Each non-compliant invoice triggers AED 100 per document, capped at AED 5,000 monthly. System failure reporting delays carry AED 1,000 per day.
Voluntary early adopters are exempt during the pilot phase starting July 2026, creating a measurable incentive for early participation.
Compliance preparation involves four steps: auditing your invoicing data against the Data Dictionary, configuring your ERP for valid XML output across all 51 mandatory fields, selecting and onboarding with an ASP, and running validation tests before your go-live date.
For businesses with annual revenue of AED 50 million or more, the mandatory phase begins January 2027 (ASP appointment required by October 2026). Smaller businesses follow by July 2027.
A gap analysis and schema-level testing prevent last-minute disruptions. Advisory-led support ensures finance, tax, and IT teams are aligned on data ownership and validation workflows from the outset. To understand where your business stands, request a readiness assessment.
What is PINT-AE and how does it work?
PINT-AE stands for Peppol International Invoice, UAE Profile. It is the official e-invoicing specification developed by the MoF and the FTA, defining the XML structure, mandatory data fields, and validation rules every e-invoice must follow. Your system generates the data, your ASP validates it against the Data Dictionary, and the invoice is transmitted through the Peppol network to the buyer and reported to the FTA.
What are the PINT-AE XML format mandatory fields for a UAE tax invoice?
A standard UAE tax invoice requires 51 mandatory fields grouped across six categories: invoice details (9), seller details (11), buyer details (9), document totals (5), tax breakdown (4), and invoice line items (13). These include TRNs, VAT category codes, line-item pricing, and amounts in AED. Additional conditional fields apply for reverse charge, zero-rated, and free zone transactions.
Does PINT-AE apply to small businesses in the UAE?
Yes. The mandate applies to all businesses conducting B2B or B2G transactions, regardless of size. Small businesses with annual revenue below AED 50 million have a later compliance deadline (July 2027), but must still issue invoices in PINT-AE format. Early preparation helps avoid rushed implementation and penalty exposure.
Can I use a PDF as my e-invoice under the UAE system?
No. PDFs, scanned documents, Word files, and spreadsheets do not qualify. The FTA requires structured XML aligned to the PINT-AE Data Dictionary. Businesses may retain a PDF for internal records, but only the validated XML is accepted for compliance, Peppol exchange, and FTA reporting.
What systems need to change for PINT-AE compliance?
Your ERP or billing system must generate structured XML aligned to the PINT-AE schema. This may require configuration updates, new data fields for coding standards (ISO country codes, UNECE units of measure), API integration with your ASP, and validation testing. Legacy or custom-built systems often need middleware to bridge existing workflows.
Is PINT-AE the same as Peppol BIS Billing 3.0?
Not exactly. Peppol BIS Billing 3.0 is the global baseline. PINT-AE is the UAE’s localized extension, adding fields and rules specific to UAE VAT law. Examples include the 10-digit TRN format, UAE transaction type codes, and mandatory AED reporting. Your ASP must support the PINT-AE profile specifically.
