Why ARR and recognized revenue never tie out.

VISIBILITY — JULY 17, 2026 —

The board deck lists $42M in ARR. The income statement recognizes $37.8M. The CEO circles both and asks which number is a lie. The honest answer — and the one that ends the meeting fastest — is that this is exactly why ARR and recognized revenue never tie out, and neither figure is wrong. They measure different things on different clocks. Chasing a dollar-for-dollar match between them is the trap. Building a bridge that explains the gap is the job.

The people fielding the "are you playing accountant" conversation are almost always tracking ARR in one system and revenue in another, with nothing formal connecting the two.

Two numbers, two clocks

ARR is a forward run-rate snapshot. It answers: if nothing changed from this instant, what would the next twelve months of subscription revenue be? It is annualized, point-in-time, and it counts a contract the moment it is signed and live.

Recognized revenue answers a different question, and answers it under rules. Under ASC 606, a SaaS contract's transaction price is recognized ratably as the performance obligation is satisfied — which for most subscriptions means evenly over the contract term. A deal that goes live on the 20th of a month contributes roughly a third of that month's ratable slice, not a full month. ARR does not care about the 20th. Revenue does.

So the two numbers diverge structurally, not accidentally. ARR leads; recognized revenue trails. The SEC's guidance on non-GAAP measures exists precisely because run-rate figures like ARR are useful but are not GAAP, and the two must never be presented as interchangeable.

The mechanics that create the gap

Walk the flow and the divergence becomes obvious.

Bookings are the contracts signed in a period. A one-year, $120K deal signed on March 15 is $120K of bookings and $120K of ARR the day it's live.

Deferred revenue is what you've billed but not yet earned. Bill that $120K annually up front and the full amount lands in deferred as a liability. The FASB's revenue standard requires you to release it as you deliver — not when the cash arrives.

Recognized revenue is the slice released each month: roughly $10K, starting mid-March, so March's recognized amount from this deal is closer to $5.5K.

Accounts receivable tracks what's billed and owed but uncollected — a balance-sheet item that has nothing to do with either ARR or recognized revenue, though it gets dragged into the confusion constantly.

Four terms, four different timelines. ARR jumps to $120K instantly. Recognized revenue creeps up over twelve months. Deferred starts high and amortizes down. A reconciliation that expects these to equal each other in any given month is asking gravity to stop.

The consensus on the r/FPandA threads that surface this quarterly is blunt: stop trying to make them equal. The teams that keep re-running the numbers looking for a tie-out are solving a problem that does not exist.

The bridge, not the reconciliation

The fix is a standing bridge — a walk from ARR to recognized revenue that layers in each source of divergence as a line item. Rebuilt from beginning ARR, it looks like this:

Start with beginning ARR

Take the run-rate at the start of the period. This is the anchor.

Layer the timing of contract starts

New logos and expansions that went live mid-period contribute full ARR but only partial recognized revenue. Every deal live on the 12th or the 20th is a stub month of revenue against a full month of ARR. This line alone explains most of a growing company's gap.

Layer ramp deals

Ramped contracts — where the customer pays $20K in year one, $40K in year two — book ARR at the current tier while revenue recognizes on a schedule that may straddle the ramp differently. ARR says one thing today; the 606 schedule says another across the term.

Layer mid-period changes

Upsells, downsells, and churn all move ARR the instant they happen and move recognized revenue over the remaining term. A downsell on the 25th cuts ARR now; revenue keeps recognizing the old amount for most of that month. This is the same asymmetry that makes net and gross revenue retention diverge, and it belongs in the same conversation.

Reconcile against the deferred balance

The change in deferred revenue is the ledger's own record of the timing gap. If the bridge is right, it ties to the movement in the deferred balance. This is the check that turns a story into an audit-ready schedule.

Do this once and the gap stops being an accusation. It becomes a line-item explanation the CFO can read to the board in under a minute.

Why the bridge collapses monthly

The bridge is not hard to build. It is hard to keep standing when ARR lives in the CRM or a spreadsheet and recognized revenue lives in NetSuite or the billing system, with a manual export stitching them together each close. Every month someone rebuilds the join, re-keys the mid-period changes, and re-derives the deferred movement by hand. The bridge is only as current as the last person who rebuilt it. This is the same fragility that the tooling that governs the finance stack tends to expose first.

The teams that never field the "who's wrong" question generate both numbers off the same source — one definition of a contract, one live view feeding both the run-rate and the recognition schedule. When ARR and revenue reconcile continuously instead of at month-end, the bridge is standing, not reassembled. That live-data posture is the same discipline behind reading the Rule of 40 and CAC payback together and behind every SaaS metric a finance leader should own outright: the numbers are only as trustworthy as their common source.

See how finance teams run ARR and recognized revenue off one live source. →

For more on closing the visibility gap between what you report and what you can defend, the Visibility desk tracks it.

■