Closing a month with cloud costs takes three things: a fixed data cut-off, a reconciliation of cost export against invoice for each provider, and a list of the amounts still open at the cut-off, with the evidence finance needs to decide on any accrual. AWS and Azure keep changing a month's data for days after it ends, and the invoice can arrive after your close date. Below: when each figure becomes final, a reconciliation sheet layout, and the questions finance should settle first.

When AWS and Azure cost data becomes final

A cost export is a data snapshot; the invoice is the accounting document. Both providers document how long a month keeps moving.

AWS: Data Exports, the invoice and later adjustments

  • CUR 2.0 in AWS Data Exports refreshes at least once a day. After the billing period ends, AWS may update the previous period's delivery within the first two weeks.
  • The invoice is generated when the billing period closes. On the Bills page of the Billing and Cost Management console the bill status then reads Issued; open months read Pending and show estimated charges.
  • The bill_invoice_id column tells you whether a row is final: it stays blank until AWS assigns the row to an invoice.
  • The month can still change afterwards. AWS calculates Developer, Business and Enterprise Support from final usage charges and documents that these appear on the sixth or seventh of the following month. Credits and refunds can follow later.
  • AWS Marketplace usage charges are billed on the second or third day of the month. The Invoices tab on the Bills page lists invoices per service provider, so expect more than one.

Every timestamp in the export is in UTC. Daily totals built in UK or Central European time shift cost across the month boundary.

Azure: estimates, period close and the invoice

  • For Enterprise Agreement and Microsoft Customer Agreement (MCA) accounts, costs typically reach Cost Management within 8 to 24 hours; pay-as-you-go can take up to 72 hours.
  • Everything is an estimate until the invoice exists. Microsoft states that open-month estimates ignore tiered pricing and use the highest tier.
  • Azure typically closes the billing period up to 72 hours after it ends, and usage charges can still change until the fifth day after. The invoice is the final figure.
  • The MCA invoice date is typically five to 12 days after the billing cycle ends.
  • Cost Management excludes support, taxes and Azure credits. In the cost details export, CostInBillingCurrency is before credits and taxes; on the invoice, Total = Charges - Azure Credit + Tax.

Google Cloud follows the same pattern. Setting up the Google Cloud billing export covers the BigQuery side.

Month endsAWS: invoice issued, rows receive a bill_invoice_idDay 6 or 7: support charge appearsWithin two weeks: delivery updated; credits and refunds can followAzure: period closes within 72 hoursUntil day 5: usage charges can still changeDay 5 to 12: MCA invoice, the final figure
What still moves after the month ends: on AWS the invoice, the support charge and later credits; on Azure the period close, usage changes and the invoice

Set the data cut-off

The cut-off is an agreement between engineering and finance, not a technical moment. The monthly cloud cost review shows where it sits in the monthly rhythm. For the close itself, agree:

  1. The date the cloud figures go to finance.
  2. For each provider, the data version that counts: for AWS, the export execution with its timestamp and Manifest.json; for Azure, the dated export run.
  3. Whether the invoice is available by then. If not, the amount is an estimate and is labelled as one.
  4. Where changes after the cut-off go: as a correction row in the following month, never into the approved report.
  5. Who signs off the figures.

Set the AWS export to Create new. AWS then stores each execution under its own path with a timestamp and execution ID, so the cut-off version stays provable. Overwrite keeps only the latest version.

The reconciliation sheet per provider

Keep one row per provider and billing account, with these columns:

ColumnContent
Billing accountAWS management account, Azure billing profile or Google Cloud billing account
Invoicing entityLegal entity on the invoice, Marketplace kept separate
Service periodBilling period as stated on the invoice
Data versionExport execution and timestamp
Invoice numberbill_invoice_id for AWS (blank means not yet final), InvoiceId for Azure
Export netTotal excluding tax, in invoice currency
Invoice netSubtotal before tax
Explained differencesBy category, from the next table
ResidualExport net minus invoice net minus explained differences
StatusConfirmed, estimated or open
Owner and review dateName and date of the next check

For AWS, this query against CUR 2.0 in Athena returns the building blocks of one row. The table name and partition depend on your setup:

SELECT
  bill_billing_entity,
  line_item_legal_entity,
  bill_invoice_id,
  line_item_line_item_type,
  line_item_currency_code,
  ROUND(SUM(line_item_unblended_cost), 2) AS unblended_cost
FROM cur2
WHERE billing_period = '2026-09'
GROUP BY 1, 2, 3, 4, 5
ORDER BY 1, 2, 3, 4;

Rows with a blank bill_invoice_id are not final. Leave Tax rows out of the net comparison, show Credit and Refund separately, and use bill_billing_entity to split Marketplace purchases from AWS services. AWS bills in US dollars by default, so check line_item_currency_code against the invoice currency. For Azure, group the actual-cost export by InvoiceId, PublisherType and ChargeType.

Explain the differences

CauseAWSAzureTreatment
TaxSeparate Tax rowsNot in Cost ManagementReconcile net, tax separately
CreditsCredit rows, also after finalisationNot in Cost Management; on the invoice as Azure creditsOwn category
RefundsRefund rows and bill type RefundChargeType = Refund, with PreviousInvoiceId on MCARecord the original period
SupportSixth or seventh of the following monthNot in Cost ManagementOwn row, possibly known only after the cut-off
Marketplacebill_billing_entity = AWS Marketplace, separate invoicesPublisherType = Marketplace, on MCA usually the same invoiceReconcile against the matching invoice
CommitmentsUpfront payment as Fee or SavingsPlanUpfrontFeeChargeType = PurchaseReconcile actual, not amortised cost
RoundingAWS treats the invoice amount as finalPortal rounds, export files do notLabel as rounding only when a residual remains after everything else

AWS also documents that the Bills page excludes refunds while Cost Explorer includes them, so never compare a Cost Explorer total with the invoice without checking that row. On Azure, credits do not cover partner and third-party products from Microsoft Marketplace or Azure support plans; those amounts are payable whatever the credit balance.

Late corrections after the close

An approved month is never overwritten. When a credit, a support charge or a corrected export delivery arrives after the cut-off, record a correction row with the original period, date received, amount, currency, document number, the provider's reason (such as the description on the Credit row) and the month in which it is reported.

Finance decides how large a correction must be before the previous month's report gets a new version instead of showing the change in the current month. Write the rule down once.

YesNoCredit, support charge or corrected delivery after the cut-offCorrection row: original period, date received, amount, currency, document number, reasonAbove finance's materiality threshold?New version of the previous month's reportShown in the current month
A correction after the cut-off never overwrites the approved month; finance's materiality rule decides whether the previous report gets a new version or the current month shows it

The evidence engineering hands finance for an accrual decision

Whether uninvoiced cloud usage is accrued, and how, is finance's call under the company's accounting policy, with the tax adviser or auditor where needed. This section is not accounting advice. Engineering supplies the evidence:

  • Amount per provider and billing account from the cut-off export, net and in invoice currency
  • Which parts already carry an invoice number and which are estimates
  • What can still move: AWS support, credits, Azure processing up to the fifth day, tiered pricing in Azure estimates
  • The expected invoice date according to the provider's documentation
  • The split by cost centre under the agreed allocation, with the unallocated remainder
  • Upfront payments for Savings Plans, Reserved Instances or Azure reservations as a separate item
  • The query and data version, so every figure can be reproduced

Finance should answer these questions in advance:

  1. Above what amount are outstanding cloud invoices accrued?
  2. Is the export amount at the cut-off the basis, and how are expected credits or support charges treated?
  3. Which exchange rate applies to US-dollar amounts?
  4. In which month do differences between estimate and invoice appear?
  5. How are credit notes for earlier months handled?
  6. Who signs off the cloud figures, and by when?

Common mistakes

  • A live dashboard as the close figure. The next refresh changes the value, and nobody can reproduce the approved number.
  • Missing Marketplace invoices. The Bills page lists invoices per service provider, and for accounts based in EMEA (excluding Turkey and South Africa) only purchases from EMEA-eligible sellers are billed by AWS EMEA SARL; other purchases are billed by Amazon Web Services, Inc.
  • Empty files read as zero cost. In Overwrite mode AWS can overwrite surplus chunks with empty data when an export shrinks.
  • Accounts that join the organisation mid-month. AWS bills the management account for a member account's usage only from the date it joined; earlier usage stays on the original owner's invoice.

What Costfluent covers

Costfluent reads billing data through read-only connectors for AWS, Azure and Google Cloud, presents it in euros and states the ECB rate method for each converted amount. Saved cost reports keep the close view with the same filters and can be emailed on a schedule; allocation rules and segments show cost per cost centre as showback. On the Custom plan, invoice reconciliation compares each issued provider invoice with the cost Costfluent ingested for the same month, shows the residual and exports the month. Costfluent does not post accruals, lock periods or write to the general ledger. See Costfluent for finance.

Sources and method

Checked on 2026-10-10. AWS Understanding export delivery, Viewing your finalized report, CUR 2.0 line item columns, CUR 2.0 table dictionary, billing columns with the BillingEntity values, Understanding your bill, Differences between billing data and Cost Explorer data, Effective billing date and Paying for products in AWS Marketplace; Microsoft Understand Cost Management data, Understand your Microsoft Customer Agreement invoice, Cost details fields, Marketplace billing and Azure credits on MCA. The reconciliation sheet, query and question list are Costfluent recommendations, not accounting advice.