Clearing underwriting conditions in one pass means reading each condition word by word, sending the exact document it names, checking that document against the request before upload, and answering any new question the document raises in the same package. Most second rounds come from bank statement conditions answered with a partial page set or a letter with no proof.
What is an underwriting condition actually asking for?
An underwriting condition is a written request that names a fact the underwriter cannot yet confirm and, usually, the document that would confirm it. Read it as two parts: the fact in doubt and the evidence wanted. A response that supplies the evidence but leaves the fact in doubt will not clear.
Take a common wording: "Provide source of $8,400 deposit on 4/12 to checking ending 0917, with supporting documentation." The fact in doubt is where that money came from. The evidence wanted is something that shows the origin, such as the statement of the account it left, a sale receipt or a settlement statement. A letter that says "this was from selling my truck" states the fact but supplies no evidence, so it covers half the condition.
Break each condition into checkable pieces
Before you request anything, rewrite each condition as a short list of things that must be true when you are done. For the deposit above, that list is:
- The amount on the source document matches $8,400, or the difference is explained.
- The date on the source document comes before or on 4/12.
- The payer or account named on the source document belongs to someone the underwriter can identify.
- The borrower's own account history shows the money landing, which it already does.
Each item is now a yes or no check you can run on whatever the borrower sends.
Watch the small words
Underwriters choose words with care. "All pages" means blank pages too. "Most recent" means the latest statement the bank has issued, not the latest one the borrower downloaded. "Signed and dated" means both. "Business" in front of "account" means the account titled to the company, not the personal account used for business. Missing one of these words is the most common reason a correct document still bounces.
Prior to docs and prior to funding condition groups
Conditions arrive in groups that tell you when each one must be cleared. Prior to docs (PTD) items must be cleared before the lender will draw closing documents. Prior to funding (PTF) items can be cleared at or after signing, before money moves. Clearing PTD items first protects the closing date.
Some lenders add a third group, prior to closing, for items the settlement agent collects at the table, such as a signed final application. Others fold those into PTF. Your approval letter will say which labels this lender uses.
Sort the list before you start
On receipt of the approval, sort the full condition list by group, then by who must supply each item. Borrower items go out first because borrowers are the slowest source. Third-party items, such as a payoff letter or a title update, go out the same day so they run in parallel.
Know which group a statement condition sits in
Bank statement conditions usually land in PTD, because they bear on income or assets the approval depends on. An updated statement requested to show funds to close can land in either group depending on the lender. If the closing is near, ask the lender whether a statement item can move to PTF. Some will allow it for an asset refresh, few will for an income question.
A condition response sheet for one bank statement file
A condition response sheet is a table you build before upload that lists each condition, the document you are sending, and the check you ran on it. It forces you to prove each item is complete and gives the underwriter a map of the package. The sheet below is an example with made-up values.
| No. | Condition (abridged) | Group | Document sent | Check run before upload |
|---|---|---|---|---|
| 1 | All pages of March statement, checking ending 0917 | PTD | Bank PDF, pages 1 to 6 of 6 | Page count printed on each page, opening balance equals February closing balance |
| 2 | Source $8,400 deposit on 4/12 | PTD | Buyer's cashier's check copy, bill of sale, letter | Amount and date match, buyer named on both |
| 3 | Explain 3 NSF fees in May | PTD | Signed letter with dates | Each fee date in the letter matches the statement |
| 4 | Business account owned by borrower | PTD | State registry printout | Borrower named as sole member, business name matches statement title |
| 5 | Updated statement dated within 30 days of closing | PTF | Bank PDF for August, all pages | Statement date within window, no new large deposits |
What the check column buys you
The check column is where most resubmits are caught. Item 5 shows why. An updated statement can contain a new large deposit that did not exist when the file was approved. If you upload it without reading it, the underwriter finds the deposit and issues a new condition. If you read it first, you source the deposit in the same package.
Upload in a predictable order
Number each upload to match the sheet and place it in the order the lender expects. The order most lenders and investors want is covered in the guide to loan file stacking order for lenders and investors. A file that arrives sorted is read faster than one that arrives as a loose pile.
Why do bank statement conditions come back a second time?
Bank statement conditions loop because each statement answers one question and can raise another. A new month shows a new deposit. A missing page hides a transfer. A business account reveals a second owner. The cure is to read every statement you send as closely as the underwriter will, before it leaves your desk.
The four loops seen most often
- The partial statement. The borrower sends pages 1 and 2 of a 5-page statement, often because the later pages look empty. The condition reissues for the full set.
- The transfer with no other side. A $5,000 transfer in from savings needs the savings statement. When that arrives, it shows the money came into savings from somewhere else, and a new sourcing condition follows.
- The refresh that adds a deposit. An updated statement, sent to show funds, contains a deposit that now needs a source.
- The screenshot. An online banking capture lacks the bank name, the account number or the date range, so the underwriter asks for the bank-issued PDF.
Breaking the loop
For each statement, run three checks before upload: all pages present and numbered, opening balance matching the prior closing balance, and every deposit above the borrower's usual size already sourced. Software helps with the second and third checks. TrueBankFlow, for example, flags large and out-of-pattern deposits with the date and the statement line, so a processor can see before upload which items an underwriter will ask about.
Each loop also costs calendar time. How those extra rounds add up across a pipeline is the subject of what slows underwriting turn times.
Explanation letters that satisfy a deposit condition
An explanation letter clears a deposit condition when it names the deposit by date and amount, states where the money came from in one or two sentences, and is paired with a document that proves the source. A letter on its own clears only conditions that ask for an explanation and nothing more.
What a usable letter contains
- The account, the date and the amount, copied from the statement.
- The plain source: "proceeds from the sale of my 2016 Ford F-150 to John Doe."
- A reference to the attached proof: "bill of sale and copy of check attached."
- The borrower's signature and date.
What to leave out
Letters that run long tend to open new questions. A borrower who explains a deposit and then adds that they "also do some side work for cash" has just told the underwriter about income that is not on the application. Draft the letter from the facts, have the borrower check it for accuracy, and keep it short. The borrower must agree it is true, and the borrower signs it.
NSF and overdraft letters
When a condition asks about NSF fees or overdrafts, the letter should list each event with its date and give the cause. A one-time timing gap reads differently from a run of overdrafts across several months, and the underwriter will compare the letter to the statement line by line.
Condition responses that open new conditions
The most costly mistake in clearing conditions is sending more than the condition asks for without reading it first. Every extra page is something the underwriter must review, and anything in it that conflicts with the file becomes a new condition. Send what is asked, read all of it, and answer what it shows.
Examples of self-inflicted conditions
- Uploading a full year of statements for a second account when only the last two months were asked for, which brings ten months of new deposits into review.
- Sending a revised profit and loss statement that shows a different net figure from the income worksheet.
- Attaching a gift letter for funds that were never in question, which then needs a donor statement.
- Forwarding a borrower's email thread that mentions a new car purchase.
Data that belongs to the borrower
Statements and analysis reports in a condition package hold personal financial data. Who you share it with, and in what form, has rules of its own. Whether a third-party analysis of those statements counts as a consumer report is a separate question, covered in whether bank statement analysis is a consumer report.
When to phone the underwriter about a condition
A phone call beats another upload when the condition is unclear, when the document asked for does not exist, or when a second round has already failed. A five-minute conversation can turn a condition into a document the borrower can actually produce. Confirm what was agreed in writing afterward.
Good reasons to call
- The condition asks for a document the borrower cannot get, such as a statement from an account that was closed years ago. Ask what would serve in its place.
- The wording could mean two different things, and the two answers need different documents.
- The same condition has come back twice and you do not know why.
- Clearing the condition would change the loan in a way the borrower must decide on, such as dropping an income source.
Calls that waste the underwriter's time
Calling to ask whether a document "will be fine" before sending it rarely helps; the underwriter needs to see it. Calling to argue a guideline rarely helps either. If you believe a condition is wrong under the program rules, that belongs in a written exception or appeal, not a phone call.
After the call
Send a one-paragraph note to the underwriter that restates what was agreed, then add that note to the condition response sheet beside the item. When a teammate picks up the file, the record of the call is there.
Once the package is clean, analyzing statements before submission cuts the number of statement conditions in the first place. If your team wants that step done with totals tied back to statement lines, you can request early access to TrueBankFlow.