Finance may be looking at accounts, departments, accruals, invoices, budgets, and forecast lines.
The CIO may be looking at applications, vendors, contracts, projects, risks, business commitments, and technology decisions.
Both views can be valid.
The problem appears when leadership expects one answer.
The same dollar can have two stories Finance might see software spend running above plan.
The CIO might know that the increase came from an approved acquisition, additional cloud capacity, a new analytics initiative, or an enterprise license change.
The number and the explanation often live in different places.
That creates friction.
Finance asks:
Why did this increase?
IT begins reconstructing what happened.
Procurement checks the contract.
A project leader searches for an approval.
Someone finds an email.
Eventually, the story comes together.
This is an expensive way to answer a basic management question.
Reconciliation comes first Before discussing strategy, both teams need confidence in the baseline.
If IT and Finance are working from different numbers, the meeting quickly becomes a reconciliation exercise.
Budget and actuals need to align with the financial source of record.
Once that baseline is trusted, the more useful conversation can begin.
Why did the number change?
Finance owns financial truth. IT owns much of the context. Finance is well equipped to explain how money was recorded.
The Office of the CIO often holds the information explaining why the spend occurred.
For example:
A project was accelerated.
A contract was expanded.
A vendor introduced a new commercial model.
Usage increased.
A business unit requested additional capability.
An executive approved incremental spend.
The financial system may capture the transaction without preserving all of that decision context.
Capture the reason close to the decision Suppose a cloud workload is approved in February.
Usage ramps during March and April.
The financial effect becomes visible in May.
By May, Finance sees an increase.
The CIO should be able to trace that increase back to the February decision.
The useful record would include:
what was approved,
why it was approved,
who owned the decision,
the expected financial impact,
and what should happen next.
That changes the budget meeting.
Move from reconciliation to decision The goal should be a shared operating view where Finance and IT can move quickly from the number to its explanation.
Then the conversation changes from:
Whose number is right?
to:
What decision do we need to make?
That is a much better use of both the CIO's and CFO's time.
Related Insights
More on shared evidence for the CIO–CFO budget conversation:
What is a CIO Operating System? — the operating layer that connects evidence to decisions.
CIOs need better evidence for where to place the next dollar — spend evidence before the next allocation.
Why technology budgets keep surprising CIOs — variance as an operating problem, not a spreadsheet surprise.
How CIOs should explain technology budget variances — a defensible story when the number moves.
Token prices fell. AI bills rose. The CIO forecast still has to work. — consumption economics the CFO will ask about next.
If you want a private briefing on connecting technology evidence to executive decisions, request a private briefing.