A cloud cost reporting cadence fixes which question is put to the billing data daily, weekly and monthly, and it follows the data's cut-off: daily, provisional data can show anomalies and deployments; weekly, trends and their owners; monthly, and only then, closed figures against budget, forecast and invoice. A cost report on the wrong cadence either answers a question its data cannot yet carry or arrives too late: a month-to-date total sent every day is an estimate, and a report read only monthly shows a wrongly sized resource after it has run for a whole month. The cadence therefore decides how long a mistake costs money before anyone sees it.
How it works
The FinOps Foundation's Framework (CC BY 4.0) places reporting in the Inform phase, beside the capabilities Data Ingestion, Allocation, Forecasting and Unit Economics. The capability itself is Reporting & Analytics, in the domain Understand Usage & Cost. It separates routine, formal reporting from ad hoc and investigative analysis but prescribes no frequency, and the Foundation describes Inform as a phase a team keeps returning to (the three FinOps phases). Which cadence carries which question is the organisation's choice; the data sets the limits.
| Cadence | Question | Data state | Cost basis | Window | Readers |
|---|---|---|---|---|---|
| Daily | Did something unexpected start yesterday: a deployment, a new resource, an anomaly? | provisional, the latest day incomplete | effective cost | complete days against the same weekdays before | the scope's owner, operations |
| Weekly | Is a scope's trend moving, and who owns it? | provisional, but seven complete days | effective cost | seven complete days against the seven before | teams, product owners |
| Monthly | What did the month cost against budget, forecast and invoice? | final only with the invoice | billed cost for finance, effective cost for teams, both named | invoice month | finance, management, the monthly review |
Daily and weekly the subject is movement, so the basis is effective cost, with commitments spread over the usage they cover. Monthly the subject is also the invoice, and only billed cost matches it (list, billed, effective and amortized cost).
What the consoles offer per cadence
| AWS Cost Explorer | Azure cost analysis | Google Cloud billing reports | |
|---|---|---|---|
| Time units | Daily, Monthly, Hourly (opt-in, previous 14 days only) | Daily up to 92 days, beyond that Monthly; the portal holds the last 13 months | automatically daily for ranges of up to 62 days, otherwise monthly |
| Week | preset 7D: the previous day and the six before it | preset last seven days | preset L7D: daily costs for the last seven days |
| Default cost basis | unblended: reservation fees as a spike on the day charged | actual cost: purchases on the purchase day | all savings included |
| Month | calendar month in UTC | calendar month in UTC, for pay-as-you-go also the billing period | calendar month by charge period, or complete invoice months by billing period |
None of the three consoles documents a weekly granularity. A weekly report is a range of daily values, and each of those days starts at midnight UTC on AWS and Azure and at midnight Pacific Time on Google, not in your local time.
What it means for your cost
Daily. The default view raises false alarms. By default AWS shows Reserved Instance fees as a spike on the day they are charged; amortized costs turn them into an effective daily rate. Microsoft advises switching to amortized cost when watching for anomalies, because actual cost shows reservation purchases as spikes, and calls actual cost the view for reconciling the invoice. The daily view therefore runs on effective cost, ends at the last complete day and is not a report for many readers but a question to the owner once something moves (cost anomaly detection). How far each console lags, and why the last one or two days look too low, is covered in data freshness in cost reports.
Weekly. A week evens out the weekday patterns that make a daily curve noisy (trends and cost drivers). Two complete weeks are compared on the same cost basis, per owner as a saved view. The outcome is an explained trend or a task with a name on it. How such a report reaches its readers without a login is covered in report subscriptions and delivery.
Monthly. A month is final only with the invoice: on AWS when the Bills page moves from Pending, with estimated charges, to Issued; under a Microsoft Customer Agreement with the invoice generated per billing profile at the beginning of the month; on Google by the fifth business day of the following month as a rule. When the providers close the period and what still changes afterwards is covered in freshness, restatements and finalisation. A monthly report for finance therefore waits for the invoice or carries the label "estimated" with its cut-off. How the monthly cloud cost review turns the month into decisions is a subject of its own, as is what the same month contains for management and for finance.
A cadence is set up once five things are fixed:
- the question it answers and the decision that follows from it;
- the owner who acts, and the readers who are only informed;
- the cost basis, named in the report;
- the cut-off: last complete day, time zone, estimated or invoiced;
- the window and its comparison period, as period comparison describes.
Where it goes wrong
- A monthly question in the daily report. Symptom: the month-to-date total sent every day triggers questions that are moot the next day. Cause: the open month is an estimate, and the question about the month belongs to the monthly cadence.
- A purchase read as an anomaly. Symptom: the daily report jumps on the purchase day or on the first of the month. Cause: it runs on the default view, which shows fees and purchases on the day they are charged, instead of on effective cost.
- A week with a partial day. Symptom: the current week looks cheaper than the last. Cause: its latest day is still incomplete; the week has to end at the last complete day.
- A month closed before the invoice. Symptom: the figure reported to finance later differs from the invoice. Cause: the report was built on estimates before the billing period closed.
- Calendar month against billing period. Symptom: an Azure pay-as-you-go invoice matches no monthly report. Cause: its billing period is not bound to the calendar month (billing periods, cut-off and late charges).
- A cadence without a recipient. Symptom: reports go out regularly and nobody acts. Cause: no owner and no decision were fixed for the cadence.
Sources
Read on 2026-10-16. FinOps Foundation Phases and Reporting & Analytics (CC BY 4.0); AWS exploring your data using Cost Explorer, modifying your chart, choosing advanced options and understanding your bill; Microsoft customize views in cost analysis, understand Cost Management data and view and download your Azure invoice; Google Cloud Cloud Billing reports and get an invoice.