Pipeline theatre vs posted fact
CRM optimises for motion — stages, forecasts, next steps, confidence scores. Finance optimises for posted fact — invoices, credit notes, closed periods, audit trail. When leadership asks "what is actually coming in", the fight that follows is structural, not personal. Sales is not lying. Finance is not being difficult. The systems were built for different jobs.
If CRM and finance disagree every month-end, you need an owned reconciliation path — not another column in the spreadsheet, not a stand-up where everyone shares their version. Reconciliation is a product, not a Friday panic.
Design reconciliation as a product
Start with the trigger. Deal won — what record is created in finance, by whom, and by when? If the answer is "someone will do it", you already have a leak. Automate the trigger only after the manual path works twice, following the principle in when to automate.
Think carefully about which fields are promotional versus contractual. Promotional fields — forecast value, rough amount, confidence percentage — are motion indicators. Contractual fields — signed amount, billing schedule — are facts. Colour-code them in training so new hires do not post pipeline to the board deck.
Name an exception path for partial billing, change orders, and write-offs. Exceptions will happen; hiding them in email creates technical debt in day-to-day ops. And build one variance view that finance and sales both sign weekly — not monthly archaeology. That view should connect to one report the room trusts so leadership stops asking for a third export.
Month-end without blame
Run variance review as a process fix, not a performance review. Ask: what rule would have prevented this mismatch? Document the rule. Assign an owner to enforce it in the tools — not in someone's memory.
Without this discipline, you pay in re-keying and shadow spreadsheets: two people maintaining the same customer truth because neither system is allowed to win. When the handoff is the only broken slice, integrate before you replace often solves it.
Signs you need this now
Watch for these: the board deck uses CRM totals while finance uses something else, and nobody will say which is official. Commissions calculated on stage rather than on cash collected. Customer references that differ between systems, with customer service picking whichever answer is faster to find.
Commission and KPI alignment
If sales is paid on CRM stage and finance recognises cash, you have built an incentive to inflate the pipeline. Align comp and dashboards to posted fact, or document the lag explicitly — commission on invoice, not on verbal win. The same applies to ops KPIs tied to "complete" when finance needs "invoiced."
Weekly variance review should include sales leadership, not only finance — otherwise reconciliation becomes policing. The goal is a handoff product everyone maintains, not a monthly ambush.
Thin fixes that often work
Sometimes one required field at "won", one integration to create the finance record, and one report ends eighty percent of the pain. That is the integrate before you replace argument applied here. Do not buy a new CRM because the old one lacks discipline you never enforced.
Month-end should be boring — variances explained, rules updated, not a blame session. That boredom is how you know reconciliation became a product rather than a fire drill.
Book a systems review. Build or integrate when the handoff is the product. Teesside and the North East, or remotely when the fit is right.