Guide · Management visibility
How an MD gets one view of pipeline, orders and invoiced revenue
Why the CRM forecast and the ERP figures disagree, which system should own which number, and what a one-page view contains.
A managing director gets one reliable view of the business by taking each figure from the system that owns it: pipeline from the CRM, orders and invoiced revenue from the ERP, and recurring business from the customer's actual buying history. Put side by side, with agreed definitions and each sale counted once, those figures show where the business is heading and where it already stands. Most forecasting arguments come from mixing them, not from any one of them being wrong.
This guide is for managing directors and finance directors of UK manufacturers and distributors whose sales team works in HubSpot or Pipedrive while orders and invoices live in an ERP such as Sage 200, Sage 50 or Xero. It explains why the two disagree, which system should supply which figure, how to avoid counting the same sale twice, and what a useful one-page view contains.
Why do the CRM forecast and the ERP figures differ?
Because they measure different things at different moments, and often for different parts of the business.
- The CRM records intent. A deal in HubSpot or Pipedrive is an opportunity with an estimated value, a probability and an expected close date, all entered by a salesperson.
- The ERP records commitments and facts. An order is a customer commitment; an invoice is revenue. Both carry exact values and dates.
- Repeat business often bypasses the CRM. For many manufacturers and distributors, most revenue comes from customers reordering, and those orders never appear as deals. A pipeline-only forecast leaves out the largest part of the business.
- Values change between stages. The deal says one figure, the order another after negotiation, and the invoice another after part shipments, credits or price changes.
- Timing differs. A deal closes in March, the order is placed in April and invoiced in June. Each system is right about its own date.
None of these is a fault in either system. The problem starts when a single number is asked to mean all of them.
What is the difference between pipeline, orders, invoiced revenue and recurring business?
| Measure | What it is | System that should own it | How certain |
|---|---|---|---|
| Pipeline | Open opportunities, weighted or unweighted, with expected close dates | CRM | Estimate |
| Orders (order intake) | Orders received in the period, whether or not yet delivered | ERP | Committed |
| Order book | Orders received but not yet invoiced | ERP | Committed, timing uncertain |
| Invoiced revenue | Sales invoiced in the period | ERP or accounts | Fact |
| Recurring business | Expected revenue from customers' regular buying, based on their history | ERP history, shown in the CRM | Estimate based on behaviour |
Recurring business is the measure most businesses lack. It answers a simple question: if existing customers keep buying as they usually do, what will they spend? Without it, a forecast either ignores repeat revenue or relies on someone's estimate of it.
Which system should supply which figure?
The principle is that each figure comes from the system where it is created, and is only shown elsewhere.
- New business pipeline comes from the CRM, because that is where the sales team records it.
- Orders, order book and invoiced revenue come from the ERP, because that is where they are created and checked.
- Recurring business is worked out from ERP order history and can be shown in the CRM on each account, so the account manager and the forecast see the same number.
- Targets and budgets come from whoever sets them, usually finance, and should be agreed per measure, not as one total.
When the ERP is connected to the CRM, orders and invoices can appear on the account and the deal can be marked won when the order arrives, with the real value. The ERP stays the system of record; the CRM shows what sales and management need from it.
How do you avoid double-counting?
The same sale can easily appear twice: once as a deal in the pipeline and again as an order in the ERP. A few rules prevent it:
- Close the deal when the order arrives. Once the order exists in the ERP, the deal should be marked won and leave the open pipeline. Linking the two, rather than relying on someone remembering, is one of the first things a connection between the systems is used for.
- Keep repeat orders out of the pipeline. Regular reorders belong in recurring business, not as deals. Raising a deal for every repeat order inflates the pipeline and the workload.
- Report each measure separately before adding anything up. Pipeline, order book and recurring business can be combined into a forward view, but only after each is checked on its own, and never with the same order in two of them.
- Agree definitions once. What counts as an order, when a deal is won, whether values include delivery or VAT: decide once, write it down and apply it in both systems.
- Reconcile monthly. Invoiced revenue in the management view should match the accounts. When it does not, find out why before anyone uses the forward figures.
What should a useful management dashboard contain?
One page, read in a few minutes, with each figure labelled with its source. Most of the value comes from seeing the measures side by side, against last year and against target.
The table below is an illustration built from hypothetical figures for a fictional business. It shows the shape of the view, not a real result.
| Measure (illustrative) | Source | This month | Same month last year | Year to date | Target to date |
|---|---|---|---|---|---|
| New business pipeline, weighted | CRM | £410,000 | £365,000 | n/a | n/a |
| Deals won | CRM, confirmed by ERP order | £96,000 | £88,000 | £640,000 | £700,000 |
| Order intake | ERP | £1,120,000 | £1,060,000 | £9,900,000 | £10,200,000 |
| Order book at month end | ERP | £2,350,000 | £2,180,000 | n/a | n/a |
| Invoiced revenue | ERP or accounts | £1,080,000 | £1,040,000 | £9,600,000 | £9,800,000 |
| Expected recurring business, next three months | ERP order history | £2,900,000 | £2,950,000 | n/a | n/a |
| Accounts ordering within their usual cycle | ERP order history | 84% | 88% | n/a | n/a |
Alongside the figures, a useful view carries a short list of exceptions: the largest accounts buying less than last year, quotes over a set value with no reply, and orders at risk of missing their delivery date. The figures say where the business stands; the exceptions say what to do about it.
How do you establish reliable reporting?
- Agree the measures and their definitions with sales, operations and finance in the same room, before anything is built.
- Check the data underneath. Duplicate customers, inconsistent product codes, stale deals and close dates nobody has touched all distort the figures. Fix the records, not just the report.
- Connect the systems so each figure flows from its owner. Orders and invoices from the ERP, pipeline from the CRM, on a schedule or as they change, using whichever integration tool suits the job.
- Build the one-page view, then stop. Resist adding dashboards. A small number that are trusted is worth more than many that are argued over.
- Reconcile every month against the accounts, and review the definitions when the business changes.
Most of the effort is in steps one and two. The dashboard itself is usually the quickest part.
What are the limitations?
- A forecast stays a forecast. Better inputs narrow the range; they do not remove judgement.
- Recurring business assumes customers behave as they have before. It is less reliable for project-based work, new customers and volatile markets.
- Some figures belong in the accounts. Margin, cash and profitability depend on costs and adjustments that may not be in the ERP data you connect; this view does not replace the management accounts.
- Data quality limits everything. If deals are not closed when orders arrive, or customers are duplicated, the view will be wrong in ways that look precise.
What has Flowbird done in this area?
Flowbird connects HubSpot and Pipedrive to the systems that hold orders and invoices, and has done so with Sage 200, Sage 50, Xero, the Linnworks order system and the Tharstern print MIS. For Countrystyle Recycling, Flowbird reworked HubSpot, built a tailored quoting process and automated the hand-offs into service delivery; the business went on to absorb growth it reported at £4.2m with on-time service delivery held at 99.7%, as described in the Countrystyle case study. Our CRM reporting page covers the reporting and forecasting work in more detail, and manufacturing and engineering shows how orders and quotes reach the account for a manufacturer.
Where to start
The CRM & ERP Opportunity Audit is a fixed-price, two-week review of what your CRM data can and cannot tell sales and management today. It checks the data and the reporting it can carry, maps one revenue-critical process end to end, such as quote to order, and ends in a written report and a plain go or no-go. It does not need access to your ERP and does not analyse ERP data; where the mapped process passes into the ERP, the people who run it walk us through it.
For further reading, see why leadership stops trusting the dashboard and our longer article on sales forecasting in a CRM.