Cloud showback vs chargeback

Decide what happens to a team budget

Showback gives a team visibility into the cloud costs assigned to its services. Chargeback sends those expenses into the organization's official budgets or accounting systems. A monthly spreadsheet can support either model; the financial treatment determines which one you have. Ask finance whether the numbers will change departmental actuals, how they will reach the ledger and who accepts the posting.

The FinOps Foundation treats chargeback as an accounting-policy choice, not a compulsory next maturity level. Showback can remain the right model when a central budget funds infrastructure and teams already use cost reports in planning. Chargeback makes sense when budget holders need formal expense allocation or internal service recovery.

Check readiness before creating a recharge

Choose showback while ownership disputes or incomplete billing coverage would produce repeated corrections. Give each team its direct costs, its approved share of central services and the amount still unresolved. Ask teams to review those figures during their normal planning meeting. Assign someone to investigate disputed amounts and record the outcome.

Before introducing chargeback, finance should approve the receiving cost centers and the cost basis. Agree a close date, a reviewer and a correction route. Confirm how a new team enters the model and how a departing team leaves it. If these decisions are missing, a report labeled chargeback can create budget expectations that accounting has never accepted.

Keep the cost basis identical across both models

Use the same period, currency and selected provider scope when comparing showback with chargeback. Actual billed cost and amortized commitment cost answer different questions. Finance must choose the basis for the intended report and document any difference from the invoice. Keep credits and refunds visible; applying another discount to an already net billed amount understates the cost.

Microsoft says Azure cost allocation does not change its invoice or billing responsibilities. Internal chargeback happens outside Azure. Its allocation feature also excludes purchases such as reservations and savings plans. Check supported agreement types before treating Azure allocation rules as the complete input to an accounting process.

A report can precede budget posting

This illustrative September example uses USD 12,000.00 of actual costs from one selected scope. Product has USD 6,000.00 in direct charges, Operations has USD 4,000.00, and an approved support split assigns USD 900.00 and USD 600.00 respectively. Another USD 500.00 has no accepted business mapping.

Showback includes all USD 12,000.00. Under the illustrative chargeback policy, finance posts USD 11,500.00 to the two teams and holds USD 500.00 centrally for investigation. The provider bill is unchanged. Moving the unresolved amount later requires a recorded correction, so readers can distinguish a transfer between budgets from new cloud consumption.

Scroll the table sideways on smaller screens. Keyboard: focus the table and use the arrow keys.

Use a mixed model when control differs

You can charge back dedicated application resources while showing centrally funded networking separately. The FinOps Foundation describes organizations using a mix of central funding and distributed shared costs. State the policy by cost category so a team knows which figures affect its budget. A fully loaded product view may include costs that remain centrally funded in accounting.

Keep a separate field for the allocated amount and its posting status. Reviewed, accepted for posting and posted are different events. If provider charges change after close, finance decides whether to correct the prior period or issue a later adjustment. Retain the earlier report and explain the difference instead of silently replacing the team's accepted number.

Confirm the reporting boundary in Costframe

Costframe's internal statements preserve selected scope and a visible revision; they are not accounting invoices. Current owner context does not establish historical responsibility, and owning a cost center does not itself grant statement-review authority. Confirm the available reporting scope and access before adding a report to your close process.

Costframe uses read-only customer-cloud access. Azure is generally available; AWS is a private pilot and Google Cloud a private preview. No report automatically transfers your provider billing responsibility or posts a journal entry. Use the cost calculation documentation to check cost semantics, then agree the accounting handoff with finance.

Related guidance