Key Takeaways

• Rollover is a policy decision with a balance sheet consequence, not a customer-friendliness toggle.

• A customer granted 1,000 monthly credits who uses 400 accumulates 7,200 unused credits in a year under uncapped rollover, and zero under no rollover.

• Capping rollover at one period's grant holds the carried balance flat at 1,000 credits instead of letting it compound.

• Rollover and expiry are separate settings that contradict each other if you configure them independently.

• Promotional credits are the case to exclude from rollover, because they were never paid for and carrying them forward turns a one-time incentive into a permanent discount.

What are the types of credit rollover?

Four policies cover almost every implementation, and they differ in how much of the unused balance survives period close. Billing platforms vary in which of these they expose as configuration rather than code, and Flexprice documents its own rollover rules under Credits and Wallets.

The policies, from most restrictive to least:

• No rollover. Unused credits expire at the end of the billing period. Simple, predictable, and the version customers complain about most.

• Capped rollover. Credits carry forward up to a limit, usually one period's grant. The balance stays bounded while the customer keeps some benefit.

• Time-limited rollover. Credits carry forward but expire a fixed number of periods later, so a March grant unused in April still dies in June.

• Uncapped rollover. Everything carries forward indefinitely. Generous, and the version that quietly builds a liability nobody modeled.

Teams also split the policy by credit source, which matters more than the policy itself: purchased credits roll over, promotional and trial credits don't. See best tools for managing promotional credits in saas. A customer who paid for credits has a reasonable claim on them. A customer who received 500 free credits doesn't, and rolling those forward means the promotion never ends.

How does rollover interact with credit expiry?

Expiry always wins, and treating the two settings as independent is what produces contradictory configurations. Rollover decides whether a credit survives the period boundary. Expiry decides whether it survives at all.

How the two combine:

Row 3 is the configuration most teams land on and the one they should sanity-check, because the expiry date they carefully negotiated never has any effect. If the cap already bounds the balance, the expiry setting is decoration.

The interaction also decides deduction order, which is where rollover quietly changes what a customer forfeits. If rolled-over credits and a fresh grant sit in the wallet together, burn-down should consume the older balance first. Consume the fresh grant first and the rolled-over credits age into expiry unused, which produces exactly the outcome rollover was supposed to prevent.

What does rollover cost you on the balance sheet?

Every rolled-over credit is deferred revenue you've collected and not yet earned, so uncapped rollover compounds a liability while capped rollover holds it flat. The revenue is the same either way. The timing of recognizing it is not.

A customer granted 1,000 credits a month who consumes 400, tracked across a year:

At $0.01 per credit, that month-12 uncapped balance is $72 of deferred revenue per customer. Across 1,000 customers on the same plan it's $72,000 sitting as an obligation, growing every month, against credits the customer may never consume.

Three consequences worth planning for before the policy ships:

• Revenue recognition stretches out. You can't recognize credit revenue until the customer consumes the credits or they expire, so uncapped rollover defers recognition indefinitely.

• A customer who churns with a large rolled-over balance may have a refund claim on it, depending on the contract.

• Forecasting gets harder, because a customer can consume twelve months of accumulated credits in one month and generate no new revenue while doing it.

The policy I'd default to: purchased credits roll over with a cap of one period's grant and a hard expiry at twelve months, promotional credits don't roll over at all. That keeps the liability bounded, gives paying customers a real benefit, and stops a trial incentive from becoming permanent.

Related terms

Rollover only makes sense alongside the terms that grant, consume, and bound a credit balance.

• Credit burn-down is the deduction process whose order decides whether rolled-over credits get used.

• Billing period is the boundary rollover carries a balance across.

• Consumption-based pricing explains why customers fund a balance in the first place.

• Spending cap is the control for customers without a credit balance to draw down.

• Credit memo is a different instrument entirely, reducing an invoice rather than funding usage.

FAQ

Should prepaid credits expire?

Usually yes, on a horizon long enough to feel fair, commonly twelve months. Credits with no expiry stay on your balance sheet indefinitely and defer revenue recognition with them. Credits that expire in thirty days generate support tickets and rarely survive a procurement review.

What's the difference between credit rollover and credit expiry?

Rollover decides whether unused credits survive the end of a billing period, and expiry sets a date after which credits die regardless of how many periods they've survived. A credit can roll over eleven times and still expire in month twelve.

Do promotional credits roll over?

They shouldn't, in most designs. Promotional and trial credits exist to drive a first action, and carrying them forward converts a one-time incentive into an open-ended discount. Configuring rollover per credit source rather than per wallet is what makes that distinction enforceable.

Does rollover count as deferred revenue?

Yes, for credits the customer paid for. Money collected against unconsumed credits is an obligation until the customer consumes them or they expire, which is why an uncapped rollover policy defers revenue recognition further with every period.