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
- Community lenders
Community lenders
A community lending team may know its borrowers well, but a loan decision still needs an identifiable request, reviewer and source of funds. The app connects a borrower to the lending organization, application and provider account. The Credit Officer can carry the case from intake into servicing while an Independent Credit Approver records a separate decision.
How Loan Management System is set up for you
Borrower intake
Use the borrower code, contact and eligibility note so the officer can locate the right party before entering requested principal.
Decision trail
Attach the supporting material to the application, then keep the approver's reason against the revision they reviewed.
Provider handoff
Record the instruction ID and wait for verified disbursement or settlement evidence before treating the case as confirmed.
Servicing follow-up
Compare due schedule rows with source-identified repayments and keep amount or date differences visible.
A community lending team may know its borrowers well, but a loan decision still needs an identifiable request, reviewer and source of funds. The app connects a borrower to the lending organization, application and provider account. The Credit Officer can carry the case from intake into servicing while an Independent Credit Approver records a separate decision.
Begin with one lending organization and a small set of active borrowers and accounts. Choose a Credit Officer and a different Independent Credit Approver. Prepare a case that can be approved, then rehearse one returned case with a clear reason. Set up the provider account IDs and decide who receives provider event confirmations. This creates a path from the borrower's request to the provider's disbursement evidence without changing the original application when a later event arrives.
Next, load a dated repayment schedule for the pilot account. Compare a repayment that matches the expected account, amount and confirmed receipt date with one that differs by date. The unmatched item should remain visible for investigation. Review a servicing adjustment on the same parent application and check its decision and operation receipt. This gives the team a realistic test of authority and evidence before broader use.
Agree how the organization time zone affects receipt dates and who can view internal attachments. The Auditor should be able to trace the selected case within their authorized scope. The App Administrator can maintain membership and borrower records, while credit decisions stay with the independent reviewer. See [implementation](/loan-management-system/implementation) for the rehearsal sequence.
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.