In loan processor vs underwriter terms, the processor builds the file and the underwriter decides on it. The processor collects documents, orders reports, checks that everything is complete and chases conditions. The underwriter reads the evidence against the guideline and approves, conditions or declines. Bank statement work splits between them: completeness for one, judgment for the other.
How do loan processor and underwriter duties split?
Loan processor and underwriter duties split along one line: the processor gathers and organizes, and the underwriter evaluates and decides. A processor asks "is everything here and consistent?" An underwriter asks "does this evidence meet the program, and is the risk acceptable?" Each role depends on the other doing its half well.
The table below shows a typical split on a mortgage or small business file. It is an example; each lender's job descriptions set the actual lines.
| Task | Loan processor | Underwriter |
|---|---|---|
| Application and disclosures | Checks completeness, tracks deadlines | Reads declarations and history |
| Third-party orders | Orders appraisal, title, verifications | Reviews the results |
| Income documents | Collects pay stubs, returns, statements | Calculates qualifying income |
| Bank statements | Checks pages, months, names, balance chain; gets explanations | Decides which deposits count and what a pattern means |
| Credit | Pulls the report, collects explanation letters | Weighs the credit history |
| Conditions | Logs, requests and returns them | Writes them and signs them off |
| Decision | None | Approve, condition, suspend or decline |
The processor's work shapes how fast an underwriter can decide. A complete, well-labelled file can be read once. A file with gaps gets read, suspended and read again.
Where does bank statement work sit between processor and underwriter?
Bank statement work sits on both sides. The processor owns the completeness checks: every page, every month, the right account holder, a connected balance chain and an explanation for each large deposit. The underwriter owns the meaning: whether a deposit is income, whether a transfer counts, and whether an NSF pattern matters for this program.
Processor-side statement tasks
- Confirm page counts and statement periods are complete.
- Match account numbers and names to the application.
- List large deposits, transfers, recurring creditor payments and NSF events.
- Get written explanations and source documents before submission.
Underwriter-side statement tasks
- Decide which deposits are eligible income and which are excluded.
- Apply the program's expense factor or averaging method.
- Judge whether a declining trend or overdraft history changes the decision.
- Write any condition that follows from the statements.
The processor's list is the arithmetic and paperwork the underwriter would otherwise do first. That is why the handoff matters: a processor who sends a deposit list with sources attached gives the underwriter a head start. Software can do much of that list. How analysis tools differ, and what they produce for each side, is compared in cash flow analysis software for lenders.
Processor and underwriter roles on a three-person lending team
On a three-person lending team, one person often processes, one underwrites and one originates, with overlap when volume spikes. The roles can share tasks, but the decision authority should not move. A processor can prepare a statement summary for the underwriter; the processor should not approve the income it shows.
A sample division
For example, a small business lender with three staff might divide work this way:
- Originator. Takes the application, explains the documents needed, manages the borrower relationship.
- Processor. Runs intake and orders, reviews statements for completeness, builds the deposit list and condition log.
- Underwriter. Calculates income or cash flow, writes conditions, decides and signs the approval.
When the underwriter is out, files wait or go to an outside reviewer. Many small lenders use contract underwriting to cover vacations and volume peaks without asking the processor to sign decisions.
Keeping the line visible
Write the split down. A short role sheet that says which tasks each person owns, and which they may only prepare, prevents drift. It also gives your quality control reviewer a standard to test against. A mortgage quality control plan usually samples files for exactly this: whether the person who signed the decision had the authority to make it.
When a processor should not make the underwriter's call
A processor should not make the underwriter's call whenever the answer depends on the guideline, a risk judgment or an exception. Even an experienced processor who could reach the same answer should prepare it and pass it on. The decision belongs to the person whose name and authority sit on the approval.
Calls that stay with the underwriter
- Excluding or counting an irregular deposit in qualifying income.
- Accepting a letter of explanation as enough for an NSF cluster.
- Treating a transfer from a business account as eligible funds.
- Granting any exception to a program limit.
What the processor does instead
The processor writes up the facts: the item, the date, the amount, the borrower's explanation and the documents attached. Then the processor flags it for the underwriter. That record serves the decision now and the audit later.
TrueBankFlow fits on the processor's side of this line: it organizes and summarizes the statements, flags out-of-pattern deposits and NSF events, and leaves the decision with the underwriter. Lending teams can request a spot.