Two people open Salesforce during the same meeting. One says there are 24 opportunities to follow up. The other says 31. Ten minutes later, everyone is debating the reports rather than deciding what to do about the opportunities.
Different totals do not automatically mean Salesforce is calculating incorrectly. The reports may be answering different questions, including different records or showing information to people with different access.
The useful first step is to compare what each report means. Leave the dashboard redesign until you know why the numbers disagree.
Write the question before checking the chart
“We need a pipeline report” leaves plenty of room for interpretation. Does that mean all open opportunities, those expected to close this month, or only opportunities above a particular stage?
Write a specific question in ordinary language. For example: “What is the value of open opportunities owned by our sales team and expected to close this calendar month?”
That sentence gives you a reference point. You can now check whether both reports are intended to answer it.
Compare the filters and dates
Look at the selected date field as well as the period. A report filtered by Created Date is asking something different from one filtered by Close Date.
Also compare ownership filters, stages, record types and any conditions excluding records. “My opportunities” and “all opportunities” are not interchangeable.
Salesforce’s report filter reference explains the different filter types. Ask your administrator to help interpret anything unclear rather than changing a shared report during the meeting.
Check what is being counted
A count of report rows may not be the count of distinct customers or opportunities you have in mind. The report type and related records included can affect what each row represents.
Likewise, a total amount, an average and a record count answer different questions, even when the charts look similar.
Pick a handful of records that appear in one report but not the other. Trace why each is included or excluded. A concrete example is usually easier to investigate than a disputed headline number.
Consider who is looking at the report
Users can have different access to records. A dashboard may also run in a different viewing context from a report someone opens directly.
Ask an administrator to check the intended access and dashboard configuration. Do not solve a reporting disagreement by giving everyone wider access to customer information.
The aim is to make the reporting appropriate for its audience and explain any legitimate differences.
Look at the underlying information
Once the definitions and configuration agree, check whether the relevant records are complete and current. Missing owners, outdated stages or inconsistent dates can all undermine the answer you need.
Agree who should update that information and when. A report can reveal gaps, but it cannot establish the business process for keeping records useful.
Keep a short note of the report’s purpose, included records and owner. Give it a descriptive name so colleagues know when to use it.
End with a decision people can make
The purpose of reporting is to support action. Once a report is understood, ask what someone should do when they see it: follow up an enquiry, review a stalled opportunity or investigate missing information.
If your reports are causing more debate than clarity, Estuary Connect’s Salesforce consultancy can help review the questions, data and setup behind them. Tell us which numbers aren’t adding up.