Cloud usage does not arrive on the same clock as the month-end close. A cost export is a changing view of usage; an invoice states what the supplier billed. Treating them as interchangeable is a reliable way to create next month's reconciliation problem.
Agree the cut-off before closing
Finance and engineering should record the export timestamp, invoices received, and how later usage will be handled. AWS describes timing, rounding, credit and tax differences between billing views and Cost Explorer. Azure describes current-month costs as estimates that may change before the invoice closes.
| Difference | Check first |
|---|---|
| Invoice exceeds export | Tax, support, Marketplace, missing accounts and data latency |
| Export exceeds invoice | Billing period, credits, cost basis and usage not yet invoiced |
| Later correction | Original period, arrival date, amount and follow-up report |
Keep one reconciliation row per provider with source, period, currency, residual and owner. Archive the data cut used for the approved report. A dashboard refresh should not silently rewrite a closed management view.
Give finance the evidence, not a journal entry
For material uninvoiced usage, ask which evidence supports an accrual under the company's accounting policy and how it will be reversed or settled. The answer depends on the entity, reporting framework and invoice. Engineering can establish usage, timing and uncertainty; finance owns the posting.
The useful close is one where a later reader can see what was confirmed and what remained open, even if the provider's final data arrived after the meeting.
Read next
Monthly cloud cost review, finance solution and cost report in the glossary.
Sources and method
Checked on 25 September 2026: AWS billing differences, Azure cost data. The tables and review steps are Costfluent recommendations.