READING THE FILE
How an Underwriter Reads a Business Bank Statement, Line by Line
An underwriter reads bank statements in a fixed order, and the figures that decide the file are rebuilt from the rows rather than read off the totals.
An owner uploads three months of bank statements and then hears nothing for a week. The question that follows is always some version of the same one. What is the person on the other end actually reading?
Not the summary page. An underwriter reads the transaction detail, in a fixed order, and the order is the decision. Balance first. Then deposits. Then debits. Then the shape of the month. By the last page the file is mostly decided, and almost none of that came from a figure printed on the statement. The figures that matter are built from the rows.
That is the whole trick. Your bank prints totals. The person reading it builds different ones.
The balance gets read before the deposits
The first number pulled is average daily balance, because it is the only one on the page that measures cushion instead of activity.
Two shops can move identical money and look nothing alike. Take one billing 41,283 dollars a month that carries an average daily balance of 9,127. Take a second that deposits the same 41,283 and averages 1,382, because every Friday it sweeps the account down to the owner. Same revenue. Two completely different files.
The reason is arithmetic, and it has nothing to do with whether the business is good. A repayment product debits on a schedule the business does not control. If the proposed payment is 287 dollars every business day, that is roughly 6,027 dollars a month leaving in small pieces, on days nobody chose, whether or not a customer paid that week. The underwriter is not asking whether you can afford that out of revenue. They're asking whether the account absorbs it on the worst day of the month, with payroll already gone and the big receivable still out.
Some statements print average daily balance in the summary box. Plenty do not, and then it has to be rebuilt from the daily ledger, which is why a statement with a missing page is treated as a statement that cannot be read at all.
A thin average sitting under strong revenue is not an automatic decline. More often it narrows the shape of what gets offered, toward a smaller amount or a weekly debit instead of a daily one, because the constraint being solved is the floor rather than the annual figure. Owners hear the smaller number and assume their revenue was doubted. Usually it wasn't. The cushion was.
Revenue is not the same thing as money arriving
The second pass splits deposits into revenue and everything else, because a total deposit line on its own is close to meaningless.
Money that lands in a business account without being revenue includes:
- a transfer from another account the owner controls
- an owner injection or a family loan
- proceeds from a funder that already advanced against the business
- a refund, a chargeback reversal, a returned payment coming back
- an insurance settlement or the sale of a vehicle
All of it inflates the deposit total. None of it repeats next month, which is the only quality the file cares about.
A practiced reader finds those without being told. Round figures are the first flag, because paying customers almost never send exactly 15,000 dollars. A mirror is the second: money out of one account on a Tuesday, the identical figure into this one on the same Tuesday. Descriptor text is the third and the loudest, since an ACH credit carries the originating company's name, and a funding company's name is rarely subtle about it.
So the revenue the file is built on is not what the statement totals. It's what survives the scrub.
Deposit count carries a separate signal from deposit size. A restaurant with three deposits in a month is showing batch settlement from its processor, which is ordinary. A general contractor with three deposits in a month is showing three customers, which is a concentration problem regardless of how large those deposits were. If one payer is a large share of the month, the underwriter has quietly started underwriting that payer too, and they have no file on them at all.
Timing inside the month gets noted as well. A business whose deposits cluster in the first week and then go quiet after the tenth has a different risk shape from one taking money in on most days, even at an identical total. The second is being paid continuously. The first is being paid on somebody else's terms, and the file will start asking who those payers are and how long they usually take.
The debits say who is already in the account
Recurring debits get sorted into groups before anything is judged. Rent. Payroll. Insurance. Processor fees. Utilities. Then the group that gets read hardest: payments to somebody who already advanced money against this business.
Those have a shape that is hard to disguise. A fixed amount. Weekdays only, skipping Saturday and Sunday and every bank holiday. The same ACH descriptor, month after month. Daily or weekly rather than monthly, which no landlord and no utility has ever billed.
From that shape a reader reconstructs the obligation without being handed a contract. A debit of 287 dollars across roughly 21 business days is about 6,027 dollars a month. Set against 41,283 dollars of scrubbed revenue, close to one dollar in every seven the business collects is already committed before the owner decides anything. That figure gets carried straight into the affordability math for whatever is being requested now.
Two other debit patterns get flagged. Personal spending run through the business account is not fatal on its own, and it is common in a small operation, but it changes how the rest of the file reads. Transfers out to a second entity raise a harder question: where did that money go, is there a second set of statements, and does the business the file describes match the business the money describes.
The shape of the month, not the total
Three statements get compared, never added together.
The trend is read first. A third month weaker than the first month is a different business from a third month stronger than the first, even at identical averages. Seasonality gets a pass when the trade explains it, which is why a landscaping company's February is read against a landscaping company's June rather than against the calendar.
Then the intra-month dip. Every account has a floor, and the floor usually sits a day or two after payroll clears. What gets tested is where that floor lands relative to the payment being contemplated.
A file does not get declined over the size of the average. It gets declined over where the floor sits on the third Tuesday.
Returned items and negative days get counted here as well, and they carry more weight than almost anything else on the page. They have their own arithmetic and their own thresholds, and they are the fastest single way for a strong-looking file to stop.
Where a file dies without a phone call
Most declines at this stage are not arguments. They are unanswered questions.
An unexplained deposit of 38,000 dollars in a month that otherwise runs 9,000 is a question. An unexplained debit of the same size is a bigger one. A screenshot from a banking app instead of the statement the bank issued is a question about the document itself. A missing page is the same question, louder. Revenue on the application that the statements do not support is not a question at all, it's a contradiction, and it changes what every other number in the file is worth.
The part owners rarely hear is how that gets resolved internally. An underwriter holding an unexplained row does not call to ask. They assume the less favorable of the two available explanations, because nobody has ever been written up for being too careful, and they move to the next file in the queue.
And the fix for almost all of it is a paragraph. Which deposit was the truck. Which account holds the rest of the revenue. Which debit was the equipment payoff and which month it ends. Sent unprompted, alongside the statements, before anyone has to wonder.
Common questions
how many months of bank statements do business lenders ask for
Three consecutive months is the common starting request, and six or twelve months gets asked for when the business is seasonal or the amount is larger. The months have to be consecutive and current, meaning the most recent closed statement period. A gap in the middle usually gets the whole set sent back.
do lenders count transfers between my own accounts as revenue
No. Transfers in from another account you control get stripped out of the deposit total before any revenue figure is calculated, because they are the same dollars counted twice. The same treatment applies to owner injections, refunds and money advanced by another funder.
what is average daily balance and why does it matter more than my ending balance
Average daily balance is the balance the account held on an average day of the month, rather than on the one day the statement closed. It matters because a repayment schedule hits on days the business does not pick, so what counts is the cushion on an ordinary day. An ending balance can be flattered by one deposit landing on the last afternoon.