A cloud invoice is the document with which the provider demands payment for one billing period: issued by a named legal entity, in one currency, with line items, credits, a tax line where one applies, and payment terms. It is not the billing data. The invoice states what is owed; the export explains where the total came from. Teams that treat the two as one reconcile numbers that were never meant to match and explain cut-off and scope as if they were usage.

How it works

All three providers meter usage continuously, price it, and close the billing period, normally the calendar month, a few days after it ends. Only then is the invoice generated; until then the console and the exports show estimates. Every invoice names the issuing entity, the currency, the period and an invoice number that ties its lines to the billing data; which entity and which currency depend on the account and the agreement, and the chapter Europe: currency, tax and sovereignty covers both. The structure of the line items differs by provider.

AWS

AWS issues the invoice when the monthly billing period closes (status "Issued"), and immediately for one-time fees such as an All Upfront reservation purchase. The Bills page shows charges by service and region and, in the management account of an organization, by member account. With consolidated billing the management account pays for all member accounts and receives one bill per seller of record; usage is combined across accounts for volume tiers, Reserved Instances and Savings Plans, and the member accounts' own bills are informational. The Invoices tab lists one invoice per billing period for each service provider you transacted with: AWS service charges and third-party Marketplace purchases are separate documents. Support fees are calculated per member account from its usage, subject to a monthly minimum. Totals are in US dollars; an invoice issued in another currency shows that amount as well. Taxes are shown per service, with tax invoices as separate documents.

Azure

On Azure the agreement type decides the layout. Under a Microsoft Customer Agreement one invoice is generated per billing profile, which Microsoft puts at five to twelve days after the billing period ends. The invoice summary names sold-to, bill-to, invoice number, invoice date and payment terms; the billing summary shows charges, credits, Azure credits applied, subtotal, tax and total due. Below it come the invoice sections, each broken down by product order and service family, with unit price, quantity, charges/credits, Azure credit, tax rate, tax amount and total per line. Usage between the end of the period and the invoice date belongs to the next invoice.

A pay-as-you-go subscription receives an invoice by email per billing period, with usage lines at meter level and the columns name, type, resource, region, consumed, rate and value. The matching usage file is normally ready within 72 hours after the invoice is issued; the sum of its Cost column equals the usage charges on the invoice, and it carries no tax. External Marketplace services appear on a separate invoice.

Under an Enterprise Agreement usage draws down the Azure prepayment. An invoice is raised when usage exceeds the credit balance, for services billed separately, and for Marketplace purchases the credit does not cover. Azure usage with a cost comes first, then Marketplace, then the usage covered by credit with no amount. An invoice with more than 1,000 line items is split into several.

Google Cloud

Google Cloud bills per Cloud Billing account. An invoiced account generally receives one invoice a month, available by the fifth business day of the following month; transactions involving resellers or several countries can be split across invoices. Self-serve accounts receive a statement instead, which is not a bill because the payment method on file is charged automatically. Both documents hold only a summary. The lines by project, service, SKU and consumption model are in the cost table in the console, whose totals match the invoice under the default filters; credits and usage-based discounts appear there as separate lines, and tax is attributed per project.

What it means for your cost

The invoice is the amount finance pays and books; the billing data is the explanation behind it. Three things decide whether the two agree.

First, granularity. An AWS invoice sums by service, an MCA document by invoice section and product, Google by billing account. The resource, the tag and the team exist only in the export. Allocation works from the export, payment from the invoice.

Second, scope. Exports and cost analysis show usage and purchases, often without tax, support and credits. Azure Cost Management lists those three explicitly as not included and adds a rounding adjustment once the invoice exists so that the cost file and the invoice agree; on the AWS Bills page taxes are a tab of their own. The invoice carries everything.

Third, cut-off. The invoice knows the invoice month; the export knows when the usage happened. Google documents that late-reported usage can roll to the next invoice, so the cost of an invoice month differs from the cost of the calendar month; Azure puts usage after the period end on the following invoice. A cost report should therefore say what it rests on: invoice or export, invoice month or usage month, and which cost measure it shows.

Where it goes wrong

  • Reconciling the PDF to the export without settling scope. Symptom: the export falls short of the invoice by the tax, support or credit amount, and the gap is hunted in usage. Cause: the invoice carries lines the export does not hold. Reconcile usage charges against usage charges, as Microsoft's own walkthrough does for the pay-as-you-go invoice.
  • Invoice month confused with usage month. Symptom: the month-over-month comparison jumps although usage was flat. Cause: usage from the last days of the month sits on the next invoice but in the export on the day it occurred.
  • A credit landing on a later invoice. Symptom: one month looks too expensive, the next too cheap. Cause: AWS can apply a credit or refund after the bill is finalised and then updates the reports; on Azure, credits from returns appear in the billing summary of the invoice in which they are booked.
  • Several invoices per month. Symptom: one document is booked as "the invoice" and the rest is missed. Cause: AWS splits by seller of record and Marketplace, Google by reseller and country, Azure by billing profile and, under an Enterprise Agreement, at 1,000 line items.
  • Reading an estimate as the invoice. Symptom: the figure taken from the console no longer holds on the invoice date. Cause: every amount is an estimate until the period closes; Azure notes charges can be rerated until the invoice is issued.

Sources

Read on 2026-10-15. AWS Understanding your bill, Consolidating billing for AWS Organizations, Support charges for accounts in an AWS Organizations, What are AWS Cost and Usage Reports?; Microsoft Understand your Microsoft Customer Agreement invoice, Review your individual Azure subscription bill, Review your Azure Enterprise Agreement bill, Understand Cost Management data, Understand usage details fields; Google Cloud Get a Cloud Billing document such as an invoice, statement, or receipt, View and download the cost details of your invoice or statement.