Supporting Document Verification and Identity Check Checklist
Use this checklist to verify borrower identity, income, assets, liabilities, and lender-specific documents before lodgement. It helps catch missing evidence, mismatches, and unresolved stipulations before the file is submitted.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Mortgage Lending · Consumer Finance · Brokerage · Banking · Credit Unions
Overview
This checklist is for reviewing a borrower file before lodgement or submission. It walks the reviewer through the core evidence that usually determines whether a file is complete: application identifiers, government-issued identity documents, income evidence, asset and liability statements, lender-specific forms, disclosures, and any outstanding stipulations.
Use it when a file needs a documented pre-submission quality check, especially where responsible-lending, AML/KYC, or lender policy requires proof that the supporting documents match the application. It is useful for both manual and digital workflows because it records what was checked, what matched, and what still needs follow-up. The checklist is also a good fit when multiple people touch the file and you need a clear handoff record.
Do not use it as a substitute for underwriting judgment, legal review, or a full compliance program. It is not meant for post-settlement audits, fraud investigations, or customer onboarding outside a lending context unless you adapt it. If your product has unusual document rules, self-employed income treatment, foreign income, or enhanced due diligence requirements, customize the checklist so the reviewer is not forced to improvise. The value of this template is that it turns a scattered document chase into a repeatable file verification step with clear deficiencies and sign-off.
Standards & compliance context
- This template supports responsible-lending and file-completeness controls by creating a documented record of identity, income, and asset verification before submission.
- It can be aligned with AML/KYC expectations by capturing identity checks, source-of-funds explanations, and exception approvals in one place.
- For regulated lenders, the checklist should be mapped to internal policy, lender conditions, and applicable consumer credit or banking compliance requirements.
- If your process includes privacy or consent forms, keep those items in the checklist so the file shows authority to collect and use borrower information.
- Where enhanced due diligence is required, add custom fields for additional verification rather than relying on the base checklist alone.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Inspection Details
This section anchors the file review so every later check can be tied back to the correct application, reviewer, and checklist version.
-
Application file identifier recorded
Enter the loan application, deal, or file reference used for this inspection.
- Borrower name matches file records
- Inspection date and reviewer captured
-
Lender or product-specific checklist version confirmed
Record the lender policy, product guide, or internal checklist version used for this review.
Identity Verification
This section matters because identity mismatches, expired IDs, and incomplete verification are common reasons a file cannot proceed.
- Primary government-issued photo ID provided and legible
- Identity document details match applicant record
- Secondary identity or verification method completed where required
- Name, date of birth, and address are consistent across documents
- Identity verification exceptions documented and approved
Income and Employment Evidence
This section confirms the borrower can support the declared income with current, consistent evidence.
- Recent pay slips or income statements provided
- Income documents are within acceptable recency period
- Employment status verified against supporting evidence
- Tax returns, W-2s, or equivalent income evidence provided where required
- Declared income aligns with supporting documents
Assets, Liabilities, and Funds Verification
This section helps the reviewer validate source of funds, savings, and debt disclosures before the file moves forward.
- Recent bank statements provided for required period
- Bank statements show account holder name and account details
- Deposit funds and savings source documented
- Large or unusual transactions explained and supported
- Declared liabilities supported by statements or credit evidence
Lender-Specific Documents and Compliance
This section captures the forms, disclosures, and consent items that often vary by lender or product.
- All lender-specific forms completed and signed
- Required disclosures provided to applicant
- Privacy, consent, and authority to act documents complete
- Outstanding lender stipulations identified and tracked
Review Outcome and Sign-Off
This section records the final decision, outstanding deficiencies, and the reviewer’s accountability for the file.
- File is ready for lodgement
-
Deficiencies or non-conformances documented
List any missing, inconsistent, or expired documents and the required corrective action.
- Inspector signature
How to use this template
- 1. Enter the application file identifier, borrower name, inspection date, reviewer name, and the lender or product checklist version before you start checking documents.
- 2. Compare the borrower’s primary ID, secondary verification method if required, and personal details against the application record and mark any mismatch as a documented exception.
- 3. Review income evidence, employment proof, tax documents, and bank statements against the declared figures and note whether each item is current and acceptable for the file type.
- 4. Confirm that assets, liabilities, source-of-funds explanations, lender forms, disclosures, and consent documents are present, signed, and consistent with the application.
- 5. Record every deficiency or non-conformance, assign follow-up actions for missing or unclear items, and only mark the file ready for lodgement when all required evidence is complete.
- 6. Capture the final reviewer sign-off and retain the completed checklist with the file so the submission trail shows what was verified and when.
Best practices
- Check the borrower name, date of birth, and address across every document before you review the numbers, because identity mismatches often explain later income or asset discrepancies.
- Treat unreadable scans, cropped pages, and missing statement pages as deficiencies, not minor issues, because they can hide critical information.
- Flag large or unusual deposits with a source explanation and supporting evidence instead of accepting a verbal explanation alone.
- Use the lender’s current checklist version for every file and retire outdated versions so reviewers do not miss product-specific stipulations.
- Separate critical verification failures from administrative omissions so the reviewer can escalate identity or source-of-funds issues immediately.
- Document the exact document reviewed, the date range covered, and any exception approval so the file can be reconstructed later without guesswork.
- If the borrower is self-employed, add the required business financials and tax evidence up front rather than waiting for underwriting to request them.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this checklist used for?
This checklist is used to confirm that a borrower file is complete and internally consistent before lodgement or submission. It focuses on identity, income, assets, liabilities, and lender-specific documents so missing evidence is caught early. It is especially useful for responsible-lending, AML/KYC, and pre-approval review workflows.
Who should complete the checklist?
It is usually completed by a loan processor, credit analyst, compliance reviewer, or another authorized file reviewer. The person completing it should be able to compare source documents against the application record and flag discrepancies. If your process requires escalation, the reviewer should route exceptions to the appropriate approver before sign-off.
How often should this checklist be used?
Use it for every file that requires document verification before lodgement, not just for higher-risk applications. Many teams run it at the end of document collection and again immediately before submission if the file has changed. Re-running it after new documents are added helps prevent stale or incomplete evidence from slipping through.
Does this checklist replace AML/KYC or responsible-lending procedures?
No. It supports those workflows by standardizing what gets checked and recorded, but it does not replace your institution’s policies, legal review, or jurisdiction-specific obligations. You should align the checklist with your internal AML/KYC controls, responsible-lending requirements, and lender conditions. If your process includes enhanced due diligence, add those steps as custom fields or sections.
What are the most common mistakes this template helps catch?
Common misses include expired or unreadable ID, income evidence outside the acceptable recency window, bank statements that do not match the applicant name, and unexplained large deposits. Teams also miss lender-specific forms, unsigned disclosures, or stipulations that were never cleared. This checklist makes those deficiencies visible before the file is sent onward.
Can I customize this for different lenders or products?
Yes. The template is designed to be adapted for lender-specific document lists, product rules, and approval thresholds. You can add required forms, change the acceptable recency period for income evidence, or include extra verification steps for self-employed borrowers, guarantors, or joint applicants. Many teams maintain one base checklist and duplicate it by lender or product type.
How does this fit with digital document systems and integrations?
It works well alongside document management systems, loan origination platforms, and identity verification tools. You can use it to confirm what was received, what was verified, and what still needs follow-up even if the source documents live elsewhere. If your workflow supports attachments or comments, link the checklist items to the underlying evidence and exception notes.
What should I do when there is a discrepancy or exception?
Document the discrepancy clearly, note which document or data point conflicts, and mark whether the issue is resolved or still open. Do not treat an exception as a pass unless your policy allows it and the required approval has been recorded. If the mismatch affects identity, income, or source-of-funds verification, escalate it before lodging the file.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
MangoApps in Okta Integration Network automates user provisioning, SSO, and access management for stronger security and less admin work.
Ready to use this template?
Get started with MangoApps and use Supporting Document Verification and Identity Check Checklist with your team — pricing built for small business.
