How to define revenue metrics that finance and sales both accept
Ask finance and sales for last quarter’s revenue and you will get two numbers. Neither team is wrong. They are answering different questions with the same word, and until someone writes down what the word means, every quarterly review starts with a reconciliation nobody planned for.
Why the two teams disagree
Sales counts what was sold, when it was sold. Finance counts what was earned, when it was earned. A contract signed in March for a service delivered over the next twelve months is March revenue to a sales leader and one twelfth of that per month to a controller. Add discounts, multi-year terms, usage pricing, and refunds, and the gap gets wide enough that each side starts to suspect the other’s number.
The disagreement is not about accuracy. It is about definition. That means it can be settled on paper before the quarter, instead of in a meeting after it.
One definition per metric, one owner
Every metric that appears in a deck gets one written definition, one formula in plain words, and one owner, a person who can be asked what it means. If two teams need different versions, they are two metrics with two names. “Revenue” and “bookings” are not competing versions of the same thing. They are different things, and the slide should say which one it is showing.
The owner is not whoever runs the query. It is the person who decides what the metric means and signs off when the definition changes. Finance owns revenue. Sales operations owns bookings. RevOps usually ends up owning the bridge between them, which is where most of the confusion lives.
Bookings, billings, and revenue
Bookings are the value of contracts signed in the period. They measure selling, and they belong to sales. Billings are what was invoiced in the period. They are what cash collection follows, and they belong to finance operations. Revenue is what was earned in the period under whatever recognition policy finance applies. It belongs to the controller.
In any given month the three can be far apart and all be correct. An annual prepaid contract is one booking, one billing, and twelve months of revenue. A monthly usage contract is twelve of each. None of that is a problem. The problem is a slide labeled “revenue” that is actually bookings, shown to someone who will compare it to the income statement.
Decide when to recognize
Recognition is finance’s call, and the metric definitions should defer to it. What RevOps has to decide is everything upstream of that: what date goes on a booking, signature or start date; what counts as closed-won in the CRM, a signed contract, a verbal yes, or a purchase order; and what happens to a booking when the deal changes after signing.
Pick one answer for each and write it down. The classic fight is a deal signed on the last day of a quarter that starts on the first day of the next. With definitions in place, it is a booking in one quarter and revenue in the next, and nobody has to argue about it.
Edge cases decided in advance
The list of edge cases is finite and mostly predictable: discounts and credits, refunds and clawbacks, multi-year contracts, mid-term upgrades and downgrades, churn before the contract ends, foreign currency, pilots that convert, and deals that come through a partner.
For each one, write what happens to bookings, billings, and revenue. One line, not a paragraph. When a new case shows up, the owners decide it within the week and the decision joins the list. The goal is that nobody has to invent an answer during a close.
Change control
Definitions will change. Pricing changes, a new product line launches, an accounting standard gets updated. The rule is that a definition changes only with a short written note: what changed, why, from which period, and whether history is restated. The dashboard carries a version number. A trend line that crosses a definition change gets a marker on it.
Without that, every change becomes a silent break in the series, and six months later nobody can explain why the number jumped.
Metrics that finance and sales both accept are not a compromise between their two numbers. They are both numbers, each with a name and an owner, and a written explanation of the gap between them. The agreement comes from the definition existing before anyone needs it.