Consumer Loan Application Intake SOP
Use this consumer loan application intake SOP to verify the applicant, collect required documents, obtain credit authorization, and route a complete file for underwriting or decision.
Trusted by frontline teams 15 years of frontline software
Built for: Consumer Lending · Credit Unions · Community Banks · Fintech Lending
Overview
This Consumer Loan Application Intake SOP template standardizes the front-end workflow for accepting a consumer loan application and preparing it for decision. It covers the practical steps a loan officer or intake specialist performs: verifying the applicant and loan request, giving the checklist and disclosures, collecting the completed application and supporting documents, checking the file for completeness, obtaining credit authorization, pulling credit, reviewing obvious exceptions, and submitting the file or escalating it when something is missing or out of tolerance.
Use this template when your team needs a repeatable intake process for personal loans, installment loans, secured consumer loans, or similar products. It is especially useful when multiple roles touch the file, when documents arrive in stages, or when you need a clear audit trail of who verified what and when. The structure helps reduce rework, missed disclosures, and premature underwriting submissions.
Do not use this SOP as a substitute for underwriting policy, legal review, or product-specific credit criteria. It is not the place to define approval thresholds, pricing rules, or adverse action logic. If your process is fully automated, use this template to document the human control points, exception handling, and escalation path around the system workflow.
Standards & compliance context
- The template supports ISO 9001-style documented information control by making the intake steps, verification points, and handoff record explicit.
- It helps maintain a defensible audit trail for consumer lending by capturing authorization, document collection, and exception escalation in a consistent sequence.
- If your process involves sensitive or hazardous operational controls, the same structure can support internal governance expectations similar to permit-to-work and verification-based procedures, though this template is for administrative lending intake.
- Add institution-specific privacy notices, credit authorization language, and retention rules before use so the SOP matches your legal and policy requirements.
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
Steps
This section matters because it defines the exact sequence the intake role follows from verification through escalation.
-
Verify the applicant and loan request
The loan officer verifies the applicant’s identity using approved institution procedures and confirms the requested consumer loan product, amount, and purpose. The loan officer records the applicant name, contact information, and application date in the loan origination system.
If identity cannot be verified or the request is outside approved lending authority, the loan officer escalates the file to a supervisor before continuing.
-
Provide the application checklist and disclosures
The loan officer provides the consumer loan application, required disclosures, and the document checklist for the selected loan product. The loan officer explains which items are required, which items are optional, and the deadline for returning missing documents.
The loan officer confirms the applicant understands any authorization language related to credit reporting and information verification.
-
Perform AML/KYC screening
The loan officer performs AML/KYC screening per 31 USC §5318 and FinCEN guidance, documenting beneficial ownership information and source of funds as required by institution policy.
If screening results indicate a potential match, suspicious activity, or unresolved identity concern, the loan officer escalates the file according to compliance procedures before continuing.
-
Confirm applicant age and legal capacity
The loan officer confirms the applicant is at least 18 years old and has the legal capacity to contract under applicable law and institution policy.
If the applicant is a minor, under guardianship, or otherwise lacks capacity, the loan officer stops processing and escalates the file for supervisory review.
-
Document loan purpose
The loan officer documents the stated loan purpose and verifies it is consistent with the selected consumer loan product and institution policy.
If the purpose is unclear, inconsistent, or not permitted for the product, the loan officer requests clarification or escalates the file before proceeding.
-
Collect the completed application and supporting documents
The loan officer collects the completed application and reviews the submitted documents against the checklist. The loan officer captures or uploads all received documents into the loan file and marks any missing items as outstanding.
Required documents may include income verification, government-issued identification, proof of address, and collateral information if applicable.
-
Review the file for completeness
The loan officer verifies that all required fields are completed, signatures are present where required, and supporting documents are legible and current. The loan officer confirms that any missing or inconsistent information is documented in the file.
If required information is missing, expired, or inconsistent, the loan officer contacts the applicant for correction or escalates the issue according to lending policy.
-
Obtain credit authorization and pull credit
The loan officer confirms the applicant has provided valid authorization to access credit information before initiating the credit pull. The loan officer retrieves the credit report through approved systems and associates the report with the application file.
If authorization is missing or invalid, the loan officer stops the process and obtains the required consent before proceeding.
-
Review credit results for obvious exceptions
The loan officer performs a preliminary review of the credit report for obvious exceptions such as identity discrepancies, recent delinquencies, bankruptcies, or fraud alerts. The loan officer records any notable findings in the application notes.
If the report contains a fraud alert, identity mismatch, or other exception outside normal processing tolerance, the file is escalated for supervisory review.
-
Submit the completed file for decision
The loan officer submits the completed application, supporting documents, and credit report to underwriting or the designated decision authority according to institution workflow. The loan officer records the submission timestamp and the assigned reviewer or queue.
The loan officer notifies the applicant that the file has been submitted and explains the next expected milestone.
-
Escalate the file with exceptions
The loan officer documents the exception, attaches any supporting notes, and escalates the file to the appropriate supervisor, underwriter, or fraud review queue. The loan officer does not submit the file for standard decision until the exception is resolved or an exception-based review is completed.
The loan officer records the escalation reason and the person or team notified.
-
Regulatory Compliance Checkpoints
The loan officer confirms required consumer lending compliance checks are completed before the file advances to decisioning.
(a) The loan officer confirms TILA disclosures were provided per 12 CFR 1026.19 at least 3 business days before consummation when applicable.
(b) The loan officer verifies AML/KYC information per FinCEN guidance, including name, date of birth, address, and government-issued ID type.
(c) The loan officer documents Fair Lending review notes and confirms the file was processed without prohibited discrimination or inconsistent treatment.
How to use this template
- 1. The process owner configures the application checklist, disclosure set, required documents, and escalation thresholds for the specific consumer loan product.
- 2. The intake role verifies the applicant identity and confirms the requested loan product, amount, and purpose against the submitted application.
- 3. The intake role provides the checklist and required disclosures, then collects the signed application and supporting documents from the applicant.
- 4. The intake role reviews the file for completeness, obtains credit authorization, pulls credit, and checks the results for obvious exceptions or deviations.
- 5. The intake role submits the completed file for underwriting or decision and escalates any incomplete, unauthorized, or exception-bearing file to the designated reviewer.
Best practices
- Verify the applicant identity before discussing loan terms, pulling credit, or accepting sensitive documents.
- Use a product-specific checklist so the intake role requests the same documents for every applicant in that loan category.
- Record the exact date, time, and method of credit authorization before any bureau pull occurs.
- Flag missing signatures, expired documents, and mismatched names immediately instead of waiting until the end of the review.
- Define clear escalation criteria for income gaps, identity mismatches, adverse credit findings, and incomplete disclosures.
- Keep the intake file organized in the same order every time so underwriting can review it without hunting for documents.
- Document every exception with the reason, the owner, and the next action so the file has a traceable handoff.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this consumer loan application intake SOP cover?
It covers the front-end intake process for a consumer loan file: applicant verification, application checklist delivery, document collection, completeness review, credit authorization, credit pull, and submission for decision. It also includes an exception path for missing information or obvious credit issues. The template is meant to standardize what happens before underwriting, not replace underwriting criteria. Use it as the intake control point for a branch, call center, or lending operations team.
Who should run this SOP?
A loan officer, lending associate, branch representative, or centralized intake specialist can run it, as long as the role is trained on identity verification, disclosure handling, and credit authorization requirements. A competent person should own the review for completeness and escalation. If your process separates intake from decisioning, this SOP should stop at submission and hand off cleanly to underwriting or an automated decision engine. The assigned role should be named in the template before rollout.
How often should this SOP be used?
It should be used for every consumer loan application that enters the intake queue, whether the application is submitted in person, by phone, or through a digital channel. The checklist and disclosure steps should happen at the time of intake, before any credit pull or file submission. If your institution accepts incomplete applications, the SOP should define when to pause, when to request missing items, and when to close the file as incomplete. Consistent cadence reduces rework and non-conformance.
Does this template address regulatory or compliance needs?
Yes, at a process level it supports documented information control, disclosure handling, and traceable decision handoff. It can be adapted to align with consumer lending compliance expectations, privacy controls, and internal audit requirements. The template does not replace legal review or institution-specific policy, but it helps ensure the intake record shows who verified what, when authorization was obtained, and why a file was escalated. Add your required notices and retention rules before use.
What are the most common mistakes this SOP helps prevent?
Common failures include missing signatures, incomplete income or identity documents, pulling credit before authorization, and sending an incomplete file to underwriting. Another frequent issue is failing to document exceptions clearly, which makes later review difficult. This SOP also helps prevent inconsistent treatment between applicants by forcing the same checklist and verification steps every time. That consistency is especially important when multiple staff members handle intake.
Can I customize this SOP for different loan products?
Yes, and you should. Consumer installment loans, auto loans, unsecured personal loans, and secured loans often require different document sets, disclosure packets, and exception thresholds. Keep the same intake structure, but swap in product-specific checklists, verification rules, and escalation criteria. If you serve multiple products, add a field or branch in the template so the actor knows which checklist applies.
How does this fit with digital applications and integrations?
The SOP works well as a manual control layer around an online application portal, CRM, document management system, or loan origination system. You can map each step to a system action, such as uploading documents, logging authorization, or triggering a credit bureau pull. If your workflow is automated, keep the human verification and exception review steps explicit so the process does not skip control points. The template is also useful for audit trails because it clarifies what should be recorded in each system.
How is this better than ad-hoc intake?
Ad-hoc intake often creates uneven document requests, missed disclosures, and unclear handoffs to underwriting. This SOP gives the team a repeatable sequence, clear ownership, and defined escalation criteria for exceptions. That makes it easier to train new staff, review files, and spot where delays are happening. It also reduces the chance that an incomplete or unauthorized file reaches decisioning.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
AI employee self-service assistants cut HR and IT support time with instant answers, automated routing, and better employee experience.
-
A vendor-agnostic checklist covering architecture, frontline access, AI, compliance, and payroll to evaluate any scheduling platform.
-
See how Power Tables and Live Boards give frontline operations structured, queryable data instead of scattered spreadsheets and chat threads.
Ready to use this template?
Get started with MangoApps and use Consumer Loan Application Intake SOP with your team — pricing built for small business.
