Appearance
Originate and underwrite a personal loan
A credit union wants a clear path from a new personal-loan application to a priced offer, without operators guessing which screen to open next.
What you use
- Applications to find and work the file
- Application detail for underwriting, offers, and documents
- Pricing Engine if the offer comes from an offer table
- Customers to see the person across applications
Worked example
Riverbend Credit Union receives an application for a $15,000 Personal Installment Loan from an applicant with a 705 FICO score.
- An agent opens Applications, filters to new or unassigned files, and opens the application.
- On application detail they confirm applicant data, then use the Underwriting tab to run the credit and decision flow.
- The workflow lands on an approved outcome. The Pricing Engine selects the published, active offer table for that product and outcome and returns rate and term.
- The agent reviews the offer on the Offers tab and continues documents or next steps from the same file.
- If they need the person’s other files later, they open Customers and use the customer record.
Best practices
- Work from the application list and agent dashboard, not from a one-off spreadsheet of IDs.
- Confirm the product and applicant data before you treat an offer as final.
- If the offer looks wrong, check whether the offer table is published, active, and assigned to this product and outcome — see Pricing Engine.
- Use assign and tags when more than one person will touch the file. See Assigning and tags.