Prepare a Commercial Deposit Concentration Review

A large or irregular deposit hits a commercial account and the CFO wants to know what it means for the relationship right away. The money might come from a spring conference schedule, a one time asset sale, or a new client contract. Whatever the source, the pattern needs a story that holds up under review, not just a number on a statement. A commercial banker who treats the dollar amount as its own explanation sets up a harder conversation later, when the designated review team asks questions the banker cannot answer. Good preparation turns a vague deposit pattern into a documented operating narrative that the customer does not have to repeat from scratch.

Why This Conversation Goes Wrong

Most bankers do not fail this conversation because they lack knowledge of the rules. They fail because they treat it as either an accusation or a formality, and both extremes backfire. Treat it as an accusation and the CFO gets defensive, gives short answers, and stops volunteering useful detail. Treat it as a formality and the banker skips the real questions, promises the deposits will be fine, and leaves the review team with nothing but a dollar figure and a guess.

There is also a trust problem hiding underneath. The CFO sees a longstanding banking relationship and expects the banker to vouch for them on the spot. The banker sees a pattern that changed and knows the review process exists for a reason. Neither side benefits from pretending those two positions are the same thing. The banker who says too little frustrates the client. The banker who promises too much creates a problem for the bank and for the client when the review does not go the way the banker implied it would.

Timing makes this worse. These calls often happen after the deposits already posted, so the CFO wants a fast answer and treats every follow up question as a delay. The banker has to ask for documentation anyway, because a fast wrong answer costs more than a careful right one.

How To Prepare Before You Pick Up The Phone

Before the call, pull the account history and look at the deposit pattern over at least the past year, not just the recent spike. Note the size, the frequency, and whether anything about the pattern lines up with a known business cycle for that customer, such as a seasonal event schedule or a contract renewal date.

Write down the specific facts you need from the customer. For a conference business like the one below, that means the event calendar, a sample reconciliation showing how registration fees turn into deposits, and the name of the person who owns records of incoming payments. For a different customer, it might mean a client contract, an invoice schedule, or a distributor agreement. The facts change by industry, but the discipline stays the same. It is the same habit you would use to Discover the Facts Behind an Equipment Purchase or to Handle a Delayed Commercial Financial Statement. Gather documents first and draw conclusions second.

Decide in advance what you will and will not say about outcomes. You are not the reviewer, and you cannot promise how the review will resolve. Write that boundary down before the call, because it is much harder to hold to it in the moment when a client you have known for years is pushing you for reassurance.

What To Say

Northpoint Events runs several large conventions every spring, and the deposits that follow those events changed the account's typical monthly pattern. The CFO calls the banker directly.

"These deposits are bigger than what you usually see from us, and I want to make sure this does not slow anything down on our accounts," the CFO says. "Is there a problem here?"

The banker responds without guessing at an answer. "Nothing here tells me there is a problem, and nothing here tells me there is not one. What I need is enough detail so the team that reviews transactions can look at facts instead of a number. Can you send over the event calendar for this spring, a sample reconciliation that shows how registration payments turn into these deposits, and the name of whoever owns those payment records on your side?"

"I can get you all of that today," the CFO says. "But I need to know what happens after. Will this change how you handle our account?"

"I cannot tell you the outcome of a review before it happens, and I would not want to guess," the banker says. "What I can tell you is that a clear, documented pattern gives the review team what it needs to move through this efficiently. Once I have the calendar and the reconciliation, I will confirm who on our side owns this file and when you should expect to hear back."

That exchange does three things. It answers the CFO honestly without minimizing the review or inflating the risk. It asks for specific documents instead of a general explanation. And it sets a clear next step instead of leaving the CFO to wonder when someone will call back.

Mistakes To Avoid

Do not promise a result. Saying something like "this should be fine" feels reassuring in the moment, but it puts you on the hook for a decision that is not yours to make, and it makes the eventual real answer look like a broken promise if the review takes longer or asks for more.

Do not accept a dollar figure without a source. "It is from our spring events" is a starting point, not documentation. Ask for the calendar, the invoices, or the remittance detail that lets someone else confirm the story without calling the customer back.

Do not suggest the customer change its deposit behavior to make the review go faster or look cleaner. That crosses from gathering facts into shaping them, and it puts both the bank and the customer in a worse position than an unusual but honest deposit pattern would.

Do not let the call end without a summary. If you hang up without repeating back the source of funds, the timing, who owns the documentation, and when you will follow up, the customer is left guessing and the review team gets a weaker handoff.

How To Practice And Score This Conversation

This conversation is hard to get right on the first real attempt, because the pressure to reassure a client is strongest exactly when you should be asking questions instead. Rehearsing it with a counterpart who plays a pushy or anxious CFO exposes the moments where you would normally cave and offer a guess about the outcome.

A manager reviewing a recorded practice run or a live call should score three things. First, did the banker ask for specific documentation, the calendar, the reconciliation, and a named record owner, rather than accepting a general explanation. Second, did the banker avoid promising an outcome while still giving the customer something concrete, such as a clear description of what happens next. Third, did the call end with a recap that a review team could use without calling the customer again.

DealSpeak lets a commercial banker rehearse this exact scenario against an AI counterpart that plays the CFO, pushes back the way a real client would, and scores the response against those same three points. Running through it once before a real call surfaces the reassuring phrases you reach for under pressure, so you can replace them before a client hears them. Banking teams that want more scenarios like this one can find a full set of Banking practice conversations built around the calls commercial bankers actually have to make.

Final Thought

A deposit pattern is not a mystery to solve alone on the phone. It is a set of facts to gather, document, and hand to the people whose job is to evaluate them. Get the facts right and specific, and you protect the relationship and the review at the same time.