PeelBack Demo Series: Transparent Showback That Builds Alignment
Why Do Business Units Dispute Their IT Bill — and How Do You Fix It?
What a business unit is actually objecting to when they push back on a bill that’s completely accurate
Key Takeaway: A finance leader can hand a business unit a completely accurate bill and still get pushback, not because the math is wrong, but because accuracy was never actually what they were checking for.
The Problem
Picture a business unit head reviewing their monthly technology allocation. The total is correct, it reconciles against the source data, and finance can prove it if asked. That business leader still pushes back, asks for a meeting, and treats the number as negotiable. Multiply that across a dozen business units and showback stops functioning as a reporting exercise and starts functioning as a monthly negotiation.
Why This Happens
The dispute usually isn’t about the math. It’s about context: a single total, delivered on its own, doesn’t tell a business leader anything about where it came from or whether it’s fair, and a number without context tends to get challenged by default, regardless of how accurate it is.
Four Questions Every Business Stakeholder Asks
Four questions come up again and again: What am I actually paying for? Why do I own this cost and not someone else? Can anything I do change this number next month? And am I being charged fairly compared to other business units?
Also Covered in This Session
The session also covers the concept of a “chain of custody” for an IT cost charge, tracing one application’s cost back to the business unit that consumes it, how connecting cost to ownership shifts conversations from disputes to decisions, and extending the same accountability model to shared AI models and token consumption.
See It In Practice
This session shows that chain of custody in action inside MagicOrange. Starting from a business unit’s monthly bill, the walkthrough drills into one specific application driving that spend to show its total cost of ownership and named owner, then opens a Sankey-style diagram tracing the full path of that charge from the general ledger through towers and solutions to the business unit. It closes by applying the same approach to shared AI models and token consumption.
Executive takeaway: A showback bill people accept isn’t a better-formatted total. It’s a total they can trace, question, and eventually influence.
Frequently Asked Questions
Usually because the bill answers what was spent but not where it came from, why they own it, or whether it's fair relative to other business units. Without those answers, a stakeholder has no basis for accepting the charge, even when it's accurate.
Chargeback formally bills a business unit for its technology consumption, while showback reports that same consumption for visibility without actually charging the unit. Many organizations start with showback before moving to chargeback as trust in the numbers grows.