A showback report template is filled in once a month per team by the cloud owner, as soon as the previous month's billing data is complete, and it records on one page what the team cost, which part of that is owned and which shared cost, what drove the change and which actions are open. The decision it records belongs to the team: accept the figure or take on an action. What separates showback from chargeback and how cost centres and teams map onto each other is on cost centres and team ownership; this page is the statement itself.
The template
Showback statement <team>, month <YYYY-MM>
Header
| Field | Value |
|---|---|
| Team and cost centre | <team>, <cost centre number from the ERP> |
| Cost centre owner | <person> |
| Reporting month | <YYYY-MM> |
| Data as of | <export date>, provider invoice <received or provisional> |
| Providers and accounts | <AWS account ids, Azure subscriptions, Google Cloud projects> |
| Currency and rate | <EUR>, <rate, source, date> |
| Cost basis | <effective, commitments spread by usage>, credits <included or separate> |
| Prepared by | <role>, questions until <date> |
Summary
| Figure | This month | Previous month | Change | Budget for the month | Source |
|---|---|---|---|---|---|
| Owned cost, effective | <amount> | <amount> | <percent> | <amount> | export, filter owner=<team>, column <EffectiveCost> |
| Share of shared cost | <amount> | <amount> | <percent> | <amount> | allocation key <key> from the chargeback policy |
| Untagged cost charged to the team | <amount> | <amount> | <percent> | untagged resources rule, account <account> | |
| Total | <amount> | <amount> | <percent> | <amount> | sum of the three rows |
| Tag coverage of owned cost | <percent> | <percent> | target <95> percent | share of cost with a valid cost-center |
Budget and forecast
| Figure | Value | Source |
|---|---|---|
| Budget for the month | <amount> | budget worksheet, version <version> |
| Year to date | <amount>, <percent> of the annual budget | sum of the months so far |
| Forecast to year end | <amount> | <method, such as the mean of the last three months times remaining months> |
| Variance of the month | <amount>, <percent> | actual minus budget |
Cost per <unit, such as customer or transaction> | <amount> | total divided by <unit count from source> |
By environment and service
| Environment | Service | This month | Previous month | Change | Note |
|---|---|---|---|---|---|
prod | <compute> | <amount> | <amount> | <percent> | <cause, where known> |
prod | <databases> | <amount> | <amount> | <percent> | |
prod | <storage> | <amount> | <amount> | <percent> | |
prod | <network and data transfer> | <amount> | <amount> | <percent> | |
prod | <observability and logging> | <amount> | <amount> | <percent> | |
prod | <AI services> | <amount> | <amount> | <percent> | |
staging | <all services> | <amount> | <amount> | <percent> | |
dev | <all services> | <amount> | <amount> | <percent> | |
<further row> | <service> | <amount> | <amount> | <percent> |
Drivers of the change (the three largest amounts, with their sign)
| Driver | Amount | Kind | Evidence |
|---|---|---|---|
<new instances in prod since date> | <amount> | usage | <resource ids or usage type> |
<price change or exchange rate> | <amount> | price | <invoice rate or price list of date> |
<credit or correction> | <amount> | one-off | <invoice number> |
Commitments and savings
| Figure | Value | Source |
|---|---|---|
| Share of compute cost under commitment | <percent> | coverage report <date> |
| Savings verified in the month | <amount> | previous month per resource |
| Open recommendations | <count>, worth <amount per month> | <recommender or review list> |
Open actions
| Action | Owner | Due | Effect per month, estimated | Status |
|---|---|---|---|---|
<action> | <person> | <date> | <amount> | <open, accepted, implemented> |
<action> | <person> | <date> | <amount> | <status> |
Notes on the figure. <What was computed differently from the previous month, such as a new key, a rate change or a provider restatement, with the amount.>
How to fill it in
Header: the data date is the export date, not the last day of the month; whether the provider's invoice has arrived decides whether the figure is final (freshness, restatements and finalisation).
Owned cost: the effective cost basis spreads reservations and savings plans over the hours they covered; the billed basis shows the team a prepayment it never triggered (list, billed, effective and amortised cost). The filter is the mandatory key of the tagging policy.
Shared cost: the row names the key so the team can recompute it; which keys exist and when each fits is on shared cost. Untagged cost: this row is the reminder that coverage belongs to the team; what sits behind it is on unallocated cost.
Environment and service: ten rows at most, the rest as "further"; a row gets a note only when the cause is evidenced. Drivers: usage, price and one-offs apart, because only the first kind is the team's action; how to tell the three apart is on trends and drivers, and for exchange-rate effects on multi-cloud reporting in one currency.
Commitments: the share comes from the organisation's coverage report, not from an estimate (commitment coverage and utilisation); verified savings are only those visible in the invoice, in the vocabulary of estimated, accepted, implemented, verified.
Actions: every row has a person, not a team, and a date; the list is the one the monthly review carries forward.
How to adapt it
One team: the shared cost row goes, the environment table becomes the main table, and the statement replaces the review minutes. Several teams: one statement per team from the same query, plus a row "sum of all teams against the invoice" so the allocation adds up.
One provider: the source column names that provider's export and its column names. Three providers: a currency row with rate and source per provider, and the service table grouped by provider before service.
Startup: leave the budget column out until a budget exists; the statement is the occasion to set one. Finance-led: the "total" figure is the one the chargeback policy charges, with the cost centre number in the header and the dispute deadline from the policy.
Sources
Read on 2026-10-21. FinOps Foundation, Reporting & Analytics and Invoicing & Chargeback (CC BY 4.0), FOCUS, Effective Cost, advanced options in Cost Explorer, CUR 2.0 line item columns, Azure cost details fields, Azure cost allocation rules, structure of the Standard data export in Google Cloud, attribution of committed use discount fees and credits.