How cloud credits work, and what expires first

A credit balance is one of the more misunderstood things in cloud billing, mostly because it looks like money and behaves like a coupon. Four rules explain almost every question that comes up.

Rule one: credits apply to an invoice, not to a purchase

You do not spend credits at the point of use. Usage is metered normally, an invoice is calculated, and eligible charges are then drawn from the credit balance. Anything not covered is billed to your payment method as usual.

This is why a valid payment method is required even on a credit funded account, and why an account with a healthy balance can still generate a real charge in the same month.

Rule two: they expire, and the order matters

Every credit carries an expiry date. Providers apply the soonest expiring eligible credit first, which is in your interest and worth knowing when you are holding several.

Two consequences:

• A large balance with a short window is worth less than a smaller one with a long window, if your burn rate cannot consume it in time.
• Unused credit is not refunded, converted or carried forward. It simply stops existing.

When planning around a credit, the honest calculation is expected monthly spend multiplied by months remaining, compared against the balance. If the balance is larger than that product, the excess is decorative.

Rule three: coverage has edges

The exclusions are similar across providers and follow a logic: credits cover the provider’s own metered services, not money that leaves the provider.

Commonly excluded:

• Third party marketplace software and subscriptions, because that revenue belongs to the seller.
• Support plan fees on some programmes.
• Upfront payments for reserved capacity or commitments.
• Certain premium or specialist services, which vary by provider and by credit.
• Taxes, in most jurisdictions.

The definitive list arrives with the credit itself. Read it rather than assuming, particularly if a large part of the planned spend is on a marketplace product.

Rule four: each provider has its own vocabulary

AWS calls them promotional credits, applies them per account, and lets you see the balance and expiry in the billing console. Organizations can share credits across member accounts depending on the credit’s terms.

Azure distinguishes the free trial credit from monthly credits attached to some subscription types and from sponsorship credits. They attach to a subscription, and moving a subscription between agreements can affect them.

Google Cloud attaches credits to a billing account rather than a project, which is why credit appears to go missing when you work in a project linked elsewhere. The mechanics are in Google Cloud account options.

Smaller providers issue trial credits with simpler terms, usually a flat balance with a short window and few exclusions.

Using a credit balance well

1. Check the expiry first. It determines whether the balance is useful for your project or merely large.
2. Spend it on the expensive things. Credit is best applied to the services you would otherwise hesitate over, not to the free tier.
3. Do not build a permanent architecture on temporary money. Design something you can afford at list price, then let the credit cover the ramp.
4. Watch the excluded line items. A marketplace database subscription paid in cash while credit sits unused is a common and avoidable mistake.
5. Set a budget alert anyway. Credits mask real spend until they run out, and the first uncovered invoice is the one that surprises people.

Where to read more

Provider specific detail is in AWS account types explained, Azure account types explained and Google Cloud account options. For what happens once the credit runs out, cloud pricing models compared covers the commitment mechanisms that reduce the ongoing bill.