Understanding Cloud Credits: How Promotional Balances Actually Work
Cloud credit reduces an invoice; it does not stop a meter. This guide explains where AWS, Azure, Google Cloud and Oracle attach a balance, the four kinds of credit you may receive, the charges credit refuses to absorb, and how expiry is applied.

A credit is a balance, not a payment method
Cloud credit is one of the most misunderstood objects in a cloud account. People treat it like money in a wallet, transferable and generic. It behaves more like a coupon book stapled to one specific billing relationship, with rules about what it can pay for and a date after which it stops working.
Mechanically, a credit is a balance the provider holds against your billing entity. Usage is metered as normal, charges are calculated as normal, and then eligible charges are reduced by whatever balance remains. Nothing about your architecture changes. Only the final amount owed changes.
That distinction matters because it explains almost every surprise people report. Credit does not stop meters. It does not prevent a runaway job. It does not move with a resource when the resource moves. And when it runs out or expires, the same workload keeps running and simply starts producing an invoice.
Where the balance is actually attached
Every provider hangs credit off its billing object, and the shape of that object differs. Knowing which one holds your balance tells you exactly what you can and cannot restructure without losing it.
On AWS the credit sits on the account and is visible under Credits in the Billing and Cost Management console. In an organization with consolidated billing, the management account controls how credit sharing behaves across member accounts, which is one more reason the structure described in our guide to AWS Organizations and multi-account design is worth getting right early.
On Google Cloud the balance belongs to the Cloud Billing account, not to any project. You can re-point a project at a different billing account, and the credit stays behind with the old one. The relationship is unpacked in projects and billing accounts explained.
On Azure, credit is associated with the subscription created under the offer that granted it, which is why an upgrade path from a free offer to pay-as-you-go is handled as a subscription change. On Oracle Cloud, trial credit belongs to the tenancy and is separate from the Always Free allocation that persists afterwards.
Four kinds of credit, four sets of rules
Trial credit
Granted automatically at signup on several platforms. It normally carries the shortest expiry window and sometimes restricts which services or instance families it can offset. It is designed for evaluation, not for running production.
Program credit
Issued through startup, research, education or partner programs after an application. These awards usually have longer horizons, may arrive in tranches tied to milestones, and often come with named restrictions in the award letter. The overview of startup credit programs across the major clouds describes how the schemes differ.
Service credit
A remedy, not a gift. When a service misses its published availability commitment, the provider issues credit against future bills after you file a claim within the window set out in the service level agreement. It arrives after the fact and it is capped by the agreement.
Promotional credit
Codes handed out at conferences, in partner bundles or with hardware purchases. These are the most tightly scoped of the four. Read the terms attached to the code itself, because service, region and expiry restrictions are common.
Charges credit commonly refuses to absorb
No provider lets credit offset everything on the invoice. The exclusion lists differ in detail, but the same categories appear again and again, and they are precisely the categories that catch teams out at the end of a billing period.
| Charge type | Why it is usually excluded |
|---|---|
| Taxes and regulatory fees | Collected on behalf of a government rather than earned by the provider |
| Third-party marketplace software | Billed through the provider but owed to an independent vendor |
| Paid support plans | Sold as a separate subscription rather than as metered usage |
| Upfront commitment purchases | Reservations and similar prepayments settle against the payment method directly |
| Some specialist or preview capacity | Restricted deliberately while the provider manages scarce hardware |
Treat the table as a prompt to check, not as a substitute for the terms in your own account. The authoritative answer is always in the credit detail page beside the balance, where each grant lists its eligible services and its expiry date.
How the balance gets consumed
At invoice time the provider works through eligible charges and applies credit to them, generally consuming the grant that expires soonest first so that value is not wasted. Once eligible charges are exhausted or the balance reaches zero, everything remaining is billed to the payment method on file.
Two consequences follow. First, a long-dated grant can sit untouched while a short-dated one drains, so a single headline balance tells you less than the per-grant breakdown does. Second, partial coverage is normal: an invoice can be mostly offset by credit and still charge you for the excluded lines described above.
Credit also does not survive structural moves. Balances are tied to a billing entity and are not transferable between separate accounts, tenancies or billing accounts, so consolidating two environments means deciding which balance you are prepared to strand.
Finding the balance yourself
Learn the path in the console before you need it. On AWS, open Billing and Cost Management and choose Credits, which lists each grant with its amount remaining, its expiry and its eligible services. On Google Cloud, open Billing, select the billing account and use the Credits view; project-level cost pages will not show it.
On Azure, the balance for a credit-bearing offer appears under Cost Management and Billing in the credits view for the relevant billing profile. On Oracle Cloud, the tenancy overview separates remaining trial credit from the Always Free entitlement.
Pair the console with programmatic cost visibility so the trend is visible without logging in. Useful starting points include aws ce get-cost-and-usage for AWS Cost Explorer data, az consumption usage list for Azure, and a BigQuery billing export queried from gcloud for Google Cloud. Our guide to cloud cost monitoring and budget alerts shows how to wire those into notifications.
If you operate accounts sourced through the marketplace, the same discipline applies. The Google Cloud account listings and the AWS account listings describe what each option includes in its own terms, and support channels are the place to confirm specifics before you build on top of a balance.
Questions people ask about credit
Does credit expire even if I never use it?
Yes. Nearly every grant carries an expiry date set when it is issued, and an unused balance simply lapses on that date. The expiry is shown per grant in the billing console, so check each one rather than assuming the whole balance shares a single deadline.
Can I move credit to another account?
Generally no. Credit is bound to the billing entity it was issued against. Some providers allow sharing across accounts that sit inside one consolidated billing arrangement, which is a different thing from transferring a balance to an unrelated account.
Will a workload stop when the credit runs out?
No. Resources keep running and charges start landing on the payment method. This is the single most common cause of an unexpected invoice, and it is why budget alerts should be configured while the balance is still healthy.
How does credit interact with a free tier?
They are separate mechanisms. A free tier removes charges for a defined set of usage automatically and permanently or for a fixed period. Credit offsets charges that were generated. The differences are covered in free trial versus pay-as-you-go billing, and the AWS and Google Cloud comparison shows how the two vendors frame their entry offers.
Where is this documented officially?
AWS describes the mechanism in its billing credits documentation, and Google publishes the equivalent in its billing credits guidance. Both pages list the eligibility rules that apply to grants on those platforms.
Questions about a cloud account?
Ask about products, variants, availability or purchasing on either channel.


