HOME
Taxes & compliance
UAE eInvoicing roles and responsibilities: who owns onboarding and exceptions?

UAE eInvoicing roles and responsibilities: who owns onboarding and exceptions?

Guide8 min read | Posted on September 28, 2026 | By Ashish Abraham

Under UAE eInvoicing, every business in scope must appoint an Accredited Service Provider (ASP). An ASP is a company accredited by the Ministry of Finance (MoF) to validate eInvoices, convert them to the UAE format and send them on. The rules are clear about what the ASP does.

They are less direct about who inside your business looks after everything else. Someone has to decide when a customer or supplier is ready to exchange eInvoices. Someone has to fix a rejected invoice before it becomes late. And someone has to tell the Federal Tax Authority (FTA) if a system failure stops you from invoicing. Signing with an ASP does not answer these questions.

This guide explains what stays with your business whichever ASP you choose, gives you a starting role map, and walks through onboarding and exception handling, including what changes for VAT groups and multi-entity businesses.

What does an ASP handle, and what stays with your business?

Every in-scope invoice passes through five parties, called corners:

• Corner 1: the supplier's own system creates the invoice data.

• Corner 2: the supplier's ASP validates it, converts it to the UAE format if needed, and sends it on. The format is PINT AE, the UAE version of the Peppol International (PINT) model.

• Corner 3: the buyer's ASP receives and validates it, then passes it to the buyer.

• Corner 4: the buyer's own system receives the invoice.

• Corner 5: the FTA receives tax data from both ASPs.

For a full walkthrough, see how the 5-corner model works.

Corners 2 and 3 are the ASPs' job. Corners 1 and 4 are your own systems. But the legal responsibility stays with you. Section 5.2 of the UAE Electronic Invoicing Guidelines, version 1.1 (Guidelines v1.1) has a responsibilities table. It notes that ASPs carry out the exchange and reporting in practice, "although the compliance obligation remains with the supplier (or buyer in the case of self-billed invoices)".

So a useful test for any task is this: even if your ASP does the work, your business answers for the result.

Each business also works with one ASP for all of its eInvoicing. Section 9 of Guidelines v1.1 says each business should onboard with only one ASP for all its eInvoicing needs. That makes the ASP relationship one relationship to own, not several.

Which eInvoicing jobs continue after go-live?

Connecting to an ASP is usually a project, with a start date, an end date and a team from finance, tax and IT. That team can step back once go-live is complete.

Three jobs do not end at go-live. They need a named owner for as long as you issue and receive eInvoices:

• The ASP relationship. Someone tracks your ASP's accreditation status and contract, and knows what to do if that status changes. The MoF publishes the register of accredited service providers.

• Customer and supplier onboarding. Every counterparty needs correct identifiers and a working ASP connection before eInvoices can move.

• Exceptions and incidents. Rejected invoices, missing confirmations and system failures each need someone to act, and some have legal deadlines.

None of these needs a new hire. Each needs a named person, even if one person holds all three, and a written plan for what happens when something goes wrong.

Who should own each part of UAE eInvoicing?

Use this table as a starting point and replace the roles with the ones in your business. Every row needs a clear answer. It does not need to match this table.

Activity	Usually owned by	Escalates to	Why it needs an owner
ASP relationship and accreditation status	Finance or tax lead	Finance director	Not appointing an ASP on time costs AED 5,000 a month under Cabinet Decision No. 106 of 2025
Customer and supplier onboarding	AP, AR or shared services team	Systems owner	eInvoices cannot move until identifiers are confirmed and a test invoice goes through
Rejected invoices and missing confirmations	AP or AR team	Systems owner, then ASP support	Each eInvoice not issued and sent on time costs AED 100, up to AED 5,000 a month
System failure notice to the FTA	Systems owner	Finance or tax lead	Late notice costs AED 1,000 a day, for the issuer and the recipient separately
Telling the ASP about changes to your registered details	Finance or tax lead	Systems owner	Late notice costs AED 1,000 a day
Entity-level setup in a VAT group or multi-entity business	Group finance or shared services lead	Entity finance lead	Each entity needs its own identifiers and ASP connection

The penalties come from Cabinet Decision No. 106 of 2025. For the full list, see UAE eInvoicing penalties.

A small, single-entity business can give every row to one finance lead. A group with five legal entities needs the same rows answered five times, once for each entity.

How does ownership change as a business grows?

In a single-entity business, one person, often whoever already handles tax or finance compliance, can hold all three jobs. That works well as long as the ASP details, each counterparty's onboarding status and the exception contacts are written down, not kept in one person's head.

In a larger or multi-entity business, the jobs multiply by legal entity, not by department. Each entity in scope has its own registration details, its own onboarding status and its own exception owner. One shared services team can do the daily work for all of them. But each entity still needs its own confirmed answer, not an assumption that all entities are in the same state.

What does customer and supplier onboarding involve?

Before eInvoices can move between you and a counterparty, confirm three things:

Their Tax Registration Number (TRN) is correct, where they have one. Not every business has a TRN.
Their Tax Identification Number (TIN) gives a working Participant Identifier on the Peppol network. The TIN is the first 10 digits of a TRN from any FTA tax registration. The Participant Identifier is scheme 0235 followed by that 10-digit TIN.
A test invoice reaches them through their ASP.

The third step catches most problems. If you skip it, you often find out a counterparty was not ready only when a real invoice is rejected.

Your own business has onboarding steps too. Appendix 3 of Guidelines v1.1 asks businesses to check their company details in EmaraTax, the FTA's online portal, before onboarding. A business with no FTA tax registration gets a TIN through EmaraTax. You then select your ASP in EmaraTax, and your Participant Identifier is created through that ASP. For the steps, see UAE eInvoicing onboarding through EmaraTax.

Most businesses onboard counterparties in waves: the highest-volume customers and suppliers first, smaller ones later. Track each one with a simple status: confirmed, pending or blocked. That way nobody has to remember whether a supplier is ready.

Two things slow onboarding down most often:

• Inconsistent records. The same company entered under slightly different names or addresses by different people over the years. A person reading a PDF never notices. An automated check does.

• Skipping the test exchange. Treating EmaraTax registration as the last step, when the test invoice is what proves the connection works.

For cleaning up customer, supplier and item records, see ERP integration and master data for UAE eInvoicing.

Who deals with a rejected invoice, a missing confirmation or a system failure?

These are different events with different owners and deadlines. Treat them separately.

A rejected invoice. This is usually a data problem, such as a missing mandatory field, an identifier that does not match, or a value that fails the format check. A standard Tax Invoice has 51 mandatory fields under the MoF's mandatory fields guidance. Whoever issued the invoice should know the same day and fix it. Finding out at month-end means the process broke earlier. See UAE eInvoice errors, rejections and statuses.

A change to your registered details. Article 5(3) of Ministerial Decision No. 243 of 2025 requires you to tell your ASP in writing about any change to the details registered with the FTA. You must do this within five business days of receiving confirmation of the change. Appendix 3 of Guidelines v1.1 gives examples, such as joining or leaving a tax group or deregistering from a tax.

A system failure. This is when a technical fault stops you from issuing, sending, receiving or reporting invoices, not when one invoice fails. Article 12 of the same Decision requires every issuer and every recipient to notify the FTA within two business days. Your ASP must also tell you and the FTA about disruptions to its own service, by email to e-invoicingsupport@tax.gov.ae. Its notice does not replace yours. See UAE eInvoicing system failure: reporting, fallback and recovery.

Agree in advance who is told first for each event, and by when. Day to day, that saves more time than knowing every technical fix.

What stays local to each entity in a VAT group?

A shared services team can run finance for several entities. The eInvoicing connections underneath it are still separate.

Under section 9 of Guidelines v1.1:

• Each member of a tax group must be onboarded for eInvoicing.

• Each member has its own TIN, taken from its own TRN, not the group representative's.

• Each member gets its own Participant Identifier.

• Members may choose different ASPs.

So a group can standardise on one ASP, but the rules do not require it.

Transactions between members of the same VAT group have a 24-month grace period, from 1 January 2027 to 1 January 2029. After that, eInvoicing applies to them too. Invoices to and from anyone outside the group follow each member's normal go-live date.

What ownership mistakes slow down a UAE eInvoicing rollout?

• Treating the ASP appointment as the end of the job. The compliance obligation stays with your business.

• Naming an owner only after something breaks. The first rejected invoice then becomes an improvised response.

• Tracking onboarding from memory. A counterparty's readiness gets assumed instead of confirmed.

• Treating every problem the same way. A rejected invoice, a changed registration detail and a system failure each have a different deadline and a different person to notify.

• Forgetting to update the ASP. Changes such as joining or leaving a tax group need to reach your ASP within five business days of the FTA's confirmation.

• Assuming one shared services team means one connection. Each entity still needs its own.

When should you name eInvoicing owners?

Now. You do not need to wait until you have chosen an ASP. Naming an owner for the ASP relationship, onboarding and exceptions, in writing and before go-live, costs nothing. For the wider preparation steps, see the UAE eInvoicing readiness and implementation guide.

Zoho Software Trading LLC is a Ministry of Finance-accredited eInvoicing service provider for the UAE, with accreditation number 121988, as shown on the MoF register of accredited service providers.

Explore UAE eInvoicing with Zoho Books

Frequently asked questions

Who should own the ASP relationship inside a business?

Usually whoever already handles tax or finance compliance. They should track the ASP's accreditation status and contract, and know what to do if either changes.

Can a business use more than one ASP?

Not for one entity. Section 9 of Guidelines v1.1 says each business should onboard with only one ASP for all its eInvoicing. In a tax group, different members may choose different ASPs.

What is the difference between a TIN and a TRN?

A TRN is the Tax Registration Number the FTA issues when a business registers for a tax. The TIN is the first 10 digits of that TRN. The TIN is used to build the Peppol Participant Identifier, so check which one a form asks for.