Why do my reports not match?
Short answer
Reports that disagree usually come from different date ranges, different filters, or one report counting a stage the other excludes. Compare the exact filters and date windows side by side before assuming the underlying numbers themselves are wrong.
Before you start
- The two specific reports or dashboards that disagree.
- The exact numbers each one is showing.
- Access to the filters and date range settings for both.
- Knowledge of which pipeline stages or statuses should count as a conversion.
Step by step
- 1
Write down the exact numbers and the discrepancy
Note both figures and the specific difference rather than a general sense that something is off.
A precise gap is much easier to trace than a vague feeling that the reports disagree.
- 2
Compare the date ranges side by side
Confirm both reports are pulling from the identical start and end dates.
A one-day difference in range is one of the most common causes of mismatched totals.
- 3
Compare the filters applied to each report
Check whether one report filters by team member, source, or tag while the other does not.
Two reports on the same metric can still disagree if their underlying filters are not identical.
- 4
Check what each report counts as a conversion or stage
Confirm both reports define a won deal or completed job using the same pipeline stage.
One report counting an earlier stage than the other explains a gap without any data being wrong.
- 5
Look for timezone differences between reports
Confirm both reports use the same timezone for calculating a day's boundaries.
A timezone mismatch can shift records into a different day between two otherwise identical reports.
- 6
Check for duplicate or merged records affecting one report
See if a recent merge changed a count in one report but has not yet reflected in the other.
Reports that refresh on different schedules can briefly disagree after a data change.
- 7
Rebuild one report to mirror the other exactly
Match filters, date range, and stage definitions on both reports and compare again.
Matching every setting exactly either resolves the mismatch or narrows it to a real data issue.
What good looks like
- The actual cause of the mismatch is identified instead of assumed to be a bug.
- Reports get rebuilt to use consistent filters and definitions going forward.
- The team trusts the numbers because the discrepancy was explained, not ignored.
- Future reports are set up to avoid the same avoidable mismatch.
Common mistakes
The ways this goes wrong in support, and what to do instead.
Assuming the data itself is wrong›
Time gets spent questioning the platform when two reports simply used different filters.
Do this instead: Compare filters and date ranges side by side before questioning the underlying data.
Not checking pipeline stage definitions›
One report counts a deal as won a stage earlier than the other, producing a permanent gap.
Do this instead: Confirm both reports use the identical stage or status to define a conversion.
Comparing reports on different refresh schedules›
A recently merged or updated record shows in one report but not yet in the other.
Do this instead: Refresh both reports and allow time for updates to sync before comparing numbers again.
Frequently asked
6 questions about fix reports that do not matchRelated guides
Pick the next thing to set up, or back up a step if something here assumed work you have not done yet.
Do this next
The natural follow-on tasks once this one is working.
More in Support
Nearby tasks that share the same setup and vocabulary.
Was this guide helpful?
Tell us what worked and what didn't. It shapes what we rewrite next.
You didn't get into business to be in the tech business.
Managed Tech clients hand this to us. We build it, test it, maintain it, and add to it as the business changes, so nobody on your team has to become the person who knows how the system works.