Applications - list, filters, and reading the grid
Route: /loans/applications
Purpose
Credit operations and loan officers use this list to find applications, prioritize work, and open detail for underwriting, servicing checks, or customer callbacks.
What you see
- Table of applications with columns such as applicant name, product, amount, stage, risk flags, and-where configured-NBE compliance indicators.
- Filters for status, product, date ranges, risk tier, score bands, and compliance flags (wording matches your deployment).
- Search that waits briefly after you type (debounced) before querying.
What you do
- Narrow with filters instead of scrolling thousands of rows.
- Open a row to read the detail page (
/loans/applications/[id]). - Export only if your bank policy allows-and prefer filtered extracts.
Reading NBE columns (Ethiopian deployments)
“NBE” refers to National Bank of Ethiopia alignment checks where the product encodes them. A flag is informational on this list; interpretation belongs to your policy and legal team. For analyst depth, use the monorepo doc LOAN_ORIGINATION_AGGREGATE_NBE.md when writing internal training.
Common misunderstandings
- List compliance column ≠ final legal opinion-detail tabs explain context.
- Stale row after a teammate acted? Refresh the list once (see Global UX patterns).