Most IT spend figures reported to the CFO are wrong — not because the data is missing, but because it lives in too many systems with no single reconciliation layer. Finance sees the invoice. IT sees the contract. Procurement sees the renewal. None of them are looking at the same number at the same time.
The result is a gap. Not a small one. In most enterprises, the gap between what finance reports and what IT actually spends sits somewhere between eight and fifteen percent. That gap is not an accounting error. It is a structural feature of how IT spending is tracked.
The three layers that don't talk to each other
Enterprise IT spend flows through at least three separate systems: the general ledger, the software asset management tool, and the contract repository. Each of these systems was built to solve a different problem, and none of them were designed to be reconciled against each other automatically.
The general ledger captures what was paid. The software asset management tool captures what is licensed. The contract repository captures what was agreed to. When you try to answer the question "what are we spending on this vendor," you are pulling from all three, and the answer is different depending on which one you start with.
Why the fix is not more data
The instinct when the numbers don't reconcile is to collect more data. More granular invoice line items. More frequent license counts. More detailed contract metadata. But the problem is not the volume of data. It is the absence of a deterministic reconciliation layer — a set of rules that takes the three sources and produces one number that is the same every time you run it.
Without that layer, every report is a manual exercise. The analyst reconciles the three sources by hand, documents their methodology in a spreadsheet comment, and produces a number that is accurate as of the moment they closed the file. Six months later, when the auditor asks how that number was produced, the answer is "I don't know — the analyst who built it left."
What a deterministic layer looks like
A deterministic reconciliation layer has three properties. First, it is rule-based: the same input always produces the same output, with no judgment calls embedded in the computation. Second, it is auditable: every output can be traced back through the rules to the source data, step by step. Third, it is versioned: when the rules change, the old rules are preserved so that historical numbers can be reproduced under the methodology that was in effect at the time.
With those three properties, the IT spend number stops being a quarterly exercise and starts being a system. The CFO can ask the question on a Tuesday afternoon and get the same answer they would get on a Thursday morning, without anyone having to reconcile a spreadsheet.
That is what TekLedger is built to do.