UAE eInvoicing functional responsibility matrix: a practical RACI guide for Finance, Tax, AP, AR, IT and ASP coordination

Published 24 October 2026 · Official legislation links checked against the project’s regulatory source register · Other official sources last reviewed 22 October 2026 · 17 min read

UAE eInvoicing readiness is a cross-functional change, not simply an IT installation or an accounts payable project. Finance owns business process outcomes, Tax interprets tax treatment with the appropriate advisers, accounts receivable (AR) and accounts payable (AP) operate the seller and buyer workflows, and IT coordinates data, interfaces, access and operational support. Procurement, Legal, Records Management and executive sponsors have supporting responsibilities. An Accredited Service Provider (ASP) supplies an important part of the service arrangement, but appointing a provider should not be treated as a substitute for defining the company’s own controls.

This guide proposes a practical responsibility model for organising that work. It distinguishes the wording of the UAE eInvoicing framework from recommended internal governance. It is an implementation aid, not legal or tax advice and not an official allocation of duties among job titles. The legal requirements attach to the relevant persons, transactions and roles under the applicable instruments; a company’s RACI chart is an internal management tool.

1. Start with the official framework and scope

Use the official English text of Ministerial Decision No. 243 of 2025, the official English text of Ministerial Decision No. 197 of 2026, and the Ministry of Finance eInvoicing programme information as starting points. Check the current wording and any later official instrument before relying on a date, technical requirement, penalty, or detailed reporting procedure. A summary or this responsibility matrix does not replace the instruments themselves.

Before assigning tasks, document whether the legal entity and each relevant transaction are in scope, the organisation’s implementation category, its relevant Registrant status, any Tax Group considerations, and whether special arrangements such as self-billing or agents apply. Do not assume that every invoice type or counterparty follows the same path. The trading partner onboarding guide and Article 6 Issuer and Recipient obligations guide provide more detailed context.

2. Responsibility matrix: who leads each workstream?

In this table, A means the internal role accountable for coordinating the outcome; R means the role doing the work; C means a role to consult; and I means a role to keep informed. These are suggested company assignments, not statutory job titles. Assign one accountable internal owner per row, adapt the table to the organisation’s size, and document any delegated authority.

*ASP participation depends on the signed service scope and confirmed operating model. Confirm which activities the provider performs, what evidence it returns, and which actions remain with the business. Do not infer a statutory transfer of responsibility from a technical delegation.

For a small company, one person may hold several roles. That is acceptable if responsibilities are explicit and critical actions have a review or escalation path. Where possible, separate master-data changes, tax-rule approval, payment release and production configuration so one person cannot silently introduce and approve a material error.

3. What each function should own

Finance and the executive sponsor

Finance should own the end-to-end process map, business case, cross-functional issue log, reconciliation design and readiness reporting. The executive sponsor should provide resources, settle conflicts between departments, approve the company’s risk appetite and make the internal go/no-go decision. This management decision does not replace any legal requirement or official implementation date.

Tax and Legal

Tax should maintain a source-backed decision log for scope, transaction classification, tax treatment, credit-note scenarios and exceptions. Legal or an appropriately qualified adviser should review contractual changes, liability wording, data handling, service commitments and unresolved legal interpretations. Record the source, date checked, interpretation, owner and next review date for each material decision. Escalate ambiguity rather than turning an assumption into a rule embedded in software.

Accounts payable (AP)

AP should define how supplier documents enter the process, how supplier and purchase-order details are matched, how exceptions are routed, and how a failed or disputed document is resolved before it affects payment controls. Agree with IT which statuses are visible to AP and how the team identifies missing, duplicate, rejected or corrected documents. Do not treat a PDF or email attachment as proof that every required electronic workflow has been completed. See the AP and Recipient workflow guide.

Accounts receivable (AR)

AR should own customer billing triggers, customer master-data quality, invoice and credit-note exception handling, and communication with sales and customers when a transaction cannot progress normally. Define how cancelled, amended, disputed or credited transactions are linked to the original business record. See the AR and Issuer workflow guide.

IT, data owners and security

IT should document source systems, field mapping, validation, interfaces, monitoring, identity and access controls, change management, backup and recovery. Finance and Tax—not IT alone—must approve the business meaning of tax-sensitive fields and exception rules. Data owners should identify the authoritative source for customer and supplier identifiers, addresses, tax registration information, item data, currency and transaction references. The data mapping and system integration guide provides a technical companion.

Procurement and the ASP

Procurement should coordinate due diligence and contract review with Tax, Finance, IT and Legal. The team should confirm the provider’s accreditation status from an authoritative current source, the exact service scope, implementation responsibilities, support coverage, incident escalation, data export, continuity arrangements and exit assistance. Ask the ASP to demonstrate the actual workflow and evidence it can provide. Do not assume the contract, provider portal or an informal sales statement resolves every legal interpretation.

ASP appointment deadline and accreditation status

Give one person, usually in Procurement or Legal with Finance consulted, the job of tracking the ASP appointment date for the company’s category and confirming that the chosen provider holds current accreditation. The appointment dates in the timetable this site tracks (see the key dates) are:

• Annual revenue AED 50 million or more: appoint an ASP by 30 October 2026.
• Annual revenue below AED 50 million: appoint an ASP by 31 March 2027.
• Government entities: appoint an ASP by 31 March 2027.

Ministerial Decision 168/2026, in force from 1 October 2026, replaced the earlier service-provider rules (Decision 64/2025 and its amendments, including Decision 56/2026). It removed the former pre-approval stage and introduced direct accreditation, so an earlier pre-approval label is not the same as accreditation under the current framework. Reconfirm a provider's current accreditation status through official channels before you appoint it. In practice, a provider still described as “pre-approved” should not be recorded as accredited in the company’s files until the owner has checked the official text of Ministerial Decision No. 168 of 2026 and the Ministry of Finance list of Accredited Service Providers. Record the date of that check and the source. Our ASP accreditation guide on Decision 168/2026 covers the questions to ask.

Tax Group intra-group transactions

Ministerial Decision 197/2026, which amended Decision 243/2025 with effect from 1 October 2026, treats Business Transactions between members of the same VAT Tax Group as Excluded Transactions for 24 months starting 1 January 2027 (amended Article 4(1)(f)). Check the full list of exclusions in the official text. Tax should own the list of legal entities that are members of the same VAT Tax Group and keep it current. AR, AP and IT should agree how intra-group transactions are flagged in the source systems so that they are not routed for exchange by mistake, while transactions with parties outside the group still are. Ask the ASP how that flag is used in its configuration, and test it before go-live. The Tax Group exclusion guide explains the exclusion and its time limit, and the participant identifiers and endpoints guide covers how counterparties are addressed.

Outages and incident notification

Decision 197/2026 repealed Article 12 of Decision 243/2025, which had dealt with system failure, and deleted the System Failure definition from Article 1. This site has not identified a replacement statutory procedure. Cabinet Decision 106/2025 still contains penalties for failing to notify the Authority of a System Failure within the prescribed timeline, so outages need a named owner. A practical split: IT logs every interruption that affects issuing or receiving documents (start and end time, affected documents, ASP ticket references); AP and AR record which transactions were held or resent; and a Finance or Tax owner decides, on current official guidance, whether and how the Authority should be told. Label any internal response time as an internal target, not a legal deadline. The system failure and continuity guide sets out an internal continuity plan without inventing a statutory procedure.

Record retention under Article 11

Article 11 of Decision 243/2025, as replaced by Decision 197/2026, requires Electronic Invoices, Electronic Credit Notes and associated data to be kept for the period prescribed under the Tax Procedures Law and produced to the FTA on request. The MoF announcement of the amendments states that the requirement to store data in the UAE was removed. This guide does not state a number of years. Make Finance accountable for the retention policy, Tax responsible for confirming the applicable period, IT responsible for archive settings, access and export, and Legal consulted on any other data-location obligations that arise from contracts or other laws. If the ASP stores documents under the contract, the company still needs to be able to retrieve and produce them, including after the contract ends. See the record-keeping guide and the data security and governance guide.

Penalty exposure under Cabinet Decision 106/2025

Cabinet Decision No. 106 of 2025 sets the administrative penalties for eInvoicing violations. Row 1 of its table covers failing to implement the system, including failing to appoint an ASP within the ministerial timeline: AED 5,000 for each month of delay or part of a month. Rows 2 and 3 charge AED 100 for each Electronic Invoice or Electronic Credit Note not issued and transmitted through the system within the prescribed timeline, up to AED 5,000 per calendar month. Someone has to watch for these exposures before they accrue. We suggest Tax as the accountable owner, with Procurement reporting ASP appointment status, AR reporting documents that were not issued and transmitted on time, and Finance including the exception counts in its monthly readiness or close reporting. Our penalties guide explains the full table and what remains unconfirmed about it.

Day-to-day workflows that need a named owner

The matrix rows above cover governance. After go-live, the same principle applies to recurring operational work. Each of these needs an owner and a deputy:

• Incoming invoice checks (AP): receiving documents and validating them against purchase and supplier records. See the invoice intake and validation workflow.
• Rejections and discrepancies (AP and AR, Tax consulted): recording why a document is disputed and how it is resolved. See the rejection and discrepancy workflow.
• Month-end reconciliation (Finance): matching ledger entries to documents exchanged and reported. See the month-end reconciliation guide.
• Agents and representatives (Tax and Legal): where another person issues documents on the company’s behalf, confirm who controls the records and corrections. See the Article 8 agent and representative guide.
• Self-billing (Tax with AP): where a buyer issues documents for its suppliers, agree the arrangement and its evidence. See the Article 9 self-billing guide.
• Training (Finance with each team lead): make sure each person knows the steps assigned to them. See the staff training and change management guide.

4. Make handoffs explicit

Most failures occur at boundaries: Tax approves a rule but IT does not implement it; AR changes a customer field but AP uses a different record; an ASP reports an error but no employee owns the correction. Use a handoff record for each material workflow. At minimum, capture:

• Trigger and input: what starts the work, the originating system, document type, counterparty and transaction reference.
• Decision owner: who confirms the business or tax treatment and who may approve an exception.
• Execution owner: who submits, corrects, retransmits or escalates the item, and which actions are performed by the ASP.
• Evidence and status: where the source record, validation outcome, transmission status, acknowledgement and exception history can be found.
• Service target and escalation: the internally agreed response time, backup owner and escalation route. Label internal service targets clearly; do not describe them as legal deadlines unless verified in an official instrument.
• Closure: who confirms that the exception is resolved, the accounting records reconcile and the evidence is retained.

For reporting specifically, Article 6(6) names both Issuers and Recipients in relation to reporting Electronic Invoices and Electronic Credit Notes to the FTA within the timeline prescribed by the Minister. The exact timeline and operational mechanics should be confirmed from the applicable official instrument before being configured as a deadline. Consult the Article 6(6) reporting obligations guide; do not infer the reporting clock from a different Article 6 paragraph.

5. Readiness checklist

• Assign a named accountable owner and deputy for every row in the matrix.
• Record legal entities, transaction types, scope decisions, implementation category and the official source supporting each decision.
• Map the current AP and AR processes, including credit notes, self-billing or agent cases where relevant.
• Agree which master-data fields are authoritative, who can change them and who approves tax-sensitive changes.
• Document ASP responsibilities, exclusions, support hours, incident routes and evidence available under the contract.
• Test successful, rejected, duplicate, corrected and unavailable-service scenarios using representative business cases.
• Reconcile source transactions to system outcomes and retain an exception log with owners and closure evidence.
• Verify the current official reporting timeline and technical instructions before setting legal deadline rules or automated alerts.
• Approve user training, operating procedures, access rights, contingency arrangements and the internal go-live decision.
• Schedule periodic reviews of official sources, system changes, ASP service performance and unresolved issues.

Use the readiness project plan to coordinate owners and milestones, the go-live testing checklist to structure evidence, and the record-keeping and archiving guide to design retention controls.

6. Common ownership mistakes

• “IT owns compliance.” IT can implement approved rules, but business and Tax owners must determine and validate the intended treatment.
• “The ASP owns everything.” A provider may perform contracted services; the company still needs an internal owner for oversight, exception decisions and evidence.
• “AP only checks PDFs.” The team needs a defined electronic workflow, clear status visibility and an escalation process.
• “AR’s transmission completes every obligation.” Do not assume that document creation, transmission, receipt and reporting are identical events.
• “One spreadsheet is the legal source of truth.” A tracker is a control aid. Maintain a link to the official instrument and review it when the law or official instructions change.

What this guide has not confirmed

The following points affect the assignments above, but this guide has not verified them from an official source. Give each an owner who confirms it from the official instruments or FTA guidance before it becomes a deadline, alert or system rule:

• The Article 6(6) reporting timeline. Article 6(6) refers to reporting Electronic Invoices and Electronic Credit Notes to the FTA within the timeline prescribed by the Minister. This guide does not state that timeline.
• The basis for a System Failure notification timeline. Cabinet Decision 106/2025 refers to notifying the Authority of a System Failure within a prescribed timeline, but after the repeal of Article 12 we have not identified which provision now sets that timeline.
• The number of retention years. Article 11 points to the Tax Procedures Law period. We do not state the number of years here.
• The exact date from which penalties apply. We have not confirmed the precise date from which the penalties in Cabinet Decision 106/2025 are applied, or from which day a delay is counted. Check the official text and current FTA guidance.

Frequently asked questions

Does UAE eInvoicing law prescribe this exact RACI matrix?

No. This is a suggested internal operating model. The applicable legal instruments establish the relevant obligations; a company allocates internal roles to meet them.

Can one employee cover Finance, AP and Tax coordination?

Yes, where appropriate for the organisation, but document the roles separately and introduce proportionate review, access control and escalation. Do not let role consolidation hide who made a tax decision or approved a production change.

Does appointing an ASP remove the company’s need for internal controls?

No. Confirm the provider’s contracted tasks and the evidence it returns. Keep internal ownership of business decisions, exception management, reconciliation and oversight explicit. The precise legal effect must be read from the applicable instruments, not inferred from the RACI table.

Who should own the Article 6(6) reporting deadline?

Assign an internal Tax or Finance owner to verify the authoritative timeline, with IT and the ASP responsible for implementing the confirmed operating process as agreed. Both Issuer and Recipient roles are named in Article 6(6). Do not set a legal deadline from an unverified assumption.

How often should the matrix be reviewed?

Review it when an official rule or implementation date changes, an entity or transaction flow changes, the ASP arrangement changes, a material incident occurs, or responsibilities move between teams. Set a routine review cadence as an internal control and record the review date.

Who should track the ASP appointment deadline?

One named owner, usually in Procurement or Legal, with Finance consulted and management informed. That person should also confirm the provider’s current accreditation under Decision 168/2026, because a former pre-approval label is not the same as accreditation under the current framework. Row 1 of Cabinet Decision 106/2025 links a missed appointment to a monthly penalty, so the status should be reported, not assumed.

Who decides whether a transaction is between members of the same Tax Group?

Tax should own that decision and the list of group members. AR, AP and IT apply it through agreed flags in the source systems. Under amended Article 4(1)(f), the exclusion applies for 24 months starting 1 January 2027, so the owner should also diarise its end.

Now that Article 12 is repealed, who owns outage notification?

The law does not assign a job title. We suggest IT keeps the incident log and a Finance or Tax owner decides on any notification to the Authority, based on current official guidance. Because we have not confirmed which provision now sets a notification timeline, treat any response time in your procedure as an internal target.

Official sources and related guides

• Ministerial Decision No. 243 of 2025 — official English text.
• Ministerial Decision No. 197 of 2026 — official English text.
• UAE Ministry of Finance eInvoicing programme information.
• Issuer and Recipient obligations under Article 6.
• Article 6(6) reporting obligations.
• Trading partner onboarding.
• Data mapping and system integration.
• Cabinet Decision No. 106 of 2025 on eInvoicing violations and administrative penalties — official English text.
• Ministerial Decision No. 168 of 2026 on service provider accreditation — official English text.
• eInvoicing penalties under Cabinet Decision 106/2025.
• System failure and operational continuity.
• Tax Group exclusion.

Editorial note: This guide describes a recommended internal responsibility model, not a government-approved matrix. Official-source links and the project’s regulatory source register should be rechecked before relying on a legal interpretation or changing a production control.