Why pipeline is not revenue

Pipeline is not revenue because a deal in the CRM still has to pass through five steps before any money arrives: winning, contracting, delivery, invoicing and payment. At every step part of it can disappear or slip into a later period, through lost deals, discounts after signing, delayed delivery, forgotten invoices or slow payers. A forecast that stops at the pipeline therefore measures what sales expects, not what reaches the bank.

The five steps between pipeline and cash

Follow the path a euro in your pipeline takes.

1. Open deal to won. Part of the pipeline is lost, part slips to a later period. This is the part most forecast conversations are about.
2. Won to contract or order. The amount in the CRM is what the salesperson entered. The contract or order may differ: a smaller scope, an extra discount in the final negotiation, a phased start.
3. Contract to delivery. A EUR 200,000 contract for an eight-month project may deliver EUR 50,000 this quarter. With subscriptions, invoicing sometimes only starts at go-live or first use.
4. Delivery to invoice. Delivered work has to be invoiced. This is where revenue disappears for good: additional work that is not charged, an extra licence that was never added to billing, a price indexation that was forgotten.
5. Invoice to payment. An invoice is a receivable, not cash. Payment terms, disputes and credit notes decide what arrives and when.

In the CRM you usually see only step 1. The rest sits in the ERP, the project administration and the accounts. That is why CRM and ERP give different answers to the question of what your revenue is.

Where it goes wrong, step by step

Won is not the same as signed

In many businesses a deal is marked as won when the customer agrees verbally. Procurement, legal review and sometimes a renegotiation follow. Some of those won deals shrink, slip or fall through after all. If nobody updates the CRM afterwards, the original amount stays in your reports as won revenue.

The contract differs from the deal

The salesperson enters EUR 80,000. The contract comes in at EUR 72,000, because another ten percent came off for a multi-year commitment. Or the contract includes an introductory period at a lower rate. Or part of the scope is included as an option the customer can call off later. The CRM often knows nothing about it. How to trace that difference is covered in how do you check contract value against realised revenue.

Delivery determines timing

With projects, implementations and bespoke work, revenue is earned as the work progresses. A large deal won in March may produce revenue from April to December. Forecasting the full deal value in the quarter it was won overstates that quarter and understates the following ones.

Not everything is invoiced

This is the step where revenue genuinely leaks rather than merely slipping. A won deal for which no order was ever created in the ERP. An expansion the account manager promised that was never added to billing. Additional work on a project that is in the timesheets but not on the invoice. It is the classic gap between sales and invoicing, explained in detail in revenue leakage between CRM and billing.

Invoiced is not paid

For the profit and loss account the invoice counts. For the cash position the payment counts. A customer who pays in 60 days when the agreement was 30 moves your cash back by a month. An invoice the customer disputes is sometimes partly credited.

Worked example: from pipeline to bank

Worked example: suppose your weighted pipeline for the quarter is EUR 1,000,000. This is how it might look at the end of the quarter:

Of the EUR 1,000,000 mentioned in the forecast meeting, EUR 400,000 is in the bank at the end of the quarter. Most of the difference is timing and will still arrive later. The EUR 40,000 discount and the EUR 20,000 of uninvoiced additional work will never come back. The amounts are an example; the proportions vary widely by business and sector.

What this means for your forecast

A forecast is only useful when it is clear which step it predicts. Four different figures are often used interchangeably:

• Bookings: what is won or signed in the period. Relevant for sales.
• Revenue: what is delivered in the period and therefore appears in the profit and loss account. Relevant for the board and the auditor.
• Billings: what is invoiced in the period. Relevant for credit control.
• Cash: what comes in during the period. Relevant for the bank and cash planning.

A sales forecast of EUR 1,000,000 and a revenue forecast of EUR 600,000 can both be correct. The problem arises when the board hears the first figure and expects the second. The complete guide to revenue forecasting explains how to bring those layers together in one forecast.

The same applies to pipeline metrics such as coverage: they are useful for the question of whether sales has enough in the funnel, not for how much revenue will arrive. See pipeline coverage explained.

How to measure the steps

You can measure the conversion between the steps, so that your forecast takes it into account.

1. Won to contract. Put last year's won deals next to the matching contracts or orders. Calculate the average difference in amount.
2. Contract to delivery. Determine for each type of deal (project, subscription, one-off delivery) how revenue is earned over time.
3. Delivery to invoice. Compare delivered hours, materials and licences with what was invoiced. Every difference is a question.
4. Invoice to payment. Calculate the actual average payment period for each customer group.
5. Won without an invoice. Look for won deals more than two months old with no linked invoice at all. This is often the fastest way to find real leakage.

With those five ratios you can convert a pipeline forecast into a revenue and a cash forecast. It is not an exact science, but it is far more honest than assuming pipeline equals revenue.

Checklist

• Is it clear in the forecast meeting whether the discussion is about bookings, revenue, billings or cash?
• Is the deal amount updated to the contract amount after signing?
• Do you know for each type of deal how revenue is spread over the months?
• Is there a monthly check that every won deal has an order and an invoice?
• Is additional work routinely compared with what was invoiced?
• Does your cash planning use the actual payment period, or the agreed one?

Frequently asked questions

Is weighted pipeline a bad forecast, then?

It is a forecast of bookings, not of revenue. For sales that is useful. For the board it needs converting into revenue and cash, using the conversion between the steps.

Where does most revenue disappear?

It differs per business. Most of the difference between pipeline and bank is usually timing. The part that genuinely disappears often sits between delivery and invoice: work that was done but not charged.

How quickly do you spot a deal that is never invoiced?

Without a link between CRM and billing, often only at year-end, or never. With a monthly comparison, within a few weeks.

Should sales be responsible for invoicing?

Not for the invoicing itself, but for a correct handover: the right amount, the right start date and the agreements that need to appear on the invoice. The gap usually arises precisely at that handover.