L
O
A
D
I
N
G
Zoho, Odoo, ERPNext, Dynamics 365 and custom ERP, delivered by one accountable team.
The integration between your ERP and your Accredited Service Provider decides whether e-invoicing runs quietly or floods finance with rejections. Here is how to design it.
Under UAE e-invoicing, the ERP never connects to the FTA directly; it connects through an API to your Accredited Service Provider (ASP). The ASP validates invoice data, converts it to PINT AE XML where needed, exchanges it over Peppol and reports tax data to the FTA. The integration handles outbound invoices, status updates, inbound supplier invoices and reference data, keyed on unique document IDs.
In the UAE model your ERP never talks to the FTA directly. A UAE e-invoicing API integration connects the ERP (corner 1) to your Accredited Service Provider (corner 2). The ASP accepts invoice data in a format you agree with it, validates it, converts it to PINT AE XML where needed, sends it over Peppol to the buyer's ASP and reports tax data to the FTA. Confirmations then flow back to you. Inbound works the other way: your ASP receives supplier invoices addressed to your participant ID and passes them to your ERP.
That means the integration has four jobs: send outbound invoices and credit notes, receive status updates, receive inbound supplier documents, and keep reference data (participant lookups, onboarding status) in sync. Each ASP publishes its own API, so the exact endpoints differ, but the design questions are the same everywhere: what payload you send, how you identify each document, how you learn about rejections, and how you avoid sending the same invoice twice.
This page is for IT managers and ERP admins. The legal background is on the requirements page, and the wider project plan is in UAE e-invoicing implementation. For general API practice across systems, see ERP API integration in the UAE. This page explains how ERP systems are configured to support the rules; it is not tax advice. Confirm your position with your tax advisor.
The API design is technical, but several requirements are legal. Check the latest Ministry of Finance and FTA guidance before acting, because dates and details have been amended before.
The guidelines note that ASPs carry out the exchange in practice, but the compliance obligation stays with the supplier, or the buyer for self-billed invoices. Your integration must therefore surface every failure, not hide it in a log file.
Each e-invoice needs a unique identifier so duplicates are prevented. Generate or store it in the ERP before the first submission and reuse it on retries.
Cabinet Decision No. 106 of 2025 provides fines of AED 100 per e-invoice or e-credit note not issued or sent within the required timeframe, capped at AED 5,000 per month. Queues that stall over a weekend become a compliance issue, so monitoring matters.
XML, acknowledgments and associated data must be kept for the statutory retention periods and be retrievable for the FTA. The guidelines accept storage outside the UAE if records can be provided promptly in complete, readable form.
Invoice payloads contain customer names, addresses and bank details. Use TLS, scoped API credentials, credential rotation and access logs, and review the ASP contract against the UAE PDPL and any sector rules you follow.
General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.
Agree these points with your ASP and ERP team before anyone writes code or installs a connector.
A clean integration posts the invoice only after accounting approval and treats the ASP response as part of the invoice record.
One shared database: every step updates stock, finance and reports in real time.
There are four common ways to connect an ERP to an ASP. The right one depends on your platform, volumes and in-house skills.
| Pattern | How it works | Good fit | Watch-outs |
|---|---|---|---|
| Native ERP or ASP connector | A connector inside the ERP or published by the ASP sends invoices and reads statuses | Standard SaaS ERPs with modest customization | Confirm which document types and scenarios it covers, and who supports upgrades |
| Direct REST API | Your ERP calls the ASP API and exposes a webhook for callbacks | High volumes, custom billing logic, in-house IT | You own retries, monitoring and changes when the ASP versions its API |
| Middleware (Zoho Flow, Make, n8n, Power Automate, iPaaS) | Middleware listens for ERP events and calls the ASP | Several source systems feeding one ASP | Another component to monitor; check data residency and logging of the middleware |
| File exchange (SFTP or portal upload) | ERP exports files on a schedule; ASP returns status files | Legacy systems that cannot call APIs | Slower feedback on rejections; manual steps increase the risk of late issuance |
| Inbound to AP | ASP pushes supplier XML or ERP polls for new documents | Every business, since one ASP handles both directions | Matching to POs and GRNs still needs rules and exception handling |
Connector availability and API features vary by ASP and ERP edition; confirm with both before you commit.
Ranges assume one ERP and one ASP; add time for each extra billing system.
Durations are typical ranges; your plan is agreed after discovery.
Agree payload, ID strategy, status model and error mapping with the ASP; document field mapping from ERP to PINT AE.
Install the connector or develop API calls, webhook endpoint, queue and retry logic; add ERP fields and status views.
Run every scenario you issue, forced rejections, duplicate submissions, timeouts and inbound supplier documents.
Alerts on stuck queues and rejection spikes, a daily status reconciliation and an owner for API version changes.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertNot always. The guidelines describe the ASP converting data received from the supplier into the UAE standard XML if it arrives in another format. Some ASPs accept their own JSON or CSV; others expect UBL XML. Generating XML yourself gives more control but more maintenance.
Webhooks give faster feedback on rejections, which matters for timely issuance. Many teams use both: webhooks for real-time updates and a scheduled poll to reconcile anything a callback missed.
Assign the document's unique ID in the ERP before the first call and send the same ID on every retry. If the ASP supports idempotency keys, use them too, and never renumber an invoice after a failed submission.
Each legal person needs its own TIN-based participant ID and its own ASP appointment, but a single integration layer can route documents per entity. Map entity, TIN and credentials explicitly so one company's invoices never go out under another's ID.
It changes quickly as ASPs are accredited. We check current options for each platform; see Zoho UAE e-invoicing and UAE e-invoicing ERP for how platforms typically connect.
Related Solutions
Related Industries
Related ERP Platforms
Related Guides
We map your payloads, status handling and inbound flow, then build and test the integration on your ERP.
Dubai, United Arab Emirates
