A RACI matrix borrowed from a generic project-management template will tell you who's responsible for a task. It won't tell you that master data and transaction data carry entirely different ownership patterns in a UAE e-invoicing build, or that the function accountable for a field and the function that actually maintains it are routinely two different teams. Chapter 11 of Real-Time Tax Transformation (forthcoming) builds a RACI specific to the four data categories a PINT-AE implementation actually touches, and the distinctions between them explain a failure mode the site has already covered: Cognitive Responsibility Diffusion™, where accountability for a decision becomes impossible to locate because it was never assigned to begin with.
Master data
Master data is the standing configuration every transaction's tax treatment depends on — customer and supplier registration status, product classification, rate codes. Three functions touch it with genuinely distinct roles: tax is Responsible for defining the rules, finance or the MDM function is Responsible for the maintenance process that keeps fields current, and IT is Responsible for the system configuration and validation. Accountability defaults to tax in most enterprises, which creates a specific problem — tax answers for an outcome that depends on finance keeping a field current and IT building a validation neither of which tax controls. The correct split makes tax Accountable for the rules and for flagging drift from them, finance Accountable for maintenance, and IT Accountable for the configuration that enforces it, with tax Consulted before any change, not Informed after it.
Transaction data
Transaction data is generated at the point of a business event: price, quantity, delivery confirmation, a customer's registration status at order entry. Operations is Responsible for generating it, finance for recording it. The accountability gap is the one most enterprises leave unowned — whether the data is correct for a real-time transmission, at that moment, not correctable afterward. Under buffered compliance, finance absorbed this timing risk; under real-time transmission, an invoice can transmit before the underlying delivery is even recorded. The fix is making operations Accountable for completeness at the point of generation, with tax Consulted on which fields carry a transmission consequence as an input to process design, not a final check.
Contextual data
Contextual data is the evidence layer — delivery confirmations, exemption certificates, pricing basis, decision records — that makes a transmitted position defensible under audit. Most enterprises have no formal RACI for it because no equivalent obligation existed under periodic filing. Operations and finance generate most of it, typically for logistics or commercial purposes with no awareness of a tax evidence obligation, and it gets discarded once that original purpose is served. Accountability has to sit with the function that generates each type, with tax Consulted before the process is designed on what to retain, in what form, for how long, not after an audit request arrives for a document that no longer exists.
Integration syntax
Integration syntax is the mapping between internal systems and the PINT-AE document an ASP transmits. IT is Responsible for the technical mapping; tax is Responsible for the meaning each field is supposed to assert. This is the highest-risk unowned boundary in the model, because IT doesn't know the tax consequence of a mapping change and tax doesn't know the technical consequence of one. A mapping changed for a legitimate technical reason — an ERP upgrade, a field rename — can pass every ASP validation and still transmit the wrong tax meaning. Accountability needs a named role holding both dimensions, or a formal change-control process requiring tax sign-off before any mapping change goes live.
Across all four categories, the pattern repeats: the failure originates upstream, in a maintenance process finance didn't govern or a mapping IT changed without review, and the penalty lands on tax regardless of where the gap actually opened. A RACI that assigns Accountable to tax for the output without assigning Accountable to the upstream functions for the inputs accepts that pattern as the natural order, and leaves the governance model unchanged from the one that produced the failure.