Get early access

Metric definitions / PRACTICAL GUIDE

Explain recurring revenue without counting every receipt

Define a recurring commitment metric with explicit inclusion, monthly normalisation and cancellation rules while keeping receipts and recognised revenue separate.

AI-assisted drafting · Illustrative examples · Editorial approach
Contents of this guide
THE SHORT ANSWER

A recurring-revenue metric needs a stated commitment basis, effective date and normalisation rule. Separate recurring service charges from one-off fees, taxes and receipts. Track starts, expansions, reductions and cancellations through a reconciled bridge, while keeping the metric distinct from recognised revenue and collected cash.

01

Specify what recurs and when it becomes eligible

A payment is not recurring merely because the customer has paid before. Define the contractual or operational commitment represented by the metric and the effective date used for inclusion. A planning measure might track active committed recurring service fees at month end, while another tracks fees billed during the month. Those are different populations and should not share an unexplained recurring revenue label.

Identify one-off setup work, usage charges, taxes, discounts and credits. Decide whether minimum committed usage belongs in the recurring base and how variable overages are reported. Avoid counting an uncertain renewal as a committed period merely because the customer has historically renewed. Retain the source contract or subscription reference and any known end date so the metric can be reconstructed from eligible records.

02

Normalise periods and changes consistently

For a monthly-normalised commitment measure, an annual recurring fee can be divided by twelve under the stated internal rule. Keep the original billing cadence and amount, because normalisation does not change when money is due. Define whether temporary discounts reduce the metric during their effective months and how mid-month starts or cancellations affect a month-end snapshot versus a period flow.

Build a bridge from opening recurring base through new commitments, expansion, contraction and churn to closing base. Classify each change once and retain the effective timestamp. A cancelled contract that remains active until its paid service end can require different operational and commercial views. State which view applies rather than allowing whichever system status changes first to decide the reported total.

03

Keep commitment, recognition and collection distinct

A large annual prepayment increases cash received but need not increase a monthly-normalised recurring base by the full receipt. Likewise, a delayed payment can leave the commitment measure unchanged while creating a collections issue. Show those concepts separately and use the applicable approved accounting policy for recognised revenue. The IFRS 15 link offers background on that separate recognition question, not a universal definition of a management recurring metric.

The example below is fictional and defines its own snapshot rule. Pair the headline with the recurring base bridge, customer concentration and material exclusions where they affect planning. A rising base can result from price changes rather than more customers, and a steady base can hide offsetting churn and expansion.

Keep scheduled future starts outside the active snapshot unless the label explicitly includes them. Reporting them in a separate committed-future view can support planning without implying that the service is already active at the measurement date.

Where a contract includes a temporary free period, document whether the commitment view uses its current effective fee or an averaged term value. Those choices can produce different monthly profiles without any difference in the signed contract.

PUT IT IN CONTEXT

Fictional subscriptions: a prepayment is not all monthly recurring value

A fictional scenario to explain the method, not a customer result or a market benchmark.

A fictional service defines month-end recurring base as active committed service fees normalised to one month, excluding setup work and tax. Ten monthly subscriptions contribute 100 units each, and one active annual subscription contributes 2,400 divided by twelve, or 200. The base is therefore 1,200 units per month.

During the next month, a new monthly subscription adds 150, an existing customer expands by 50, and a 100-unit subscription ends before month end. Closing base is 1,200 plus 150 plus 50 minus 100, or 1,300. A separate 500-unit setup receipt does not enter the recurring base. The annual subscription's full cash receipt remains a collections event.

The scenario assumes fixed commitments and no mid-month proration to isolate the definition. Its invented values demonstrate a reproducible bridge, not formal revenue recognition or evidence that a particular cancellation treatment fits every commercial contract.

TAKE THIS INTO YOUR NEXT CONVERSATION

A practical next-step checklist.

  • Define active commitment and effective date.
  • Separate one-off, variable and tax components.
  • Document monthly normalisation and cancellation rules.
  • Reconcile opening base to closing base.

Common questions.

Does an annual prepayment all count as monthly recurring value?

Not under a monthly-normalised definition. Retain the billing amount separately and apply the stated normalisation.

Can recurring base stay flat while customers leave?

Yes. Expansion or new commitments can offset churn, so publish the components as well as the closing total.

Further reading & source context.

These primary references provide background. They are not evidence for the fictional example above and do not endorse Accuralytix.

Found an error or a missing qualification? Send an editorial correction.

FROM READING TO YOUR NEXT MOVE

Check my data readiness.

Use a practical tool to turn this idea into a clearer starting point.

Check my data readiness