Once you have allocated costs using tags, what do you do with that information? There are two main cultural approaches, and choosing the right one for your organization's maturity level is as important as the technical implementation.
1. Showback (Visibility Without Consequence)
This is the "friendly" approach. At the end of the month, the FinOps team creates dashboards and reports for each department head showing them: "Here is what your team spent on the cloud this month, broken down by service and project."
- Goal: To create awareness and social pressure. No manager wants to be at the top of the "highest spenders" list without a good reason. Visibility alone changes behavior.
- Financial Impact: None. The central IT department still pays the actual bill. The department's official budget is untouched.
- Best for: Organizations new to FinOps, or those with immature tagging coverage. You need accurate data before you can fairly charge anyone.
2. Chargeback (Real Financial Accountability)
This is the "serious" approach. The costs are not just shown — they are actively transferred from the central IT budget to the individual department's budget in the company's finance system (the ERP, like SAP or Oracle Financials).
- Goal: To make cloud costs a real constraint that competes with other budget priorities. If an engineering manager overspends on AWS, they have less money to hire new developers or fund travel.
- Financial Impact: Real. It requires integration between your cloud cost data and your company's accounting software, which is a non-trivial engineering and finance operations project.
- Best for: Organizations with mature tagging (>90% coverage), accurate allocation models, and executive sponsorship for the cultural shift.
3. Amortized Chargeback (The Nuanced Middle Ground)
A practical variant of chargeback that handles reserved capacity and committed use discounts. If your company buys a 3-year Reserved Instance upfront for $30,000, that cost should not hit one team's budget in month one. Amortized chargeback spreads that cost evenly across the commitment period ($833/month), making the financial impact predictable and fair for the consuming team.
Most companies start with Showback to build muscle memory and data quality, then move to Chargeback as their FinOps practice matures. Jumping straight to Chargeback with poor tag coverage is a recipe for political conflict — teams will (correctly) dispute charges they cannot verify.