Dashboard
Welcome
TOTAL PRE-SCREENINGS
—
THIS MONTH
—
PIPELINE AMOUNT
—
CONVERTED TO APPLICATION
—
PIPELINE OVERVIEW
Pre-screenings
Loading...
| ID | APPLICANT | PAN | LOAN TYPE | AMOUNT | STAGE | SCORE | BSA | CREATED | ASSIGNED |
|---|
NO PRE-SCREENINGS FOUND
New Pre-screening
Fill borrower details to create a new pre-screening record
Loading form...
—
—
·
—
·
—
COMPOSITE SCORE
ASSIGNED TO
—
Bank Statement Analyser
Standalone BSA — no enquiry needed. Upload a PDF and get instant credit analysis.
BORROWER DETAILS (OPTIONAL)
✓ AI memo is configured server-side. Leave blank to use server key, or enter your own to override.
BANK STATEMENT PDF
ⓘ
Supported banks: HDFC · Axis Bank · Union Bank · Canara · SBI · ICICI · Kotak · IndusInd · Yes Bank. Analysis takes 15–45 seconds depending on statement length.
PAST BSA ANALYSES
Loading history...
Credit Bureau Reports
Pull CIBIL and other bureau reports for any borrower
ⓘ
Live CIBIL API credentials are being onboarded. Reports below are mock data for demonstration. Equifax, Experian and CRIF credentials expected in 7–10 days.
NEW BUREAU PULL
SELECT BUREAUS
TransUnion CIBIL
SELECTED ✓
Score 300–900 · Most widely used
Equifax India
CREDS PENDING
Score 300–900 · Good for retail
Experian India
CREDS PENDING
Score 300–900 · New-to-credit
CRIF High Mark
CREDS PENDING
Score 300–900 · Best for MSME
⚠
Pulling credit reports without borrower consent violates the CIC Act 2005. Ensure written consent is on record before proceeding.
Configuration
Platform settings and administration
PIPELINE STAGES
Define the stages a pre-screening moves through, from intake to disbursal or rejection.
LOAN TYPES
Define the loan products offered. These appear in the pre-screening form and the new application modal.
SCORE WEIGHTS BY LOAN TYPE
Weights should sum to 100% per loan type. The composite score is a weighted average of BSA, CIBIL (normalised), business vintage, and manual override scores.
AGREEMENT TEMPLATES
Upload a Word (.docx) file. Use
{{placeholder}} tags anywhere in the document — they will be filled automatically from pre-screening data when you generate an agreement.
Loading…
AVAILABLE PLACEHOLDERS
Click any tag to copy it. Paste inside
{{ }} in your Word document exactly as shown.
SYSTEM
CUSTOM PLACEHOLDERS
Define extra placeholders not in the pre-screening form — e.g. witness_name, branch_address. You will be prompted to fill these each time you generate an agreement.
USERS
Platform users and their assigned roles.
ROLES & PERMISSIONS
Define what each role can see and do. ★ = system role (cannot be deleted).
Applications
Loading...
| APP ID | APPLICANT | LOAN TYPE | AMOUNT | PAN | STATUS | CREATED |
|---|
—
—
—
CIC Report
Generate TUDF files for CIC submission
AUTO GENERATE FROM LMS
Pulls all live loan records, computes DPD from EMI schedule, and generates TUDF files for all 4 CICs in one click.
RECORDS PREVIEW
FILES GENERATED
CIC CREDENTIALS
Saved credentials are auto-filled into the file header. Passwords are stored server-side in field_config.json.
CIBIL (TransUnion)
EQUIFAX
EXPERIAN
CRIF HIGH MARK
FILE HEADER
BORROWER NAME & DEMOGRAPHICS
IDENTITY & CONTACT
ADDRESS
ACCOUNT / TRADE LINE
PAYMENT HISTORY
| MM/YYYY ⓘ | DPD Code ⓘ | Overdue ₹ ⓘ | Balance ₹ ⓘ | Payment ₹ ⓘ |
|---|
ⓘ
DPD codes: STD=Standard, 000-900=days past due, SMA=Special Mention, SUB=Substandard, DBT=Doubtful, LSS=Loss, XXX=No data
REVIEW & GENERATE
VALIDATE & GENERATE
Click Validate before generating.
FILES READY
ONLINE MAINTENANCE (OLM) — DATA CORRECTION GUIDE v1.0 · Mar 2026
OLM templates are structured to capture corrections in a standardized and controlled manner, aligned to the UCRF for each bureau. Each row represents a single, clearly defined correction request. Covers all 3 data repositories: Consumer · Commercial · MFI.
META FIELDS — COMMON TO ALL OLM SUBMISSIONS
| Field | Length | Type | Values / Notes |
|---|---|---|---|
| Member Code | 10 | Mandatory | Valid 10-char Member Code assigned by any CIC |
| OLM Type | 2 | Optional | 01 = Complaint-related · 02 = Non-complaint-related |
| Date of Complaint | 8 | Conditional | Only when OLM Type = 01. Format: DDMMYYYY |
| Complaint Raised Through | 2 | Conditional | 01 = CIC · 02 = CI (Credit Institution) |
| CIC Name | 2 | Conditional | 01=CRIF · 02=Equifax · 03=Experian · 04=TU CIBIL · 05=All |
| Complaint Ticket Number | 30 | Conditional | Ticket number raised at CI or CIC end (when OLM Type = 01) |
| CIR Number | 15 | Conditional | Unique report number on which complaint is raised |
1. UCRF VALIDATION ALIGNMENT
Not all validations in this OLM guide align with the UCRF guide. Refer to the specific validations stated in this guide for OLM submissions.
2. PREVENT OVERWRITE OF CORRECTED DATA
If erroneous data continues in regular submission files after OLM correction, it will overwrite the corrected data. Provide corrected data in all subsequent submissions.
3. MANDATORY FIELD REQUIREMENTS
Red fields = Mandatory. Blue fields = Conditionally mandatory. At least one address must remain on file at all times.
4. DATE-RELATED VALIDATIONS
All dates must follow UCRF format and logical sequencing (e.g. Account opening date must precede Account closed date). Format: DDMMYYYY.
5. COMPLAINT TICKET & CIR NUMBER
Provide correct complaint ticket number and CIR number associated with the concerned CIC. Helps track complaints and issue corrected CIRs.
6. MULTIPLE BORROWERS ON ONE TRADELINE
Data corrections apply to all borrowers linked to the account. Revised CIR is sent exclusively to the original complainant. IO/BO cases: use WebPull with prescribed enquiry purpose (no footprint).
7. FILE NAMING CONVENTION
Consumer:
Consumer_OLM_<text>.xlsxCommercial:
Commercial_OLM_<text>.xlsxMFI:
MFI_OLM_<text>.xlsxFree text up to 20 chars
8. USE STANDARD OLM TEMPLATE (.xlsx)
Do not alter template content. No new columns, no renamed/rearranged/deleted sheets or columns. Multiple correction requests can span multiple sheets in one file.
9. UCRF-COMPLIANT FIELD VALUES
Use only UCRF-defined catalog/code values (e.g. "01" not "Personal Loan"). Expanded text or free-form values will cause outright rejection. New Date Reported only accepted for closed accounts.
10. META FIELDS — ALL SUBMISSIONS
Meta fields classify, track, and process OLM requests. Populate accurately — incorrect/incomplete meta fields may affect downstream processing and dispute resolution timelines.
11. SUPPRESSION — OVERVIEW
Used to remove/exclude data from credit reporting without deleting the account. Types: Account, Enquiry, Segment/Field-wise (Address, ID, Telephone, Email, Relationship, Credit Facility, Guarantor, Security, Cheque).
12. OLD / CURRENT DETAILS (ORANGE COLUMNS)
Orange columns capture existing values for record identification. Mandatory requirement for PII corrections. Must populate both: Orange (existing) + UCRF (updated). Missing either = rejection.
13. EXCEPTIONAL SCENARIOS — OUTSIDE OLM SCOPE
Not handled via OLM: Changes to Date Reported, removal of account history for specific periods, enquiry ownership/attribution changes. These are evaluated separately by the concerned CIC.
14. ENQUIRY NUMBER TERMINOLOGY ACROSS CICs
Experian → ERN (Enquiry Reference Number)
TransUnion CIBIL → ECN (Enquiry Control Number)
Equifax → Report Order Number
CRIF High Mark → CHM Reference Number
SECTION 1 — CONSUMER REPOSITORY OLM TEMPLATE
Covers: Tradeline Update · PII Update · Account & Enquiry Suppression/Unsuppression · PII Suppression · Enquiry Update · Merger & Account Change
TRADELINE UPDATE SHEET
For correction of existing tradeline (account segment) data. Cannot add new accounts. Each row = one tradeline update request.
MANDATORY IDENTIFICATION FIELDS
Member Code
Account Number
Consumer Name
Date Reported (DDMMYYYY)
Account Number
Consumer Name
Date Reported (DDMMYYYY)
FOR CLOSURE / ZERO BALANCE
Current Balance = 0
Amount Overdue = 0
DPD = 0
Written-off/Settlement amounts as per UCRF
Amount Overdue = 0
DPD = 0
Written-off/Settlement amounts as per UCRF
PII UPDATE SHEET
For corrections to Name, DOB/Gender, Identification, Telephone, Email, Address. Not for tradeline/account updates.
NAME / DOB / GENDER
Old values in orange columns → updated values in Name Field 1–5, DOB, Gender. DOB: DDMMYYYY, not future-dated.
IDENTIFICATION
Old ID Type & Number mandatory. Updates only in UCRF fields. New identifiers cannot be added via OLM.
ADDRESS
Old Address & Category mandatory. Updated details across Address Line 1–5, State Code, PIN Code, Residence Code, Category as per UCRF.
ACCOUNT & ENQUIRY SUPPRESSION / UNSUPPRESSION
ACCOUNT SUPPRESSION — ALL BORROWERS
Fields: Member Code · Account Number · Account Suppression Reason (mandatory)
ACCOUNT SUPPRESSION — SPECIFIC BORROWER
Option A: Account Number + Consumer Name + Account Type + Ownership Indicator
Option B: Using Enquiry Number (must belong to same CIC)
Option B: Using Enquiry Number (must belong to same CIC)
ENQUIRY SUPPRESSION
ID Method 1: Enquiry Number
ID Method 2: Enquiry Date + Amount + Purpose + Time (if available) + Borrower Name + (ID Type & Number OR Phone)
Suppression Reason mandatory (max 200 chars)
ID Method 2: Enquiry Date + Amount + Purpose + Time (if available) + Borrower Name + (ID Type & Number OR Phone)
Suppression Reason mandatory (max 200 chars)
KEY RULES
• Suppression along with tradeline updates for same account: both are processed
• If member reports data after suppression, data keeps updating in CIC DB
• If multiple enquiries match, latest is suppressed
• If member reports data after suppression, data keeps updating in CIC DB
• If multiple enquiries match, latest is suppressed
PII SUPPRESSION SHEET
Suppress specific PII attributes. Each row = one attribute suppression. Multiple suppressions = separate rows.
ID SUPPRESSION
Old ID Type + Old ID Number + Member Code + Account Number + Consumer NameTELEPHONE
Old Telephone Number + Old Telephone Type + Member Code + Account Number + Consumer NameEMAIL
Old Email (must match DB) + Member Code + Account Number + Consumer NameADDRESS
Old Address + Old Address Category + Member Code + Account Number + Consumer NameENQUIRY UPDATE SHEET
Update Enquiry Purpose and/or Enquiry Amount only. Each row = one enquiry update. Enquiry Number must match the bureau database. Updated values must comply with Consumer Bureau UCRF catalogue values.
MERGER & ACCOUNT CHANGE SHEET
For account mergers within same CI or portfolio/account transfer between different CIs.
MANDATORY FIELDS (ALL 4 REQUIRED)
Old Member Code
Old Account Number
New Member Code
New Account Number
Old Account Number
New Member Code
New Account Number
SCENARIOS
Same CI merger: Old = New Member Code
Portfolio transfer: Old ≠ New Member Code
Optional: Account Type / Ownership Indicator if changing
Portfolio transfer: Old ≠ New Member Code
Optional: Account Type / Ownership Indicator if changing
SECTION 2 — COMMERCIAL REPOSITORY OLM TEMPLATE
Covers: Tradeline Update · PII Update · Other Updates · PII Suppression · Suppression/Unsuppression · Merger & Account Change
TRADELINE UPDATE SHEET
Correction of credit facility/tradeline data under Commercial Bureau UCRF. Cannot add new tradelines. All updates must adhere to Commercial UCRF validations.
MANDATORY FIELDS
Member Code
Account Number
Borrower Name
Reporting / Cycle Date (DDMMYYYY)
Account Number
Borrower Name
Reporting / Cycle Date (DDMMYYYY)
CLOSURE / STATUS RULES
Closure: Balance=0, Overdue=0, DPD=0
Written-off: Written-off Amount fields required
Settled: Settlement Amount required
Restructured: All conditional fields required
Written-off: Written-off Amount fields required
Settled: Settlement Amount required
Restructured: All conditional fields required
PII UPDATE SHEET
Correction of PII and related segment details. Cannot insert new records. Mandatory control fields: Member Code · Borrower Name · Account Number.
BORROWER DETAILS
Old values in orange columns → updated in UCRF columns. Borrower Name + Account Number = control fields.ADDRESS
Old Address + Borrower Office Location Type mandatory. Updated address in UCRF address columns.RELATIONSHIP
Old Related Type + Business Entity Name / Full Name mandatory. Type determines which name is applicable.GUARANTOR
Old Guarantor Type + Entity Name / Full Name mandatory. Cannot insert new guarantor records.OTHER UPDATES SHEET
For non-tradeline attributes: Relationship · Guarantor · Security · Dishonour of Cheque · Enquiry details. Cannot insert new records.
SECURITY CORRECTION
Existing Security Type + Value of Security + Account Number mandatory.CHEQUE DISHONOUR
Existing Cheque Number + Account Number mandatory.ENQUIRY UPDATE
Only Enquiry Purpose and/or Amount can be updated. Enquiry Number must belong to same CIC.PII SUPPRESSION SHEET
Suppress existing PII values. Control fields: Member Code · Borrower Name · Account Number. Segments: Borrower · Address · Relationship · Guarantor. State & Pin Code can only be suppressed for Foreign Addresses.
SUPPRESSION / UNSUPPRESSION SHEETS (SEGMENT & ENQUIRY)
Segments: Account · Relationship · Guarantor · Address · Security · Cheque Dishonour · Enquiry
ACCOUNT SUPPRESSION — SPECIFIC BORROWER
Option A: Account Number + Credit Type
Option B: Enquiry Number (must belong to same CIC/bureau)
Option B: Enquiry Number (must belong to same CIC/bureau)
KEY RULES
Suppression/Unsuppression: existing records only
All identification fields must be accurate
Missing reason or incomplete ID = rejection
All identification fields must be accurate
Missing reason or incomplete ID = rejection
MERGER & ACCOUNT CHANGE SHEET
For portfolio buyouts and account transfers under Commercial Bureau. Does NOT modify tradeline attributes — only maps old → new structure.
ALL 4 FIELDS MANDATORY
Old Member Code · Old Account Number · New Member Code · New Account Number
SCENARIOS
Portfolio Transfer / Account Sale: Old ≠ New Member Code
Account Merger within same CI: Old = New Member Code
Account Merger within same CI: Old = New Member Code
SECTION 3 — MFI REPOSITORY OLM TEMPLATE
Covers: Tradeline Update · PII Update · PII Suppression · Other Updates · Account & Enquiry Suppression/Unsuppression · Merger & Account Change
TRADELINE UPDATE SHEET
Supports both Group-level and Member/Account-level corrections. Each row must clearly identify the correction level and populate mandatory identifiers.
COMMON MANDATORY FIELDS
Member Code
Group Name or Member Name
Date Reported (DDMMYYYY)
Group Name or Member Name
Date Reported (DDMMYYYY)
GROUP-LEVEL
Group Loan Account Number mandatory. Member-level fields alone insufficient.
MEMBER/ACCOUNT-LEVEL
Unique Account Reference Number + Account Number both mandatory.
Closure: Outstanding Balance = 0, Amount Overdue = 0, DPD = 0. Catalogue codes only — no descriptive text.
PII UPDATE SHEET
For Group-level and Member-level PII, relationship, ID, and telephone details. Orange columns (Old/Current Details) mandatory for each correction.
GROUP SEGMENT
Group Identifier (Old) + Group Name (Old) mandatory to identify the group.MEMBER SEGMENT
Member Identifier (Old) + Member Name (Old) mandatory.ACCOUNT SEGMENT
Group Identifier (Old + Updated) mandatory. Used for Group Identifier updates in Account Segment.PII SUPPRESSION SHEET
Suppress Group-level and Member-level PII, relationship, ID, address, telephone, email. Control field: Member Code (mandatory for all).
GROUP SEGMENT SUPPRESSION
Group Identifier (Old) + Group Name (Old)
MEMBER SEGMENT SUPPRESSION
Member Identifier (Old) + Member Name (Old). Group Identifier in Member Segment can only be suppressed when Loan Category = T03.
OTHER UPDATES SHEET
Group segment corrections · Member segment corrections · Enquiry Purpose/Amount updates. Enquiry Purpose must be from the official MFI UCRF enquiry purpose catalog values.
Mandatory: Member Code + Group Identifier + Group Name (for Group) — or — Member Code + Member Identifier + Member Name (for Member).
ACCOUNT & ENQUIRY SUPPRESSION / UNSUPPRESSION
GROUP LEVEL
Group Identifier + Group Name must uniquely match an existing record.
MEMBER LEVEL
Member Identifier + Member Name. Enquiry purpose from valid MFI UCRF catalog.
ENQUIRY SUPPRESSION
Identifiers must match existing record. Member Code mismatch = rejection.
MERGER & ACCOUNT CHANGE SHEET
For portfolio transfers, account number changes, account reference updates. Preserves continuity of credit history.
MANDATORY FIELDS
Old Member Code · Old Account Number · New Member Code · New Account Number
USAGE GUIDANCE
Same CI: Old = New Member Code
Portfolio transfer: Old ≠ New Member Code
Cannot ingest new accounts. Old identifiers must match existing bureau data.
Portfolio transfer: Old ≠ New Member Code
Cannot ingest new accounts. Old identifiers must match existing bureau data.
Loan Management
Loading...
PAYMENT COLLECTION CALENDAR
Loan Accounts
Loading...
| LOAN NO. | APPLICANT | PRINCIPAL | OUTSTANDING | EMI | NEXT DUE | STATUS | OVERDUE |
|---|
NO LOAN ACCOUNTS FOUND
Supply Chain Finance
Invoice-based financing · Per-invoice disbursement & collection
—
—
Accounting
Income & Expense Ledger
ADD ENTRY
—
—
Audit Log
All system actions, changes and document uploads
| TIMESTAMP | USER | ACTION | ENTITY | REFERENCE | DESCRIPTION | |
|---|---|---|---|---|---|---|
| Loading… | ||||||