Skip to main content

Application detail - tabs, origination vs servicing

Route: /loans/applications/[id]

Purpose​

This page is the single place to understand an application’s story: data submitted, scores and models consulted, policy / rules, NBE / compliance status, and-where separate in UI-post-disbursement servicing indicators (DPD, buckets, provisioning language).

How to read tabs safely​

  1. Read tab titles literally-origination approval logic may differ from servicing / regulatory sections.
  2. If a tab says “servicing” or “post-disbursement,” do not treat it as the same decision as origination approval unless your policy says so.
  3. NBE Compliance tab (when shown) summarizes validation results and warnings for operators; bank counsel remains authority on regulatory meaning.

Typical actions (tenant-dependent)​

  • Request more information from customer or branch.
  • Move stage / assign to another team member.
  • Open linked customer (Customer 360) when a button exists.
  • Jump to scoring history via deep links where implemented.

What happens when you save​

  • The system persists structured fields and often writes an audit event-your compliance team can explain what appears in audit logs.

Training note​

Capture screenshots per tab with masked customer data; label each image with origination vs servicing in the caption to avoid committee confusion.

Next: Approvals & analytics · Understanding AIS - asset classification