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

Idea in Brief

The Problem. Sellers promise unused credits will roll over without realizing the promise changes both deal economics and revenue recognition.

The Instinct That's Wrong. Treating rollover as a costless goodwill gesture because the credits "were already paid for."

The Fix. Default to use-it-or-lose-it, make any rollover renewal-conditional and capped, and recognize that a real rollover right is a material right requiring its own slice of transaction price.

Every usage-based order form eventually hits the same month-end question: what happens to unused credits? The honest market answer, at most consumption-priced software companies, is that they expire. HubSpot's Product & Services Catalog states it plainly: "Your HubSpot Credits reset monthly during your subscription term. Unused credits do not roll over into the following month." Atlassian's Rovo usage-limits documentation is equally direct — credits "Reset monthly. Do not roll over; unused credits cannot be banked for future periods." Use-it-or-lose-it isn't a negotiating tactic; it's the published default at two of the more scaled consumption businesses in software.

That default matters because rollover feels free to a seller trying to close and isn't free at all. A real carryover right changes how much of the transaction price you can recognize today, and what you owe the customer if they never come back.

What the Best-in-Class Precedent Actually Says

Snowflake's Credit Consumption Table shows how a disciplined vendor handles rollover: it tracks "unused but paid for Capacity from prior Order Forms made available for use (i.e., rolled over)" as its own line item, distinct from current-period capacity. Snowflake's 10-Q ties the right to a transaction, not a courtesy: customers "may have the option to roll over any unused capacity to future periods, generally upon the purchase of additional capacity." Rollover is renewal-conditioned, not a standing entitlement. A clause without a renewal trigger and a cap is an open-ended liability; with both, it's a retention lever.

Why Rollover Is an Accounting Question, Not Just a Contract One

Once a rollover right is incremental to what similarly-situated customers get, Deloitte's DART 11.2 treats it as a material right under ASC 606. You don't recognize the full transaction price on day one — you allocate a portion to the option itself, at its standalone selling price, and defer it. A useful construct for sizing that allocation: SSP_option ≈ (incremental discount %) × (expected future purchase) × (exercise probability). This isn't a published formula, but a way to organize the analysis using Deloitte's inputs — every real number depends on your own contract facts.

The deferred piece doesn't sit there forever. Deloitte's DART 11.12 recognizes the deferred amount as revenue — breakage — once the material right expires unexercised. EY's Technical Line reinforces the same mechanics: options tied to future purchases get allocated, then resolved through exercise or expiration, never recognized up front. A related but distinct trap: if the credits sit behind a refundable prepayment rather than a use-it-or-lose-it commit, Twilio's 10-K records that cash as a liability — a customer deposit — not revenue, until usage earns it.

Credit Reset & Rollover

Preferred: Use-It-or-Lose-It

Credits allocated under the Total Commit Amount are available for use during the applicable Term and do not carry over to any subsequent Term. Unused credits at the end of the Term expire with no cash or credit value.

Use this when: this is the market default and your starting position on every order form, matching published policy at HubSpot and Atlassian Rovo. No material right, no deferral, no breakage analysis required.

Fallback: Renewal-Conditional Carryover

Upon renewal for an equal or greater Total Commit Amount, up to fifteen percent (15%) of unused credits from the expiring Term may be carried forward into the first month of the renewed Term.

Use this when: the objection is genuine forecast risk, not price. Mirrors Snowflake's conditional structure, and the 15% cap keeps the incremental value small enough to size precisely if it is a material right.

Approval-Required: Rolling Reserve

Unused credits from any given month within the Term may be applied to cover usage in the immediately following month only ("Rolling Reserve"), subject to a maximum carryover of one (1) month's allotment at any time. Credits unused for more than two (2) consecutive months expire.

Use this when: a strategic account needs real in-Term flexibility. This is a genuine material right under Deloitte's DART 11.2 and requires finance sign-off, since someone must allocate transaction price and track expiration under DART 11.12.

Why the Vantage Point Matters

Most individual sales organizations see a rollover request once or twice a quarter — often enough to relitigate the answer from scratch, rarely enough to build muscle memory around the accounting consequences. At Revolear, we set up dozens of new Order Forms every quarter for usage-based businesses and assist our customers' sellers in the mechanics of setting up these deals. That aggregate vantage point makes the pattern visible: year-end accounting headaches rarely come from deals with no rollover. They come from deals where a seller said yes to "sure, it'll roll over" without anyone deciding which tier, or flagging that a material right had just been created.

The Takeaway

Set use-it-or-lose-it as your published default, the way HubSpot and Atlassian Rovo have. When a customer needs flexibility, give it as a renewal-conditional, capped carryover — Snowflake's structure, not an open-ended promise. Treat any rollover right broad enough to look like a real option as what it is under ASC 606: a material right that gets its own slice of transaction price today and its own recognition event tomorrow. Refundable prepayments are a related but separate trap — a deposit on your balance sheet, not revenue, until usage earns it. The clause you write in the order form and the journal entry finance books later are the same decision, made twice, by two people who should be talking to each other before either one is final.

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

When a Customer Won't Commit to a Minimum

Renewal Is Not a Blank Slate

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

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

Raja Singh is the Founder & CEO of Revolear, which powers deal structuring and order form execution for usage-based software businesses.

Sources: Snowflake 10-Q FY26 Q3 · Snowflake Credit Consumption Table · HubSpot Product & Services Catalog · Atlassian Rovo Usage Limits · Deloitte DART 11.2 · Deloitte DART 11.12 · EY Technical Line · Twilio 10-K FY24