An international investment bank moved from 180 fragmented Excel models into one automated system in 90 days, with defensible detailed service based chargebacks posted into the general ledger.
Major international bank.
Chargeback programs usually struggle at the first dispute. A business unit receives a lump-sum recharge and asks how it was calculated, and the IT finance team spends two weeks rebuilding the answer in a spreadsheet. By the third month the program is back to showback. By month six, nobody reads the report.
One number per business unit, with no itemized services, volumes or rates behind it. Nobody can understand it, so they challenge it on principle.
The recharge lives in a report. Finance makes manual adjustments or ignores it, and the two never agree.
Real chargeback needs a service catalog, rates and volumes that the business recognizes. Most attempts stop at allocation, so the business never buys in and IT finance keeps operating as an island.
Once a recharge can be understood and explained line by line, it stops being an argument and becomes an invoice.
Runs the program and calculation. Needs rate cards, allocation rules and a dispute process that does not become a personal workload.
Posts the charge. Needs journal entries that land in the ERP, reconcile to source and survive audit.
Answers for the total. Needs to show what each service costs and that the recovery is fair.
Pays. Needs to see services, volumes and rates, and to challenge a line rather than the whole bill.
Disputes end faster when the provider owns the rate and the consumer owns the volume, because neither can hide behind the other.
Four capabilities carry this. Data Studio, Analytics and AI Studio come with every one of them.
Produces the Bill of IT out of the box from the TBM cost model: towers, services, unit costs, volumes and charges, for any period.
Calculates the recharge amount, rates, markups, discounts and fixed-rate recoveries behind the charge. Move chargeback beyond IT for HR, logistics, property and intercompany.
The cloud element in the bill, allocated daily, so the cloud line is current and not a month behind.
Allocate your largest cost, labor, directly into the building blocks of the bill. See how the initiatives the business funds translate into services and charges.
Each business unit sees the services it consumed, the volume, the agreed rate and the resulting charge, all on a rate card signed off by finance and technology. Every line traces from the provider invoice to the consuming business unit, in both directions.
Showback builds visibility. Chargeback builds ownership, because nobody treats it as free once it has a price. Move each area at its own pace. Cloud can run in chargeback while AI stays in showback until a baseline exists. IT Finance signs off before charges are final, then the journals post to the ERP, so the bill matches the ledger.
Business owners see their own bill in embedded Power BI, with current and prior periods, variance, and drill-down to the consumption behind every charge. When they can check the numbers themselves, they trust them and stop disputing them.
Costed with an automated Bill of ICT, TBM-aligned, with cross-agency transparency.
eHealth Queensland.
The TBM taxonomy defines the towers and services the bill is itemized against. The FinOps Framework includes showback and chargeback in how it quantifies business value. MOTEF runs the same bill across all spend categories, so labor and AI appear beside cloud and the data center.
