Your Sales Pipeline Is Not a Cash Forecast: How to Connect Them

The sales meeting ends with a promising pipeline number. Finance opens the cash forecast and still cannot see how next month’s commitments will be funded.

Neither team has to be wrong. They may simply be answering different questions. Sales is looking at potential contracts. Finance needs to know which money is expected to arrive, on what dates, and what obligations come before it.

A deal amount is not a bank deposit. Between the two sit a decision, delivery, an invoice and a collection.

What a weighted pipeline can tell you

A common weighted pipeline calculation multiplies each opportunity’s value by its estimated probability of winning, then adds the results. HubSpot explains this approach in its guide to sales forecasting reports.

That can be a useful expected-value planning view. But the number does not tell you whether the amount represents an annual contract, a one-off project, revenue for a particular month or cash expected in the bank.

Before using it in a financial model, make the unit explicit. A$120,000 of annual contract value is not interchangeable with A$120,000 of next-month cash receipts.

Keep four dates separate

The dates that connect an opportunity to cash

Date	Question it answers	What to record
Expected signature	When might the customer commit?	Sales evidence, decision steps and the next action
Delivery or service start	When does the work happen?	Start date, duration and delivery capacity
Invoice or milestone date	When can we bill?	Deposit terms, recurring billing and acceptance requirements
Expected collection	When might the money arrive?	Payment terms and customer-specific evidence

Record the revenue recognition assumptions separately too. An invoice date is not automatically the date on which all contract revenue is earned. Have finance confirm the treatment instead of allowing a CRM field to decide it by accident.

One pipeline, three different collection patterns

Illustrative example, not customer data. Imagine three opportunities under review before November. Their hypothetical probabilities are for demonstrating the calculation, not recommended stage defaults. All figures are A$000, excluding tax and GST.

Illustrative opportunity values and win probabilities

Opportunity	Total value	Win probability	Weighted value
A: 12-month retainer	120	70%	84
B: fixed-fee project	60	60%	36
C: two-month service extension	24	80%	19.2
Total	204	Not applicable	139.2

The raw pipeline is A$204,000 and the probability-weighted contract value is A$139,200. Neither is the November cash forecast.

Now add explicit collection assumptions, conditional on winning each deal:

1. Retainer A: service begins in December, with A$10,000 billed at the start of each service month and collected in the following month. The first receipt is in January.
2. Project B: A$30,000 is collected as a deposit in November. The remaining A$30,000 is invoiced on completion in December and collected in January.
3. Extension C: A$12,000 is billed at the start of November and A$12,000 at the start of December. Each invoice is collected in the following month.

For clarity, this example assumes the planned signatures and service dates occur on time if the deal is won, and that the full contractual amounts are collected on the dates above. It models win uncertainty only. Real forecasts should also test delivery delays and collection risk.

Probability-weighted expected receipts — illustrative A$000

Opportunity	November	December	January
A: retainer	0	0	7
B: project	18	0	18
C: extension	0	9.6	9.6
Total	18	9.6	34.6

Only A$18,000 of probability-weighted receipts appears in November. January’s A$34,600 includes A$7,000 for the retainer, A$18,000 for the project balance and A$9,600 for the extension. The rest of the retainer extends beyond this three-month view.

Do not spend an expected value as though it were committed cash

The November project deposit is not an actual A$18,000 instalment. Under these simplified assumptions, the business receives A$30,000 if it wins and collects, or nothing if it loses. A 60% weight describes a planning calculation, not a customer promise to pay 60% of the invoice.

For near-term commitments, show separate views: invoiced and contracted receipts with collection assumptions; an expected-value pipeline layer; and explicit downside cases. Even a signed contract is not a guarantee that the customer will pay on the planned date.

One useful downside here is losing Project B. November’s pipeline receipts disappear entirely. The question becomes whether existing cash and confirmed collections can still cover the business’s obligations.

Give each receipt one place in the model

When an opportunity becomes a contract, move the assumption to the contracted schedule. When an invoice is issued, link it to the accounting record. When cash is received, replace the expectation with the actual movement.

Do not leave all four versions contributing to the forecast. A single transaction should not appear as weighted pipeline, contracted revenue, an unpaid invoice and a separate expected bank receipt at the same time.

A practical mapping keeps the opportunity, contract, invoice and receipt identifiers connected. The record can change state without multiplying the money.

Make the sales-to-finance handoff specific

In the weekly review, ask the owner of each material deal what changed: value, likelihood, signature date, delivery start, billing milestone or payment expectation. Update only the affected assumptions, and retain the previous version for comparison.

Then ask about capacity and spending. Winning a deal may require contractors, stock or hiring before the customer pays. A collection schedule is only one side of the cash forecast; the costs needed to deliver must be timed as well.

This is where the pipeline connects to a three-way financial model and, for the immediate payment horizon, a 13-week cash forecast.

A better question for the next pipeline meeting

Keep the sales target. Keep the weighted pipeline. Add one more question: “What does this mean for collections and delivery costs over the next few months?”

The objective is not to make sales more conservative or finance more optimistic. It is to make both teams use the same assumptions when they commit the business to something.

Explore MagicHub for our approach to connecting business planning and customer workflows. For the accounting distinction behind this guide, read why profit and cash are different.

General business education only; not accounting, tax, legal or financial advice. All values, probabilities and collection patterns are fictional. They are not benchmarks or customer results.