Sales Play

Nov 24, 2026

Rollovers, Expiry, and Refundability: The Terms That Move Revenue

Idea in Brief

The Problem. When a customer doesn't use all their credits, sellers often agree to let them roll over. It feels free, because the customer already paid.

Why It Matters. What happens to unused credits decides when the seller can count that money as revenue. For spiky usage, a rollover can also shrink the commit dramatically: it lets the customer commit to something closer to their average month than their peak.

The Fix. Default to credits that expire. When you offer a rollover, treat it as a concession with a condition: a cap, an expiry, and a renewal sized to real usage.

The Question Every Usage-Based Contract Has to Answer

In a usage-based contract, the customer commits to a set amount of credits. Some months they use less than they bought. The contract has to say what happens to the rest. There are three possible answers:

  1. They expire. Unused credits are gone at the end of the month or the term. This is often called "use it or lose it."
  2. They roll over. Unused credits carry into the next period.
  3. They are refunded. The seller pays back what wasn't used.

Each answer is fair in some deals. But they have very different effects on revenue, so the choice should be deliberate, not something a rep agrees to on a call.

What Each Answer Does to Revenue

Under the accounting rules most software companies follow (ASC 606), credits a customer has paid or been billed for, but not yet used, are a promise the seller still owes. So that money sits as deferred revenue until something happens to the credits:

  • The credits are used. The seller recognizes revenue as the customer uses them.
  • The credits expire, with no refund. The seller gets to keep the money. Accountants call this breakage. When finance counts it as revenue depends on what they can estimate; the Breakage post explains how that works.
  • The credits must be refunded. The money was never the seller's to keep. It is a liability owed back to the customer, not revenue.

A rollover delays this. As long as unused credits keep carrying forward, the seller still owes them, so that revenue generally stays deferred until the credits are used, expire, or finance can show they won't be used. An open-ended rollover can push it out for a long time.

This is a plain-English summary, not accounting advice. Your finance team and auditors decide how your contracts are recognized.

What the Market Does

The common default is that credits expire. Even in self-serve products:

For negotiated enterprise commits, Metronome, which runs billing for usage-based companies, says "most commit contracts are 'use it or lose it,'" with exceptions such as letting "a small portion (e.g. 10–20%)" carry forward if the customer renews.

Where rollover is offered, it usually comes with a condition. Snowflake's 10-Q says customers "may have the option to roll over any unused capacity to future periods, generally upon the purchase of additional capacity." The rollover is earned by buying more, not granted for free.

How a Rollover Shrinks the Commit

Rollover sounds like a small courtesy. For a customer with spiky usage, it can be the biggest concession in the deal, even though nobody touches the price.

Here is why. If credits are granted monthly and expire every month, a customer who wants to avoid overage has to commit to enough credits for their busiest month. If credits roll over, the busy month can draw on credits saved from quieter months, so the customer only needs to commit to something closer to their average. The longer credits can roll, the closer to the average they can go.

Take a customer who uses about $5K of credits most months but $35K in two peak months a year, months 6 and 12. That is $120K of usage a year, or $10K a month on average. Here is the commit they need:

  • No rollover (credits expire monthly): $35K a month, or $420K a year.
  • 30-day rollover: $17.5K a month, or $210K a year. That is 50% less.
  • 60-day rollover: $11.7K a month, or $140K a year. That is 67% less.
  • Full-term rollover: $10K a month, or $120K a year. That is 71% less.

Why does a 30-day rollover cut the commit in half? Assume the oldest credits are used first. Then in each quiet month, the customer's usage comes out of last month's leftover credits, and this month's credits carry forward untouched. When the peak arrives, it can draw on a full month of saved credits plus its own: $17.5K + $17.5K = $35K.

The customer's usage is the same $120K in every case. What changes is how much they need to commit to, and so how much committed value the seller can count on.

Illustrative numbers. The example assumes credits are granted monthly, the oldest credits are used first, the peaks fall in months 6 and 12, and the customer sizes the commit to avoid any overage.

Notice the trade-off. At a 30-day rollover, a $210K commit covers $120K of usage: coverage of 0.57, with $90K of credits expiring. Short rollovers soften the peak but still leave a commit that is too big. For a very seasonal customer, an annual pool of credits usually fits better: an annual pool works like a full-term rollover, so the customer commits to about their annual usage.

And in practice, a customer facing monthly expiry would commit somewhere between their average and their peak, and pay overage in the busy months. How close to the peak they go depends on how much overage costs (see Overage Discounts). So the example shows the most a rollover can be worth.

How to Calculate It

With a rollover of N months, the peak month can use its own credits plus up to N months of saved credits. So:

Monthly commit needed = the larger of (Peak month ÷ (1 + months of rollover)) and (Average month)

In the example, with 60-day rollover: $35K ÷ (1 + 2) = $11.7K, which is above the $10K average, so the customer needs $11.7K a month. With full-term rollover, the peak divided by 12 is below the average, so the average sets the commit: $10K.

Then compare it with no rollover:

Commit reduction = 1 − (Commit with rollover ÷ Commit with no rollover)

With 30-day rollover: 1 − ($17.5K ÷ $35K) = 50%.

The formula is a shortcut for sharp peaks with quiet months in between. If a customer has several busy months in a row, or peaks early in the term before credits have built up, work it out month by month. The direction never changes: the spikier the usage and the longer the rollover, the smaller the commit.

Why Customers Ask for Rollover

Customers also ask to roll over credits when they are simply not using what they bought. In other words, their coverage is below 1.0. (Coverage is usage divided by commit. See Underpriced Minimums.)

Take a customer who commits to $120K a year and uses $96K. That is a coverage of 0.8, and $24K of unused credits by year end. Here is what each answer does:

  • Expire. The customer loses $24K. The seller keeps it as breakage, and the renewal starts with an unhappy customer.
  • Refund. The seller owes $24K back. It was never revenue.
  • Roll over with no limit. The $24K carries into next year. The customer uses those credits first, so they need less new spend. The seller's revenue is deferred, and the commit that was too big is never fixed.
  • Roll over with a condition. Up to 15% of the commit, $18K, carries forward, but only if the customer renews, and the carried credits count inside the new commit. With about $96K of expected usage, that means roughly $78K of new commit plus the $18K carried. The other $6K expires.

The last option is the only one that helps both sides. The customer keeps most of what they paid for. The seller gets a renewal sized to real usage, so the problem doesn't repeat.

Rollover Is a Concession. Give It a Condition.

In negotiation terms, a rollover is a concession, and the examples above show how big it can be. It lets a customer with spiky usage commit to less, and it makes a commit that was too big less painful. Like any concession, it needs a condition, or it is just a discount:

  • A cap. Only a set share of unused credits carries forward.
  • A renewal trigger. The carryover applies only when the customer renews at a commit sized to their real usage, with the carried credits counted inside it.
  • An expiry. Carried credits must be used within a set period, or they expire too.

Metronome's guide to enterprise commit contracts says the same: "If rollover is permitted, the cap, timeline, and renewal conditions should be clearly defined."

The renewal trigger matters most. It turns rollover from a reason to commit less into a reason to commit again. That is the same logic as pricing overage above the commit (see Overage Discounts): the better deal should come from committing.

Set the standard rollover terms with finance before reps offer them. A conditional rollover can change the accounting: depending on its terms, part of the price may need to be set aside for the rollover right itself, and a rollover granted after signing can count as a change to the contract.

When Rollover Is the Right Call

Sometimes it is. A customer whose usage is genuinely seasonal, or a slow start the seller caused, such as a delayed onboarding, are good reasons. Then give it the conditions above.

Measure Coverage Over the Rollover Window

A rollover changes how you should read coverage. If credits can carry forward, look at coverage over the whole period they can roll through, not just one month.

Coverage over the window = Usage over the window ÷ Commit over the window

If that number stays below 1.0, the rollover isn't smoothing out a slow month. It is covering for a commit that is too big. The fix is to resize the commit at renewal, not to keep rolling credits forward.

Where AI Helps

Rollover requests usually come up late, in a renewal or when a customer sees credits about to expire. With the expiry default and finance's standard rollover terms built into the playbook, AI can calculate the customer's coverage over the window, show the rep the conditional rollover instead of an open-ended one, and route anything outside the standard terms to finance for approval.

Try it this week: list your top 25 contracts by revenue that allow rollover. For each, note whether it has a cap, a renewal trigger and an expiry, and how many unused credits are being carried today. Any contract missing any of the three is deferring revenue without enough in return.

Close the Loop

Once a quarter, look at the customers who rolled credits forward:

  • Did they renew at a commit sized to their usage?
  • Is their coverage over the window still below 1.0?
  • How much revenue is deferred in carried credits, and is it growing?

If carried credits keep growing, commits are being sized too big.

Vantage Point

The trouble with rollover rarely comes from credits that expire. In the deals we see at Revolear, it comes from a "sure, they'll roll over" that nobody capped, conditioned or told finance about.

The Takeaway

What happens to unused credits decides when the seller counts that money as revenue, and a rollover can shrink the commit more than a typical discount. Default to expiry. Offer rollover as a concession with a condition: a cap, an expiry and a renewal sized to real usage. And when a customer keeps asking to roll credits forward, check coverage. The real problem is usually a commit that was too big.

Related in this series: this post is part of the Usage-Based Contracting series on credit pricing guardrails. Read more from the series:

Underpriced Minimums: The Hidden Cost of a Small Commitment

Overage Discounts: Why Cheaper Excess Undermines Renewals

Planned Unused Credits: Breakage Is a Finance Call, Not a Sales One

Which Credit-Pricing Terms Need Approval? A Discount Authority Matrix

The Deal Desk Glossary

Raja Singh is the Founder & CEO of Revolear, the AI deal desk that runs your commercial playbook on every deal.

Sources: Snowflake 10-Q FY26 Q3 · HubSpot Product & Services Catalog · Atlassian Rovo Usage Limits · Metronome, A Practical Guide to Enterprise Commit Contracts · PwC Viewpoint, Unexercised Rights · Deloitte DART 11.12

Experience Revolear

Explore our demos, discover our technology, get a quote, and meet our team—human and AI—in our Virtual Briefing Center.