Moniepoint's 100 Billion Transactions Show Data Lineage Is an AI Governance Prerequisite

What happened

Why it matters

• ·Financial regulators are converging on end-to-end auditability as a minimum standard for AI in transaction processing. The OCC Model Risk Management: Revised Guidance (Bulletin 2026-13) and the MAS Guidelines on Artificial Intelligence Risk Management both require firms to demonstrate that AI-assisted decisions can be fully traced, a standard that cannot be met if the underlying data layer lacks chain-of-custody controls.
• ·The maker-checker pattern described in the article maps directly to human-in-the-loop requirements in emerging AI governance frameworks. Compliance teams that have addressed human oversight only at the model output level, rather than embedding it into data workflows, may find their controls fall short during regulatory examination.
• ·Many enterprises assume that vendor-provided audit logs are sufficient to satisfy AI auditability obligations. This case study illustrates that without canonical data definitions and provenance controls at the infrastructure layer, vendor logs cannot establish who or what logic was responsible for a given AI output, creating a material gap in audit trail completeness.

Governance controls affected

What to do now

• ☐Audit whether your AI systems in financial workflows can trace each output back to a specific data source, transformation step, and responsible engineer or logic unit — not just to a model version.
• ☐Map your existing maker-checker or dual-control workflows to the human oversight requirements in applicable regulatory guidance, and document where human approval gates exist only at the policy level rather than in the system architecture.
• ☐Review canonical data definitions across AI pipelines to confirm that identical terms mean the same thing in every upstream and downstream system feeding AI models used in reconciliation or credit decisions.
• ☐Assess whether your log retention policy captures the full chain of custody from raw transaction data through model input and output, and verify that logs are tamper-evident and retrievable within your audit trail SLA.
• ☐Include data governance infrastructure maturity as a criterion in your AI vendor due diligence process, specifically asking vendors whether their AI outputs can be traced to source data provenance.

What to watch next

Regulatory expectations for AI auditability in financial services are tightening across jurisdictions. The Financial Stability Board Recommendations on Agentic AI Controls in Financial Services signal that supervisors will increasingly treat data lineage gaps as control failures rather than documentation gaps. Compliance teams should also monitor how the Treasury Department AI Risk Management Framework for Financial Services translates auditability principles into examination criteria, as that framework is likely to influence how US regulators evaluate AI-assisted reconciliation and reporting systems in the near term.