Finance Says 12,000. Marketing Says 10,000. Who’s Right?

Finance says the institution serves 12,000 people. Marketing says there are 10,000. Operations has another number entirely.

So… who is right?

This is one of those questions that sounds simple until you start digging into it. And if you have ever been part of a reporting conversation like this, you know how quickly a simple number can turn into a much bigger discussion.

As a former data analyst, I have had this conversation. As a current Client Support Manager, I often see others start to have this conversation. A client will ask why one report shows one number and another dashboard shows something different. At first, it feels like something must be wrong. But many times, the issue is not that the data is bad.

It’s just that each department is answering a slightly different question. Finance may be reporting on active relationships for board or financial reporting. Marketing may be counting people who are eligible for outreach. Operations may be looking at accounts, households, relationships, or activity tied to a specific process.

No one is necessarily wrong. They are just using different definitions. That is where a single source of truth becomes so important.

The Problem Is Usually Not the Number. It Is the Definition.

When two departments report different customer or member counts, the first reaction is usually, “Which number is correct?”

But the better question is often, “What does each number actually mean?”

The difference can also come down to timing. One report may have been pulled at month-end. Another may be using daily data. Another may be based on a campaign list that was cleaned, filtered, or segmented before use.

Small differences in criteria can create big differences in reporting.

That is why a “customer count” or “member count” is not always as straightforward as it sounds. It might mean:

• Active relationships
• Total customers or members
• Primary account holders
• Joint account holders
• Households
• Accounts
• People with active loans
• People eligible for marketing
• People with valid contact information
• Relationships included in a specific reporting period

Each of those numbers can be useful. The problem starts when everyone assumes they are talking about the same thing.

Why This Matters Beyond Reporting

At first, conflicting numbers may feel like a reporting inconvenience. Someone notices the mismatch, a few emails go back and forth, and the team spends time trying to reconcile the difference.

But over time, inconsistent definitions can create bigger issues.

Marketing may build a campaign using one audience size, while Finance uses another number for performance reporting. Executives may receive reports that do not align. Operations may question whether a dashboard is accurate because it does not match the number they are used to seeing.

Eventually, people start creating their own workarounds.

One person keeps a spreadsheet. Another saves a version of a report from last quarter. Someone else asks the same analyst to pull the “real number” every month.

And before long, the institution is not just managing data. It is managing multiple versions of the truth.

That can slow down decision-making, weaken confidence in reporting, and make it harder for teams to act quickly.

If people do not trust the numbers, they are less likely to use the dashboards. If they do not use the dashboards, they go back to manual reports. And if they go back to manual reports, the organization loses the value of the tools it invested in.

A Single Source of Truth Does Not Mean One Number for Everything

One common misconception is that a single source of truth means there should only be one number.

But that is not always realistic or helpful.

Finance, Marketing, Operations, Lending, and Leadership may all need different views of customer and member data. The goal is not to force every department to use the exact same number for every situation. The goal is to make sure everyone understands what each number represents, where it comes from, and when it should be used.

A single source of truth helps create shared definitions, trusted data sources, and clear reporting logic. That way, when Finance says 12,000 and Marketing says 10,000, the conversation can move from:

“Who is wrong?” to: “Which definition are we using for this decision?”

That shift matters. It reduces confusion and helps teams choose the right number for the right purpose.

A Real-World Example: The Campaign List vs. the Official Customer or Member Count

Here is a common example.

Marketing is preparing a checking account campaign. They pull a list of 10,000 people who have a valid email address, are not already using the product, and meet the campaign criteria. From their perspective, that is the audience they can reach.

At the same time, Finance is preparing a board report and lists the institution’s total active relationships as 12,000. Their number may exclude certain account types, inactive relationships, or people who do not meet the institution’s official reporting definition.

Both numbers may be accurate. But they are not measuring the same thing.

Marketing is asking, “How many people can we reach with this campaign?” Finance is asking, “How many active relationships do we officially serve?”

Those are two different questions. Without clear definitions, it can look like a data problem. With clear definitions, it becomes much easier to understand the difference.

Another Example: Accounts vs. Individuals vs. Households

Another place this comes up often is the difference between accounts, individual relationships, and households.

One customer or member may have multiple accounts. A household may include multiple people. A joint account may appear differently depending on how the data is pulled. If one report is counting accounts and another is counting individuals, the numbers will not match. If another report is grouping by household, that number may be different again.

Again, that does not mean the data is wrong. It means the organization needs to be clear about the question being asked.

Are we measuring individual relationships? Product usage? Household penetration? Account volume? Campaign eligibility? Portfolio growth?

Each of those questions may require a different lens. A single source of truth helps make sure those lenses are clearly defined, consistently applied, and easier to explain.

What a Single Source of Truth Actually Solves

A single source of truth does not magically eliminate every data question. There will always be times when teams need to look at information in different ways.

What it does provide is a cleaner, more reliable foundation to work from.

It helps financial institutions:

• Define key terms consistently across departments
• Understand where each number comes from
• Reduce duplicate or conflicting reports
• Build trust in dashboards and analytics
• Save time spent reconciling numbers manually
• Support better conversations between teams
• Make decisions using shared context

Most importantly, it helps people stop debating the data and start using it.

When definitions are clear, teams can spend less time asking, “Why does my report look different?” and more time asking, “What should we do next?”

That is when reporting becomes more than a monthly task. It becomes a tool for better decision-making.

This Is Where Data Governance Becomes Practical

Data governance can sound like a big, formal concept. But in day-to-day reporting conversations, it is really about clarity.

It is knowing what an “active customer” or “active member” means. It is knowing which system is the source for a specific field. It is knowing who owns certain definitions.

It is knowing that when a dashboard shows a number, the team understands how that number was created. That clarity does not have to happen all at once. A good starting point is to identify the terms your teams use most often and where confusion tends to happen.

Customer or member count is a great example. So are households, accounts, products, balances, relationships, closed records, inactive records, and campaign eligibility. Once those definitions are documented and aligned, reporting becomes easier to trust.

And when reporting is easier to trust, teams are more likely to use it.

Technology Helps, But Alignment Comes First

Analytics platforms are powerful, but they are only as useful as the definitions behind them.

If every department brings different assumptions into the system, the dashboards may still create confusion. The platform may display the data correctly, but users may interpret it differently. That is why the work behind the scenes matters.

A strong analytics foundation combines the right technology with the right data structure, definitions, and processes. It gives teams a shared place to access information, but it also gives them the context to understand what they are seeing.

For Lodestar clients, that foundation often starts with bringing core and third-party data into a structured warehouse, applying business logic, and making that information available through reporting, dashboards, and analytics. When data is centralized and organized in a way teams can understand, it becomes easier to build trust in the numbers and use them consistently.

This is especially important as financial institutions move toward more advanced analytics, predictive insights, and AI-ready decision-making. If teams do not trust the basic numbers, they are not going to trust the more advanced ones.

Clean, consistent definitions are not just a reporting detail. They are part of building confidence in the institution’s data strategy.

How to Start Building Better Data Alignment

For many institutions, the path to better alignment does not start with a massive overhaul. It starts with a few focused conversations.

Ask questions like:

• What are the most common numbers our teams report on?
• Which numbers create the most confusion?
• Are departments using the same definitions?
• Which system should be considered the source for each data point?
• Who owns the definition of key terms?
• Where are manual workarounds still happening?
• Do our dashboards clearly explain what each metric means?

These questions can reveal where teams are aligned and where clarification is needed.

From there, institutions can begin building a stronger reporting foundation. That may include a data dictionary, standardized dashboard definitions, clearer report documentation, or a governance process for reviewing and updating key terms.

The goal is not perfection. The goal is progress.

Every shared definition makes reporting easier. Every clarified metric reduces confusion. Every trusted dashboard helps the organization move closer to using data with confidence.

The Bottom Line

So, if Finance says 12,000 and Marketing says 10,000, who is right?

Maybe both of them. The real issue may not be the number itself. It may be that the organization has not clearly defined which number should be used, when, and why.

A single source of truth helps financial institutions create that clarity. It gives teams shared definitions, trusted reporting, and a better way to work from the same data foundation. Because when everyone understands what the numbers mean, the conversation gets a lot more productive.

And once teams can trust the data, they can spend less time reconciling reports and more time using insights to better serve customers and members, improve operations, and make smarter decisions.

Need help creating a clearer source of truth for your institution’s data? Lodestar helps banks and credit unions centralize core and third-party data, strengthen reporting, and build analytics foundations teams can trust.