How treasury sales teams shift from reactive discovery to data-driven advisory.
Relationship banking has always been built on trust and a deep understanding of client needs. Treasury sales is no different. At its core, the role is about showing up with insight, adding value in every interaction, and growing relationships in a way that works for both the client and the bank.
What has changed is the environment treasury teams now operate in.
Cash moves quicker than it used to, clients spread balances across more accounts, and data is everywhere, but rarely where bankers need it. At the same time, expectations are rising: from clients, from internal stakeholders, and from the market.
Treasury is being pushed to deliver more insight and more commercial results. But it’s happening in an environment where visibility into a client’s day-to-day financial reality is patchy at best.
The visibility gap
Business clients are generating more financial data than ever before. Their ERP systems capture supplier relationships, payment timing, receivables trends, working capital cycles, and cash flow patterns in real time. That’s exactly the kind of detail treasury teams need to give better advice and build sharper proposals. But banks rarely see it directly.
Instead, treasury still relies on fragmented inputs: point-in-time exports, inconsistent spreadsheets, and client conversations. The result is a sales process that often starts with incomplete information and progresses slowly, even when urgency is high.
By the time a proposal is built, the client’s situation may have already shifted and the competitive landscape may already be set.
The environment changed faster than the sales model
If you work in treasury sales, none of this feels theoretical. The market really has become tougher, and you can hear it in earnings calls and investor updates. Deposit competition is back in focus, margins are tighter, and banks are pushing harder to grow fee based revenue through treasury services, payments, and FX.
At the same time, clients are behaving differently. More businesses are actively managing yield, spreading balances across institutions, and adopting specialist providers for payments and working capital. Even when a bank remains the “primary” relationship, activity is increasingly distributed.
This is part of a much bigger shift in commercial banking. We dug into it in our Commercial Banking Predictions for 2026, and honestly, it’s hard to see things slowing down.
But what makes this shift particularly hard to manage in treasury is that attrition rarely looks like churn. It’s quieter than that. Payment flows move bit by bit. A new provider gets trialled. Receivables start landing somewhere else. And by the time anyone notices, the relationship has already lost ground.
In this environment, treasury teams are forced into reactive conversations, not because they’re doing anything wrong, but because the sales process still depends on discovery to create basic context.
As with any sales function, the usual advice is to “ask better discovery questions”. But that misses the point.
Treasury teams already know how to do discovery well. The problem is that it’s now the bottleneck. If treasury sales wants to be more advisory, it has to be more data-driven. And that starts not with better questions for clients, but with tougher questions about the bank’s own operating model.
The questions treasury teams should be asking about their own process
1. Why does opportunity timing depend on the client?
Most treasury conversations begin when the client hints that something’s under review. Sometimes it’s obvious: they say they’re looking at new cash management options. Other times it’s subtler, like a comment about cash concentration or liquidity structures.
Either way, the trigger comes from them. The client defines the moment, the problem, and often the shape of the solution, all before treasury is even fully engaged. In some cases, the client has already had a conversation with another bank or provider.
When your model depends on the client surfacing the opportunity, you’re structurally reactive. And the focus becomes speed and pricing, rather than insight.
2. Why does discovery rely on manual document collection?
This is where a lot of critical treasury sales time gets lost, even in the highest performing teams.
A deal gets moving and the requests start: statements, AR and AP reports, cash flow exports. Maybe a few screenshots from the ERP. Then come the follow ups, because, inevitably, something is missing, the format is unusable, or the numbers don’t line up the way you expected.
When discovery depends on clients pulling and sending documents, the process becomes constrained by their time, priorities, and reporting capability. The sales cycle slows, momentum fades, and treasury teams end up spending more time validating spreadsheets than delivering insight.
In many cases, proposals are built before the bank has enough reliable data to properly qualify the opportunity.
It also creates unnecessary friction for the client. From their perspective, they are repeatedly being asked to extract information their systems already contain.
If business context only arrives through document chasing, discovery will always lag behind the opportunity.
3. How much of our sales process compensates for missing data?
If you mapped out your typical treasury sales process on a whiteboard, most of the steps would look reasonable at first glance.
There’s an initial discovery call. Then a follow up to request documents. Time set aside to review what comes back. A few clarifications when something is missing or unclear. Internal discussions to reconcile numbers from different sources. Alignment with the relevant product specialist. A proposal meeting. Sometimes multiple proposal meetings when assumptions need to be adjusted. The list goes on.
Some of these steps are essential. But how many exist simply because information was not available at the start?
When access to information is delayed, your process stretches to fill the gap.
Each missing report creates another touchpoint. Each inconsistency requires another internal conversation.
Over time, it becomes normalized, it’s “just how treasury sales works.” In many cases, though, the root cause can be traced back to data access.
4. Are we building proposals on perception instead of evidence?
Treasury teams pride themselves on strong discovery. But even the best discovery is still based on what the client can articulate.
A client may describe cash flow pressure as a liquidity issue, when the real driver is receivables timing. They may ask for a payments solution because they’re frustrated with processing, when the real issue is supplier concentration and negotiation leverage.
If your systems don’t allow you to independently validate inflows, outflows, receivables trends, supplier concentration, and payment mix, then your proposals will always be shaped primarily by perception.
It may be directionally right, but it increases the risk that you’re solving the wrong problem or missing a larger opportunity.
5. Can we see beyond our own balance sheet?
Most banks operate with a limited field of view. They see activity within their own accounts and rely on what clients choose to disclose, but that, inevitably, creates structural blind spots.
Today’s businesses are multi-banked. Receivables, payables, reserves, FX, cards, and credit facilities are often spread across different providers. If you only see on-us activity, you only see part of the story. That has real consequences for deposit defence.
Attrition is rarely a single event, it’s gradual. Balances taper off. Inflows get redirected. Secondary accounts become the main operating account. By the time it shows clearly on your balance sheet, share of wallet has already shifted.
Early warning signs usually exist, sometimes 90 days before a business fully moves. Without visibility into the broader financial footprint, those signals are easy to miss.
The outcome is predictable churn that no one acts on early enough because no one can see it clearly enough.
How on-demand ERP data access solves these issues
With the right connectivity layer in place, treasury teams can pull structured data directly from systems like NetSuite, Sage, QuickBooks, Xero, Microsoft Dynamics, and SAP. That includes cash flow activity, AR/AP aging, customer and supplier concentration, payment timing, and working capital trends.
The impact is straightforward: instead of relying on point-in-time exports and emailed documents, the bank works from current data pulled directly from the system of record.
That shift addresses a core tension in treasury sales: teams are expected to lead with insight, but are often forced to operate with incomplete information.
Permissioned ERP access reduces that gap and gives teams a stronger starting point. Below, we outline how.
1. Opportunity signals show up earlier: Treasury teams don’t have to wait for a client to announce a review process. Shifts in cash flow, payables behaviour, or working capital pressure become visible sooner. Conversations start earlier and from a stronger footing.
2. Discovery moves faster: Document chasing falls away. Required data can be accessed directly, which keeps momentum intact and shortens time to proposal.
3. Less friction, lower cost to serve: Fewer follow-ups, fewer clarifications, and less manual reconciliation. Over time, this lowers cost to serve and makes the sales model more scalable, enabling teams to support more clients and grow revenue without proportionally increasing headcount.
4. Stronger proposals and cleaner internal alignment: Recommendations are grounded in verified operating data, not assumptions. That builds credibility with clients and makes it easier to align risk, product, and commercial stakeholders.
5. Clearer view beyond the bank’s own rails: ERP data reveals how funds move across accounts and providers, including where receivables land and where payments are routed. That matters for deposit defence. Drift can be spotted earlier, before it turns into permanent attrition.
The result is a treasury function that spends less time reconstructing the past and more time advising on what to do next.
| Questions treasury teams should ask | The underlying problem | Commercial impact | How permissioned ERP data helps |
| Why does our sales cycle only begin once the client asks for help? | Treasury engagement is triggered by client signals, not by proactive insight | The bank enters late, is forced to compete on price and speed, and loses the chance to shape the opportunity | Surfaces early signals in cash behaviour so teams can engage before the client starts a formal review |
| Why does our process rely on clients manually supplying critical data? | Discovery depends on clients pulling reports, exporting files, and emailing documents | Delays proposals, increases admin effort, and weakens client experience | Removes document chasing by pulling structured data directly from the system of record |
| How many steps in our sales motion exist only because we don’t have the right data upfront? | Sales workflows expand to compensate for missing or incomplete data | Longer cycles, more touchpoints, more internal coordination required | Reduces back and forth by providing consistent, complete data from the start |
| Are we building proposals on perception instead of evidence? | Proposals are shaped by what clients describe, not what the data proves | Missed opportunities, incorrect assumptions, weaker recommendations | Enables validation of inflows, outflows, AR/AP trends, and working capital drivers to build proposals grounded in evidence |
| Can we see beyond our own balance sheet? | Banks only see on-us activity and whatever the client shares | Harder to spot deposit drift, weaker deposit defence, missed cross-sell | Reveals off-us activity through ERP signals such as external accounts, receivable routing, and payment destinations |
What this means for treasury sales teams
Treasury teams are being asked to show up more like advisors. The problem is they’re often expected to do that without the visibility that makes advisory work possible in the first place.
If insight only comes after a discovery call and a batch of emailed documents, it’s always going to be late. If you can only see what sits on your own balance sheet, you’re going to spot deposit drift after it’s already happened. And if proposals are built on partial information, there’s a real risk you’re treating the symptom instead of the root issue.
Advisory-led treasury comes down to closing the distance between data and the bankers responsible for acting on it. That’s the gap Codat is focused on bridging.
We work with commercial banks to give treasury and relationship teams secure, permissioned access to the financial data they need to have smarter conversations and move with more confidence.
If you’re rethinking how treasury sales should work in your bank, and want to see how permissioned ERP data could support that shift, complete the form below and we’ll walk you through it.
