Ask a programme director who owns a failed transmission in week three after go-live and you will usually get a function named, not a person — which is the answer that means nobody.

UAE programmes are entering their final implementation quarter with steering committees, RACI charts and a named programme director. Few of them have an answer to who owns a rejected invoice on the third Tuesday of February 2027, once the steering committee has held its closure meeting and the programme director has moved to the next portfolio item.

The Compliance Project Handover Illusion™

The Compliance Project Handover Illusion™ is the belief that a completed implementation transfers cleanly into business-as-usual because a go-live date passed and a project closed. It treats handover as an event that follows delivery rather than a deliverable of it. The illusion holds until the first decision that requires cross-functional authority arrives without a programme structure to convene it.

Tax, IT or Finance Is an Accountability Question

The question surfaces in nearly every steering committee that launches an e-invoicing programme, and it is usually asked after the budget line has already been assigned to one function and the other two have been copied on the kickoff email. Tax sees a compliance obligation with a legal deadline. IT reads the same programme as a system integration with a defined scope: connect the ERP to an accredited service provider, map the fields, pass the schematron validation, done. Finance treats it as a change to the invoice-to-cash cycle for the shared services team to absorb.

Treated as a positioning debate, this consumes a year that programmes do not get back. Treated as an accountability question, it produces something useful: a decision about who is answerable once the programme structure dissolves. During implementation, the ambiguity stays masked, because a director convenes the functions and decisions get made by someone paid to make them happen. After close, the same decisions require a standing owner, and in most enterprises none was ever named.

Shared Ownership Becomes No Ownership

Cognitive Responsibility Diffusion™ is the mechanism. Accountability gets assigned to a title while the decision is made by a process, and the process runs across functions none of which holds the complete picture. A product classification sits in master data, maintained by Finance or an MDM team. The rate that applies to it sits in the determination engine, configured by IT to a specification Tax provided. The transaction was generated by Operations, which recorded the business event without reference to its tax consequence. The document that transmitted the position was produced by the ASP integration layer.

When the authority queries that position, the answer requires someone who can trace the chain from business event to transmitted document. A RACI structured around titles leaves the failure point untouched, because the failure point is an unowned boundary rather than a missing title. The only letter in a RACI that cannot be shared is Accountable, and two Accountables for the same decision point produce the same outcome as none.

The Four Domains to Name Before Close

Four standing ownership domains carry the operating risk after go-live, and each needs a named person rather than a function:

  • Determination — who owns the correctness of the tax logic embedded in system configuration, and who approves a change to it before it goes live.
  • Transmission — who owns the transmission pipeline’s operating state, including certificates, queues and acknowledgement reconciliation.
  • Exception response — who holds the decision right to resolve a rejected or flagged transaction within the window a real-time environment allows, without further approval.
  • Evidence — who owns the ability to reconstruct any transmitted position from source data when an authority query arrives.

Handover Is a Deliverable

Each of those four domains needs a name against it, a defined scope, and a date on which the accountability transfers — produced by the programme, signed off before closure, and reported as a deliverable in the same way an integration test result is. A programme that cannot produce that document is not finished, whatever the dashboard says on 2 January 2027.

The alternative is discoverable in week three, when a transmission fails and four functions each point to another.