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
- Multi-entity lenders
Multi-entity lenders
A lending team working across organizations needs to know which entity owns each borrower and case. Organizations carry codes, currency and time zone. Borrowers, team members, applications and servicing reviews link back to an organization. Those relationships help the team route a request to the right officer and ensure the independent reviewer acts within the intended scope.
How Loan Management System is set up for you
Entity context
Set up organization identities before adding borrowers, officers and accounts.
Case assignment
The application owner and borrower counterparty show who is preparing the request and whose loan is under review.
Review boundary
The decision records the reviewer and source revision, allowing the team to verify independence and scope.
Provider trail
Provider account and event IDs let the team reconcile funding and repayments for the correct entity.
A lending team working across organizations needs to know which entity owns each borrower and case. Organizations carry codes, currency and time zone. Borrowers, team members, applications and servicing reviews link back to an organization. Those relationships help the team route a request to the right officer and ensure the independent reviewer acts within the intended scope.
Choose two organizations with different team members and borrowers. Enter their active settings, currencies and time zones, then link one provider account to a borrower in each. Have a Credit Officer prepare a request for the first organization and an Independent Credit Approver from its authorized scope review it. Try the same case with a member of the other organization. The test should show that selecting a familiar borrower name is not enough to cross an organization boundary.
Carry the accepted pilot case into provider submission and confirmation. Check that the disbursement points to the correct application and account. Add a schedule and a source-identified repayment. The officer should be able to explain the match using account, amount and confirmed date, while an Auditor can inspect the retained decision and evidence. If a provider event arrives against the second organization's account, investigate it as a mismatch.
Agree which team owns organization membership, who may maintain borrower details and who reviews each lending entity's exceptions. Test the App Administrator's configuration access separately from credit approval. Review [roles](/loan-management-system/roles) and [data model](/loan-management-system/data-model) when setting up the first entities.
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.