Start a Treasury Sweep Account Discovery

A company that calls about a sweep account is really asking one question. Where does our cash sit overnight, and who controls it. As a treasury specialist, your job in this first conversation is not to design the sweep structure. It is to learn how money already moves through the company's accounts, so the bank can build something that matches how the business actually operates instead of how it wishes it operated. Get this discovery conversation wrong and you either promise a setup the bank has not reviewed, or you leave the meeting without the operating details underwriting actually needs.

Why This Conversation Goes Wrong

Most specialists want to sound helpful on this call. A controller says their team moves cash manually every morning, and the natural response is to reassure them that automation will fix that. That response is a mistake. You have not seen the account structure, the approval chain, or the restricted balances yet, and a promise made before review creates an expectation the bank may not be able to meet.

The second failure is accepting a vague answer as a complete one. When a controller says balances move every morning, ask which morning, which account, and who actually presses the button when the usual person is out. Companies describe their cash process the way they wish it worked, not always the way it actually works. Your job is to find the gap between those two descriptions, because that gap is usually where the real risk sits.

The third failure is drifting into advice the company has not asked for and the bank has not authorized you to give. A specialist who tells a controller how much cash to keep on hand, or which investment vehicle fits their liquidity needs, has stepped past discovery and into a role that belongs to the company and its own advisors.

How To Prepare Before The Call

Walk into the discovery conversation with a clear picture of what you need to learn, not what you plan to recommend. Pull the account list for every entity involved, note which accounts are operating accounts and which hold restricted or reserved funds, and identify who currently has signing authority on each one.

Prepare three things before you dial in.

1. A list of every account that might participate in the sweep, along with its current purpose.
2. The names and roles of people who can confirm daily balances and approve transfers.
3. A short set of questions about timing, since payroll, vendor payments, and collections rarely land on the same schedule.

Preparation like this keeps the conversation grounded in facts you can verify later. It also signals to the company that this is a structured review, not a sales conversation, which tends to make controllers more forthcoming about the manual workarounds they might otherwise hide.

What To Say During The Discovery

Mason Healthcare runs several operating accounts, and its controller moves balances by hand every morning. Here is how that conversation might actually unfold.

You open with a direct question. "Walk me through last Friday. Which account received your collections, which account paid payroll, and who noticed if a balance came in wrong."

The controller answers plainly. "Collections land in our main operating account. Payroll pulls from a separate account two days before each pay date. If a balance looks off, I usually catch it myself when I check the online portal each morning."

That answer is useful, but it has a hole in it. Push on the gap. "What happens on a morning when you are out sick or on vacation. Who checks the balance then."

The controller pauses. "Honestly, nobody does automatically. We would probably catch it later in the week."

That single exchange gives you more than a generic script would. You now know the transfer is manual because no backup person owns it, not because the company chose manual review on purpose. You also know payroll timing, which accounts touch each other, and where an exception could sit unnoticed for days. Write that down as a fact for the bank's review. Do not tell the controller whether Mason Healthcare should hold more cash in reserve or whether a particular sweep structure fits their liquidity needs. Those are decisions for the company and its own advisors, and stepping into that role undermines the trust you are trying to build.

Mistakes That Undermine The Review

A few habits will quietly damage this conversation and the review that follows.

Do not promise a specific sweep configuration, transfer schedule, or yield before the bank's formal review is complete. A specialist who says "we will set this up as a same day zero balance sweep" before underwriting has looked at the accounts is making a commitment the bank has not approved.

Do not let the company treat you as its cash advisor. If a controller asks how much operating cash they should keep on hand, redirect them to the company's own finance leadership or outside advisor. Answering that question yourself blurs a line that protects both the bank and the customer.

Do not accept the first answer as the complete answer. Controllers often describe the process that exists on paper, not the one that happens when someone is out or a holiday shifts the payroll date. Ask about the exception, not just the routine.

Do not leave the call without naming the records and the authorized contact the next meeting will need. A vague close means someone has to redo this discovery work later, which wastes the company's time and yours.

How To Practice And Score This Conversation

This conversation is hard to get right the first time you try it live with a customer, so rehearse it first. A manager can run a roleplay where one person plays the controller and gives answers that sound complete but hide a gap, the way Mason Healthcare's controller did. Score the specialist on three things. Did they ask about the exception, not just the routine. Did they avoid promising a configuration or giving liquidity advice. Did they close with a specific list of records and contacts needed for the next step.

DealSpeak gives treasury specialists a way to run this exact roleplay against an AI counterpart that answers the way a real controller would, including the vague first answer that needs a follow up question. You can review the transcript afterward and see exactly where the questions got specific and where they stayed generic.

Once you can run a sweep discovery cleanly, the next conversation in this same relationship is often about who can see and move the money once the structure is live. You can practice that with the guide to Run a Treasury User Access Audit Conversation. If the account holders on the call need training on the new setup afterward, Build a Treasury User Training Plan covers how to plan that session. For more roleplay scenarios built for this role, see the full set of Banking practice conversations.

A good discovery call ends with a fact based map of how cash actually moves, not a promise. Get the exception owner named and the records list confirmed, and the bank's formal review has everything it needs to move forward.