One case file
Tasks, documents and queries
The platform carries configured cases from intake to audit evidence, aligned to how your program already runs. The credit decision stays with the lender.
The platform runs the stages, rules and roles participating entities already agreed on, configured to that process rather than assumed.
Mannjal builds and configures the technology. Credit policy, underwriting, approvals and outcomes stay with the regulated lender.
The platform replaces scattered emails, spreadsheets, manual follow-ups and disconnected document movement with a structured workflow.
Teams can see what was submitted, validated, flagged, assigned, changed and left pending without leaving the case.
Each partnership program gets one workspace, where every case runs through the same configured workflow, so applications, checks, queries and reports move together.
Structured entry, document upload, field capture, and Excel or credit appraisal memo ingestion, organized by case and section.
Mandatory data and document availability, plus the affordability, collateral and eligibility checks configured for the program, with the rules and thresholds set by the lender, before a file reaches review.
Task assignment, query resolution, maker-checker steps and exception routing through the agreed process.
Dashboards, management reports, application packs, approval notes and export files for handoff or audit review.
Configured signals and third-party outputs trigger the right validation, task or handoff, based on program scope.
The platform highlights what is pending, delayed, missing, or flagged, so the right team can act at the right time.
Route third-party checks and lender-system handoffs through the same case workflow.
These controls are covered in the security evidence pack. See the security and trust detail
Role-based access, section-level visibility, user-specific permissions, maker-checker workflow steps and segregation of duties.
User actions, workflow movement, document events, application programming interface activity and status changes are recorded with timestamps and the user who performed each action.
The platform runs logically segregated portals or instances, with role-based access boundaries for each participating entity.
On Mannjal-hosted deployments the platform runs on Indian regions, Mumbai primary with Delhi as DR; self-hosted deployments run inside your own perimeter.
See it run on one of your programs, from intake to audit evidence, with a founder.