Cross-Functional FP&A: Driving Synergy Between Finance and Sales Teams

In most businesses the sales forecast and the financial forecast are two different numbers, produced by two different teams, and neither side entirely believes the other. Finance thinks sales is optimistic; sales thinks finance is obstructive. Both are usually right.

Cross-functional FP&A means closing that gap — not through better software, but through a shared set of definitions, a common view of the pipeline, and a working relationship that lets both sides be honest. This covers what that actually involves.

Why the Two Forecasts Diverge

Understanding the causes matters, because they are structural rather than personal, and the usual remedies address the wrong thing.

Different incentives

Sales teams are typically measured on bookings against target. That rewards optimism in the pipeline — a deal kept at 60% probability looks better than one written off. Finance is measured on the accuracy of what it reports to the board and the bank, which rewards conservatism. Neither behaviour is dishonest; both are rational responses to how each function is judged.

Different definitions

What counts as a “qualified” opportunity, when a deal is “closed”, whether revenue is recognised on signature or delivery — these frequently mean different things in the CRM than in the ledger. Much of what looks like disagreement about the forecast is actually disagreement about definitions nobody has written down.

Different time horizons

Sales works to the quarter or the month; finance works to the year and the covenant test. A pipeline that looks healthy against a quarterly target can be inadequate against an annual plan, and neither team sees the other’s horizon by default.

Different data

Sales works from the CRM, finance from the accounting system, and the two rarely reconcile. Where the CRM records a £100k opportunity and the ledger eventually shows £82k of recognised revenue across two periods, both records are correct and neither team can explain the difference without effort.

What Actually Works

Agree definitions before anything else

Write down what each pipeline stage means, what qualifies a deal to enter it, and what has to be true for it to close. Agree how the CRM value relates to recognised revenue — net of discount, excluding VAT, spread over what period. This is unglamorous and it removes most of the friction, because it converts arguments about the number into questions about the assumptions.

Calibrate the weightings against history

Most pipelines carry probability weightings that were set once and never tested. Compare the weighting at each stage against what actually converted over the past several quarters. If deals at 60% convert at 35%, the model is not wrong — it is uncalibrated, and correcting it improves the forecast immediately without anyone changing behaviour.

One forecast, jointly owned

The single most effective structural change is producing one forecast that both functions sign, rather than a sales number that finance then adjusts privately. Where finance applies a haircut nobody discusses, sales learns to inflate to compensate, and the two drift further apart each cycle.

Finance in the pipeline review, not just the results meeting

Attending the weekly or monthly pipeline review — listening rather than challenging — gives finance context that no report provides, and gives sales visibility of why finance asks what it asks. It costs an hour and changes the relationship more than any process document.

Report contribution, not just revenue

Sales teams generally see revenue and rarely see margin. Where a business has meaningful variation in profitability by product, customer or contract type, showing sales the contribution rather than the top line changes which deals get pursued. This is frequently the highest-value thing FP&A can provide, and it requires the underlying analysis to exist in the first place.

Pricing and Discounting: Where It Matters Most

The clearest test of whether finance and sales are genuinely working together is how discounting is handled.

The problem

Discount authority is often delegated by percentage without reference to margin. A 10% discount on a high-margin product and a 10% discount on a low-margin one have entirely different consequences, and a salesperson working to a revenue target has no reason to distinguish them.

What better looks like

Discount thresholds set against contribution rather than headline price, so the authority reflects the actual cost of the concession. Deal-level margin visible to the person negotiating. And an understanding, shared with the sales team, of how much additional volume a given discount requires to stand still — which is usually far more than instinct suggests.

What FP&A Brings, and What It Needs Back

What finance provides

• Contribution and profitability analysis by product, customer, channel and deal.
• Realistic conversion modelling based on actual historical performance rather than assumed rates.
• The consequences of pricing and discount decisions, quantified.
• Capacity and cash implications of the pipeline — whether the business can actually deliver what is being sold, and fund the working capital to do it.

What finance needs in return

• Honest pipeline data, including deals that have gone quiet.
• Early warning of significant deals moving in or out of a period.
• Context on why deals were won or lost, which rarely appears in the CRM.
• Visibility of what has been committed to customers — payment terms, service levels, contractual obligations — that finance will have to fund or deliver.

That last point causes more problems than any other. Terms agreed in a negotiation to close a deal frequently land on finance as a working capital consequence nobody flagged.

Systems: A Note of Realism

Integration between CRM and financial systems helps, and it is not the answer on its own. A business that has not agreed its definitions will simply produce disputed numbers faster and at greater expense.

The sensible sequence is: agree definitions, calibrate the model against history, establish the joint forecast routine, and only then invest in connecting the systems to remove the manual effort. Businesses that buy the integration first commonly find it reflects a process nobody agreed and gets worked around within months.

For most mid-market businesses, a reliable monthly reconciliation between CRM pipeline and reported revenue — even done manually — delivers more than an integration project.

Making It Stick

Put it in the reporting rhythm

Joint forecast review as a standing item, on a fixed date, with both functions present. Collaboration that depends on goodwill decays; collaboration built into the reporting calendar does not.

Give someone the job

Where cross-functional working is everybody’s responsibility it is nobody’s. In larger businesses this is a finance business partner role; in smaller ones it is part of the FD or FP&A lead’s remit. Either way it needs naming.

Measure the forecast, not the forecaster

Track forecast accuracy over time as a shared metric, reviewed jointly. The purpose is calibration, not blame — and if it becomes a stick, the pipeline data will degrade rather than improve.

Recruit for it

The capability that makes this work is not technical. It is the ability to sit in a commercial conversation, understand what is being decided, and make the financial consequences clear without shutting the discussion down. That is a specific profile, and it is worth screening for it explicitly — our guide on finance business partnering covers what to look for.

Frequently Asked Questions

What is cross-functional FP&A?

Financial planning and analysis carried out jointly with the commercial functions — principally sales — rather than in isolation. In practice it means shared definitions, a single jointly-owned forecast, and finance contributing to commercial decisions before they are made rather than reporting on them afterwards.

Why do sales and finance forecasts disagree?

Usually for structural reasons: different incentives (bookings against target versus reporting accuracy), different definitions of what counts as qualified or closed, different time horizons, and different underlying data in the CRM and the ledger. It is rarely a matter of one side being wrong.

How do you improve forecast accuracy?

Start by comparing a past forecast line by line to what was actually recognised, to establish where the variance comes from. Then agree definitions, calibrate stage weightings against real historical conversion, and produce one forecast that both functions own. Systems integration helps later, not first.

Who should own the joint forecast?

Both functions jointly, with one named individual responsible for producing it — typically a finance business partner or the FP&A lead. What does not work is finance privately adjusting a sales number, because sales inflates to compensate and the gap widens each cycle.

Do we need integrated systems to do this?

No. Systems reduce manual effort but do not create agreement. Most mid-market businesses get further with a disciplined monthly reconciliation between pipeline and recognised revenue than with an integration project built on definitions nobody has settled.

What size of business does this apply to?

Any business where sales and finance are separate functions — which is most beyond a handful of people. The mechanics scale down: a business with one FD and three salespeople still benefits from agreed definitions and a single forecast, it just does not need a formal business partnering structure to achieve it.

Adrian Lawrence FCA

Founder & Managing Director, FD Capital

Adrian Lawrence FCA is the founder of FD Capital and a Fellow of the Institute of Chartered Accountants in England and Wales (ICAEW). He holds a BSc from Queen Mary College, University of London, and has over 25 years of experience as a Chartered Accountant and finance leader working with private, PE-backed and owner-managed businesses across the UK. He founded FD Capital in 2018 to connect growing businesses with the Finance Directors and CFOs they need to scale — and personally interviews candidates for senior finance appointments.

→ View Adrian’s ICAEW profile