Why it matters
A lender that opens a package and finds a missing page, last year's statement or someone else's ID declines or stalls the file, and remembers it. Reviewing each document before it can go out is the processor's main quality check. In the CRM, only received or verified documents can be attached to a submission, and a rejected document drops out of the checklist.
Step by step: review an upload
- 1Open the deal's Documents & stips tab and scroll to Documents. Each file shows its type, status (Received, Verified, Rejected), statement month, page count, size, and who uploaded it when.
- 2Click the file name to open it in a new tab. Every download is logged.
- 3Check it against the checklist below.
- 4If it is good, click Verify. The matching checklist item becomes Approved.
- 5If it is wrong, open the menu and choose Reject…. Give a Reason (missing pages, blurry, wrong month). The checklist item goes back to Requested, so it shows up in the next stips request.
- 6If it was uploaded as the wrong type, use the menu's Change type to options (application, bank statement, MTD statement, driver's license, voided check). For any other type, remove the file and upload it again with the right Document type.
Before you verify
0 of 7Suspect an altered statement? Do not verify it. Leave an Underwriting note and tell your manager. See Red flags and fraud signals.
Conditions on the Underwriting tab
The Underwriting tab lists the same checklist items as Conditions, with a decision on each. Processors and managers can decide them.
- Approve a condition when it is satisfied. An approved condition counts as done even if no file of that type is on the deal (useful for a verbal landlord check).
- Decline… with a reason when it is not acceptable. A declined condition stays open whatever is uploaded, until you Reopen it.
- Add condition adds one or more condition types at once, such as Landlord / lease verification or UCC search.
- Underwriter notes save as you type and keep a version history.
Who can do it
Processors, managers and owners can upload, verify, reject and remove documents. Agents can upload and verify but not remove. Removing a document takes it off the deal and the checklist; the file is kept for the audit trail.
Try it in the app
Signed in? Open the screen this lesson covers.
Finished this lesson?
0 of 8 lessons in Processor playbook
Progress is saved in this browser. Sign in to keep it across devices.
Related lessons
- Processor playbookYour document queue: finding the files that need youThere is no separate document inbox: build your queue from the Deals board, stage filters and each deal's checklist count, then work it oldest first.
- Reading bank statementsRed flags and fraud signals in bank statementsA checklist for altered statements: edited PDFs, font and math mismatches, round-number and stuffed deposits, mismatched names and dates, and how to verify.
- Underwriting and analysisDecision notes and the audit trailWrite the underwriter's notes, decide conditions, record decline reasons and know which actions the CRM logs, so every decision on a file can be explained.
- Compliance basicsRecordkeeping checklist for every dealWhat to keep on each deal so you can answer a merchant, funder or regulator: application, consents, disclosures, statements, offers, contracts and messages.