1. Home
  2. Blog
  3. E-Invoicing

E-Invoicing

How to Connect Your CRM or ERP to UAE E-Invoicing

Connecting a CRM or ERP to UAE e-invoicing means mapping your invoice data to PINT AE, building a secure link to your Accredited Service Provider, and adding a workflow for rejections, credit notes and alerts. Here is how the project runs.

SZ
Sahil ZainiFounder & Developer
·24 Oct 2026·6 min read

To connect your CRM or ERP to UAE e-invoicing, you add an integration layer that takes each invoice or credit note from your system, converts it into the PINT AE format, sends it to your Accredited Service Provider (ASP) through its API, and records the result back in your system, with alerts for anything rejected. Most businesses do not need to replace their ERP or CRM; they need a reliable connector, clean data and a tested workflow in place before 1 January 2027 (revenue of AED 50 million or more) or 1 July 2027 (below AED 50 million).

The three layers of an e-invoicing integration

  1. Your system of record. The ERP, CRM or POS where invoices are created. In our own stack that is FORMA ERP, Consultant CRM or ZainiPOS, but the approach is the same for any system.
  2. The integration layer. Software that extracts invoice data, validates it, maps it to PINT AE, communicates with the ASP and writes statuses back. This is where most of the project effort goes.
  3. The ASP. The accredited provider that validates, transmits and reports. Choosing one is covered in how to choose an ASP.

The legal requirements behind all three come from Ministerial Decisions No. 243 and 244 of 2025, published by the Ministry of Finance. If you need the background, start with our complete guide to UAE e-invoicing.

Step 1: Assess what your system can give you

The first question is not which ASP but whether your current software holds complete invoice data in a form that can be extracted automatically. Your integrator will check:

  • Does the system have an API, a database we can read, or at least a scheduled export?
  • Are invoice numbers unique and sequential per legal entity?
  • Does each customer record carry legal name, address and TRN fields?
  • Does each line carry a VAT category and rate, not just a VAT amount?
  • Are credit notes linked to the invoices they correct?
  • Are issued invoices locked against editing?

Gaps found here are fixed in the system or in the mapping layer before any connection is built. This is also the point at which some businesses conclude that their spreadsheet or legacy system has reached its limit; our article on signs you have outgrown Excel covers that decision.

Step 2: Map your fields to PINT AE

PINT AE, the UAE profile of the Peppol international invoice, defines where every value belongs. Mapping is the exercise of saying: our customer field X becomes buyer legal name; our item tax code Y becomes VAT category Z. A good mapping document lists each PINT AE element, the source field in your system, any transformation (for example date format or rounding) and the rule applied when the source is empty. Our explainer on what PINT AE is describes the main groups of fields.

Two areas deserve special attention. Rounding: agree one method and apply it consistently so line totals, VAT per rate and document totals reconcile. Foreign currency: capture exchange rates and AED equivalents at invoice time so the figures reported to the FTA match your VAT return.

Step 3: Build the connection to the ASP

With a mapping agreed, the integration layer is built against the ASP's sandbox. A typical outbound flow looks like this:

StageWhat happensWhat your team sees
IssueUser finalises an invoice in the ERP or CRMNormal invoice screen
Pre-checkIntegration validates required fields locallyImmediate warning if data is missing
ConvertInvoice is converted to PINT AENothing; automatic
TransmitDocument is sent to the ASP over a secure APIStatus: pending
ResultASP accepts or rejects; status is written backStatus: accepted or rejected with reason
DeliverCustomer's ASP receives it; PDF copy emailed if you wishDelivered status, PDF sent

Inbound supplier invoices follow the reverse path into your purchase ledger.

Step 4: Design the exception workflow

Integrations fail at the edges, and the penalties are designed around those edges. Under Cabinet Decision No. 106 of 2025, published by the Federal Tax Authority, an e-invoice or e-credit note not transmitted on time costs AED 100 per document, capped at AED 5,000 per month, and a system failure not notified to the FTA on time costs AED 1,000 per day. Your workflow therefore needs:

  • A rejection queue with the ASP's error message in plain language and a one-click resend after correction.
  • Automatic retries for temporary network problems, with a limit, after which a person is alerted.
  • Alerts by email or WhatsApp to named owners when documents stay pending beyond an agreed time.
  • An outage procedure stating who contacts the ASP, who notifies the FTA and how the incident is logged.
  • A full audit trail of every attempt, response and user action.

Step 5: Test, pilot, go live

Testing runs in three rounds. First, sandbox tests with a library of cases: standard invoice, zero-rated line, mixed rates, foreign currency, credit note, consumer without TRN. Second, live tests with a few cooperative customers, ideally during the pilot that opens on 1 July 2026. Third, parallel running for a month, in which every invoice goes through the integration while staff still check a sample by hand. Only then switch off the old process.

Step 6: Keep it running

Specifications and APIs change. Keep the mapping separate from the ERP code, version the connector and agree a maintenance arrangement that includes specification updates. Keep company master data in one place and add an ASP notification to your change checklist, because failing to notify the ASP of changes to registered data costs AED 1,000 per day. Finally, confirm that the integration layer, your ERP hosting and all backups store documents inside the UAE, as Article 11 of Ministerial Decision No. 243 of 2025 requires. Our article on UAE data residency explains hosting choices.

Frequently asked questions

Can my existing ERP be connected to UAE e-invoicing, or do I need a new one?

Most systems that store invoices in a database and expose an API, export or database access can be connected. The integration layer maps your fields to PINT AE and talks to your ASP. Replacement is only necessary when the current system cannot produce complete, consistent invoice data, for example spreadsheets or very old software with no way to extract records.

How long does an e-invoicing integration take?

A straightforward integration with a well-documented ERP and ASP typically takes a few weeks from mapping to sandbox approval, followed by a period of live testing. Complex cases with several legal entities, multiple currencies or heavy customisation take longer. Start in 2026 so you are live well before 1 January or 1 July 2027.

Does the integration need to handle incoming supplier invoices too?

Ideally yes. Your ASP receives invoices from your suppliers' ASPs, and a good integration brings them into your purchase ledger automatically, matched to purchase orders where possible. This is where much of the efficiency gain lies, so plan for inbound handling even if you launch with outbound first.

Where should the integration store the e-invoice files?

Inside the UAE. Article 11 of Ministerial Decision No. 243 of 2025 requires electronic documents to be stored in the UAE, and VAT records must generally be kept for 5 years. Confirm that your ERP hosting, the integration layer and any backups meet this, and ask your ASP the same question in writing.

What if the ASP changes its API or the PINT AE rules change?

Build the integration with a separate mapping layer and version your connector so a change on the ASP side does not require rewriting your ERP. Agree a maintenance arrangement with your integrator that covers specification updates. The pilot period from 1 July 2026 is exactly when such refinements are most likely.

How Zaini Developers can help

This is the work we do. Zaini Developers, based in Dubai, UAE and India, builds the integration layer between your ERP, CRM or POS and the accredited provider you choose, and ships FORMA ERP, Consultant CRM and ZainiPOS with PINT AE output built in. We are not an ASP or a tax agent; we are the engineers who make the connection work and keep it working. See our services, try our live demos, or contact us for an assessment of your current system.

Free E-Invoicing Readiness CheckAnswer 8 quick questions and get your score and action plan by e-mail.
Check my readiness

Let's build together

Have a project in mind?
Let's build it together.

Every project is quoted to your exact requirements — no fixed price list, no surprises.

120+Projects delivered
100+Happy clients
5+Years experience
Chat with usReplies within the day