Cloud cost reporting for accountants hands finance what it can book: totals that match each invoice and its issuer, net with VAT shown separately, in the invoice currency, split by cost centre, with credits and refunds as lines of their own. The invoice is what counts, not the console: consoles and exports show estimates, leave out tax or spread commitments that the invoice states as one amount. Without this form, finance recomputes the cloud invoice by hand every month or books a total that belongs to no cost centre. How it is booked, accrued or capitalised is for finance to decide with the tax adviser or auditor; this page describes the data for it.
How it works
In the FinOps Foundation's Framework (CC BY 4.0), the Finance persona brings financial expertise: budgeting, forecasting, cost allocation, chargeback, invoice reconciliation and accounting compliance (core and allied personas). The capability Invoicing & Chargeback, in the domain Manage the FinOps Practice, covers the work with finance and accounting. It names the usual obstacles: invoices arrive days after month end, summarised invoices are hard to map to cost centres, and commitment discounts may not show on the invoice at all. Among the tasks it lists are checking the invoice with finance every month for discounts, credits, taxes and one-off charges, and supplying estimates and later true-ups for the close.
The fields for this are in the exports, and FOCUS gives them provider-neutral names.
| Content | FOCUS | AWS CUR 2.0 | Azure cost details | Google standard export |
|---|---|---|---|---|
| Invoice | InvoiceId | bill_invoice_id, blank until final | InvoiceId (MCA, pay-as-you-go) | invoice.month |
| Issuer | InvoiceIssuerName | bill_invoicing_entity, seller in line_item_legal_entity | PublisherType separates Microsoft and Marketplace (MCA) | invoice.publisher_type |
| Billing account | BillingAccountId | bill_payer_account_id | BillingProfileId | billing_account_id |
| Currency | BillingCurrency | line_item_currency_code | BillingCurrency | currency |
| Amount | BilledCost | line_item_unblended_cost | CostInBillingCurrency, before credits and taxes | cost, credits in credits |
| Tax | ChargeCategory Tax | line_item_line_item_type Tax | not included | cost_type tax |
| Credit, refund | ChargeCategory Credit, for closed periods ChargeClass Correction | line_item_line_item_type Credit, Refund | ChargeType Refund with PreviousInvoiceId; credits not included | credits, cost_type adjustment |
Once the invoice is issued, the sum of BilledCost per InvoiceId and InvoiceIssuerName may differ from the payable amount on the invoice by no more than the specification's rounding tolerance, and BillingCurrency must be the invoice's currency. The reconciliation step by step is covered in reconciling exports with the invoice, the cost centre fields in cost centres and team ownership.
Documents and recipients
When each provider issues its invoice is covered in accruals and the month-end close; for the hand-over, what counts is who receives the documents and how the PO number gets onto them.
AWS sends the monthly invoice, as a PDF if you opt in, to the root user, the billing contacts under Payment preferences and the alternate billing contact; once a billing contact is set, the root user no longer receives it. The Bills page lists invoices per service provider, with AWS EMEA SARL tax invoices in a section of their own. AWS matches up to 100 active purchase orders, each with up to 100 line items, to invoices by issuing entity, period and invoice type.
Azure generates one monthly invoice per billing profile under a Microsoft Customer Agreement. Once opted in, owners, contributors and invoice managers receive it by email, and further recipients such as the accounts team can receive it without access to the profile. The PO number and bill-to address can be changed, after which the invoice is regenerated. Under pay-as-you-go, each subscription receives an invoice of its own.
Google Cloud emails the invoices of an account that pays by invoice to a list of contacts. The PO number appears in the document's header details; after a change the invoice may have to be regenerated. Self-serve accounts receive statements, which Google says are not bills, alongside tax invoices and credit or debit memos.
What it means for your cost
Billed or amortised. Invoice, payment and reconciliation use billed cost. Charging cost centres suits effective cost, in which a prepaid commitment is spread over the usage it covers: in FOCUS the purchase row then carries an EffectiveCost of zero, the usage carries its share, and over the term both totals agree (list, billed, effective and amortized cost). The spread in the export is the provider's calculation, not a booking; whether and how a prepayment is deferred is for finance and the auditor to decide.
Net, in the invoice currency, tax apart. The hand-over shows net amounts in the invoice's currency and the tax per invoice separately. When a cloud invoice carries VAT is covered in VAT and reverse charge, how the providers set and convert the invoice currency in invoice currency and exchange rates; the tax treatment is for your tax adviser.
Credits in plain sight. A credit or refund stands as a line of its own that refers to the original invoice, rather than being netted quietly into one cost centre's cost. AWS may update reports after finalisation when credits or refunds for the month follow, and FOCUS marks corrections to closed periods with ChargeClass Correction (credits, refunds and corrections).
The monthly hand-over to finance therefore contains:
- per invoice: number, issuer, billing account, period, currency, net, tax, gross;
- per invoice and cost centre, the net billed amount and, where agreed, the effective amount;
- credits and refunds with the original invoice;
- the unallocated remainder as a line of its own;
- the cut-off, the export version and the reconciliation result, so every figure can be reproduced.
What of this is supplied before the invoice as an estimate for an accrual is covered in accruals and the month-end close and the guide cloud costs at month-end; capitalisation and P&L placement in capex, opex and capitalising cloud cost and cloud cost in the P&L. In the monthly cloud cost review, the hand-over is the part finance signs off.
Where it goes wrong
- Amortised reported as the invoice amount. Symptom: in the month a commitment is bought, the reported total differs from the invoice. Cause: effective cost was handed over instead of billed cost.
- Net against gross. Symptom: the Azure export falls short of the invoice by the tax. Cause:
CostInBillingCurrencyis the amount before credits and taxes. - Calendar month instead of invoice. Symptom: the monthly total matches no invoice. Cause: the filter used the usage date instead of the invoice; Google advises
invoice.monthfor this. - A credit hidden in a cost centre. Symptom: one cost centre looks cheaper for a month. Cause: the credit was netted instead of handed over as a line.
- An invoice that never arrives. Symptom: accounts learns of the invoice only from the payment. Cause: recipients and billing contacts are not maintained.
- A missing PO number. Symptom: accounts payable rejects the invoice. Cause: on AWS no active purchase order matched the issuer, period or invoice type; on Azure and Google the number was not entered and the invoice not regenerated.
Sources
Read on 2026-10-16. FinOps Foundation FinOps Personas and Invoicing & Chargeback (CC BY 4.0); FOCUS 1.4 InvoiceId, InvoiceIssuerName, BillingAccountId, BillingCurrency, BilledCost, EffectiveCost, ChargeCategory and ChargeClass; AWS bill columns, line item columns, understanding your bill, customizing your Billing preferences and managing your purchase orders; Microsoft understand usage details fields, understand Cost Management data and view and download your Azure invoice; Google Cloud structure of standard data export and get an invoice.