← Agent catalogue

AI Agent Profile · LendingIQ · Bengaluru

Portfolio Risk Head AI

Invoked via: internal orchestration APIRuntime: AWS Bedrock · ap-south-1Model: Claude Sonnet 4Context window: 200K tokens

DivisionRisk division

Resume

What this agent does

The Portfolio Risk Head AI reads the live portfolio, interprets what the numbers mean, and surfaces what the credit team needs to act on — before it becomes a problem. It produces portfolio health reads, builds vintage curves, maps concentration risk, and runs the early warning engine that decides which accounts need attention this week. It does not contact borrowers, initiate collections, or restructure loans. It identifies and narrates; humans act.

Primary functions

Portfolio Health Read

Triggered on schedule or on-demand

Invoked when: monthly MIS available, board pack due, or ad-hoc senior query

  • Reads the full portfolio snapshot — outstanding book, product mix, DPD bucket distribution, NPA stock and flow, write-offs, and collection efficiency — passed as structured data at invocation time.
  • Compares the current snapshot against the prior period (if provided) and narrates the direction of travel: what improved, what deteriorated, and what is showing an early trend worth watching.
  • Does not maintain its own database or remember the last snapshot autonomously. Prior period data must be injected alongside current data for comparison to work. If only one period is provided, it reads that period in isolation without inferring trends.
  • Frames the health read at the level requested — board-level summary (3–4 headline observations), management MIS (segment-wise deep dive), or specific product/geography slice.
Output: Portfolio health narrative — headline observations, segment performance table, DPD movement commentary, NPA flow analysis, and 2–3 flagged areas requiring management attention.

Vintage Analysis

Triggered monthly or at product review

Invoked when: new cohort data available, product under review, or policy change impact assessment needed

  • Reads disbursement cohort data — loans grouped by month of origination — and tracks how each cohort's NPA or DPD rate has evolved over its seasoning period, month by month.
  • Identifies whether newer vintages are performing better or worse than older vintages at the same point in their lifecycle. A newer vintage that is running hotter at 6 months than older vintages ran at 6 months is a leading indicator of policy or market deterioration.
  • Links vintage performance to the policy version, credit officer, product variant, or channel in effect at origination — so when a bad vintage is found, it can be traced back to what changed at the time it was booked.
  • Cannot compute the vintage curves from raw transaction data. It needs the cohort NPA-by-month matrix already aggregated. It interprets the curves; it does not build them from ledger transactions.
Output: Vintage analysis narrative — cohort comparison table, deviation from expected trajectory, traceability to origination conditions, and policy recommendation if deterioration is systematic.

Concentration Risk Mapping

Triggered monthly or at limit review

Invoked when: monthly MIS available, new large disbursement, or sector/geography limit review due

  • Maps the portfolio across every concentration dimension in the data provided: sector, geography (state / district), borrower size, product type, ticket size band, channel of origination, single-borrower group exposure.
  • Measures each dimension against the concentration limits in the current credit policy (retrieved via RAG) and flags where the portfolio is approaching, at, or beyond a limit — with the actual figure, the limit, and the headroom remaining.
  • Identifies hidden concentrations that a single-dimension view misses — e.g., a portfolio that looks diversified by sector but is heavily concentrated in one district within a sector, with correlated flood or drought risk.
  • Does not decide what concentration limits should be — that is the Head of Credit Policy AI's role. It reports against the limits that currently exist and flags where they may be insufficient given the concentrations it can see.
Output: Concentration risk map — exposure by dimension, limit utilisation table, hidden correlation flags, and a prioritised list of concentrations requiring active management or limit review.

Early Warning Strategy & Account Flagging

Triggered on CBS refresh or bureau update

Invoked when: weekly CBS pull, monthly bureau refresh, or GST compliance update received

  • Runs a configured set of early warning triggers across the active book — DPD creep (account moving from 0 DPD to 1–29 DPD), bureau score drop above threshold, GST filing lapse, ECS bounce frequency increase, overdraft utilisation crossing 85%, and collections field visit outcome flagged negative.
  • For each triggered account, reads the account history and available signals and produces an account-level deterioration narrative: what signals fired, when they started, what the account looked like at origination versus now, and what combination of signals suggests a genuine risk versus a one-off blip.
  • Scores the urgency of each flagged account — not as a calibrated probability, but as a triage priority (Immediate action / Monitor closely / Watch list) — so the collections and credit team knows which 20 accounts to call this week versus which 80 to revisit next month.
  • Recommends an action category for each account — borrower call, field visit, restructure discussion, additional collateral request, or refer to collections — but does not initiate any of these actions itself.
Output: Weekly early warning report — triggered accounts by triage priority, signal summary per account, deterioration narrative, and recommended action category for the credit and collections team.

Knowledge base

Live Portfolio MIS & CBS Data

The primary input — injected at invocation. Repayment status, DPD buckets, disbursements, NPA stock and flow. Not stored between sessions.

Vintage Cohort Matrix

Pre-aggregated cohort NPA-by-month data passed in context. The agent interprets the curves; it does not compute them from raw transactions.

Concentration Limits (RAG)

Current credit policy concentration limits retrieved at invocation. The agent reports portfolio position against these limits — always the live version, never cached.

Early Warning Rule Set

Configured trigger thresholds — DPD creep, score drop, GST lapse, ECS bounce rate, OD utilisation — maintained by the credit team and loaded at runtime.

Bureau Score Refresh Feed

Monthly updated bureau scores for active borrowers. Used to detect score deterioration since origination as an early warning signal.

Collections CRM Notes

Field visit outcomes, promise-to-pay records, and borrower contact history — used to contextualise whether a DPD signal is a payment delay or a genuine risk event.

Hard guardrails

Will notInitiate borrower contact, collection calls, or field visits. It identifies accounts and recommends action; humans in the collections and credit team execute.
Will notRestructure, reschedule, or write off an account. Remediation decisions require human credit authority — the agent provides the information case, not the approval.
Will notGenerate vintage curves or DPD bucket analysis from raw ledger transaction data. It needs aggregated MIS exports. Passing raw transaction files will not produce reliable output.
Will notRetain portfolio data or account flags between sessions. Each weekly early warning run must inject the full current dataset — the agent has no memory of which accounts were flagged last week unless that log is re-injected.
Will notForecast portfolio NPA for future quarters. It reads current and past data. Forward-looking NPA projection requires a dedicated forecasting model — this agent's output is backward and present-looking only.

Known limitations

Cannot work with raw CBS transaction data. All analysis requires pre-aggregated MIS exports — DPD buckets, cohort matrices, segment summaries. The data engineering pipeline must aggregate before passing to the agent.Build a structured MIS export layer upstream. Define standard schemas for the four data inputs — portfolio snapshot, vintage matrix, bureau refresh, and CBS DPD file.
Early warning triage is rules-based, not machine-learned. The trigger thresholds — score drop of X points, DPD creep to Y days — are set by the credit team and applied by the agent. If the thresholds are wrong, the flags will be wrong.Review and recalibrate early warning thresholds quarterly against actual default outcomes. Adjust based on false positive and false negative rates from the prior quarter's flags.
Concentration analysis is only as multi-dimensional as the data provided. If the MIS export does not include geography or channel fields, those concentration dimensions cannot be analysed.Ensure the MIS export schema includes all concentration dimensions defined in credit policy — sector, state, district, channel, ticket band, and group exposure.
Vintage analysis cannot trace poor performance to root cause without origination metadata. If the cohort data does not include policy version, credit officer ID, or channel at origination, the traceability linkage cannot be made.Tag every disbursement record with the policy version active at that date, origination channel, and processing team. This metadata is what turns vintage analysis from descriptive to actionable.
Collections CRM notes are taken at face value. Field visit observations and promise-to-pay records are input data — the agent cannot verify them or detect if they are inaccurate or optimistic.Collections team discipline on CRM data quality directly affects the quality of early warning output. Garbage field notes produce unreliable account-level triage.
Agent Profile · Portfolio Risk Head AI · LendingIQ · BengaluruLast updated April 2026 · For internal use

Important Reads

Learn more about how to deploy Portfolio Risk Head AI to your lending workflow.