IT vs Finance: Who Should Own E-Invoicing Implementation in UAE Enterprises
NOV 03, 2026

IT vs Finance: Who Should Own E-Invoicing Implementation in UAE Enterprises

Your e-invoicing project has a go-live date, an ERP change request in the queue, and two departments each waiting for the other to take the lead. Finance assumes integration is an IT job. IT assumes tax rules are a Finance problem. Meanwhile the Federal Tax Authority (FTA) mandate runs on its own calendar. This article gives you a working ownership framework for UAE enterprises: which decisions belong to Finance, which belong to IT, who signs off at each phase, and what breaks when the split is wrong. You will leave with a structure you can put in front of your CFO this week.

Why ownership is contested in UAE e-invoicing projects

The UAE did not build a central government portal. It adopted a decentralised model on Peppol, a global network for exchanging structured business documents. Under the five-corner model, your business sends invoices through an Accredited Service Provider (ASP), the buyer receives them through its own ASP, and tax data is reported to the FTA as a Continuous Transaction Control (CTC) flow. Invoices follow the PINT-AE specification (the Peppol International Invoice format, UAE profile).

The framework is set out in Ministerial Decisions No. 243 and 244 of 2025, published by the Ministry of Finance, with a phased rollout by revenue band and a separate date for government entities. The mandate covers B2B and B2G e-invoicing in the UAE, with B2C excluded for now.

This is why ownership is awkward. Half the work is deciding what an invoice must say (tax content). The other half is making your systems say it correctly, every time, to an external network (integration). The two halves live in different departments.

What Finance must own: tax logic, invoice content and the ASP decision

In the readiness assessments we run, the most frequent gap is that nobody can say who approved the tax code mapping table. That table belongs to Finance.

Finance should own:

  • Tax treatment mapping. Standard-rated, zero-rated, exempt, out-of-scope and reverse charge supplies each map to specific PINT-AE fields. Someone with VAT judgement must sign that mapping, not someone who knows the API.
  • Transaction scope. Which invoice types are in scope, how credit notes are linked to original invoices, how self-billing and summary invoices are handled.
  • Master data accountability. Customer Tax Registration Numbers, Peppol identifiers and tax codes. IT can maintain the records, but Finance is answerable for their accuracy.
  • ASP selection criteria from a compliance view. Sector coverage, exception handling, reporting confirmations and support response times matter more than connector count. A neutral comparison of ASP options against your invoice profile is where many finance teams ask for outside help.
  • Reconciliation and controls. Matching what the ERP issued, what the ASP transmitted and what the FTA acknowledged, with an audit trail that survives a tax audit.

What IT must own: integration, data pipelines and system resilience

IT cannot decide a VAT treatment. Finance cannot design a retry queue. IT’s remit is everything between the ERP and the ASP.

IT should own:

  • Integration pattern. Native connector, middleware or direct API, chosen for your landscape, including SAP, Oracle, Dynamics, Zoho, Tally or a legacy system that stays in place past go-live.
  • The data pipeline. Extraction from source modules, transformation into PINT-AE XML, and validation before anything reaches the ASP.
  • Resilience and incident handling. Queuing, retries, monitoring, and a documented path for malfunctions, since Ministerial Decision No. 243 of 2025 sets out system failure obligations.
  • Security and archiving. Access control, encryption in transit, and retention of issued and received invoices for the statutory period.
  • Environments and cutover. Test tenancy with the ASP, data migration, rollback plan.

The ownership model that works: Finance accountable, IT responsible, CFO sponsoring

PwC describes the UAE mandate as more than a tax project, one that needs finance, tax, IT and procurement working together. The practical question is what “together” means on a Thursday afternoon when an invoice has just been rejected.

The split that holds up:

  • CFO as sponsor. The role that can settle a Finance versus IT disagreement without a six-week delay. Sponsorship means budget authority and decision rights, not weekly task management.
  • Finance as accountable owner. The function that answers to the FTA for invoice content owns the outcome.
  • IT as responsible delivery lead. Owns the build, the environments and the technical runbook.
  • Tax or Compliance as the rule-setter. Interprets the Ministerial Decisions, the FTA data dictionary and later clarifications.

By phase:

  • Scope and impact assessment: Finance leads, IT supplies the system inventory.
  • Gap analysis against the PINT-AE data dictionary: joint. Finance decides what each field means, IT decides where it comes from.
  • ASP selection: Finance leads, IT runs technical due diligence.
  • Integration build: IT leads, Finance supplies written business rules.
  • User acceptance testing: joint sign-off on real cases, including partial deliveries, credit notes and intercompany invoices.
  • Go-live and ongoing operation: Finance owns rejections and reconciliations, IT owns uptime and incidents.

Three failure patterns we see when ownership is unclear

The integration project. IT owns it end to end, the connector works, and invoices fail on content: wrong tax category codes, missing buyer identifiers, credit notes with no reference. Nobody owns rejections, so they sit.

The tax project. Finance selects an ASP on a strong compliance pitch, then discovers the ERP cannot populate several mandatory fields. Staff re-key data into a portal, and the project quietly becomes manual.

The shared project with no sponsor. Both departments contribute, but every boundary decision escalates and waits. Advisers quoted by Gulf News have flagged unclear ownership as a common risk, and this is what it usually looks like.

Multi-entity groups: central governance, local execution

Groups with several UAE entities face a second ownership layer. Entities may fall into different mandatory phases based on revenue, run different ERPs, and sit inside a VAT group with its own treatment questions.

What works is a group-level data dictionary and ASP policy owned centrally by Finance, with entity-level IT teams responsible for their own integrations against that standard. One steering group, one rulebook, several delivery tracks. Without that, the group ends up reconciling four interpretations of the same rule.

Where an outside compliance advisor fits between Finance and IT

Many of the projects we support start with the same request: translate the regulation into requirements that IT can build and Finance can sign. Few enterprises can fill that bridging role internally, because it needs VAT knowledge and ERP fluency in the same room.

An advisor positioned outside the ASP market can compare providers without a commission at stake, run the readiness assessment, write the mapping rules, sit in testing, and stay on after go-live to manage rejections and regulatory updates. The background of a UAE-based audit and tax practice explains why that advice leans toward controls rather than software features.

Conclusion: decide the owner before you decide the vendor

The framework in short: Finance is accountable for invoice content, tax logic, master data and the ASP decision. IT is responsible for integration, pipelines, resilience and cutover. The CFO sponsors and arbitrates. Every phase has a named signatory from each side, and groups add a central rulebook with local delivery. Agree this first, and vendor selection, testing and go-live become sequencing problems rather than political ones.

If you want a second opinion on your current ownership structure, or a readiness assessment that gives Finance and IT a shared requirements document, talk to our UAE e-invoicing specialists. AA Tech works alongside your teams and your chosen ASP, not in place of them. For related reading on PINT-AE mapping, ASP selection and ERP-specific integration, visit the e-invoicing blog library.

Frequently asked questions

Who should own e-invoicing implementation in a UAE company, Finance or IT?

Finance should be the accountable owner, because it answers to the FTA for invoice content, tax treatment and master data accuracy. IT should be the responsible delivery lead for ERP integration, data transformation into PINT-AE format and system resilience. A CFO-level sponsor resolves disputes between the two. Projects led by one function alone tend to stall at the boundary between tax rules and system behaviour.

What does the IT team actually do in a UAE e-invoicing rollout?

IT designs the integration between your ERP and your ASP, builds the pipeline that converts invoice data into PINT-AE XML, validates output before transmission, and sets up monitoring, retries and incident handling. It also manages test environments, cutover and archiving. IT does not decide VAT treatments or transaction scope. Those decisions come from Finance as written business rules that IT implements.

Does the UAE e-invoicing mandate apply to both B2B and B2G transactions?

Yes. Under Ministerial Decisions No. 243 and 244 of 2025, the Electronic Invoicing System applies to business-to-business and business-to-government transactions for persons conducting business in the UAE, with specific exclusions listed in the Decisions. Business-to-consumer transactions are outside the current scope until the Minister decides otherwise. Government entities have their own implementation date, separate from the revenue-based phases that apply to businesses.

When does e-invoicing become mandatory for large businesses in the UAE?

Ministerial Decision No. 244 of 2025 sets a phased rollout. Businesses in the first revenue band must appoint an ASP first and begin issuing e-invoices from 1 January 2027, with remaining businesses following from 1 July 2027 and government entities from 1 October 2027. The Ministry of Finance has amended the ASP appointment deadline since the original Decision, so confirm current dates on mof.gov.ae before planning.

Who should choose the Accredited Service Provider, Finance or IT?

Finance should lead ASP selection with IT performing technical due diligence. Finance evaluates compliance coverage, exception handling, reporting confirmations and support commitments. IT evaluates connector compatibility with your ERP, API documentation, test environment quality and data security. Selecting on technical fit alone risks content failures after go-live, while selecting on compliance pitch alone risks an ERP that cannot populate mandatory fields. Both views are needed before signing.