Improve a Treasury Account Reconciliation Conversation

A treasury specialist hears the same opening line on almost every reconciliation call, the reports take too long. That line sounds like a request for a new report, but it rarely is. It is a symptom, and if you respond to the symptom instead of the cause, you build a report nobody needed and the client's close still takes two days next month. This kind of call is where reconciliation conversations most often go wrong, and getting it right takes more than a friendly tone.

Why this conversation goes wrong

Most specialists want to help fast. A controller complains about hours lost to reconciliation, and the instinct is to offer a fix, a new file format, an integration, a dashboard. That instinct skips the one step that actually matters, finding out where the hours go. Reconciliation effort hides in a dozen different places. It might sit in a bank file that arrives late, in manual mapping of payment references, in duplicate entries between two systems, or in an internal approval chain that has nothing to do with the bank at all. If you propose a solution before you know which of these is true, you either solve the wrong problem or you solve a problem the client never had. The client walks away frustrated, and you have burned trust you will need for the next conversation. The fix is not a better pitch. It is better discovery, asked in plain language, before anyone talks about a solution.

How to prepare

Walk into the call with facts, not assumptions. Pull whatever history you have on the account, including recent exception volume, prior service requests, and the accounts the client actually uses day to day. Write down the questions you need answered rather than trying to remember them mid call. You want the client to walk you through a real, recent close, not describe reconciliation in the abstract. Ask them to have a specific month in mind, ideally the most recent one, so the answers are concrete instead of general impressions. Prepare a short list of the details you need. First, when does data arrive and in what form. Second, which internal system receives that data and who touches it along the way. Third, what breaks or gets flagged, and how often. Fourth, what the team currently does by hand. Going in with this structure keeps the call from drifting into a general complaint session and keeps you from filling silence with a premature offer to help.

What to say

Consider a call with a controller at a manufacturing company who opens with the familiar complaint.

The controller says, "Reconciliation eats two full days every month across our main accounts. We need something that gets us out of the spreadsheets."

Instead of naming a product, the specialist starts with the close itself. She says, "Walk me through the last close you did. When did the bank file land, and what did your team do with it once it arrived."

The controller explains that the file lands on schedule every morning, no complaints there. The trouble starts after that. Someone on his team has to manually match each payment reference in the bank file to the right invoice in their accounting system, because the references do not line up automatically. That matching work eats most of the two days.

The specialist follows with a narrower question. "Can you send me a sample of what that mapping looks like, and tell me who manages your accounting system on the technical side." She does not promise a new file layout or a system integration on the call. She notes the pain point precisely, manual reference mapping, and gets the name of the person who would need to be involved in any technical review. That single exchange turns a vague complaint into a specific, ownable problem, and it took two questions to get there.

Mistakes to avoid

A few habits sink this conversation more than any other. First, offering a solution before you understand the workflow. It feels responsive, but it usually guesses wrong. Second, treating the client's internal process as something you can redesign for them. The client owns its accounting procedures, and workflow changes are the client's call, not yours. Third, ending the call without a baseline. If you cannot state how many accounts are involved, how many hours the close takes, and which exceptions recur, you have nothing to measure improvement against later. Fourth, asking questions that only confirm what you already assumed, rather than questions that could surprise you. Fifth, letting the client leave without agreeing on what a better close actually looks like for them. Some teams want fewer hours. Others want fewer errors, or fewer people involved. A generic goal like faster reconciliation is not specific enough to act on.

How to practice and score it

This conversation is hard to get right cold, because the pressure to sound helpful fights against the discipline of asking questions first. A manager can score a specialist on a few concrete things. Did the specialist ask about a specific recent close instead of accepting a general complaint. Did the specialist identify a measurable pain point before mentioning any tool or service. Did the call end with a clear baseline, covering accounts, hours, and recurring exceptions. Did the specialist avoid promising an outcome that depends on systems or approvals outside the bank's control. Rehearsing this scenario before it happens with a real client is worth the time. DealSpeak's Banking practice conversations page lets treasury specialists run this exact call against a realistic counterpart and get scored on those points. The same discovery habit carries over when you Map an ACH Exception Workflowwhere the real cause is often buried in exception codes rather than in the hours a controller reports. It also applies if the conversation shifts toward fraud concerns, where you can Review a Treasury Check Fraud Pattern using the same method of asking before proposing.

After the call

Send the client a short summary of the baseline you agreed on, and set a date to revisit it after a busy month, since close time swings with volume. A good reconciliation conversation does not end with a promise. It ends with a clear, shared picture of where the time actually goes.