These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Loan Management System
- Who it's for
- Specialty finance teams
Specialty finance teams
Specialty finance teams often coordinate internal credit work with an external lending provider. A single case needs to show who prepared the request, who approved it, which instruction was sent and what the provider actually confirmed. The application, account, evidence and receipt records give each person a place to check their part of that sequence.
How Loan Management System is set up for you
Structured request
The application records borrower, organization, owner, requested principal and revision.
Separate authority
The approver records an outcome and reason for the reviewed revision before the application status changes.
External effect
The instruction identity and provider event ID connect the approved case to verified disbursement evidence.
Account servicing
Schedules and repayments share a loan account, so due and received amounts can be compared without matching borrower names alone.
Specialty finance teams often coordinate internal credit work with an external lending provider. A single case needs to show who prepared the request, who approved it, which instruction was sent and what the provider actually confirmed. The application, account, evidence and receipt records give each person a place to check their part of that sequence.
Start with one organization, a set of borrowers and their existing provider accounts. Map each provider account's external ID to the account record. Choose who owns incoming disbursement and repayment events and how event IDs are retained. A pilot request should show a decision, provider instruction, verified response and schedule on the same account. A delayed provider response should stay in the pending worklist until its evidence is checked.
Then test the exception path. Send a repayment with the correct amount but a different confirmed receipt date. It should remain unmatched or become an exception for investigation. Submit a servicing adjustment and have a separate approver decide it against the current revision. Compare the operation receipt with the actual decision and status. A receipt whose effect is missing should point to the discrepancy rather than masking it as completed work.
Before expanding, agree who maintains borrower eligibility notes and which attachments are internal or shared. Confirm that a member of one organization cannot act on another organization's case. Use the [application review](/loan-management-system/processes/application-review) and [disbursement confirmation](/loan-management-system/processes/disbursement-confirmation) paths to train the operators who will work with the provider.
Features to start with
Roles on the team
- Credit Officer
- Prepare assigned operational records and execute eligible reviewed actions. Own organization and draft scope only; accepted, posted and provider evidence is read-only; guarded workflows authorize every transition.
- Independent Credit Approver
- Review eligible revisions independently and reconcile operational evidence. Approve or reject through guarded actions only; no unrestricted editing of protected or executed records; a reviewer cannot approve their own submission.
- Auditor
- Read authorized evidence and reports in a scoped, read-only audit view. No record writes and no action execution.
- App Administrator
- Maintain organization configuration and membership. Administrative membership does not confer approval, financial or execution authority and cannot grant an independent reviewer entitlement.
Set up Loan Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.