Every Function in the Enterprise Has a System of Record. Except AI.

Picture the quarterly business review. The CRO walks in with pipeline and bookings pulled from Salesforce. The CFO has the close from the general ledger. The CHRO has headcount and attrition from Workday, the CIO has incident and asset counts from ServiceNow, and the CISO has the quarter’s access review from Okta. Nobody in the room debates whether those numbers are right. They argue about what to do about them, which is what a leadership meeting is for.

Then the Head of AI presents. The slide was built from a spreadsheet, and the spreadsheet was built from four vendor consoles, last month’s cloud invoice, a license count from procurement, and an HR extract to map API keys to teams. The total does not match the figure the CFO has for AI, because the ledger sees invoices and the consoles see usage, and nothing in the company ties one to the other. Ten minutes go to reconciling instead of deciding. That scene is playing out in most large companies right now, and it is not a competence problem. Every other function in the room is reporting from a system of record. AI is reporting from a spreadsheet, because AI is the one function that still does not have one.

The numbers say the same thing. In KPMG’s Q2 2026 AI Pulse survey of 204 US leaders at companies above $1 billion in revenue, 66% said they have AI cost monitoring dashboards and 61% have cost reviews in their approval process, yet only 26% report full, real-time visibility into what their AI costs to operate, and only 36% have any direct token or usage controls. Two thirds have a dashboard. One quarter has the record underneath it. A dashboard without a system of record is a chart of whatever happened to be exported that week.

What the nine already have in common

A system of record is the authoritative source for one kind of data, the place everyone agrees is correct when two reports disagree. Geoffrey Moore’s 2011 paper for AIIM drew the line between these transactional backbones and the “systems of engagement” people actually work in, and the distinction has held up: the engagement layer changes every few years, the records underneath it do not. We covered the definition and its three properties, authoritative, complete and durable, in What Is an AI System of Record?, so this post takes the definition as given and looks at the list instead.

Look at how each of the nine came to exist and a pattern appears. None of them was adopted because the function wanted better software. Each one arrived when a function’s spend or its risk crossed a threshold where a spreadsheet stopped being an acceptable answer to the board or the auditor. The ledger predates computers because money crossed that threshold first. CRM took hold when a sales organization’s pipeline became too valuable to live in individual reps’ notebooks. FinOps tooling appeared when cloud bills got large and variable enough that finance could no longer wait for the invoice to learn what engineering had done. AI crossed the same threshold in 2025 and 2026, as coding agents and model APIs moved from per-seat licenses to usage-based billing and the monthly figure started moving with behavior rather than with headcount. The record is late, and the rest of this post is about what it should look like when it arrives.

The ten systems of record, and what each one teaches AI

Here are the nine systems of record a large enterprise runs today, the question each one is trusted to answer, and the discipline each one established that an AI system of record has to inherit. The tenth row is the one that has been missing.

Visibility: the CRM and the CMDB

Every sales leader enforces the same rule, usually in those words: if it is not in the CRM, it did not happen. The rule is not about tidiness. It exists because a forecast built on deals that live in someone’s inbox is not a forecast, and because the moment one rep’s deals are allowed to live outside the system, every number downstream of it becomes negotiable. IT learned the equivalent lesson the hard way with the configuration management database: you cannot patch, secure, or decommission a server you do not know you run, so the inventory comes before the policy. Applied to AI, those two rules are the whole case against tolerating shadow AI. The usage that happens in unsanctioned tools is not a side issue to be cleaned up later; it is the part of the record that is missing, and every adoption figure, cost figure and risk assessment is wrong by exactly that amount. Olakai treats the inventory as the first job, maintaining an app catalog of more than 800 AI tools and recording what employees do in them, so that the record is complete before anyone is asked to trust a number from it.

Money: the ledger and FinOps

The general ledger established two habits that nobody in finance questions any more. The books close, on a schedule, and the closed figure is the figure. And every dollar carries a cost center, so that “what did we spend” always has an answer to “on what, and for whom.” Cloud FinOps added a third habit two decades later: because engineers make cost decisions thousands of times a day without seeing the invoice, the spend has to be shown back to the team that caused it while they can still change course, and budgets have to warn before the month is over rather than report after it. AI spend violates all three habits by default. The provider’s console shows an estimate, the invoice arrives later with a different figure, and the two are rarely reconciled, which is why Olakai reconciles its usage data against the billing export for providers like Google Vertex AI rather than multiplying tokens by a list price and calling it cost. Attribution is harder than it was for cloud because API bills arrive by key, not by person, so a shared key is unallocated spend until someone maps it. And a budget in any analytics platform can only alert, never cap, so the useful control is the forecast alert that fires when the daily run rate points past the limit. We went through what carries over from the cloud playbook and what does not in FinOps for AI, and how Olakai’s budgets and alerts are built around that constraint.

People and identity: the HRIS and the identity provider

Workday’s quiet achievement is that there is one org chart. Finance, IT and the business all allocate against the same hierarchy of departments and managers, so a per-team figure from one system can be laid next to a per-team figure from another and the teams line up. The identity provider did the same for people: one identity, carried into every application, so that an access review can ask “what can this person reach” and get one answer rather than forty. AI breaks both. Each provider has its own notion of a user, a developer might hold an Anthropic key, an OpenAI key, a Cursor seat and a GitHub Copilot license under four spellings of their name, and none of those vendors knows the org chart. An AI system of record has to resolve them to one person in one department before any per-team or per-developer figure means anything. Olakai does that mapping across its provider integrations and then reports against the organization’s own units, which is what makes figures such as cost per employee and the power, casual, new and idle adoption cohorts comparable from one team to the next.

Provenance, outcomes and attribution: Git, ticketing and marketing automation

The last three teach the part most AI reporting skips. Git made provenance a default: every line of code has an author, a timestamp and a reason, and “who changed this and why” is a command, not an investigation. The support desk made the outcome part of the record, because a ticket count tells you nothing while a ticket with a resolution and a time-to-resolve tells you how the function is performing. And marketing automation spent fifteen years on the hardest problem of the three, attribution, connecting a touch to the revenue it eventually produced, imperfectly but well enough to fund the next campaign. AI needs all three at once. For coding tools, Olakai reads the pull request history that Git already keeps and identifies which changes AI touched without installing anything on developer machines, so provenance comes from the system of record engineering already trusts. For assistants and agents, it records the interaction and what came back, not only that an interaction occurred. And for the question the board actually asks, it ties that activity to KPIs defined in the business’s own terms, which is the attribution problem again, with tokens where the ad spend used to be.

The tenth row

Put the nine lessons together and the tenth system of record writes its own specification. It has to be complete, so anything outside it is treated as a gap rather than ignored. It has to reconcile to the invoice and allocate to a cost center. It has to use the organization’s real hierarchy and resolve every provider’s idea of a user to one person. It has to keep provenance and outcomes, not activity counts, and it has to attribute both to business results. And it has to do this across every vendor, because no function runs all of its AI through one provider and a record kept by a vendor will only ever describe that vendor. That last requirement is the one the market keeps getting wrong. Every AI vendor ships a dashboard, and every one of those dashboards is a system of engagement for its own product. None of them is the ledger.

That is the gap Olakai was built to fill: the vendor-neutral system of record for the entire AI stack, capturing every interaction and outcome from coding agents, workforce assistants and autonomous agents, down to the token and its cost, and structuring it by user, team, department, project, agent, model and vendor. Olakai Agentic covers the coding tools and agents, Olakai Assistive covers the assistants employees use all day, and both write to the same record. The point of a system of record is not the chart on top of it. It is that when the CFO and the Head of AI walk into the same meeting, they are reading the same number, and the ten minutes go to the decision.

Why AI was the exception, and why that ends now

AI did not get a system of record on schedule for three structural reasons, all covered in more depth in the definitional post. Nobody types into it, so completeness depends on coverage rather than on discipline. It spans vendors by design, so no single supplier can keep it. And its unit is the interaction and the token, so the volume is millions of events a month rather than thousands of transactions, which rules out the manual reconciliation that got finance through the first two years. Add the fact that AI is the first function whose spend crossed the threshold before its record existed, rather than after, and the spreadsheet in the opening scene stops looking like a failure of the person holding it. It is the predictable result of asking one function to report without the infrastructure every other function was given decades ago.

What ends the exception is the same thing that created the other nine. The spend is now large enough, and variable enough, that the board will not accept an estimate, and KPMG’s finding that three quarters of billion-dollar companies lack real-time visibility into AI cost is the number a board member will quote back. Dashboards were the first response, and the survey shows how far they got. The record is the second, and the enterprises that build it in 2026 will be the ones whose AI reporting looks like their finance reporting rather than like their expense reports. The signals an AI system of record should carry, and which ones a CFO will actually read, are the subject of a separate post.

Where to start

Nobody rolled out an ERP in a week, and an AI system of record does not need to cover all ten disciplines on day one. Start with the function where the spend is largest and most variable, which in most companies today is AI coding tools. Connect the providers you already pay, map the keys to people and the people to teams, and reconcile one month of usage against the invoice. The first time the Head of AI and the CFO present the same figure, the rest of the organization will understand what the record is for, and the remaining disciplines follow the way they did for every other function: because the alternative is a spreadsheet nobody trusts.

If you would like to see what the tenth row looks like with your own providers connected, talk to an expert.