Show Recurring and One-Time Revenue Without Calling Everything ARR

One month in the life of a single customer: a subscription renewed, an implementation was delivered, and metered usage ticked up. The invoice came to 420.

Multiply 420 by twelve and you get 5,040. It is a real number produced by real arithmetic, and it is the wrong thing to put on a slide under the words "annual recurring revenue per customer." Not because the multiplication is wrong. Because only one of the three things that made up the 420 was committed to happen twelve times.

What follows is an invented customer with invented amounts — 100 for one month of the recurring subscription, 300 for the one-time implementation, 20 for metered usage — so you can check the arithmetic and watch the reasoning. No company's records are involved, and the usage rule used here is a choice, not a universal convention. The point is the method: classify the parts, define the measure that annualizes one of them, and show the rest without dressing them up.

Classify the parts of the customer relationship

Start before the label. A customer relationship in a mixed business usually contains three different kinds of promise, and they deserve three different names.

The first is a commitment that continues: a contract obliging the customer to pay something on an ongoing basis until they or you end it. The second is work performed once — an implementation, a migration, a build — that may well lead to more work later but does not oblige it. The third is activity that varies: usage, seats, transactions, storage, messages. It might grow steadily for years. Nothing about that makes it committed.

The questions that separate them are short. What does the contract oblige? For how long? What ends it early, and on what terms? What triggers a bill — the passage of a month, the delivery of a milestone, the consumption of a unit? If the only thing making a payment recur is that the customer keeps choosing to buy, it is repeat business, not recurring revenue. A customer who returns next quarter for a second implementation has bought twice. That is a good sign about the customer. It is not a subscription.

Now watch the words. Sales calls a monthly platform charge a subscription, calls a support retainer a subscription, and sometimes calls a three-month project a subscription because that is how the order form was built. Product names a bundled line item after the feature it contains. None of these labels is a definition. The finance owner's definitions are. If you are assembling a deck and the finance owner's answer differs from the sales deck's answer, the sales deck is the wrong document to trust.

In the invented example, the stipulation is exact: the contract obliges 100 a month, the 300 was one implementation delivered once, and the 20 of usage accrued under a metered arrangement with no committed minimum. Three components, three statuses. Everything downstream depends on getting this classification right first — and if the contract did commit to a minimum usage spend, that floor would become a candidate for the recurring measure. That is a definition decision, and it changes the number. We will come back to it.

Explain the normalization behind the recurring number

Normalizing means expressing amounts from unlike periods on a comparable basis so they can be added or compared without lying about what they are. The recurring component is the one that supports this treatment, because a monthly commitment is genuinely the same commitment every month.

So the recurring monthly value here is 100, and its annualized amount is 1,200. That is twelve times a monthly figure, not a forecast that twelve payments will arrive. Those are different claims, and only the first one is arithmetic.

Write the definition down anyway. Not in your head — in the deck, in a sentence a reader can copy. It needs to say what counts, what does not, what basis was used, and what date the figure describes. Something in this shape:

Recurring value is the total monthly commitment of active contracts as of March 31, normalized to a monthly basis and multiplied by twelve. It includes subscription commitments. It excludes one-time implementation work and metered usage. Discounts are counted at the contracted rate actually payable. Contracts that start mid-month are prorated. Cancellations take effect at the end of the paid period.

Every clause in that sentence is a decision someone could decide differently. Do you count a customer whose invoice is unpaid? Do you count a paused account? Do you count a discount that expires in month four, and at which rate? Two companies with identical contracts can report different annualized recurring figures and both be telling the truth, because they chose different definitions. The only failure is not saying which one you chose.

Notice what is not in that sentence: any appeal to authority. ARR is not an accounting standard. It is an operating metric with a name that sounds official, and the name does not confer status. If your definition changes because the business changed — say you now count committed usage minimums — restate the prior period under the new definition and mark it, rather than publishing a series that quietly changed meaning in the middle.

That possibility is worth one more pass, because it is the most common place this goes wrong. In our example, metered usage is excluded. Suppose the contract instead committed the customer to a minimum of 20 a month in usage charges. A finance owner could reasonably include that floor in the recurring base, because it is now an obligation rather than an outcome. The recurring monthly value would read 120 and the annualized amount 1,440. Neither figure is more honest than the other. They are answers to different questions — "what is committed" versus "what was actually consumed" — and a reader can only tell which one they are looking at if you tell them.

Reconcile rather than rename the remainder

Here is where the 5,040 problem gets solved. Do not hide the excluded components, and do not relabel them. Show them beside the recurring measure, labeled by what they are.

The arithmetic reconciles, but not in a single step, and the step is worth showing. The 100, 300 and 20 add to the 420 that was billed. The way back from 1,200 runs through the same monthly base: divide by twelve to recover the 100 commitment, then add the 300 of implementation and the 20 of usage, and you are at 420 again. Subtract the excluded 320 from 1,200 without doing that first and you get 880, a number that appears nowhere in this example. Once the table names what it leaves out, a reader can walk from either figure to the other and arrive back where they started.

Resist the temptation to annualize the excluded parts so they can sit in the same column. Twelve times 300 is 3,600, and it is only meaningful if twelve implementations actually occur — which is a plan, not a metric, and belongs in a different part of the deck with that word attached.

Then keep your measures apart. Billings, recognized revenue and cash are three accounts of the same month and they routinely disagree. In the simple version of this example, the 100 is billed monthly in advance and recognized over the month it covers, so billings and recognized revenue coincide for the subscription. Change one stipulated term and they separate: if that same customer paid 1,200 upfront for a year, that month's billings would be 1,200 while recognized revenue would be 100. Same contract, same annualized recurring value, three genuinely different figures.

And if the customer left after three months, you would have billed 1,200 and recognized 300, while the 1,200 annualized figure would describe a commitment that had ended. That is a conditional, not a prediction — but it is exactly the inference a reader makes when they see an annualized number and nothing else. Annualized recurring value is not a forecast of collections. A customer billed annually who pays late gives you a metric and no cash.

A vendor's dashboard deserves the same care as a sales deck. Stripe's Billing analytics documentation, checked September 18, 2026 at https://docs.stripe.com/billing/subscriptions/analytics, describes recurring values normalized to a monthly basis and lets an account configure the definition — including choices about discounts and which subscribers count. Its standard monthly recurring revenue section excludes metered products. That is a useful demonstration that a definition has to be chosen and disclosed, and it is a good model for making the choice visible. It is not a standard your company inherits by using the tool, and one vendor's treatment of usage is not a reason your usage must be treated the same way.

Test the label against what a recipient could infer

Before the number goes on the slide, read it the way an investor, a board member or a new hire will. "Annual recurring revenue" does a lot of suggesting. It suggests this year's revenue. It suggests money already earned or reliably coming. It suggests the customer will still be there in twelve months. Your definition may establish none of those things, and the label will not explain the gap.

So put the boundaries next to the figure, not in an appendix that nobody opens. The date, the basis, and the biggest exclusion, in a line: Recurring value 1,200 annualized as of March 31; includes active subscription commitments; excludes implementation work and metered usage. That is one sentence, and it prevents most of the misunderstanding the label invites.

When the teams disagree about what belongs in the base, the answer is not to pick the larger figure. It is to hold the claim until the finance owner resolves the definition, or to rename it to something the current definition can actually support — "committed subscription value" instead of "ARR," if commitments are all you have counted. A smaller number with a definition attached is more informative than a larger one wearing the wrong name. The larger one is also the one that gets litigated later, in a meeting where the original author is not present to explain what it meant.

Two things follow from all of this, and they are unglamorous. The first is that the definitions in this article are illustrations, and this table is a construction built to make the arithmetic visible — not a record of anyone's business. A real version has to come from your own contracts and your own accounting, reviewed by the person accountable for the metric. The second is that the sentence you write is the deliverable. If you can finish the following without hedging, you have done the work:

Recurring value was 100 a month, or 1,200 annualized, as of March 31 — including active subscription commitments and excluding 300 of one-time implementation work and 20 of metered usage billed in the same month.

A reader can recover what that number leaves out, and therefore what it is worth. That is the whole job. The larger total is still available to you: 420 in billings for the month, 5,040 if you insist on multiplying it by twelve. Just do not put the wrong label on it.

Frequently asked questions

Why is multiplying the $420 invoice by twelve not a valid annual recurring revenue figure for this customer?

Only the $100 monthly subscription was committed to recur. The $300 implementation was one-time work delivered once, and the $20 of metered usage accrued under a metered arrangement with no committed minimum. Multiplying the total assumes all three parts happen twelve times, which the contract does not oblige.

When could a committed usage minimum be included in the recurring measure?

If the contract committed the customer to a minimum of $20 a month in usage charges, a finance owner could reasonably include that floor in the recurring base. Recurring monthly value would then read $120 and annualized amount $1,440. The article presents this as a definition choice between what is committed and what was actually consumed, not as one figure being more honest.

How should excluded implementation and usage amounts be shown next to recurring revenue?

Show them beside the recurring measure, labeled by what they are. In the example table, recurring subscription commitment is included as $100 × 12 = $1,200 annualized; one-time implementation is counted once when delivered; metered usage is counted as consumed and variable. Do not annualize the excluded parts unless twelve implementations actually occur, which would be a plan rather than a metric.

Why can billings, recognized revenue, and cash differ while annualized recurring value stays the same?

In the simple example, if the customer paid $1,200 upfront for a year, that month's billings would be $1,200 while recognized revenue would be $100; annualized recurring value would still be $1,200. If the customer left after three months, the company would have billed $1,200 and recognized $300, while the annualized figure would describe a commitment that had ended. Annualized recurring value is not a forecast of collections.

What should be written next to an annualized recurring figure before it goes on a slide?

Put the date, basis, and biggest exclusion next to the figure in one line. The article's example: recurring value $1,200 annualized as of March 31; includes active subscription commitments; excludes implementation work and metered usage. If teams disagree about what belongs in the base, hold the claim until the finance owner resolves the definition, or rename it to something the current definition can support.

Further reading

• Revenue, Profit, and Cash Tell Different Stories in a Pitch Deck — Read this to follow one transaction through recognition and collection, so billings, recognized revenue and cash are not quietly treated as the same recurring figure.
• Choose the Financial Story This Investor Deck Needs to Explain — Read this when the classified metrics need to become a coherent financial section; it orders revenue, profit, cash and position around the relationship the company must explain.