FinOps / Technical guide
Give finance a cloud cost report they can reconcile and question
A monthly cloud report should explain what changed, why it changed and what decision is needed. A collection of totals and recommendation counts leaves finance to reconstruct the period, price basis and ownership assumptions.
Keep the cost ledger, variance explanation and proposed actions separate. An estimated opportunity should not be subtracted from actual spend to create a hypothetical figure that looks like a reconciled result.
Ask about cloud reportingStart with the included financial population
State the billing period and its date boundaries, included accounts/subscriptions, currency and price basis. Identify whether the period is closed or provisional and when the source was refreshed. Report excluded or failed scopes alongside the total, not only in a footnote.
Keep material native currencies separate. Preserve charges with missing resource links in the included ledger and distinguish resource, service and invoice-level totals. A report cannot explain a mismatch if it silently drops unallocated spend.
| Field | Useful disclosure |
|---|---|
| Period | Previous complete month; explicit boundaries |
| Source | Provider actual cost or another named basis |
| Coverage | Included scopes and collection failures |
| Currency | Per-native-currency totals |
| Freshness | Extraction time and provisional/correction status |
Explain the change with an attributable cause
Separate workload growth, price/benefit movement, billing corrections and one-time events. Compare the same population with the earlier period. If a new subscription entered the report, show its contribution separately from organic spending growth.
Use the smallest relevant technical evidence for the decision. A service-level change can be explained with retained charges; claiming that the service is oversized requires utilization and workload constraints that a financial report may not contain.
Attach actions without converting them into receipts
For each proposed action, retain its owner, evidence period, risk, expected cost basis and outstanding questions. Show an estimate separately from approval, implementation and later verification. A closed ticket is a workflow event, not financial proof.
Costframe supports selected-period cost investigation and supported finding review. Export availability depends on the path, plan and authorization: general audit CSV is supported, while general audit PDF is disabled in the controlled launch. Dedicated reporting workflows have separate scope and permissions.
Reconcile
Check included source totals and retained unlinked charges.
Explain
Identify the principal variance drivers and any incomplete evidence.
Request a decision
Present the owner, proposed change and risk with a clearly labelled estimate.
Follow up
Revisit implemented actions with comparable billing and service evidence.
References and further reading
Provider documentation explains native capabilities. Costframe availability and limitations are stated separately in this guide.
Review reporting scope before rollout
Discuss the periods, currency treatment and available exports required for your monthly review.
Ask about cloud reporting