An accrual for cloud cost records in the month being closed the usage whose invoice has not arrived yet, so the month carries its own cost. It is needed because AWS, Azure and Google Cloud bill in arrears and issue the invoice only after the billing period ends, often after the day the books for the month are closed. The estimate comes from billing data, and the difference to the later invoice is trued up. Whether and how it is booked follows the accounting policy and is decided by the accountant with the tax adviser (in Germany, the Steuerberater).
How it works
Under § 252(1) no. 5 of the German Commercial Code (HGB), expenses and income of the financial year are recognised in the annual accounts regardless of when they are paid. IAS 1 requires financial statements to be prepared on the accrual basis (paragraph 27); with IFRS 18 that rule moves to IAS 8 (paragraph 6M). The HGB rule speaks of the financial year. Whether monthly closes accrue as well, and above which amount, is set by the accounting policy; where the financial year is the calendar year, the question at year-end mainly concerns December usage invoiced in January. Whether an outstanding invoice is recorded as a liability or as a provision for uncertain liabilities under § 249(1) HGB is for the accountant to decide with the tax adviser.
When the invoice arrives
Each provider documents how long a month stays open, Azure per agreement type:
| Provider and agreement | When it invoices | What still follows |
|---|---|---|
| AWS | The invoice is generated when the monthly billing period closes; until then the Bills page shows the status Pending with estimated charges. One-time fees such as an All Upfront reservation are charged immediately. | Support fees calculated from final usage charges on the sixth or seventh of the following month, credits and refunds under the agreement |
| Azure, Microsoft Customer Agreement | Invoice date typically five to 12 days after the end of the billing period | Usage charges can change until the fifth day after the period ends |
| Azure, pay-as-you-go | At the end of the invoice period, whose start and end vary by subscription type (Microsoft's example ends on the 15th); card charged within 10 days after the period ends | As for the Microsoft Customer Agreement |
| Azure, Enterprise Agreement | An invoice arrives when usage exceeds the credit from the Azure Prepayment, and for charges the credit does not cover: services billed separately and Marketplace | Usage within the credit draws down the prepayment without an invoice of its own |
| Google Cloud, invoiced account | Invoice for a month by the fifth business day of the following month | Late-reported usage can roll over to the next month's invoice |
| Google Cloud, self-serve account | A monthly statement, which Google says is not a bill, plus tax invoices and memos as applicable to the account and country; charged when a threshold is reached and for the balance on the first of the next month, or monthly on the second day | Charges during the month are payments, not the month's cost |
The fields that tie an export row to its billing period and invoice are covered in billing periods, cut-off and late charges.
The estimate and the true-up
At the cut-off the invoice is usually missing and the billing data is there. Per provider and billing account, the accrual in symbols is
A = E + Z - G
where E is the month's net cost in the export at the cut-off that is not yet on an issued invoice, Z the expected items the export still lacks, such as the AWS Support fee, and G the expected credits the export does not yet contain. When the invoice arrives with net amount R, the true-up is D = R - A; the policy sets the month in which D is booked.
How to spot the open part differs. On AWS, bill_invoice_id in the Cost and Usage Report stays blank until the report is final. Azure Cost Management shows estimates until the invoice exists, prices tiered rates at the highest tier during the open month, and includes neither support, taxes nor credits. Google Cloud shows usage in invoice details and reports with its actual date, even when it appears only on the following month's invoice. Where the invoice is in US dollars and the books are in euros or pounds, D also carries a currency effect (invoice currency and exchange rates). How credits and corrections appear on the invoice and in the export is covered in credits, refunds and corrections.
Prepayments such as the Azure Prepayment or an All Upfront reservation are the mirror image: the payment comes before the usage. § 250(1) HGB describes prepaid expense items for spending before the balance sheet date that is expense for a specific period after it, and the amortized cost in billing data shows the monthly consumption; how the payment is booked is for the accountant to decide with the tax adviser.
What it means for your cost
Without an accrual, each month carries the previous month's invoice. The P&L then runs a month behind the cost report, and a comparison with a budget mixes two periods. With an accrual, books and report agree on the usage month, and the true-up D shows how good the estimate was. It grows with credits, late fees, tiered prices, exchange rates and usage that rolls over to the next invoice.
For this the accountant needs, per provider and billing account:
- E, Z and G separately, net in invoice currency, with the part already invoiced kept apart,
- the billing period and the expected invoice date from the table above,
- for each item in Z and G, the reason it is still to come,
- the split by cost centre, with the unallocated remainder,
- the data version of the export, so A can be reproduced and D explained later.
The close itself, with cut-off and question list, is set out in Cloud costs at month-end: cut-off, reconciliation, accruals, and matching the export to the invoice in reconciling exports with the invoice. Where the accrual fits into the monthly routine is shown in Monthly cloud cost review: agenda and templates.
Where it goes wrong
- Payment booked instead of usage. Symptom: a month carries several charges from a Google Cloud self-serve account as cost. Cause: charges follow the threshold or payment cycle, not usage, and Google says the monthly statement is not a bill.
- Invoice month against usage month. Symptom: the true-up never reaches zero. Cause: Google Cloud rolls late-reported usage to the next invoice, and the Azure pay-as-you-go period need not be a calendar month.
- Support fee forgotten. Symptom: the month's final AWS charges exceed the accrual. Cause: AWS reflects Support fees in the prior month's report on the sixth or seventh of the month.
- Azure estimate too high. Symptom: the invoice comes in below the estimate. Cause: during the open month, Cost Management prices tiered rates at the highest tier.
- Credit read as a saving. Symptom: the invoice is below the estimate and the team reports lower cost. Cause: the estimate from Cost Management excludes credits; the invoice applies them.
- Prepaid usage accrued. Symptom: an Enterprise Agreement carries an accrual that no invoice follows. Cause: usage within the credit draws down the Azure Prepayment; only overage, separately billed services and Marketplace are invoiced.
Sources
Read on 2026-10-16. Gesetze im Internet § 249 HGB, § 250 HGB and § 252 HGB; IFRS Foundation IFRS 18 Presentation and Disclosure in Financial Statements; EUR-Lex Regulation (EU) 2023/1803 with IAS 1 and its consolidated text with IAS 8 as amended by IFRS 18; AWS Understanding your bill, Viewing your finalized report and Bill columns in CUR 2.0; Microsoft Understand your Microsoft Customer Agreement invoice, Review your individual Azure subscription bill, Understand your Azure Enterprise Agreement bill and Understand Cost Management data; Google Cloud Understand your monthly invoice, Find your account type and charging cycle and Get a Cloud Billing document such as an invoice, statement, or receipt.