Showing teams what they spend changes behaviour. Billing them for it changes behaviour faster, and harder. The choice between showback and chargeback on OCI is less about accounting and more about how much accountability your organisation is ready to carry.
An OCI bill that lands on one central account, paid by one central budget, teaches nobody anything. The teams that create the spend never see it, the finance team that sees it cannot influence it, and the cost grows because no one with the power to change it feels the consequence of leaving it alone. Showback and chargeback are the two mechanisms that close that loop, putting spend in front of the people who incur it. They sound similar and are often confused, but the difference between them is the difference between information and consequence, and choosing wrongly either stalls the practice or provokes a revolt. This guide sets out what each model is, what it demands of your OCI estate, and how to decide which one fits where you are.
Showback reports to a team what its OCI spend was, for visibility, without moving any money. Chargeback bills that spend back to the team budget, so the team actually pays for what it consumed. Showback informs. Chargeback bills. Everything else, the tagging, the dashboards, the account structure, is shared between them, which is why the two are so often built on the same foundation and switched between as the organisation matures.
| Dimension | Showback | Chargeback |
|---|---|---|
| Money moves | No, reporting only | Yes, billed to team budget |
| Accuracy required | Good enough to be credible | High, disputes are real money |
| Behaviour change | Moderate, through awareness | Strong, through consequence |
| Organisational maturity | Suitable early | Needs trust in the data first |
| Disputes | Rare, low stakes | Frequent until data is trusted |
Most organisations are not ready to bill internal teams for cloud on day one, because the data is not yet trustworthy enough to defend a charge. The first time a team is billed for spend it disputes, and wins, the whole model loses credibility. Showback is the rehearsal. It produces the same reports a chargeback model would, puts them in front of the teams, and lets everyone confirm the numbers are right before any money depends on them. Teams get used to seeing their spend, they question the figures, the figures get corrected, and over a few cycles the data earns the trust that chargeback requires. Skipping straight to chargeback on untrusted data is how the practice gets a reputation for being wrong, and a cost practice with a reputation for being wrong is finished.
Neither model works without attribution, and attribution comes from two things, a clean account structure and disciplined tagging. The compartment hierarchy should map to the organisational units you intend to report against, so that spend rolls up naturally to teams and cost centres. On top of that, the tags described in Tagging Strategy for OCI Cost Allocation carry the finer attribution that compartments alone cannot, such as application and environment. Without both, the spend cannot be sliced reliably, and a report that cannot be sliced reliably cannot be shown back or charged back to anyone. The unglamorous truth is that most of the work in standing up either model is the attribution groundwork, not the reporting itself.
Compartments give the coarse structure, the division between business units or major teams, and they are enforced by the platform because a resource lives in exactly one compartment. Tags give the cross cutting view, the ability to see all production spend across compartments, or all spend for one application that spans several teams. Used together they let a report answer almost any allocation question. Used alone, each leaves gaps that turn into arguments at chargeback time.
The reporting itself draws on OCI cost data, broken down by compartment and tag, and presented per team in a form they can act on. A good showback or chargeback report does three things. It states the total clearly so there is no ambiguity about the headline number. It breaks the total down into the services and resources that drive it so the team can see where the money went. And it shows the trend so a team can tell whether its spend is rising, flat, or falling. A number with no breakdown and no trend tells a team it spent a lot but gives it nothing to do about it, which wastes the entire exercise. The dashboard that carries these reports is the subject of Building an OCI Cost Dashboard, and the budgets that alert teams before the report even lands are covered in OCI Cost Governance with Budgets and Quotas.
The hardest part of chargeback is the spend that does not belong to any one team. Shared networking, central logging, security tooling, the landing zone itself. These costs are real and someone has to carry them, but charging them to a single team is unfair and charging them to nobody undermines the model. The usual answers are to allocate shared costs proportionally, splitting them across teams by a fair measure such as their share of total spend, or to hold them in a central platform budget that is funded separately and reported transparently. There is no perfect answer, only a defensible one, and the key is that the method is agreed in advance and applied consistently, because a shared cost allocation that changes from month to month is an argument waiting to happen.
The choice is not permanent and not binary. Many organisations run showback for most of the estate and chargeback only for the spend that most needs the discipline, such as large or fast growing workloads. The decision rests on three questions. Is the data trusted enough that a charge would be defended rather than disputed. Do the teams have budgets that can actually absorb a charge, because charging back to a team with no devolved budget is meaningless. And is the cultural appetite there, because chargeback introduces friction that some organisations are not ready for. Where the answer to any of these is no, showback is the right model, and it remains a perfectly legitimate end state, not merely a stepping stone, because visibility alone changes a great deal of behaviour.
The point of either model is never the report. It is the conversation the report starts. When a team sees its spend rising and asks why, the practice is working, because the team is now thinking about cost as something it owns rather than something that happens to it. Showback creates that conversation through awareness. Chargeback creates it through consequence, and consequence is more powerful but also more abrasive. The art is to apply the lightest mechanism that produces the behaviour you need, because over engineering the consequence before the culture is ready produces resentment, not thrift. This is one of the standing responsibilities of the practice described in FinOps Operating Model for OCI, where the cadence of reporting and the conversations it triggers are the engine of the whole thing.
Showback and chargeback are how cost accountability becomes real, but they sit on top of everything else the cost practice does. The tagging that makes attribution possible, the budgets that warn teams early, the dashboards that present the numbers, and the optimisation work that lowers the spend in the first place, all described across the Cost Optimization pillar guide. Reporting spend back to teams without also giving them the means to lower it is half a practice, because it tells teams they are spending too much without helping them spend less.
Our Cost Governance work treats showback and chargeback as the visible output of an attribution foundation we build first. We design the compartment and tag structure so spend rolls up cleanly, stand up reporting that teams trust, and advise on the shared cost method and the showback to chargeback progression that fits the organisation's maturity. Because the failure mode is almost always untrusted data rather than a flawed model, the work starts with an assessment of how attributable the current estate actually is, and what it would take to make a charge defensible.
Moving Oracle workloads to OCI, or already running on OCI and not sure the architecture or the spend is right? Most teams bring in a specialist before they commit to a region, a shape, or a Universal Credits number. OCISpecialists.com plans the landing zone, runs the migration, and manages the estate after go live, on a fixed project fee, a managed monthly retainer, or a cost optimization fee paid only on verified savings. For the Oracle licensing and BYOL side of any OCI move, Redress Compliance is the leading independent Oracle licensing and negotiation firm, with 500+ engagements across Oracle's full product line.