Skip to content

Independent marketplace for verified cloud accounts

What Cloud Credits Cover, and What They Never Cover

A credit is a conditional, time limited, provider controlled entitlement, not money. What a balance actually buys, what it refuses to buy, and how to verify it.

Credits are the most misunderstood object in cloud billing. They look like money, they appear next to a currency symbol, and they reduce an invoice. None of that makes them money. A credit is a conditional, time limited, provider controlled entitlement to consume specific services, and almost every unpleasant surprise involving credits comes from forgetting one of those four words.

This guide works through what a credit balance actually buys, what it refuses to buy, and how to confirm what you are holding.

A credit is a provider controlled balance, not money

The balance lives in the provider’s billing system. The provider sets the terms, interprets the terms and can change them. Credits are generally non transferable, non refundable, and cannot be converted to cash or moved to another account. They are applied automatically against eligible charges at the provider’s discretion and in the provider’s chosen order.

That last detail matters more than it looks. If you hold several credit grants with different expiry dates and different service restrictions, the provider decides which one is consumed first. You usually cannot direct spending at the grant expiring soonest, which means a balance can expire unused while a later grant is being drawn down.

It also means the authoritative view of what you hold is the provider’s console, not a listing, not a screenshot, not an email. Anyone transacting an account with a credit balance should log in and read the billing page themselves before and after handover. Our guide to verifying credits before and after transfer sets out exactly which screens to check.

Service restrictions written into the grant

Most credit grants are not universal. They cover a defined set of services, and the definition is narrower than people assume.

Common exclusions include marketplace software purchased through the provider but sold by a third party, support plan fees, professional services engagements, domain registration, certain licence passthrough charges, and any upfront payment made as part of a commitment purchase. Some grants are restricted to a specific product family, such as compute only or an AI platform only. Some are restricted by region. Some exclude the newest or most in demand capacity entirely, which tends to include scarce accelerator hardware precisely when you wanted it.

There is also a difference between a grant that covers a service and a grant that covers a service at any scale. Some programmes cap how much of the balance may be spent on a single category in a month, which prevents a grant intended to fund a year of experimentation from being consumed in a fortnight of training runs. Others are tied to a specific project, subscription or billing account inside the organisation rather than to the login, so moving work to a neighbouring project silently takes it outside the covered scope.

The practical approach is to read the grant terms and then test them with a small real charge. Provision something modest in the service you are planning to spend on, let the billing cycle tick over, and confirm the credit absorbed it. A day spent confirming eligibility is cheaper than a quarter spent planning around a grant that will not cover your workload. This matters most for teams planning accelerator heavy projects, so read it alongside our guide to running AI workloads on credits.

Expiry dates and how they interact with commitments

Every credit grant expires. The date may be a fixed calendar date, a period from issue, or a period from first use, and these behave differently enough that it is worth knowing which you have. Unused balance at expiry is simply lost. There is no grace period as a rule and no partial carry forward.

The interaction with commitment purchases is the part that catches experienced teams. Buying a one year or three year commitment in order to “lock in” a lower rate while you still have credits can misfire in two ways. If the commitment requires an upfront payment, that payment is often not credit eligible. And if the commitment extends past the credit expiry, you have converted a flexible balance into an obligation that survives the funding. Work out the arithmetic in both directions before committing, and see our guide to reserved, spot and on demand pricing for how those purchase models actually work.

What credits almost never pay for

Several categories sit outside almost every credit programme, and they are the categories most likely to constitute an unpleasant residual invoice.

  • Support plans, which are usually billed as a percentage of spend and frequently calculated on pre credit usage.
  • Third party marketplace software, where the provider is collecting on someone else’s behalf.
  • Taxes, which are discussed separately below because they surprise people the most.
  • Charges incurred before the credit was applied to the account, since credits rarely backdate.
  • Charges incurred after expiry, including usage from a resource you forgot was running.
  • Penalties, late fees and currency conversion charges.

Build your forecast assuming these are payable in cash. If the grant turns out to cover one of them, that is a pleasant discovery rather than a load bearing assumption.

Tax, and why the bill is not always zero

In many jurisdictions tax is assessed on the value of the services supplied rather than on the amount of cash you hand over. A credit reduces what you pay the provider and does not necessarily reduce the taxable value of what you consumed. The result is an invoice showing substantial usage, a credit applied against it, and a small tax amount still due.

This catches people who have mentally filed the account as costing nothing and have not set up a working payment method, which can lead to a failed payment and the account dropping into a restricted state over a trivially small sum. Keep a valid payment method attached and keep an eye on the invoice even while credits are covering it. The exact treatment depends on your country and your registration status, so take local advice rather than ours on the specifics.

Verifying a balance inside the console

Whatever you have been told about a balance, confirm it yourself in the provider’s own billing interface. Four things to read, in this order.

The remaining amount, which is the obvious one. The expiry date attached to each grant, because a large balance expiring in three weeks is a different asset from the same balance expiring next year. The eligibility or restriction note, which states which services the grant applies to and is often a link rather than visible text. And the recent usage history, which tells you whether the balance has been drawn against and at what rate.

Screenshots are not verification. A billing page can be captured at any point in the past, and a balance that was accurate last month tells you nothing about today. Equally, a figure quoted in a conversation, a listing or a message is a claim rather than a fact, however honestly it was offered. The only statement that counts is the one rendered by the provider to an account you control, while you are logged into it.

Do this at the moment of transfer and again a few days later once a billing cycle has processed, because applied credits and displayed balances do not always update in real time. If you are taking over an account from anyone, pair this with our post handover security checklist, since billing access and administrative access need to be secured in the same sitting. TrustCloudHub is an independent marketplace and has no visibility into any provider’s billing system, so the console is the only authority on this.

Planning a project around a finite balance

Treat a credit balance as a fixed budget with a hard deadline, because that is what it is. Divide the balance by the number of months to expiry and you have a monthly allowance. Set a spending alert at that allowance and treat crossing it as a decision point rather than a notification.

Front load the work that genuinely needs the credited services and leave the work that could run anywhere until later, because that work can move to cheaper infrastructure when the balance runs out. Many teams find the sensible pattern is credits for experimentation and burst capacity on a hyperscaler, with the steady state moved to a lower cost operator once the shape of the workload is known. That is a legitimate use of a Buy Google Cloud Account or Buy Azure Account alongside something cheaper for the baseline, and the Google Cloud and Hetzner comparison illustrates how large that gap can be for plain compute.

Finally, plan the exit before you need it. Know roughly what the monthly bill becomes at full rate, know which workloads you would move first, and know how long moving them takes. The teams that handle credit expiry calmly are the ones who wrote that down in month one.

Related comparisons

Azure vs Linode
vs

Azure vs Linode

Linode under Akamai sells predictable compute close to users. Azure sells a governed enterprise platform. This comparison focuses on hybrid…

Azure vs Civo
vs

Azure vs Civo

Civo treats managed Kubernetes as the whole product. Azure treats it as one service among hundreds. That difference in focus…

Google Cloud vs Azure
vs

Google Cloud vs Azure

Google Cloud and Microsoft Azure both cover the full hyperscaler surface, but identity, data tooling and commercial structure pull teams…

Azure vs UpCloud
vs

Azure vs UpCloud

UpCloud is a Finnish provider built around fast storage and a small, clear product line. Azure is a Windows centric…

Accounts discussed in this guide

Buy Azure Account
Buy Azure Account
Microsoft Azure

Buy Azure Account

Microsoft Azure has firmly established itself as one of the world's leading cloud computing platforms, trusted by enterprises, government agencies, and developers across the…

From$25 13 options
Buy Google Cloud Account
Buy Google Cloud Account
Google Cloud

Buy Google Cloud Account

Google Cloud Platform has emerged as one of the most powerful and versatile cloud computing environments available today, and for good reason.

From$70 5 options

Keep reading

Multi-Factor Authentication Across Cloud Providers
Security and IAM 7 min read

Multi-Factor Authentication Across Cloud Providers

MFA is the single highest-value control on a cloud login, but only if recovery is planned. This guide compares factor types, enrolment…

Need the account, not just the theory?

Browse documented configurations across every provider in the catalog, or ask us which one fits your workload.

Telegram