FinOps showback: vs chargeback: choose an allocation model
Updated: 2 November 2026Get a quote for my projectFinOps showback makes allocated costs visible to the teams responsible for them. FinOps chargeback adds an internal financial transfer. Choose the model from the quality of your allocation data and the accounting decision it must support.

On this page
- Finops showback: Where the FinOps Framework draws the line
- Cost basis: decisions to fix in writing
- Inputs to collect from finance and accounting
- A suggested three-close pilot before real transfers
- Legal entities and tax
- Dispute and correction rules
- Deliverables to specify
- Official sources
- Showback and chargeback questions
Finops showback: Where the FinOps Framework draws the line
The capability is named Invoicing & Chargeback in the current Framework, under the Manage the FinOps Practice domain. An earlier version, titled Chargeback & Finance Integration, remains archived on finops.org. The difference between the two models is formality: showback gives visibility to any group, while chargeback sends expenses to official accounting budgets. The capability treats showback as always needed and chargeback as a matter of organizational policy.
The KPIs it names are chargeback processing time, variance between management-tool spend and general-ledger charges and the variance between estimates and actuals. Ask your provider which of them it will report.
Cost basis: decisions to fix in writing
| Decision | Options | Why it matters |
|---|---|---|
| Cost type | Billed cost or effective (amortized) cost | FOCUS carries both as BilledCost and EffectiveCost. Billed cost recognizes the purchase charge in its billing period; attribution to teams still depends on your allocation policy |
| Credits and refunds | Pass to the consuming team, or hold centrally | Decides whether a credit improves one team's month or the whole company's |
| Shared cost | Central budget, fixed shares, proportional split or usage proxy | The Allocation capability lists these options. FOCUS 1.3 added columns recording the allocation method and the allocated resource or tags |
| Cut-off | Charge on usage month, or on invoice month | Late invoices and adjustments otherwise reopen closed months |
| Currency and tax | Invoice currency or budget currency; tax in or out of the charge | Must match how the receiving entity reports |
FOCUS 1.4, ratified on 4 June 2026, adds Invoice Detail and Billing Period datasets so cost and usage rows can be reconciled to the invoice by invoice ID. The FOCUS project's implementer list, however, shows AWS, Microsoft Azure and Google Cloud exports at version 1.2, so check what your provider actually delivers before promising invoice-level reconciliation. The official release overview records that ratification and the new datasets.
Want a pilot close designed for your own organization? Request a quote for this review.
Inputs to collect from finance and accounting
- The cost center hierarchy and the owner of each node.
- The chart of accounts, with the ledger account that receives cloud recharges.
- The close calendar, including the day after which a month is frozen.
- The journal format your accounting system imports.
- The legal entity structure and which entities pay which cloud invoices.
- Approval thresholds for recharges, and vendor payment terms.
A suggested three-close pilot before real transfers
- First close, showback only: send each budget owner a report with the cost basis note. No postings. Collect every mapping error and dispute.
- Second close, corrected showback: apply the fixes, publish the rule set with a version number, and measure the share of cost with a named owner.
- Third close, dry run: produce the journal entries as a file, have accounting import them into a test period and compare with the report.
- Then decide: go live, stay on showback, or move only some cost centers. The decision, and the approver, are recorded.

Legal entities and tax
When charges cross legal entities, an internal recharge can carry VAT or transfer pricing consequences that depend on the countries and the intercompany agreements in place. The Framework is an operating reference, not legal or tax guidance, so have your tax advisor review the flows before the first posting. This review belongs to you, not to the FinOps provider. Consult the European Commission VAT overview for EU context and the OECD transfer pricing guidance for transactions between associated enterprises; the actual treatment requires the relevant national rules and facts.
Dispute and correction rules
- A dispute window of fixed length after each report, and who rules on disputes.
- How late credits, re-tagging and ownership changes are treated: restate the period, or book the correction in the current month.
- The owner of unallocated cost, named and reported as its own line.
- What evidence a team must bring to contest an allocation.
Deliverables to specify
- Allocation and cost basis policy, versioned.
- Monthly showback report template and its data lineage.
- Journal file specification agreed with accounting.
- Pilot log recording each dispute and its resolution.
- Handover of the queries and a named maintainer on your side.
Official sources
Official documentation used for this page.
- www.finops.org/framework/capabilities/invoicing-chargeback/
- www.finops.org/framework/previous-capabilities/chargeback/
- www.finops.org/framework/capabilities/allocation/
- learn.microsoft.com/en-us/cloud-computing/finops/framework/manage/invoicing-chargeback
- focus.finops.org/
- www.finops.org/insights/introducing-focus-1-3/
- focus.finops.org/docs/use-cases/v1-4/reconcile-cost-and-usage-to-invoice-detail-by-invoice-id
Showback and chargeback questions
Should we start with chargeback?
A showback pilot exposes allocation and ownership problems before any amount is posted. Finance should approve the chargeback rules and the correction process first.
Is chargeback required by the FinOps Framework?
No. The Framework is an operating reference, not a law. The capability describes showback as always needed and chargeback as dependent on organizational policy.
Which cost should appear in a chargeback, billed or amortized?
Either is possible. Choose one, write it down and apply it to every team, because the choice changes recognition across periods; the allocation policy separately determines which teams bear the cost.
Validate allocation by accounts, tags and shared-cost rules before sending a team statement. Preserve a reconciliation that explains which splits the downstream reporting actually includes.
Continue your review
- FinOps consulting: cloud cost review and implementation scope
- Request a scoped FinOps quote
- How your request is handled: from enquiry to proposal
- Cloud cost allocation: tagging and ownership controls
- FOCUS billing data implementation: an acceptance checklist
- SaaS cloud unit economics: measure cost per customer
Get a quote for my cloud costs
A specialist in cloud cost control reads your request and proposes a quote.
Get my quote