Explaining Your Numbers to a Skeptical Loan Officer
A client of mine had a genuinely strong file, healthy revenue, reasonable debt load, two years in business, and still got declined at her first bank because she walked into the meeting with a stack of printouts and no clear narrative...

A client of mine had a genuinely strong file, healthy revenue, reasonable debt load, two years in business, and still got declined at her first bank because she walked into the meeting with a stack of printouts and no clear narrative connecting them. She reapplied at a second bank three weeks later, same numbers, same documents, and got approved, because the second time she led with a short, plain explanation of her business before the underwriter had to hunt for it themselves.
Why the numbers alone often are not enough
An underwriter reviewing your file is trying to build a coherent story from documents that, on their own, do not always tell one clearly. A dip in revenue two years ago might be an alarming red flag or a known, temporary event, a supplier issue, a renovation, a planned slow quarter, and the documents alone rarely distinguish between those explanations. Left to guess, an underwriter tends to assume the more concerning explanation, simply because that is the safer assumption from their side of the desk.
A short, honest explanation attached to the file, not buried in an appendix but stated plainly upfront, closes that gap before it becomes a reason for hesitation. This is not about spin, it is about giving the reader of your financials the context they need to interpret what they are looking at correctly.
What actually makes an explanation land
The explanations that work are specific, brief, and led with the point rather than the backstory. "Revenue dipped in Q3 2024 because our main supplier had a six week disruption, resolved, and revenue recovered fully by Q4" does more work in one sentence than three paragraphs describing the supplier relationship in detail before getting to what actually happened. Underwriters read a lot of files. A specific answer stated in the first sentence gets read and trusted far more reliably than a long one that makes them dig for the actual point.
Pushing back on "let the numbers speak for themselves"
This is advice I hear from business owners who feel that adding explanation looks like making excuses, and I understand the instinct, but I think it is backwards in practice. Numbers do not speak for themselves, they get interpreted by a person under time pressure reviewing dozens of files, and an unexplained anomaly reads as a risk regardless of how innocent the actual explanation would have been. Providing context is not weakness, it is doing part of the underwriter's job for them in a way that works in your favor, and the businesses I have seen decline to explain anomalies simply because they did not want to seem defensive have paid for that instinct with declined applications more than once.
A structure that works consistently
| Element | What it should do |
|---|---|
| One paragraph business summary | Orient a reader unfamiliar with your business in seconds |
| Explanation for any anomaly | Lead with what happened, then the resolution, in one or two sentences |
| Statement of what the funding is for | Specific enough that the underwriter can evaluate the actual use case |
None of this needs to be a formal business plan. A single typed page attached to your application, written the way you would explain your business to a smart stranger with two minutes to listen, does more for how your numbers get read than any amount of additional financial detail.
What happens when the explanation is missing entirely
I have sat in on enough loan meetings to see the same pattern repeat: an underwriter finds an anomaly, asks the owner about it on the spot, and gets a rambling, defensive answer that raises more questions than it resolves, not because the actual explanation was bad, but because the owner was improvising it under pressure for the first time in that exact meeting. The content of the answer was often fine. The delivery, hesitant, unstructured, visibly searching for the right words, read as uncertainty even when the underlying facts were completely reasonable.
The fix is not becoming a more polished talker in general, it is simply writing the two or three anomalies you already know will come up, before the meeting, so the first time you say the explanation out loud is not also the first time you have organized it in your own head.
Getting the framing right before you apply
Write the explanation before the meeting, not during it, so you are not improvising an answer to a question you should have anticipated. If explaining financial context clearly is not a natural skill, resources like Cuesta Comunicacion Total cover the broader skill of communicating clearly under scrutiny, which applies just as directly to a loan meeting as it does to any other high stakes conversation.
Pair this with having your core documents fully organized before the meeting, since a clear narrative attached to a messy, incomplete file still leaves an underwriter with more questions than answers. The two work together, not as substitutes for each other.
More from the blog
Funding Readiness
The Odds a Lender Sets Before You Ever Sign
A client once asked me why her interest rate seemed so much higher than the rate her friend got for what sounded like a similar...
Funding Readiness
Four Documents Every Lender Will Ask For First
The applications I approved fastest during my underwriting years almost never had the strongest numbers on paper.
Cash Flow Management
Inventory Financing for a Small Apparel Resale Business
A resale business owner I worked with faced the same problem every apparel reseller eventually hits: the best inventory...