Prepare cleaner underwriting files before the workday begins

What enters the system

UND-10442 is a purchase file: Sofia Alvarez, 641 W Concord, 20% down.

1. 01

   Application and docs

   1003, paystubs, W-2s, bank statements, ID, and the purchase contract from nCino.

2. 02

   Verification services

   Employer / SOS lookup, bureau pull for the file, and any VOE the shop already uses.

3. 03

   Policy

   Meridian’s written income and deposit guidelines — including that 45% DTI is a guideline, not a cutoff the machine may apply.

What happens overnight

1. 01

   Completeness

   Required documents are checked in. Missing pages and stale stubs are requested on the approved borrower template.

2. 02

   Verification

   Employer legal name is compared to the application. “Northline Mfg” vs “Northline Manufacturing Inc.” is an exception, not a fail.

3. 03

   Income and DTI

   Base and overtime are extracted separately. DTI is shown with and without OT when OT appears on a configured fraction of stubs.

4. 04

   Exception detection

   Large deposits without a source note, NSF patterns, and occupancy inconsistencies are listed. They are not fraud conclusions.

5. 05

   File, not decision

   Complete files are placed on the underwriter’s morning desk. Incomplete files stay in exceptions. No credit recommendation is written to Salesforce or nCino.

What the underwriter sees in the morning

Maya Chen has nine files she can underwrite and six that still need work. UND-10442 is in the second group because overtime is tagged recurring and a $9,400 deposit has no source note.

She can open the stub, the dual DTI worksheet, the statement, and the bureau pull. The bureau is attached as evidence for her. The engine does not turn 734 FICO and 41.2% DTI into an approve.

Human authority and lending governance

How a correction becomes a validated improvement

If Maya excludes overtime, UND-10442 becomes a labeled example: OT on three of four stubs is not enough in this shop. If she includes it, the opposite example is stored — with her reason.

A hypothesis that always treats overtime as recurring fails Meridian history and is discarded. Dual DTI display and large-deposit routing pass. The winning model changes how the file is prepared. It does not change who may lend.

What a 30-day pilot measures

One product (purchase, in this walkthrough). Credit performance is out of scope for the pilot.

Implementation

Systems

nCino or Encompass, bureau, CRM, e-sign, and the shop’s VOE / SOS tools.

Data required

Closed files with underwriter conditions, OT decisions, and deposit-source notes — the labeled history.

Deployment

Hardware in the institution. Shadow on historical files, supervised prep, then LOS status writes. Credit memo drafts stay off unless compliance signs a later workflow.

Who operates it

Underwriters own every credit action. Processors still collect. Compliance owns adverse action and fair-lending review. We do not sit on committee.

Security and deployment architecture

Applications, stubs, and bureau data stay inside the institution. The engine calls nCino and Experian the way your processors already do, from your network.

Lending-specific governance — ECOA, FCRA, adverse action, model risk — is why this workflow stops at the file. If someone asks the model “should we lend,” the configured answer is that it will not.