L O A D I N G
ERP + ASP model

UAE E-Invoicing Software: What Your ERP Does and What the ASP Does

Under the UAE model, invoices travel between Accredited Service Providers, not straight from your ERP to the FTA. Your software has to produce clean, complete data and handle the responses.

Free consultation

Get a Free ERP Consultation

Tell us a little about your business. A consultant will reach out within one business day.

  • No obligation
  • Vendor-neutral advice
  • Your data stays private
Quick answer Updated October 2026 · Reviewed by UAE ERP Experts consultants

What software do I need for UAE e-invoicing, and what does the ASP do?

UAE e-invoicing needs two pieces working together: an ERP that captures every FTA-required field and exchanges data with an Accredited Service Provider, and an ASP contract. Under Ministerial Decisions 243 and 244 of 2025, the ASP validates invoices, converts them to PINT AE on the Peppol 5-corner model and reports tax data to the FTA. Check the latest Ministry of Finance and FTA guidance for dates.

  • UAE e-invoicing uses a decentralised Peppol-based 5-corner model with the PINT AE specification.
  • The FTA published the required e-invoicing data fields in February 2026.
  • Businesses with revenue of AED 50 million or more face mandatory e-invoicing from 1 January 2027.
  • Businesses below AED 50 million face mandatory e-invoicing from 1 July 2027, per current guidance.

Two pieces of software, one invoice

When people talk about UAE e-invoicing software, they often picture one product that sends invoices to the government. The UAE design is different. Ministerial Decisions No. 243 and 244 of 2025 set out a decentralized, Peppol-based "5-corner" model. Your ERP or accounting system creates the invoice data. An Accredited Service Provider (ASP) validates it, converts it to the PINT AE specification if needed, and delivers it to your buyer's ASP. Tax data is reported to the Federal Tax Authority as part of the flow.

That means you need two things working together: an ERP that captures every required field and can exchange data with an ASP, and an ASP contract. The FTA published the required data fields in February 2026, and many of them, such as buyer identifiers, item classification and specific tax breakdowns, are not stored in older setups.

This page explains the split of responsibilities and what your ERP must do. For a full project view including ASP selection and testing, see e-invoicing solutions; for platform-by-platform readiness, see ERP for UAE e-invoicing.

Two pieces of software, one invoice
  • ERP owns the invoice data and business rules
  • ASP owns format conversion, validation and Peppol exchange
  • FTA receives tax data through the network
  • Your buyer receives a structured invoice through their ASP
UAE Compliance

E-invoicing rules that define the software split

Dates and scope below reflect the published decisions as of October 2026. They have been amended before, so always check the latest Ministry of Finance and FTA guidance.

5-corner Peppol model

Corner 1 is the supplier, corner 2 the supplier's ASP, corner 3 the buyer's ASP, corner 4 the buyer, and corner 5 the FTA, which receives tax data. Businesses do not connect directly to the FTA for e-invoice exchange; they work through an ASP.

PINT AE specification

Invoices are exchanged as structured data under PINT AE, the UAE specification of the Peppol International invoice model. A PDF or a scanned image is not an e-invoice under this model.

Timeline for large businesses

Businesses with revenue of AED 50 million or more must appoint an ASP by 30 October 2026, with e-invoicing mandatory from 1 January 2027. Voluntary participation opened on 1 July 2026.

Timeline for other businesses

Businesses below AED 50 million must appoint an ASP by 31 March 2027, with the mandate from 1 July 2027. Government entities follow from 1 October 2027.

Credit notes and corrections

Credit notes are expected to be exchanged electronically in the same way as invoices. The ERP must link them to the original e-invoice and send them through the ASP rather than issuing paper corrections.

General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.

What your ERP must be able to do

These are the software capabilities we check on the ERP side. The ASP will have its own requirements for the connection format.

  • Store all FTA-required data fields on customers, items and invoices, including buyer identifiers and tax category codes
  • Validate mandatory fields before an invoice can be posted, not after it is rejected
  • Send posted invoices and credit notes to the ASP automatically through an API or connector
  • Receive and store the ASP's status: accepted, rejected, or delivered, with the reason for any rejection
  • Prevent edits to an invoice once it has been sent, and force corrections through credit notes
  • Receive incoming e-invoices from suppliers via the ASP and create draft purchase bills
  • Keep the structured invoice file and any ASP reference alongside the ERP record
  • Give finance a queue or dashboard of failed or pending submissions
  • Handle multi-entity setups where each TRN may have its own ASP registration
ERP Workflow

The e-invoice lifecycle between ERP and ASP

This is the path for a single outgoing invoice. Incoming invoices follow the reverse route, arriving from your ASP into the ERP as draft bills.

  1. 1Invoice drafted in ERP
  2. 2Field validation
  3. 3Posted and sent to ASP
  4. 4ASP validates and converts
  5. 5Delivered to buyer's ASP
  6. 6Tax data reported to FTA
  7. 7Status returned to ERP

One shared database: every step updates stock, finance and reports in real time.

ERP side versus ASP side

Clear ownership avoids finger-pointing when an invoice is rejected. This is the typical split; your ASP contract will define it precisely.

ERP side versus ASP side
Your ERPAccredited Service Provider
Invoice data and calculationsCreates invoice lines, tax amounts and totalsDoes not change business data
Master dataHolds customer, item and tax codesMay validate identifiers against the network
FormatExports data in ERP or agreed formatConverts to PINT AE and validates against the specification
DeliverySends to ASP via API or connectorDelivers over Peppol to the buyer's ASP
FTA reportingSupplies complete tax dataReports tax data to the FTA as required
RejectionsShows errors and blocks re-posting until fixedReturns error codes and reasons
Incoming invoicesCreates draft bills and matches to POsReceives from senders' ASPs and passes to ERP
ArchiveKeeps accounting record and attachmentsMay keep transmission records per contract

Responsibilities can vary between ASPs. Check the latest Ministry of Finance and FTA guidance for any change to the model.

Implementation Timeline

Getting your software ready

Typical durations for a single entity on Zoho, Odoo, ERPNext or Dynamics 365. Groups with several TRNs or custom billing systems take longer.

Durations are typical ranges; your plan is agreed after discovery.

  1. Field gap analysis

    1-2 weeks

    We compare your invoice and master data against the FTA's required fields and list what is missing.

  2. Data model changes

    2-3 weeks

    New fields, validations and tax category mapping are added to customers, items and invoice templates.

  3. ASP connector

    2-4 weeks

    We connect the ERP to your chosen ASP using its API or a supported connector, including status callbacks and incoming invoices.

  4. Testing

    2-4 weeks

    Sample invoices, credit notes and edge cases are run through the ASP's test environment until rejections are cleared.

  5. Live and monitoring

    Ongoing

    Finance monitors the submission queue and we support fixes during the first billing cycles.

Serving the UAE

UAE E-Invoicing Software across all seven emirates

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.

FAQs

UAE e-invoicing software questions

Still have a question? Our consultants are happy to help.

Ask an Expert
Can our ERP send e-invoices directly to the FTA?

Not under the published model. Exchange goes through Accredited Service Providers on the Peppol network, and tax data reaches the FTA through that flow. Your ERP connects to your ASP. Check the latest Ministry of Finance and FTA guidance for any change.

Do we need new accounting software?

Usually not. Most modern ERPs can be extended to store the required fields and connect to an ASP. Very old or heavily customized systems may be harder to adapt, and that can be a reason to migrate.

Will a PDF invoice by email still be accepted?

Once you are in scope, a PDF alone is not an e-invoice under the UAE model. You can still send a PDF copy for convenience, but the structured PINT AE invoice exchanged through the ASPs is the one that counts.

What happens when the ASP rejects an invoice?

The ASP returns an error, and your ERP should show it to the user and block the invoice from being treated as issued. The fix is usually a missing or wrong field on the customer or item, after which the invoice is resent.

Does the ASP replace our ERP?

No. The ASP handles format, validation and exchange. Your ERP still creates invoices, calculates tax, records receivables and posts to the ledger.

Can you connect our ERP to any ASP?

We work with the ASP you choose, provided it offers an API or connector we can integrate with. We can also help you shortlist ASPs based on your ERP and invoice volume.

Free Consultation

Check your ERP for e-invoicing gaps

We will compare your invoice data to the required fields and plan the ASP connection.

Location

Dubai, United Arab Emirates

Free consultation

Send us your requirements

  • No obligation
  • Vendor-neutral advice
  • Your data stays private
Chat with an ERP expert