This argument happens in boardrooms and budget meetings more than most companies would like to admit. Sales presents their quarterly figures and they look healthy. Finance presents theirs and the numbers are lower, sometimes materially so. Both teams are confident in their data. Both have exports and spreadsheets to back them up. The meeting stalls while people figure out which version of reality is correct, and sometimes it never really gets resolved, just deferred until next quarter when the same argument happens again.
There's a version of this problem that is purely political, where one team is being selective about what they count. But usually it's more structural than that. Sales and finance are measuring genuinely different things, and the mismatch is baked into how each department was set up to operate.
The timing gap
Sales records a win when the contract is signed or the deal is closed. From a sales perspective, that's the moment of success. The revenue is earned. The quota is hit. The commission is on its way.
Finance recognises revenue according to accounting rules, which in most businesses means when the service is delivered or when the invoice is paid, not when the deal is signed. For a project that starts in Q2 but was contracted in Q1, sales might count it in Q1 and finance won't touch it until Q2 or Q3.
This timing difference alone can create a significant gap. In businesses with long delivery cycles or multi-year contracts, the gap between booked revenue and recognised revenue can span years. Neither number is wrong. They're just measuring different stages of the same commercial event, and if your management meetings don't make that distinction explicit, the confusion is essentially built in.
The definition gap
Beyond timing, there's often a genuine disagreement about what counts. Sales tends to report total contract value, or bookings, or pipeline at various stages of probability. Finance tends to report invoiced revenue, net of discounts and adjustments, under the recognition methodology required by your accounting standards.
When someone asks "how much did we sell last quarter," sales answers with one number and finance answers with a different one, because they're answering a slightly different version of the question. The word "sold" does a lot of work and each department has a reasonable interpretation of what it means.
This is fundamentally a definitional problem before it's a data problem. The technical fix, connecting systems and unifying reporting, will not resolve a disagreement about definitions. That requires a business decision about which metric is the one the company uses for what purpose, and that decision needs to be made by leadership, documented, and communicated to both teams.
The data quality dimension
Separate from definitions and timing, there's often a third layer: actual errors in one or both systems. A deal in the CRM with the wrong value because the contract was amended and nobody updated the record. An invoice in finance for a different amount because a discount was applied at billing that wasn't reflected in the original deal record. A customer who exists under two different names in two systems, causing their revenue to be counted differently.
These errors don't explain the whole gap, but they add noise that makes the legitimate definitional differences harder to see. And they create justified scepticism: once people have been burned by errors in the data, they stop trusting any of it, including the parts that are accurate.
What resolution looks like
The companies that solve this tend to do three things. They agree on a shared glossary: bookings means X, recognised revenue means Y, and the difference between them is reported explicitly rather than hidden. They build a single reporting layer that draws from both systems and presents both metrics alongside each other, clearly labelled, so that leadership isn't choosing between competing reports but looking at a coherent picture. And they fix the underlying data quality issues that generate errors and erode trust in both systems.
None of this requires replacing your CRM or your finance system. It requires connecting them, documenting the definitions, and producing a single view that makes the relationship between the two numbers transparent rather than opaque.
If your leadership team is spending meeting time arbitrating between sales and finance numbers instead of acting on them, Lucendata can help build the unified reporting layer that ends that conversation. Have a look at lucendata.co.