Loan lifecycle, approvals, and exceptions
Every bank names stages differently. Below is a generic journey you can map to your product catalog and policy manual. Exact screens and statuses in Decision PRO are subject to deployment configuration.
Happy path in business terms - map each box to your Decision PRO statuses in workshops.
Typical stages (business terms)
| Stage | What the bank usually expects |
|---|---|
| Intake | Application captured with minimum data quality checks |
| Assessment | Income, obligations, bureau (where used), and policy rules evaluated |
| Decision | Approve / decline / refer with reasons aligned to committee policy |
| Fulfillment | Conditions, documentation, and disbursement handoffs (if in scope) |
| Servicing / workout | Post-booking changes, hardship, or collections-adjacent workflows (if enabled) |
Approvals
- Delegated approval within limits is common for speed.
- Committee referral happens when policy requires human judgment beyond delegation.
- Dual control may apply for sensitive changes (bank policy, not universal product law).
:::note What this means for you
Map each Decision PRO status to your committee minutes and delegation matrix during implementation workshops.
:::
Exceptions
An exception is any case that cannot proceed on the happy path: missing data, policy edge case, integration timeout, or fraud suspicion routing-handling rules vary by bank and deployment.
Collections-adjacent work
Some deployments include collections workflow experiences (tasks, timelines, coach-style assistance). Availability, modules, and regulator fit are subject to deployment configuration. If your program includes collections features, your AIS account team will confirm scope and evidence expectations.