CHARGE THE BUSINESS FOR
WHAT IT ACTUALLY USES
Every team says their bill looks wrong. Their usage doesn’t match what they’re being charged, because the charge was never built from usage in the first place.
—
The bill everyone gets is last year’s budget divided by twelve, not what anyone consumed.
—
The one time you tried to change a team directly, they disputed it and you backed off for eighteen months.
—
Shared infrastructure shows up as ‘‘other’’, and ‘‘other’’ keeps growing.
THE BILL NOBODY TRUSTS
Most cost allocation efforts skip a step. They go straight to billing a team for what they supposedly used, before anyone has checked whether the underlying number is right. The first time a team gets charged for capacity they didn’t touch, or for a shared system with no clear allocation logic, they push back, and they’re right to. That one bad bill outlives the program that sent it.
Sequencing check
What it takes before you bill for it
| Question | What has to be true first | Status |
|---|---|---|
| Coverage | What has to be true firstSpend is tagged and traced to a team or service, not estimated | ✓ In place |
| Shared costs | What has to be true firstSplit by a documented rule, not left in "other" | — Not yet |
| Ownership | What has to be true firstSomeone in finance signed off on the allocation logic | ✓ In place |
| Trust | What has to be true firstTeams have already seen the number as showback, and it held up | — Not yet |
Any row marked "not yet" is a reason the bill will get disputed. Billing before all four hold is what turns one bad invoice into an eighteen-month setback.
The number is hard to trust because a service’s real cost rarely lives in one place. The general ledger tracks spend by vendor and account, not by the service it supported. Shared infrastructure, the platform three teams run on, the licenses nobody remembers assigning, gets lumped into an ‘‘other’’ line that grows every quarter because nobody owns untangling it.
‘‘A TEAM BILLED ONCE FOR THE WRONG WILL DISPUTE THE NUMBER FOR YEARS, EVEN AFTER IT’S FIXED.’’
WHAT IT TAKES
Not a chargeback rollout on day one. Visibility first, then billing, in that order.
Define what counts as a service — not a vendor, not a GL line — and map every cost to it, direct and shared, with a documented rule for anything that gets split.
Define the service, then map to it
Show that number back to the teams consuming it before anyone’s charged for it, so the allocation logic gets tested against reality while the stakes are still low.
Show it back before you bill it
Start with the biggest or most cost-literate consumers, and leave genuinely shared infrastructure on showback rather than forcing a split nobody believes.
Move the ready teams onto billing
WHY WE CAN SAY THAT
01
We’ve built these service cost models from inside Fortune 100 finance and technology organizations, not from a slide template.
We’re tool-agnostic. We’ve implemented in Apptio, ServiceNow ITFM, Serviceware, Nicus, Excel, and custom-built models, whichever one your organization actually needs.
02
We don’t move a team onto formal billing until the number has already survived a quarter of showback. What travels across every engagement is that order.
03
IF THAT ISN’T THE ONE YOU WERE HANDED
Six assignments, one practice behind all of them. If this isn't the one you were handed, here are the other five.
BRING US THE BILL SOMEONE DISPUTED
Thirty minutes with someone who's done this before. Send the allocation that got pushed back on, and you'll leave with a read on whether it's a data problem or a sequencing one.
Falconbridge helps CIO and CFO teams get clear, defensible answers on technology spend, including cloud, SaaS, and AI.