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
- Features
- Borrower and account setup
Borrower and account setup
Keep each borrower, lending organization and provider account connected.
OverviewBorrower directory×
Loan Management System · Borrower and account setup
New
Borrower directory
Borrowers
| Name | Code | Organization | Contact name | Eligibility note | |
|---|---|---|---|---|---|
| Borrower 628 | CDE-767 | ORG-3677 | Contact 884 | EN-852 | |
| Borrower 998 | CDE-890 | ORG-8541 | Contact 287 | EN-461 | |
| Borrower 113 | CDE-377 | ORG-5116 | Contact 132 | EN-910 | |
| Borrower 938 | CDE-939 | ORG-7558 | Contact 151 | EN-949 | |
| Borrower 966 | CDE-920 | ORG-1471 | Contact 127 | EN-345 |
6 of 6 records
Borrower 628Borrowers · BRR-51964
CodeCDE-767
OrganizationORG-3677
Contact nameContact 884
Eligibility noteEN-852
What you can do
Establish the lending parties
A lending case starts with a known organization and borrower. The App Administrator maintains the organization name, code, active setting, time zone and currency. Each borrower belongs to an organization and carries a name, code, contact, address and eligibility note. The active setting helps the team distinguish current parties from records retained for prior cases. The same borrower can own a provider-linked loan account and appear as the counterparty on an application. Those links give a reviewer a way to follow the case from request to servicing.
The account record holds an account code, provider, external account ID, currency and active setting. Treat the provider identity as a controlled reference: a transposed external ID can make an otherwise correct schedule or repayment appear to belong elsewhere. A Credit Officer can use the account link to inspect disbursements, dated schedule rows and source-identified repayments. The account is the bridge between the borrower and the provider’s servicing information.
How the work is organized
- Organization scope. The App Administrator maintains the lending organization and its members before the Credit Officer prepares a case.
- Borrower identity. The borrower code and organization link give the team a stable party to select for an application.
- Provider account. The account code and external ID tie disbursements, schedule rows and repayments to the same borrower.
What to agree during setup
Agree who maintains borrower eligibility notes and who confirms the provider account ID. Choose how inactive borrowers and accounts are handled when older applications remain open. Set the organization’s time zone before reviewing dated provider events; the team should interpret receipt dates consistently. Decide which organization owns each member and which Credit Officer prepares its applications. The App Administrator should test that maintaining membership cannot grant an independent credit decision to the same person who submitted a case.
For a pilot, create an active borrower in one organization and a loan account linked to that borrower. Record a provider ID using the provider’s own account reference. Then create an application for the same organization and borrower. The reviewer should be able to move among those records without matching names manually. Keep an older inactive borrower as a second case to check how retained history is found without treating it as new intake.
Check the handoff on an actual case
Suppose a borrower has one existing provider account and requests further principal. The Credit Officer selects that borrower as the application counterparty. Before submitting, check that the organization on the case is the borrower’s organization and that the account belongs to the same borrower. If a repayment later arrives against a different account ID, stop at the mismatch and investigate the provider reference. Changing the borrower name to make a line item fit would destroy the trail from the original request.
The App Administrator and Credit Officer can inspect the same case from different responsibilities. The administrator maintains party and membership records. The officer prepares the operational application. The Independent Credit Approver uses those links when judging the application, but does not inherit administrative access merely because the borrower record exists.
What your team sees
- Borrower directory — Active borrower records with their organization and contact details.
- Loan account register — Provider-linked accounts with borrower, currency and external ID.
Follow the work through
See application review for the next case handoff and implementation for the first operating cycle.
What it keeps track of
Data model- Organizations
- Lending organizations whose loan operations are run in this app.
- Borrowers
- Borrowers eligible for loan applications.
- Loan accounts
- Loan accounts owned by a borrower.
- Team members
- Preparers, approvers, auditors and administrators working in the organization.
- Users
- Users
Who uses it
Permissions- App Administrator
- Maintains organizations, borrowers and team membership.
- Credit Officer
- Selects the borrower and account for operational work.
- Independent Credit Approver
- Checks identity and scope during review.
- Auditor
- Reads authorized case history.
Set up Loan Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.