Churn has a date, and most companies have never written down which one it is. Four candidates compete for the label: the day the customer gave notice, the day the contract expired, the day access was switched off, and the day the last invoice cleared. On a single enterprise account those dates can sit two quarters apart.
The four candidate dates
Notice date. The customer tells you they are leaving. This is the operational trigger for a save motion and the right date for an at-risk ARR view, because it is the earliest moment the loss is known. Contract end date. The subscription term expires and billing stops. This is the right date for revenue retention, because it is the date ARR actually leaves the base and the only one that reconciles cleanly to finance. Service termination date. Access is revoked. It often trails the contract end by weeks during a data export or transition period, and it belongs to support rather than to reporting. Last payment date. Useful for involuntary churn, where nobody sends notice and the signal is a failed charge followed by silence.Running notice date and contract end date side by side gives you the two things you need. One populates the pipeline of accounts you can still save. The other produces a retention number the CFO will sign.
The cases that need a written rule
- Contracts that lapse without a cancellation notice, where auto-renew was never enabled and the account simply goes quiet. - Payment failures that resolve after 45 days, which should not appear as a churn and a reactivation in the same quarter. - Accounts paused or suspended by agreement, which are neither active nor lost until the pause window closes. - Consolidation of several subsidiary contracts into one parent agreement, which reduces logo count without losing a dollar of ARR.
Each of these has a defensible answer. None of them has a default answer, which is why the decision has to be made once and written into the metric definition rather than relitigated every quarter by whoever is building the deck.
Why the timing changes the forecast
Recognition timing shifts ARR between periods without changing the annual total, and that shift lands directly in the plan. Recognize at notice and the base drops a quarter early, making the current period look worse and the next period look artificially stable. Recognize at contract end and you carry revenue that has already been lost, which reads as strength right up until the cliff arrives.
Cohort math is more sensitive still. A customer counted as churned in month 11 rather than month 13 moves out of the first year retention curve entirely, and that single reclassification changes the survival curve every downstream model is trained on. Keep the rule fixed, restate history when the rule changes, and check that net revenue retention and the ARR waterfall agree on the same event dates before either number reaches a revenue forecast.
Frequently Asked Questions
Should churn be recognized when notice is given or when the contract ends?
Recognize revenue churn on the contract end date so retention reconciles to ARR, and track the notice date in a separate at-risk view. A customer who gives notice in March for a December expiry is still paying through December, and moving the ARR out in March breaks the tie between the retention report and the revenue ledger.
Does a downgrade to zero seats count as churn or contraction?
Churn. If the recurring revenue on the account reaches zero, the account is gone regardless of whether a contract technically remains open. Leaving a zero dollar account in the active base inflates logo counts and drags average revenue per account down for no reason.
What happens if a churned customer comes back?
Set a win-back window, commonly 90 days, and apply it consistently. Inside the window, treat the return as a reversal and restore the original cohort. Outside it, book the account as a new logo with a new start date. Without a written window, the same event gets counted differently every time it happens.
How should an acquired customer be handled?
If the acquirer keeps the contract and the revenue continues under a different parent, that is an account merge and not churn. If the acquirer consolidates onto a competing vendor and the revenue stops, it is churn, and it usually belongs in a mid-contract churn bucket rather than a renewal loss.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like when do you count a customer as churned into prescriptive action for your team.
Schedule a Demo