Credits, refunds and corrections

A credit is a negative amount the provider sets against charges before the invoice is issued; a refund returns money for a line item already invoiced, and a correction changes that line after the fact. All three move the invoice total, but they sit in different places on the invoice and in the export, and often belong to a different billing period from the usage they relate to. Mixed up, a credit reads as lower usage and a refund as a cheap month.

How it works

A credit (promotional, programme or contractual) has a scope, eligible services and an expiry date. A correction arises because quantity, price or account data were wrong. A discount, by contrast, lowers the rate and belongs with the cost measures in list, billed, effective and amortized cost. The field name does not settle which is which: Google also carries discounts in its credits field.

AWS

AWS applies credits automatically to eligible services until they are used up or expire: the one expiring soonest first, then the one with the fewest eligible services, then the oldest, each against the largest service charge first. In an organisation with credit sharing on, a credit covers the account that owns it first, then the account with the highest spend. The management account can turn sharing off under "Billing preferences" or restrict a credit to certain accounts through Cost Categories; the setting in force on the last day of the month applies. The "Credits" page shows each credit's status (Active, Paused, Exhausted, Expired), expiry date and the amount remaining as of the last billing cycle. In CUR 2.0, credits appear as line_item_line_item_type Credit and refunds as Refund, which AWS describes as negative charges, with bill_bill_type Refund marking refund lines. AWS issues refunds after the monthly bill closes, and the legacy Cost and Usage Reports write them to separate files; when a credit or refund lands after finalisation, AWS updates that month's report.

Azure

Under a Microsoft Customer Agreement, Azure credits belong to a billing profile and are applied automatically to eligible charges when the invoice is generated. They do not cover partner and third-party products in Microsoft Marketplace, Azure support plans, or software not billed as Azure consumption; IsAzureCreditEligible shows this per line. The "Azure credits" tab under "Billing" > "Payment methods" shows the balance after the last invoice and each credit's expiry date, balance and status. The invoice's billing summary separates "Azure credits applied" from "Credits", the credits from returns. Cost details carry no credits, and refunds only under a Microsoft Customer Agreement, as ChargeType Refund with PreviousInvoiceId pointing to the original invoice. When an invoice is voided, the Billing API lists it with the status Void; a document of type CreditNote refers to it through creditForDocumentId, and the voided invoice's billedDocumentId names the invoice billed in its place. Under an Enterprise Agreement the "Credits + Commitments" page shows balances, new credit, adjustments and the amounts applied.

Google Cloud

Google attaches credits to the usage row: the credits struct in the standard export gives each credit's credits.id, credits.amount and credits.type. The types show how far the term reaches: PROMOTION for promotional and programme credits and FREE_TIER, but also COMMITTED_USAGE_DISCOUNT, SUSTAINED_USAGE_DISCOUNT, DISCOUNT for contractual spending-based discounts, SUBSCRIPTION_BENEFIT, RESELLER_MARGIN and FEE_UTILIZATION_OFFSET, which offsets the fees of spend-based committed use discounts. Google's example query builds the invoice total as cost plus the sum of credits.amount, and its sample output shows the credits as negative. Adjustments arrive as rows carrying adjustment_info: billing modifications such as GOODWILL or SLA_VIOLATION as separate line items, corrections such as USAGE_CORRECTION or PRICE_CORRECTION as rows on the original SKU that negate the original charge and, where needed, restate it, identical to the original row except cost, credits, usage.amount and export_time. An account on monthly invoicing receives a credit memo, which reduces the amount payable, or a debit memo, which increases it. A credit memo can apply to a previous, the current or a future invoice; the export shows a memo in the month it was issued, the cost table only those applied in the invoice period. Refunds for Postpay accounts go to the original payment method.

FOCUS

In FOCUS 1.4, ChargeCategory Credit is for financial incentives or allowances unrelated to other charges and Adjustment for other modifications; by definition Usage, Purchase and Tax include negative amounts and refunds. ChargeClass is Correction when a row corrects a billing period already closed, and empty otherwise, including for a correction within the current period.

What it means for your cost

A credit lowers billed cost, not usage, and belongs to the period it is applied in. Once introductory credit is used up or expires, billed cost rises at unchanged usage. A cost report before credits therefore shows consumption, one after credits shows payment. Separating promotional credits from discounts before building effective cost shows which part of the saving remains when the credit ends. How introductory credits arise and run out is covered in free tiers and introductory credits.

Refunds and corrections change the past: AWS updates a finalised report, Google books memos to the month they were issued, Azure points back to the original invoice. A report therefore fixes whether it assigns a refund to the month it was booked, as the invoice does, or to the month of the usage, as the cause does; either is coherent, a mix is not. The invoice period is covered in billing periods, cut-off and late charges, when export data becomes final in freshness, restatements and finalisation, month-over-month comparison in period comparison and the document itself in anatomy of a cloud invoice. How credits and refunds are booked is for your tax adviser and auditor to decide.

Where it goes wrong

• A credit read as falling usage. Symptom: a team's cost drops with nothing changed and later jumps. Cause: a credit covers charges until it is used up or expires, and the report shows cost after credits.
• A credit on the wrong account. Symptom: one member account shows almost no cost, another carries the rest. Cause: AWS spreads shared credits by spend and expiry date unless sharing is turned off or restricted through Cost Categories.
• A refund in the wrong month. Symptom: a closed month changes its total, or the following month looks too cheap. Cause: AWS updates finalised reports, Google books memos to the month they were issued, and the report has not decided which month it follows.
• Google's credits summed as promotional credit. Symptom: total credits exceed any credit ever granted. Cause: the field also holds committed use discounts, sustained use discounts and contractual discounts; only credits.type separates them.
• Azure export and invoice apart by the credit. Symptom: cost details exceed the invoice amount. Cause: they hold no Azure credits, which the invoice deducts under "Azure credits applied".

Sources

Read on 2026-10-16. AWS Applying AWS credits, Line item columns, Bill columns, What are AWS Cost and Usage Reports?; Microsoft Track your Azure credit balance for a Microsoft Customer Agreement, Understand your Microsoft Customer Agreement invoice, Understand usage details fields, Ingest cost details data, Invoices - Get, Review your Azure Enterprise Agreement bill; Google Cloud Structure of standard data export, Example queries for Cloud Billing data export, Resolve Cloud Billing issues, Get a Cloud Billing document such as an invoice, statement, or receipt; FinOps Foundation Charge Category, Charge Class, FOCUS column library.