Solution
Pipeline, bookings, and revenue on one definition, so sales and finance stop reconciling the same customer two different ways.
Contact UsContact us for a Free Assessment. We'll follow up within 2 business days.
The weekly revenue meeting needs a number it can open. Pipeline comes from the CRM. Bookings follow a definition sales and finance write down together. Recognized revenue comes from the ledger, and it should agree with the financial reporting pack.
Power BI is where that view usually lives. The result that matters is one definition both teams will use when someone asks what revenue is.
Sales and finance can both be careful and still walk into the meeting with two lists of customers and three meanings of revenue. These are the usual breaks.
Sales has an account billing does not, or billing has an invoice the CRM never recorded. Until the lists are compared, a pipeline total and a revenue total answer different questions, even when the meeting uses one word for both.
Pipeline is work that might close. Bookings are what you count as won, under a definition you choose. Recognized revenue is what the books say was earned. Using the words interchangeably makes a forecast look wrong when the vocabulary was the problem.
An opportunity marked Closed Won with no invoice, or an invoice with no opportunity, changes the total depending on who exports the data. The meeting then debates the file. The customer conversation waits.
Duplicate accounts, blank amounts, stale close dates, and stages nobody maintains will move a forecast more than the arithmetic will. Looking at that quality is part of getting a number you can use. It does not have to become a separate project that blocks the first view.
If recognized revenue in the weekly view does not match revenue in the month-end pack, finance will not use the weekly view when the books are the question. The two pages have to share the ledger figure for what was earned.
Pipeline is the open work in the CRM: opportunities that are not won and not lost, with the amount and the close date sales will stand behind. A weighted pipeline applies the stage weights you already use. We do not invent a weighting scheme and present it as a forecast.
Bookings need a sentence you can read back. One common definition is Closed Won in the CRM and invoiced in billing. Another company means the signed order, before any invoice. The assessment uses your sentence. The view counts records that meet it, and lists the records that do not.
Recognized revenue is the revenue accounts on the general ledger for the period finance names. It is not the sum of Closed Won. It should tie to the same ledger total as the financial reporting pack. Deferred amounts, credits, and timing stay visible in that tie-out.
The view shows the source total, the total under the agreed definition, and the records in between. A Closed Won opportunity with no invoice stays on an exception list when the definition requires an invoice. It is not added to recognized revenue to make the page match the CRM.
Pipeline is checked back to the CRM it came from: the same opportunities, amounts, and stages. It is not checked to the general ledger, because it has not been earned. Recognized revenue is the figure that ties to the ledger. Keeping those checks apart is what shortens the meeting.
See CRM data quality before forecasting for what to inspect in the CRM before a forecast is built on pipeline amounts and stages.
These are examples of products teams already run. They are not badges, and they are not a list you have to match. Bring the CRM and the billing or accounting system you use.
For many teams that is Salesforce, HubSpot, or Dynamics 365 Sales. The pipeline total comes from there: stage, amount, close date, and account. If your CRM is a different product, the work starts from that product.
Invoicing and recognized revenue sometimes live in one system, and sometimes in two. Recognized revenue still has to come from the ledger. Teams often close in QuickBooks Online, Xero, NetSuite, Sage Intacct, or Microsoft Dynamics 365 Business Central. Name the one that holds your revenue accounts.
We connect those systems for this view. Replacing the CRM or the accounting product is a separate decision, and it is not the default.
Synthetic example
The sample uses one written definition so the figures have a job. Pipeline is open CRM opportunities. Bookings are Closed Won and invoiced. Recognized revenue is the revenue accounts on the trial balance. Those three are not supposed to equal each other.
These figures are synthetic. They are a fictional week, not a SnapBiz client, not a quote, and not a real company's pipeline. Every amount below is labeled synthetic.
Open opportunities only. Closed work is not in this line.
Synthetic figure. Unweighted open pipeline $240,000 across 12 fictional opportunities. Weighted with the sample stage weights: $150,000.
Tie-out. Both amounts come from the same fictional CRM extract. Weighting does not add opportunities. It only applies weights already on the stages. This is not a forecast.
The sample definition is Closed Won in the CRM and invoiced in billing. Records that miss either test are listed, not counted.
Synthetic figure. CRM Closed Won sums to $83,000. Of that, $3,000 sits on three opportunities with no invoice. Bookings in the sample meeting: $80,000.
Tie-out. $83,000 minus the $3,000 exception is $80,000. The three opportunities are named on the exception list. They are excluded because this sample requires an invoice. A different definition would change the total. The list of exceptions would remain.
What the books say was earned in the period. This is the figure that should match the financial reporting pack.
Synthetic figure. Revenue accounts for the sample month: $64,000.
Tie-out. That $64,000 is the ledger figure. It should match the month-end pack for the same period. It does not have to equal bookings of $80,000. Both can be right when some invoices are not yet earned. The view should show that timing, not force the two numbers together.
The records that failed the bookings definition. They are the difference. They are not a win rate and not a growth claim.
Synthetic figure. Three Closed Won opportunities, $3,000 combined, with no invoice in billing.
Tie-out. The $3,000 stays on the list. It is not pushed into recognized revenue, and it is not left inside bookings while the definition says invoiced.
Nothing in the sample is a client result. The open pipeline of 12 opportunities and the three closed opportunities without invoices are different records. The $240,000, the $80,000, and the $64,000 answer three different questions on purpose.
The first build is the view the weekly meeting can open, with definitions written down. A typical set includes the following.
Pipeline, bookings, and recognized revenue, each with an owner. The bookings sentence is the one the view enforces.
The weekly view refreshes from those systems. It does not depend on a private export the night before.
Records that fail the definition, including duplicates and missing amounts when you want those in scope. The list is part of the view, not a side file.
The same revenue total the month-end pack uses for the period finance names, with timing differences shown rather than smoothed.
One place sales and finance can look before they argue about a customer.
How to refresh, who can see the view, and what to do with an exception. Managed Data Services is a later option if you want the view kept current.
The assessment is a conversation, not a build. We use it to see which revenue number is stuck, and whether a shared view is the right first project.
Contact us for a Free Assessment. We'll follow up within 2 business days.
If the work is worth doing, the next step is a paid build. Keeping the view current is a separate decision after that.
Contact UsFinancial reporting is the month-end pack that ties to the ledger: profit and loss, balance sheet, cash, aging, and variance. This page is the revenue picture sales and finance share. Recognized revenue should agree with that pack. Pipeline and bookings are not the ledger, and the view should not present them as if they were.
A forecast uses pipeline amounts, stages, and close dates. Duplicate accounts, blank amounts, and stages that are not maintained will change the result even when the math is fine. The assessment asks whether the CRM is fit to forecast. Records that fail the definition stay on an exception list. They are not smoothed into the total.
Usually no. We connect the systems you already run. Replacing a tool comes up only when that tool is the reason the numbers cannot be trusted. That is a separate decision, not the starting point.
Pipeline should tie to the CRM it came from: the same opportunities, amounts, and stages. It should not tie to the general ledger, because it is not revenue that has been earned. Recognized revenue is the figure that ties to the ledger. The view keeps those checks separate.
No. The weekly check is synthetic. The amounts show how definitions and an exception list work. They are not a pipeline we delivered, a growth rate, or a company we work with.
The revenue view has to agree with the close when the question is what was earned, and it depends on the services that connect the systems.
Contact us for a Free Assessment. We'll follow up within 2 business days.
Contact Us