Lending Advisors: Discuss a Financial Statement Variance Without Interpreting It

A borrower calls with a financial statement that looks nothing like the last one, and the first question out of their mouth is whether it will sink the deal. You are not the person who decides that. Your job is to keep the borrower calm, keep the conversation on process, and route the real explanation to the person who can actually give it. Get that boundary wrong and you either scare the borrower or make a promise you cannot keep.

Why This Conversation Goes Wrong

A lending advisor talks to borrowers all day about numbers, so it feels natural to comment on them. A borrower shows you receivables that jumped forty percent and asks if that is a problem, and the easy answer is to say something reassuring like "that should be fine" or "underwriters usually like growth like that." Neither statement is yours to make. You have not run the analysis, you do not know what else is in the file, and you are not the person accountable for the credit decision.

The bigger risk is not being wrong. It is that a casual reassurance becomes something the borrower repeats later, as in "the advisor told me the increase looked fine." Now you are being quoted as a source of underwriting judgment you never had. The safer failure mode is silence or vague deflection, but that leaves the borrower anxious and unclear on what happens next. Neither extreme serves the borrower. The middle path, explaining process without touching substance, takes practice because it does not come naturally in the moment.

How to Prepare

Before you take a call like this, know three things cold. First, know exactly who reviews financial statements at your institution and what that team actually does with a variance, so you can describe the process accurately instead of vaguely. Second, know what documentation your institution accepts as an explanation for a changed figure, a letter from the accountant, a signed note from the borrower, a copy of a new contract, whatever your process calls for. Third, know how to log a borrower's context in the file so it reaches the reviewer without you interpreting it first.

Write down the two or three sentences you will use to redirect an interpretation question before you need them. Under pressure, most people either overexplain or blurt out an opinion they did not intend to give. A prepared line, said the same way every time, keeps you consistent. Also prepare a short list of questions you will ask the borrower, who prepared the statement, when the underlying change happened, whether the person who prepared it is reachable for a follow up question. Those questions move the conversation forward without requiring you to judge anything.

What to Say

Picture a small catering company that picked up a large seasonal contract. The new financial statement shows receivables far higher than the prior one, and the owner is on the phone before the reviewer has even opened the file.

The owner says, "Our receivables jumped a lot since last quarter. Is that going to hurt us?"

You say, "I cannot tell you how the review team will read that number, that call is theirs to make once they have the full picture. What I can do is make sure they get a clear explanation from the right source instead of guessing at it. Can you tell me who prepared this statement and when the new contract started?"

The owner explains that the accountant added the receivable once the seasonal contract was signed in July, and that the accountant can answer questions directly if needed.

You say, "That is helpful. I am going to note in the file that the increase relates to a seasonal contract signed in July, and I will include your accountant's contact information in case the reviewer wants to confirm it directly. Once the review team has looked at the full application, I will update you on next steps."

Notice what did not happen. You did not say the variance was normal, big, small, or good news. You did not guess how it will land. You gathered a fact, identified a person who can confirm it, and told the borrower exactly what happens next.

Mistakes to Avoid

Do not tell a borrower that a variance is good, bad, typical, or a problem. You do not have the full file and you are not the reviewer. Do not suggest accounting fixes, do not recommend restating a figure, and do not tell a borrower to adjust their books to make a number look different. That is not your role and it can create real problems for the borrower if a lender later asks why a document was changed after the fact.

Do not promise a specific outcome or timeline you do not control, such as "this will get approved" or "you'll hear back by Friday" unless that date comes directly from the review team. Do not let the conversation end without a next step. A call where you sympathize but produce no documented fact, no named contact, and no follow up point has not actually helped the borrower, even if it felt supportive in the moment.

One more trap. Do not let the borrower's anxiety pull you into filling silence with speculation. If you do not know something, say so plainly, then say what you will do about it. "I don't know how the team will weigh this, but I will get you an answer" is a complete, honest response. It requires no guessing.

How to Practice and Score This

A manager coaching an advisor on this conversation should watch for three things. Does the advisor separate empathy from prediction, meaning do they acknowledge the borrower's concern without answering the question the borrower actually asked. Does the advisor gather the specific facts needed, who prepared the document, when the change occurred, who can confirm it. Does the call end with something concrete, a documented note, a named contact, and a stated point when the borrower will hear back.

Run this as a role play with a borrower who pushes for reassurance more than once. A realistic version has the borrower ask the same question three different ways, "is this bad," "should I be worried," "will this slow things down." A strong advisor gives the same steady, process focused answer each time without getting worn down into an opinion. That repetition under pressure is exactly what breaks untrained advisors, so it is worth testing directly rather than assuming a good answer once means the advisor has the skill.

DealSpeak lets an advisor rehearse this exact scenario against an AI borrower that varies the pressure and tone, then scores whether the advisor drifted into interpretation or held the line on process. It is a useful way to catch the habit before it shows up on a real call. For a related boundary problem, see Lending Advisors Explaining the Guarantor Information Process Clearlywhich covers a different version of the same discipline, explaining a requirement without predicting its outcome. The same logic applies when a borrower pushes back on documentation requests, covered in Lending Advisors Explain an Insurance Documentation Request Clearly.

This conversation is not about being cold or withholding help. It is about giving the borrower something more useful than a guess, a clear next step and a name they can trust. Advisors who practice this until it feels automatic protect both the borrower and themselves. For more scenarios built around this kind of boundary, see the full set of Financial Services practice conversations.