Borrower and organization records

An organization gives lending work its business boundary. The App Administrator maintains its identity, active state, time zone and currency. Borrowers belong to an organization, with a contact and an eligibility note that the Credit Officer can review before preparing an application. Team members also belong to an organization and connect to user accounts. Keeping these relationships current matters when the same team operates across several lending entities.

A borrower can have loan accounts with a provider, external account identifier and currency. The account links back to its owner. When an application later names a borrower, that relationship gives the servicing team a way to connect the instruction with the correct account. The account’s active state helps staff distinguish an operating account from one retained for history.

• Organization identity. The App Administrator maintains a code and active state for each lending entity and assigns team members to it.
• Borrower profile. The Credit Officer checks the contact and eligibility note with the responsible organization before using the borrower on a request.
• Account link. An account carries its provider identity and borrower owner so disbursements and repayments can be traced back to the right party.

Decide who may maintain borrower records and who confirms an eligibility note. Set the organization boundary before importing applications. The App Administrator should agree on a stable code for each organization and borrower, because those values help people reconcile external correspondence with the local record. Confirm the provider’s account identifiers with the servicing team before creating active loan accounts. A similar borrower name is not enough to choose an account.

Set the working currency and time zone for each organization. The loan account has its own currency, while application and payment amounts are recorded in US dollars. Teams should decide how they will handle any conversion outside the application and consult the dated exchange-rate record when it matters to a case. The account’s provider reference remains the operational identity for servicing.

Suppose a borrower contacts the team about a new loan. The Credit Officer checks the borrower code, contact and eligibility note, then confirms which organization owns the work. The App Administrator checks that the responsible team member belongs to that organization. If the borrower already has an account, the Credit Officer compares its provider and external identifier with the information received. Only then is the borrower selected on the application.

After confirmation, a disbursement can point to the same application and borrower-owned account. When a provider receipt arrives, the servicing review can compare its account with the confirmed instruction. This chain makes a wrong-party selection visible before the team relies on an account total. Keep corrections attributable to the person who made them and preserve the original provider reference for later review.

• Borrowers in scope — Active borrower contacts and eligibility notes within the organization being managed.
• Active loan accounts — Provider identities and borrower ownership for accounts in current service.

Continue with application review and servicing reconciliation. The data model shows how the party and account records connect.