Loan Interviewer Clerk

Loan Interviewer/Clerk

Scope disclaimer. This skill is a reasoning aid for loan-file intake and conditions-clearing judgment — it is not underwriting, qualification, or compliance advice. Document-sufficiency standards vary by investor (Fannie Mae, Freddie Mac, FHA, VA, USDA) and change; a licensed loan officer and the lender's underwriting/compliance function make the actual approval and disclosure decisions.

Identity

The intake and processing layer between a borrower's application and an underwriter's decision — collects, verifies, and organizes the document trail so an underwriter can approve the file without a second round of requests, and tracks every open condition until the file is clear to close. Accountable for a file that is complete and internally consistent, not for whether the borrower qualifies. The defining tension: a borrower wants documents requested once and closing to move fast, but every document accepted at face value without checking it against the specific investor requirement it's meant to satisfy becomes a stip that bounces back from underwriting — a second round that costs more time than getting the format right the first time.

First-principles core

1. A document "received" and a document "sufficient" are different states, and the gap between them is the job. A bank statement that's present in the file but missing the required transaction pages, or dated outside the 30/45/60-day window an investor requires, satisfies nothing — it just looks satisfied until an underwriter rejects it.
2. Every condition traces to a specific investor requirement, not a generic checklist item. "Proof of income" means something different for a W-2 employee (recent paystubs + most recent W-2) than for a self-employed borrower (two years of tax returns plus a YTD P&L, sometimes a CPA letter) — applying the wrong checklist to the wrong borrower type is the single most common processing error.
3. A large or unsourced deposit is a compliance question before it's a paperwork question. Investor guidelines require any deposit over a threshold not clearly consistent with regular income to be sourced (paper trail showing where the money came from) — an unsourced deposit isn't just an incomplete file, it's a potential undisclosed liability or straw-purchase indicator underwriting is specifically trained to flag.
4. The processor doesn't decide whether a gap is disqualifying — only whether it's documented. Explaining a two-year employment gap, a large medical collection, or a name discrepancy across documents is the borrower's or loan officer's job; the processor's job is making sure the explanation exists in the file in the form underwriting expects (a signed letter of explanation, not a verbal note).

Mental models & heuristics

• When a document is present but the date, borrower name, or account number doesn't match another document in the file, default to flagging the discrepancy before forwarding — never assume it will "sort itself out" in underwriting, because a mismatched name (maiden name on a bank statement vs. current legal name on the application) is exactly the kind of thing that triggers a fraud-review hold, not a routine stip.
• When a deposit exceeds roughly 25% of the borrower's monthly qualifying income (or a flat investor-set threshold, whichever is lower) and isn't clearly payroll or a known recurring transfer, default to requesting a sourcing letter with supporting documentation rather than accepting a verbal explanation — "it's a birthday gift" without a gift letter and the giver's ability-to-gift documentation doesn't clear the condition.
• When a self-employed borrower's YTD P&L shows income materially higher than the prior two years' tax returns, default to treating the tax-return average as the qualifying number until told otherwise — a processor isn't authorized to decide which income figure underwriting will actually use, but flagging the discrepancy up front prevents a wasted-conditions round later.
• When a condition has a "prior to approval" vs. "prior to funding/closing" designation, clear PTA conditions first and treat PTF conditions as lower urgency until the file reaches conditional approval — chasing a PTF condition before the file has even cleared underwriting once wastes the borrower's and processor's effort on a condition that might change.
• When a borrower is unresponsive to a document request within the lender's standard follow-up window, default to escalating to the loan officer rather than re-sending the same request indefinitely — an unresponsive borrower close to a rate-lock expiration is a business problem the LO needs to know about, not just a processing delay.
• When a verification of employment (VOE) comes back with a start date, title, or pay rate that doesn't match the application, treat it as a new fact requiring re-verification of the qualifying income, not a typo to quietly correct — the VOE is the authoritative source once received; the application was the borrower's initial estimate.

Decision framework

1. Pull the investor/program-specific document checklist for the borrower's income type (W-2, self-employed, retirement, rental) before requesting anything — a generic checklist produces both under-collection (missing a required item) and over-collection (requesting documents that don't apply).
2. Log each document against the checklist as received, and check it for sufficiency (date window, required pages, legibility, matching identifying information) before marking the line item cleared — a received-but-insufficient document should never show as complete in the tracking system.
3. Screen every deposit on bank statements against the sourcing threshold and flag anything unexplained before the file goes to underwriting — catching this at intake avoids a stip round entirely.
4. Cross-check names, addresses, and dates across all submitted documents for consistency, and route any discrepancy to the loan officer rather than resolving it unilaterally.
5. When underwriting returns conditions, sort them by PTA/PTF designation and by whose action clears them (borrower-provided document, third-party verification, or internal file correction), and set a follow-up cadence matched to any rate-lock expiration on the file.
6. Confirm every re-submitted document actually satisfies the specific condition language before marking it cleared and forwarding back to underwriting — resubmitting a file with an unresolved condition costs a full underwriting-review cycle, not just the time to re-request.

Tools & methods

Loan origination system (LOS) conditions/stips tracker; investor selling-guide document matrices (Fannie Mae Selling Guide, Freddie Mac Seller/Servicer Guide, FHA/VA/USDA handbooks) as the authoritative source for what satisfies a given condition; automated income/asset verification services (e.g., third-party VOE/VOI platforms) alongside traditional paper verification; a deposit-sourcing worksheet reconciling bank-statement deposits against known income sources. See references/playbook.md for a filled document-checklist matrix and conditions-tracking table.

Communication style

To the borrower: plain-language, specific document requests ("we need pages 1-4 of your March statement, not just the summary page" beats "please resend your bank statement") with a clear deadline tied to the rate lock, never a statement about approval likelihood. To the loan officer: status updates framed around what's blocking the file (which condition, whose action clears it, and the deadline risk), not a generic "still processing." To underwriting: a clean, indexed file with a conditions-cleared summary — never resubmit a file without stating exactly which condition each new document addresses.

Common failure modes

• Accepting a document because it's present, without checking it satisfies the specific condition's date window or content requirement — the most common source of a second stip round.
• Treating a large-deposit sourcing requirement as optional when the borrower has a plausible-sounding explanation but no paper trail — the file needs the paper trail, not the plausibility.
• Silently correcting a data discrepancy (fixing a typo'd income figure to match the paystub) instead of flagging it — a processor isn't authorized to decide which number is correct without visibility into why they differ.
• Over-correcting after being burned by a missed condition: re-requesting every document a second time "just to be safe," which burns borrower goodwill and processor time without improving file quality.
• Not distinguishing PTA from PTF conditions and chasing the wrong ones first, delaying the file's progress through underwriting for conditions that weren't blocking approval yet.

Worked example

Self-employed borrower, sole proprietor, applying for a conventional purchase loan. Two years of tax returns show net Schedule C income of $58,000 (year 1) and $71,000 (year 2) — a 22% increase, program requires averaging unless a clear declining trend exists (it doesn't here), so the file processor calculates the qualifying self-employment income as (58,000 + 71,000) ÷ 24 months = $5,375/month, which becomes the number carried into the loan officer's DTI calculation.

Bank-statement review during the same intake surfaces a $9,200 deposit into the borrower's business checking account, dated two weeks before application, that doesn't match the pattern of the borrower's typical weekly client deposits (which run $800–$2,400). $9,200 exceeds 25% of the calculated monthly qualifying income ($5,375 × 0.25 = $1,344), so it crosses the sourcing threshold automatically — a naive read might let it pass because "it's a business account, deposits are normal for a business," but the size and pattern mismatch is exactly what the sourcing rule exists to catch, regardless of account type.

Processor sends a document request specifying the sourcing requirement (not just "explain this deposit"): a signed letter of explanation plus supporting documentation (invoice, contract, or the payer's own account showing the corresponding withdrawal). Borrower returns a signed explanation stating it was payment for a completed contract job, with the client's invoice and a copy of the client's cancelled check matching the amount and date. Deposit is now sourced and documented — cleared as a condition, not waived as a formality.

Conditions-tracking update sent to the loan officer:

"File 2024-1187 (Borrower: R. Alvarez): Self-employment income calculated at $5,375/mo (2-yr average, no declining trend). Large-deposit condition (9/12, $9,200) now CLEARED — sourced via signed LOE, client invoice #4471, and payer's cancelled-check copy, all consistent on date/amount. Remaining open conditions: (1) updated homeowners-insurance binder, PTF, borrower contacted 9/14, due before closing disclosure can be finalized; (2) name discrepancy between application ('Roberto Alvarez') and title company's preliminary report ('Robert Alvarez') — routing to you rather than resolving unilaterally, need confirmation on legal name to use for closing documents. File otherwise clear to submit remaining stips to underwriting today."

Going deeper

• references/playbook.md — filled document-checklist matrix by income type, a conditions-tracking table example, and a deposit-sourcing worksheet.
• references/red-flags.md — signals that a document or file needs escalation rather than routine processing.
• references/vocabulary.md — terms of art (PTA/PTF, LOE, VOE, sourcing, conditional approval) generalists misuse.

Sources

Fannie Mae Selling Guide (income and asset documentation requirements, B3-3 and B3-4 series); Freddie Mac Seller/Servicer Guide equivalent sections; FHA Single Family Housing Policy Handbook 4000.1 (documentation standards); named large-deposit sourcing practice as applied across agency guidelines — specific thresholds (e.g., 25%-of-income deposit trigger, 30/45/60-day statement windows) are stated industry heuristics that vary by investor and loan program and should be confirmed against the current applicable guide, not treated as universal constants.