Why
Chargeback makes cloud cost a real P&L line item. Teams optimise when spend hits their budget — showback alone lacks teeth for organisations that need stronger accountability. Without chargeback, cloud is “someone else’s budget” and optimisation recommendations are suggestions, not obligations.
What
Formally charge cloud costs back to consuming business units through internal invoicing or journal entries. Reconcile chargeback figures against the cloud bill and integrate into departmental P&L reporting.
How
Confirm Allocation Maturity
Chargeback requires mature allocation. Before activating, verify: tag coverage >95% (spend-weighted), shared cost allocation rules in place (S1-04 to S1-06), and showback reports reviewed for at least 2 months without disputes. Incorrect chargeback figures erode trust with BU leaders — get allocation right first.
Agree on Chargeback Methodology with Finance
| Decision | Options |
|---|---|
| Billing frequency | Monthly (most common) or quarterly |
| Cost basis | Actual cost, amortised cost, or blended rate |
| Shared cost treatment | Include proportional share, or exclude and keep central |
| Currency | Cloud billing currency or local currency conversion |
| Reconciliation tolerance | Typically ±1% variance acceptable |
Document the methodology and get Finance sign-off before the first chargeback cycle.
Build the Chargeback Report
The chargeback report maps allocated cloud costs to Finance cost centres and GL codes. Output: a file or API payload that Finance can import into ERP (SAP, NetSuite, Oracle) as journal entries.
| Field | Source |
|---|---|
| Cost Centre | From cost-center tag or account-to-CC mapping |
| GL Account | Agreed with Finance (e.g., “Cloud Infrastructure”) |
| Amount | Allocated cost from billing pipeline |
| Period | Billing month |
| Description | “Cloud costs — [BU Name] — [Month]” |
Reconcile Against Cloud Bill
Sum of all chargeback entries must equal the total cloud invoice (±tolerance). Common discrepancy sources: tax/credits exclusion, currency conversion rounding, amortisation timing differences, and unallocated spend.
Go Live and Monitor
Run one month as “shadow chargeback” (generate the entries but don’t post to GL). Compare against showback reports. Address discrepancies. Then go live with Finance posting journal entries.
Deliverable Checklist
- Allocation maturity confirmed (>95% tag coverage, shared costs allocated)
- Chargeback methodology agreed with Finance
- Chargeback report built (mapping to GL codes / cost centres)
- Reconciliation process operational (±1% tolerance)
- Shadow month completed without disputes
- Journal entries posted to ERP
- Monthly chargeback cycle operational