Documentation Requirements

Overview

Credit products can specify required documentation that must be collected during the lending process. Documentation requirements define which document types are needed and at which stages of the process they must be provided.

Configuration Architecture

Two-Layer Configuration:

SDK Layer: Document States and Types

Configured By: Implementation team during platform setup

SDK Configuration Defines:

1. Document States: When documents are required in the process

   • Application Submission

   • Underwriting Stage

   • Pre-Approval

   • Before Disbursement

   • Post-Disbursement (servicing docs)

2. Document Types: Available document categories

   • Proof of Income (pay stubs, tax returns, bank statements)

   • Identity Verification (passport, national ID, driver's license)

   • Address Verification (utility bills, lease agreements)

   • Employment Verification (employment letter, HR confirmation)

   • Collateral Documentation (vehicle registration, property title)

   • Bank Statements

   • Tax Returns

   • Business Financial Statements (for business loans)

SDK Documentation:

• Document States Configuration - Defining process stages

• Document Type Definitions - Available document categories

Admin Panel Layer: Product-Specific Requirements and Templates

Configured By: Business users, product managers

Admin Panel Configuration:

1. Select which document types are required for specific product

2. Create document templates (for generated documents)

Note: Document stage assignments, validation rules, and exception handling are all configured at the SDK level. The Admin Panel allows selection of required document types and template creation only.

Configuring Documentation Requirements for Products

Accessing Documentation Configuration

Navigation:

1. Navigate to Settings → Credit Products

2. Select the product to configure

3. Locate the Documentation Requirements field

Important: Documentation Requirements is a field on the Credit Product form, not a separate tab. The field allows you to select which SDK-defined document types are required for this product.

Step 1: Select Required Document Types

View checklist of available document types (defined in SDK) and select which are required for this product:

Example for Personal Loan Product:

Required Documentation Checklist:
☑ Proof of Income
  - Pay Stubs (last 3 months)
  - Bank Statements (last 6 months)
☑ Identity Verification
  - National ID or Passport
☑ Address Verification
  - Utility Bill or Lease Agreement
☐ Collateral Documentation (not applicable for unsecured)
☐ Business Financial Statements (not applicable for personal loan)

Example for Auto Loan Product:

Required Documentation Checklist:
☑ Proof of Income
☑ Identity Verification
☑ Address Verification
☑ Collateral Documentation
  - Vehicle Registration
  - Vehicle Insurance Policy
  - Vehicle Inspection Report
☐ Business Financial Statements

Example for Business Loan Product:

Required Documentation Checklist:
☑ Proof of Income (business + personal)
☑ Identity Verification (business owners)
☑ Address Verification (business address)
☑ Business Financial Statements
  - Balance Sheet
  - Income Statement
  - Cash Flow Statement (last 2 years)
☑ Tax Returns
  - Business Tax Returns (last 2 years)
  - Personal Tax Returns of owners
☐ Collateral Documentation (if secured)

Step 2: Document Stage Assignment (SDK-Configured)

Important: Document stage assignment (when documents are required in the process) is configured at the SDK level, not in the Admin Panel. The Admin Panel displays these assignments but cannot modify them.

Your development team configures which documents are required at each stage:

Example Stage Assignments (configured in SDK):

Document Type: Proof of Income
Required At Stage: Underwriting Stage
Result: Proof of Income must be uploaded before underwriting can begin

Multiple Stages Example (configured in SDK):

Document Type: Vehicle Insurance Policy
Required At Stages:
- Pre-Approval (proof of insurability)
- Before Disbursement (active policy required)
Result: Initial insurance quote needed for approval, active policy before funds released

To Change Stage Assignments: Contact your development team to modify SDK configuration.

Step 3: Configure Document Templates (Admin Panel)

If the system generates documents for the product (e.g., loan agreements, disclosure forms):

1. Navigate to Settings → Document Templates

2. Create or select templates for this product

3. Templates are associated with products separately

Note: Template creation is covered in Document Templates.

Example:

Product: Personal Loan

Generated Documents:
- Loan Offer Letter → Template: "Personal Loan Offer 2025"
  - Generate on: Application Approved (SDK-configured trigger)
  
- Loan Agreement → Template: "Personal Loan Agreement Standard"
  - Generate on: Offer Accepted (SDK-configured trigger)

Step 4: Validation Rules (SDK-Configured)

Important: Document validation rules are configured at the SDK level. The Admin Panel cannot configure validation rules.

What SDK Configures:

• Expiration date checking

• Document age requirements

• File format restrictions

• File size limits

Example Validation (configured in SDK):

Document Type: National ID

Validation Rules:
✓ Must not be expired
✓ Maximum age: Current (not expiring within 6 months)
✓ Accepted formats: PDF, JPG, PNG
✓ Maximum file size: 5MB

Note: There is no OCR text extraction feature in the Admin Panel. Any automated data extraction from documents requires custom SDK implementation.

To Change Validation Rules: Contact your development team.

Step 5: Exception Handling (SDK-Configured)

Important: Exception handling rules for missing or invalid documents are configured at the SDK level.

What SDK Configures:

• Process blocking rules

• Manual override permissions

• Alternative documentation options

• SLA and auto-decline rules

Example (configured in SDK):

Document Type: Proof of Income

If Missing or Invalid:
→ Block underwriting process
→ Send notification to applicant
→ SLA: 5 business days
→ If not provided: Route to exception workflow

Admin Panel Role: Users can perform manual overrides (if permitted by their role) and view document status. Cannot configure the exception handling rules themselves.

Product-Specific Documentation Examples

Personal Loan (Unsecured)

Document Requirements:

• Proof of Income: Required at Underwriting

• Identity Verification: Required at Application Submission

• Address Verification: Required at Underwriting

• Credit Report: Auto-pulled by system

Documentation Template:

• Loan Offer Letter

• Loan Agreement

• Disclosure Documents (regulatory)

Auto Loan (Secured)

Document Requirements:

• All Personal Loan documents PLUS:

• Vehicle Information: Required at Application Submission

• Vehicle Inspection Report: Required at Pre-Approval

• Vehicle Insurance: Required at Pre-Approval and Before Disbursement

• Vehicle Registration: Required at Before Disbursement

Documentation Template:

• Loan Offer Letter (includes vehicle details)

• Auto Loan Agreement

• Security Agreement (vehicle as collateral)

• Disclosure Documents

Mortgage Loan

Document Requirements:

• Enhanced income verification (2 years history)

• Property Appraisal: Required at Underwriting

• Property Title Search: Required at Pre-Approval

• Home Insurance: Required at Pre-Approval and Before Disbursement

• Property Tax Documentation: Required at Underwriting

• Employment Verification Letter: Required at Underwriting

Documentation Template:

• Pre-Approval Letter

• Loan Estimate (regulatory requirement)

• Closing Disclosure (regulatory requirement)

• Mortgage Agreement

• Deed of Trust / Mortgage Deed

Document Collection Workflow

From Applicant Perspective

Step 1: Application Submission

• System shows required documents for selected product

• Applicant uploads Application Submission stage documents

• System validates file formats and basic requirements

Step 2: Underwriting Stage

• If Underwriting stage documents missing, system requests them

• Notification sent to applicant

• Application cannot proceed until documents provided

Step 3: Pre-Approval

• Additional documents may be required based on risk assessment

• System validates document quality and content

• Manual review by underwriter

Step 4: Before Disbursement

• Final documents collected (insurance policies, signed agreements)

• System validates all stages have required documents

• Blocks disbursement if any documents missing

From Admin Perspective

Document Status Dashboard:

Application #12345 - Auto Loan

Document Status:
✓ Proof of Income (3 files) - Verified
✓ Identity Verification (1 file) - Verified
✓ Vehicle Registration (1 file) - Verified
✗ Vehicle Insurance Policy - MISSING
  Status: Requested from applicant (2 days ago)
  SLA: 3 days remaining

Action Required: Cannot disburse without insurance policy

Implementation Resources

Admin Panel Configuration

• Credit Product Configuration - Setting up product documentation requirements

• Document Templates - Creating generated document templates

SDK Configuration

The following capabilities require SDK team involvement:

• Document states and process stages definition

• Document type definitions

• Document validation rules

• Generation triggers

• OCR and data extraction (custom implementation)

Summary: Admin Panel vs SDK Responsibilities

Capability	Admin Panel	SDK
Define document types	✗	✓
Define document states/stages	✗	✓
Select required documents for product	✓	-
Assign documents to stages	✗	✓
Create document templates	✓	-
Configure generation triggers	✗	✓
Set validation rules	✗	✓
Configure exception handling	✗	✓
OCR/data extraction	✗	✓ (custom)
View document status	✓	-
Perform manual overrides	✓ (if permitted)	-
Upload/download documents	✓	-

Related Topics

• Credit Product Setup - Comprehensive product configuration

• Document Templates - Document template creation

• Workflow Fundamentals - Document-driven process flows

Related Operations

Once configured, see how documents are used in operations:

• Documents (OPS - Origination) - Managing documents during application processing

---

For additional support, consult implementation team.