Integrating for UAE e-invoicing requires connecting your ERP or accounting software to an FTA-Accredited Service Provider (ASP). The core task is building a data pipeline to map your internal financial data to the 51 mandatory fields of the Peppol PINT AE XML specification and transmitting the valid files through the ASP's API.
What is the actual engineering task?
The UAE's move to mandatory e-invoicing is not about finding new software to send PDFs. PDF and paper invoices will no longer be compliant. The mandate requires the exchange of structured data: specifically, XML files that conform to the Peppol PINT AE specification [3].
The system operates on a decentralized, five-corner model built on the Peppol network [4]. Your business (corner 1) sends an invoice through your chosen FTA-Accredited Service Provider, or ASP (corner 2). The ASP routes it through the Peppol network to the recipient's ASP (corner 3), who delivers it to the recipient (corner 4). Both ASPs report the transaction to the tax authority's platform (corner 5) [2].
From an engineering perspective, your responsibility is to get a valid invoice from your system to your ASP. This is a classic system integration and data transformation problem. You are not building a user-facing product; you are building a backend service that connects your financial source of truth to the national invoicing network.
How should a build team sequence the work?
Based on the integration projects we deliver, the work should be sequenced to de-risk the project early. The biggest risk is always the quality and accessibility of the source data.
Step 1: Data Discovery and Mapping. Before writing any code, we start with a data audit. The FTA has defined 51 mandatory fields for the PINT AE specification. Your first task is to locate where each of these 51 data points lives in your current systems-be it an ERP, CRM, or billing platform. This mapping exercise dictates the entire project's complexity and is the most frequently underestimated phase.
Step 2: ASP Selection and Connection. You will need to contract with an FTA-Accredited Service Provider. Once selected, they will provide API documentation and sandbox credentials. The technical task is to build an API client that can authenticate with and submit your generated XML files to their platform. This is usually a straightforward REST API integration.
Step 3: Build Transformation and Generation Logic. This is the core development work. We build a service that extracts data from your source systems (via API calls, database queries, or file exports), transforms it according to the mapping from Step 1, and constructs a valid PINT AE XML file. The participant identifier must be the business's TIN, which is the first 10 digits of the TRN [1]. For companies in a VAT group, each legal entity must use its own TIN, not the group's [5].
Step 4: Validation and Testing. The generated XML must be valid against the official PINT AE XSD schema. We build this schema validation directly into our CI/CD pipeline to automatically reject any code changes that produce invalid XML. You must then perform end-to-end testing in the ASP's sandbox environment to ensure the full cycle-from generation to submission to receiving a valid acknowledgement-works as expected.
What are the common technical hurdles?
Data Quality. The most common point of failure is poor source data. If a mandatory field like a buyer's address is missing or incorrectly formatted in your ERP, the integration will fail. The project must include a plan for data cleansing and enforcing data quality at the source.
Legacy Systems. Older ERPs or custom-built accounting systems often lack modern APIs. Extracting the required data can be difficult, sometimes requiring direct database connections or fragile file-based exports. This adds significant complexity and maintenance overhead compared to a clean API-based extraction.
Error Handling. The connection to the ASP is asynchronous. You will submit an invoice and get a response later. Your system needs robust error handling to process rejections from the ASP, notify the correct internal teams of the failure, and manage the resubmission process without creating duplicate invoices.
This is part of our work on system integration, and the planning discipline behind how we work.
Key takeaways
- UAE e-invoicing is a system integration project, not a compliance form.
- The core task is mapping your business data to the 51 mandatory fields of the PINT AE XML specification.
- Start with a data audit of your ERP and source systems; this is the most critical and time-consuming phase.
- Your solution must generate valid XML, connect to an ASP's API, and handle submission errors programmatically.
- Automated validation using the official XSD schema should be part of your development and deployment process.
Sources
- UAE: Technical guidance on mandatory e-invoicing fields (KPMG)
- United Arab Emirates electronic document specifications (Peppol)
- e-Invoicing UAE: Key Requirements, Implementation Timeline and Latest Updates (ClearTax)
- B2B e-Invoicing in the United Arab Emirates (UAE): EDICOM Pre-Approved e-Invoicing Service Provider| EDICOM (EDICOM)
- UAE e-invoicing mandate 2026: Readiness, ASP, and PINT AE (Avalara)