Two forecasts with two jobs
The sales forecast and the company forecast are different objects, and treating them as one version of a single number is why the reconciliation meeting is painful. The sales forecast answers what will close and when, built from pipeline, stage conversion, and rep behavior. The company forecast answers what revenue gets recognized and when cash lands, built from bookings, start dates, billing terms, and renewal assumptions. Revenue operations owns the first. Finance owns the second.Neither is a draft of the other. A deal that closes on the last day of the quarter with a February start date is a hit for sales and a miss against the revenue plan.
Where the two numbers diverge
Four gaps produce most of the difference. Timing, because bookings and recognized revenue land in different periods. Value, because deals close below the amount carried in the CRM. ORM's illustration of the gap is a pipeline carrying an average deal size of $80,000 against closed-won deals averaging $40,000, which also inflates pipeline coverage. Renewals, which finance models as a base and sales frequently excludes. And seasonality, which most models understate. ORM's read is that Q2 and Q4 run stronger than Q1 and Q3, and that the third month of a quarter runs stronger than the first two.
Write the bridge between the two numbers once. After that, the monthly variance conversation is about which line moved rather than whose spreadsheet is wrong.
The reconciliation meeting
Run it monthly and hold it before the board pack gets built. Bring three inputs: the sales forecasting output from the CRM, the finance plan, and the delta broken into named categories. The output is one number the CEO can carry plus an owner for each gap.
The failure mode is finance quietly haircutting the sales number. It teaches sales leadership that a submitted forecast is an opening position, and within two quarters the submitted number carries padding to survive the haircut.
Who fixes accuracy
Accuracy is a RevOps problem with a finance consumer. ORM's benchmark for new and expansion forecasting is that most teams land around 90 percent and pay for it with heavy manual effort that goes stale as conditions change. ORM targets 95 percent without manual adjustment and holds it from day one through day ninety of the quarter. The ownership consequence is direct: a number produced by hand cannot be audited by finance, and a number finance cannot audit gets discounted before it reaches the board. Publishing forecast accuracy by segment and by rep is what converts the reconciliation from a negotiation into a review.
Frequently Asked Questions
Should the sales forecast go through finance before the board sees it?
Yes, but as a reconciliation rather than an edit. Finance translates bookings into recognized revenue and cash timing, which is a different number by design. Finance rewriting the sales number without documenting the bridge hides the disagreement instead of resolving it.
What if finance and sales disagree in the last week of the quarter?
By then the disagreement is academic, because the quarter has already happened. The reconciliation has value in the first weeks of the quarter, when the shape of the quarter is still changeable and a gap between the two views can still be worked.
Does revenue operations belong under finance?
It can, and the reporting line matters less than the split of duties. What breaks the forecast is one function owning both the committed number and the method behind it, because a miss can no longer be traced to execution or to method.
How do you measure which forecast was right?
Score each against its own definition and keep the submissions immutable. Bookings forecasts get scored on bookings, revenue forecasts on recognized revenue. If submitted numbers can be edited after the fact, accuracy becomes unmeasurable and every postmortem turns into a memory contest.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like revops vs finance forecast ownership into prescriptive action for your team.
Schedule a Demo