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.
- Credit Scoring Engine
- Features
- Applicants and organizations
Applicants and organizations
Keep applicant identity, eligibility notes and organization scope together.
OverviewActive applicants×
Credit Scoring Engine · Applicants and organizations
New
Active applicants
Applicants
| Name | Code | Contact name | Organization | Eligibility note | Active | |
|---|---|---|---|---|---|---|
| Applicant 644 | CDE-567 | Contact 805 | PRT-5580 | EN-910 | Yes | |
| Applicant 270 | CDE-170 | Contact 762 | PRT-6863 | EN-157 | Yes | |
| Applicant 448 | CDE-828 | Contact 254 | PRT-4671 | EN-903 | Yes | |
| Applicant 668 | CDE-919 | Contact 522 | PRT-9929 | EN-755 | Yes | |
| Applicant 134 | CDE-178 | Contact 926 | PRT-9332 | EN-203 | Yes |
6 of 6 records
Applicant 644Applicants · APP-53023
YesCodeCDE-567
Contact nameContact 805
OrganizationPRT-5580
Eligibility noteEN-910
What you can do
Start with the applicant
The App Administrator keeps an applicant linked to the organization that owns the credit case. The applicant record holds a name, code, contact, address, active setting and eligibility note. Those details give Operations Manager a stable identity to use when a new request arrives. A returning applicant can have another application without replacing the history of an earlier request.
For example, a business applies for a new facility after an earlier case was confirmed. Operations Manager should select its existing applicant record, inspect the contact and eligibility note, and create a separate application for the new purpose and requested amount. The older decision stays with its own case. A changed contact should not make an old decision appear to belong to a different applicant.
How the work is organized
- Organization. Parties sets the operating organization, currency and time zone for applicant and application records.
- Applicant. Applicants keeps the identity, active state and eligibility note used during intake.
- People. People links named staff to the organization and their user identity for assignment and review.
What to agree during setup
Decide which organization owns each applicant and which staff may maintain applicant details. Agree how to handle an inactive applicant, a changed contact and two records that appear to represent the same party. Establish who writes the eligibility note and what evidence belongs in the application attachments instead. Keep an applicant’s code stable so staff can find the right record when names are similar.
The App Administrator maintains this reference data. Operations Manager uses it to prepare cases. Credit Reviewer needs the identity and scope to assess the submitted revision independently. Auditor can follow the recorded organization and applicant relationship when reviewing a decision later. The team should check the role boundary with a real case before using the list for routine work.
Check the handoff on an actual case
Choose an active applicant in the intended organization. Create a draft application with that applicant, a named assignee, a purpose and a requested amount. Check that the reviewer can open the case and see the eligibility note in its applicant context. Then create another application for the same applicant and verify that both cases retain their separate revisions, decisions and provider evidence. Try an inactive applicant as a deliberate exception and decide who resolves the intake issue.
What your team sees
- Active applicants. Find the applicant identity and contact before opening a new case.
- Applications in review. See cases using the applicant record before a decision.
Follow the work through
See application review and provider follow-up.
What it keeps track of
Data model- Applicants
- Applicants eligible to raise and be assessed for credit applications.
- Parties
- Parties whose credit case operations are run in this app.
- People
- Preparers, approvers, auditors and administrators working in the organization.
- Users
- Users
- Applications
- Credit applications moving through authorization, submission and confirmation.
Who uses it
Permissions- App Administrator
- Maintains applicant and organization details.
- Operations Manager
- Uses them for intake.
- Credit Reviewer
- Reads the case context, and Auditor reviews the record trail.
Set up Credit Scoring Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.