Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Revenue Operations

What Counts as Recurring Revenue?

ORM Technologies
Home/ Glossary/ What Counts as Recurring Revenue?
Definition Recurring revenue is revenue a customer is contracted to keep paying on a fixed schedule without making a new purchase decision. Subscriptions, term licenses, fixed-fee support and committed usage minimums count. Setup fees, implementation, training, one-time licenses and usage above the commitment do not.
Recurring revenue is revenue a customer is contracted to keep paying on a fixed schedule without making a new purchase decision. Subscriptions, term licenses, fixed-fee support and committed usage minimums count. Setup fees, implementation, training, one-time licenses and usage above the commitment stay out. Updated November 2026: added an include and exclude table and a worked example.

Both halves of the test matter. A predictable amount charged once fails it, even when the same customer buys it again every year. A contract that runs indefinitely but bills whatever the customer happened to consume passes only for the committed part. The same test sets both monthly recurring revenue and annual recurring revenue: ARR is the passing lines, annualized.

What counts as recurring revenue, line by line

Ask two questions of every line on a contract. Is the customer obligated to pay it again next period? Is the amount fixed or committed? A line counts only when both answers are yes.

Revenue lineCounts as recurring?How to treat it
Subscription or SaaS feeCountsAnnualized contract value, net of any discount that applies every term
Annual term licenseCountsAnnualized, the same as a subscription
Perpetual licenseStays outSold once. Sensiba's ARR guidance excludes perpetual licenses
Support or maintenance at a fixed feeCountsInclude when it renews with the subscription or license
Managed services or retainer, fixed fee, contractual renewalCountsInclude only if the fee is fixed and the renewal sits in the contract
Committed usage minimumCounts, up to the commitmentThe customer owes it whether or not they use it
Usage above the commitment (overage)Stays outTrack as a variable line; see usage overage revenue
Pay-as-you-go usage with no commitmentStays out of ARRIf you report a usage run rate, give it its own label
Setup, onboarding and implementation feesStays outOne per customer; report in services
Training, custom development, one-off projectsStays outSold per engagement; see services revenue vs recurring revenue
Hardware and pass-through costsStays outOne-time purchase
Multi-year contract, prepaid upfrontCounts at the annual valueRecurring portion divided by years in the term; the prepayment moves cash forward and leaves ARR where it was
Contracted step-up (ramp deal)Counts at the current-period rateHold later steps as contracted future ARR; see ARR for a ramp deal
First-year-only discount or free monthsCounts at the rate billed nowTreat the scheduled return to full price like a ramp step
Contract shorter than a year, built to renewCountsSensiba includes renewable contracts under one year, but does not annualize them until renewal is certain
Free trial or pilotStays outSensiba also excludes trial licenses and subscriptions
Signed but not yet liveHold in committed ARRMove it into ARR at go-live, or state that your ARR includes signed bookings
Known non-renewalRemoveSensiba excludes non-renewing subscriptions the company already knows about
ORM prices this way itself. Each module on the pricing page is quoted and paid annually, and implementation is a one-time fee scoped per deployment. Only the subscription belongs in ARR.

One contract, split line by line (illustrative)

An illustrative three-year deal, prepaid upfront:

- Subscription at $100,000 list with a 10% discount that applies every year: $90,000 a year. Counts. - Committed usage minimum: $24,000 a year. Counts. - Premium support at a fixed fee: $12,000 a year. Counts. - Usage billed above the minimum in year one: $15,000. Stays out. - Implementation: $40,000, once. Stays out. - Training: $8,000, once. Stays out.

ARR is $90,000 + $24,000 + $12,000 = $126,000. The customer prepays three years of the recurring lines, $126,000 x 3 = $378,000, so year-one cash is $378,000 + $40,000 + $8,000 + $15,000 = $441,000. Count the whole first-year invoice as recurring and you would report 3.5 times the real ARR.

The retention damage is quieter. Put the implementation, training and overage into the base and the account closes year one at $189,000 of "ARR." In year two the customer still pays every contracted line, $126,000, and gross retention reads 67% ($126,000 / $189,000). Nothing was lost.

The gray zone

A handful of cases cause most of the arguments.

Retainers. Annual retainers for advisory or managed services look recurring and often renew. They pass only when the fee is fixed and the renewal is contractual. A retainer that gets re-scoped and re-priced each year is a fresh sale each year. Overage. Overage recurs in practice at accounts that keep exceeding their floor. It still fails the contractual half of the test, which is why it lives on a separate variable line. Pete Furseth, ORM's COO, puts the forecasting side plainly: with usage pricing, revenue depends on customer behavior, so forecast the drivers of consumption instead of extrapolating last month's usage. Step-ups and temporary discounts. A contracted increase counts at the rate in effect for the current period. The scheduled increase is contracted future revenue, and it moves into ARR on the date it takes effect. A first-year discount works the same way in reverse. Price lifts at renewal. A renewal usually comes back at the same amount or with a price lift, and the lift counts from the date it applies. Watch the size. "If you are increasing price 10% a year or more, that puts pressure on the renewal," Pete says. The lift is recurring revenue with more risk attached. Repeat purchases ("reoccurring" revenue). A customer who reorders every quarter without a contract produces revenue that repeats but is not owed. Some finance writers call it reoccurring revenue. Report it next to the recurring line, never inside it, and move it in only once it is contracted. Signed, not live. A contract that is signed but not yet billing is committed, so track it as CARR until go-live. Pick one rule and print it next to the number.

Why the boundary decides other numbers

Every retention metric divides by a base of revenue that was supposed to recur. The worked example above shows how far a one-time fee in that base can move it. Net revenue retention breaks the moment the denominator includes revenue that was never going to repeat.

ORM's monthly retention waterfall shows why. It walks beginning ARR through churned customer ARR, churned product ARR, product decreases, new customer ARR, new product ARR and product increases to ending ARR, with each month opening at the prior month's close. Every line assumes the base holds only recurring revenue. A setup fee in that base shows up the next month as a contraction nobody can explain.

Capacity planning breaks the same way. A team that treats services attach as recurring will build next year's quota on a base that partly evaporates on January 1. Services still earn their place, since they often carry a customer through onboarding and show up later as retention. They just need their own line, and the recurring revenue vs total revenue split is where they belong.

Write the policy down

Publish the rule, name the specific line items on each side of it, and route every non-standard contract through the same reading. Then pick one CRM field as the source of ARR. ORM has seen a customer carry nine different amount fields (TCV, ACV, ARR, renewal amount and legacy fields left unpopulated after 2021), and sorting out which one meant what took several weeks because no single person held the history.

Forecasts miss most often because the model is built on assumptions that quietly stopped holding, and an ARR definition that drifts by deal is exactly that kind of assumption. Grounding the revenue forecast on a stable recurring base keeps the variance conversation about the market rather than about the definition.

Frequently Asked Questions

What is an example of recurring revenue?

A SaaS subscription billed every year under a contract that renews is the plainest example. A fixed-fee premium support plan, an annual term license and a committed usage minimum also count. The implementation fee on the same deal, the training days sold with it, and usage billed above the minimum are real revenue too, but they sit outside the recurring line.

Do setup and implementation fees count as recurring revenue?

Setup, onboarding and implementation fees stay out. They are charged once per customer and have to be resold with every new logo. Report them in a services line. A quarter heavy on implementation work lifts total revenue and run rate while ARR stays flat, and keeping the lines apart is what lets you see that.

Is usage-based revenue recurring?

Only the committed part. A contracted minimum counts up to its value, because the customer owes it either way. Consumption above the minimum, and pay-as-you-go usage with no commitment, depends on what customers do next month. Track it as its own variable line and forecast the drivers behind it. When an account stays above its floor, re-contract a higher minimum.

Does a multi-year prepaid contract count as recurring revenue?

It counts at its annual value. Divide the recurring portion of the contract by the years in the term, so a three-year, $378,000 prepaid subscription is $126,000 of ARR (illustrative). Prepaying moves cash and deferred revenue forward. It does not triple ARR in year one, and any one-time fees in the same contract stay out.

Is a one-year contract that auto-renews recurring revenue?

It is the clearest case, since the revenue continues unless someone acts to stop it. A one-year contract without a renewal clause still counts if it is a subscription built to renew. Pete Furseth, ORM's COO, sees auto-renew versus manual renewal as the biggest contract-level difference in renewal outcomes, so track which accounts sit on each.

Does support or maintenance revenue count?

It counts when it is contracted at a fixed rate on a fixed interval and renews alongside the subscription. Maintenance on a perpetual license counts on the same terms, even though the license itself stays out. Ad hoc support billed by the hour does not count, because the amount depends on what happened that month.

Put these metrics to work

ORM builds custom revenue forecast models that turn concepts like what counts as recurring revenue? into prescriptive action for your team.

Schedule a Demo