ARR vs revenue: the five traps.

ARR is a forward-looking run-rate built to signal momentum. Revenue under GAAP or IFRS is a recognition construct built to signal substance. On a healthy SaaS, the two stay close. On a deal, they often don't — and the gap is rarely an accident.

What follows is not about accounting standards. It's the five places where we reliably find ARR inflated, understated, or redefined, and what to ask before taking the number at face value.

Most SaaS businesses now sell a mix of seats and consumption. Seats are annualizable. Consumption is, strictly, not — it's a function of behavior that can vary month to month.

The common move is to take the last three months of usage revenue, multiply by four, and call that ARR. It inflates the number whenever consumption is trending up, and it hides volatility.

What to ask. Split the ARR into committed (minimum) vs variable (above minimum). Walk the variable component back six quarters. If it's grown steadily, fine. If it spiked in the last quarter, price the deal on committed only.

On enterprise contracts, implementation fees, set-up, and professional services can represent 10 to 25 percent of a year-one invoice. They are one-off by nature. But on a growing book, those fees are invoiced every month alongside new logos, and they sit next to subscription revenue in the ledger.

Some CRMs default to tagging the full invoice as "SaaS." The finance team inherits that tag and moves on. On a deal deck, the line reads as ARR.

What to ask. Pull the invoice-level data. Separate subscription SKUs from services SKUs. Ask whether services are recurring by design (a retainer) or one-off by design (a onboarding). Only the first belongs in ARR. The second is a lumpy professional services line that deserves its own margin analysis.

A customer pays twelve months upfront in January. Cash hits. Deferred revenue builds. Revenue releases ratably over twelve months. ARR, meanwhile, is the same figure the whole year.

That's fine — until someone reads the bookings number, adds it to ARR, and reports both as "revenue" in a board pack. Or until deferred revenue is netted against ARR for a growth metric, making the company look like it's decelerating when it's actually just collecting.

What to ask. Keep three lines visible at all times: bookings (what was contracted in the period), ARR (the annualized run-rate at period end), and revenue (what was recognized in the period). On a deal, make sure the cash flow is reconciled to deferred revenue and not to bookings.

A customer signed in Q1 for an annual contract. They notified of non-renewal in Q3. Their contract ends in Q1 of the following year. In the meantime, where do they sit?

The honest answer: in ARR, until the contract runs out. But in the NRR calculation, they should already be flagged. And in any forward-looking model of ARR, their full amount should roll off at renewal, not be assumed to renew.

On weak teams, churn is only recorded at the contract end date. On strong teams, it's recorded at the notification date and tracked in a "gross churn pipeline." The gap between the two is often where a six-point NRR difference lives.

What to ask. Pull the renewal pipeline. For every contract ending in the next twelve months, what is the renewal probability as assessed by the CSM, and what is the contracted amount? The answer rarely looks like the headline NRR.

An enterprise customer signs a three-year contract with a front-loaded discount: year one at 30 percent off, ramping to list by year three. On the sales side, the quota retirement is typically the list value. On the finance side, the ARR recorded is the year-one billed amount.

The confusion is usually innocent — but on a deal, it means the ARR reported in the data room may not match the ARR assumed in the model. One number reflects what's invoiced today; the other reflects what's contracted for later. They are both defensible. They are not the same number.

What to ask. Request the contract-level data with effective ARR by period. Model the ramp. Ask whether the company discounts on the year-one line or on the ARR line — the answer changes the valuation.

1. What share of ARR is committed vs variable, and what's the six-quarter trajectory of the variable piece?
2. Can you split the revenue by SKU, with services separated from subscription?
3. Show me bookings, ARR, and revenue side by side for the last eight quarters.
4. What's the notified-churn pipeline for the next twelve months?
5. Pull the five largest contracts. Are any of them ramp deals, and if so, at what ARR level are they sitting in the report?

If the answer to any of these is "let me get back to you," that's the finding.