Portfolio monitoring and credit deterioration

A vintage groups accounts or loans by origination period. Compare vintages at equal months on book so each has had similar time to develop losses. New accounts naturally have less observed history.

Track both account counts and balances. A small number of large defaults can matter more financially than many small late payments. State whether a rate uses original balance, current balance, or account count. Cohort definitions should remain stable through reporting changes; otherwise, a chart can improve because the denominator changed rather than because the portfolio improved.

A vintage groups accounts or transactions by their starting period. Comparing vintages at the same age helps separate the effect of time from the effect of underwriting changes. A newly approved group has had fewer opportunities to miss payments than a group observed for a year. Its lower cumulative loss is therefore not sufficient evidence of better quality.

Use a consistent definition of cohort entry, exposure, observation age, and loss. If a borrower refinances or a merchant changes terms, define how the analysis treats that event. Otherwise, a policy change can appear to improve results simply by moving difficult accounts out of the measured population. Keep the operational view of today’s portfolio alongside the historical view of comparable cohorts.

Use vintages and comparable age — the flow

1. 01GroupChoose origination cohort
2. 02AgeAlign months on book
3. 03CompareUse a consistent outcome and denominator

Use vintages and comparable age — the distinction

Calendar view

• All activity in one date period

Vintage view

• Outcomes for a comparable origination group

Vintage comparison

Fictional educational excerpt / Not for execution

Vintage comparison

Illustrative data; not a real customer record or a prescribed policy.

1. 1

   January cohortmonth 6

   Six months observed

2. 2

   June cohortmonth 1

   One month observed

3. 3

   Fair comparisonequal age

   Different maturity can mislead

Losses develop over time

Use vintages and comparable age — control and failure modes

Control design

Compare cohorts at equal age. Losses develop over time.

Failure mode 1avoid

Rank new cohorts as safest immediately. Their outcomes may be immature.

Failure mode 2avoid

Mix count and balance rates. The measures differ.

Failure mode 3avoid

Change denominators without annotation. The trend becomes misleading.

A roll rate measures movement from one delinquency state to another over a defined period. Cure measures movement back toward current status. Both need clear state definitions and observation windows.

A borrower can make a payment and still remain delinquent if the payment does not satisfy the overdue obligation. Record contractual due amounts, payments, and allocation rules. Separate operational posting errors from actual repayment failure. A rising roll rate may signal economic stress, collection problems, or a data defect; investigate before selecting the response.

Watch movement between states — the flow

1. 01StateClassify the account at period start
2. 02MovementObserve payments and obligations
3. 03TransitionClassify the period-end state

Watch movement between states — the distinction

Payment received

• Some value was paid

Cured account

• Required overdue obligation was resolved

Delinquency transition

Fictional educational excerpt / Not for execution

Delinquency transition

Illustrative data; not a real customer record or a prescribed policy.

1. 1

   Start30 days past due

   Defined opening state

2. 2

   Paymentpartial

   Does not necessarily cure

3. 3

   Endstill overdue

   Apply the contractual allocation

Any payment is not automatically a cure

Watch movement between states — control and failure modes

Control design

Calculate states from obligations and allocation. Any payment is not automatically a cure.

Failure mode 1avoid

Mark all payers current. That can hide remaining arrears.

Failure mode 2avoid

Ignore posting delays. They can distort delinquency.

Failure mode 3avoid

Assume every roll-rate change is economic. Process and data changes also matter.

Concentration can arise from industry, geography, supplier, platform, sponsor bank, or customer type. Two merchants with different names may depend on the same marketplace or logistics provider. Map shared dependencies alongside legal counterparties.

Set concentration measures in the units that matter: exposure, revenue, liquidity need, or operational capacity. A partner handling 60 percent of payouts creates a different issue from an industry holding 60 percent of credit exposure. Stress the relevant failure and assign an owner. Diversity in logos is not the same as diversity in failure modes.

Concentration can hide behind apparently different customers. Several merchants may depend on one supplier, one advertising channel, one acquiring partner, or one seasonal event. Their business names are different while their failure trigger is shared. A useful portfolio map records those common dependencies and tests a scenario in which the dependency fails. The response might involve limits, more available cover, a different payout schedule, or a planned reduction in new exposure. Diversification should describe independent loss drivers, not merely a large count of accounts.

Measure common exposures — the flow

1. 01LinkIdentify shared dependencies
2. 02MeasureUse the relevant exposure unit
3. 03StressAssess a common failure

Measure common exposures — the distinction

Counterparty count

• Number of named relationships

Risk diversification

• Independence of important loss drivers

Concentration record

Fictional educational excerpt / Not for execution

Concentration record

Illustrative data; not a real customer record or a prescribed policy.

1. 1

   Merchants80

   Separate businesses

2. 2

   Platformone

   Shared acquisition channel

3. 3

   Exposure share60 percent

   Common dependency concentration

Many entities can fail together

Measure common exposures — control and failure modes

Control design

Measure shared drivers beneath legal names. Many entities can fail together.

Failure mode 1avoid

Use logo count as diversification. Names do not reveal common dependencies.

Failure mode 2avoid

Mix revenue share with credit exposure. The risk units differ.

Failure mode 3avoid

Ignore operational partners. Their failure can affect many accounts.

Declining receipts, rising refunds, growing delinquency, or changed settlement behavior can indicate deterioration. Each signal also has alternative explanations. Define the evidence needed to move from observation to action.

An early-warning program needs thresholds, owners, review cadence, and permitted responses. Avoid a queue that only produces alerts without decisions. Record whether an intervention helped, harmed, or had no clear effect. A limit reduction can reduce future exposure while creating customer consequences and notice duties. Apply the relevant process before changing terms.

Use early warnings with a response — the flow

1. 01SignalObserve a meaningful change
2. 02ReviewTest cause and data quality
3. 03ActUse an approved documented response

Use early warnings with a response — the distinction

Early warning

• Reason to investigate

Adverse decision

• Action requiring its own basis and process

Deterioration review

Fictional educational excerpt / Not for execution

Deterioration review

Illustrative data; not a real customer record or a prescribed policy.

1. 1

   Receiptsdown 25 percent

   Illustrative signal

2. 2

   Causeseasonality unresolved

   Needs context

3. 3

   Actionreview before limit change

   No automatic legal conclusion

Signals need interpretation and a response

Use early warnings with a response — control and failure modes

Control design

Connect warnings to accountable review. Signals need interpretation and a response.

Failure mode 1avoid

Reduce every limit from one data point. The cause may be temporary or erroneous.

Failure mode 2avoid

Ignore notice implications. Term changes can carry duties.

Failure mode 3avoid

Count alerts as completed reviews. Detection is not resolution.

Collections and account exit should preserve accurate balances, lawful communication, dispute routes, and access controls. A defaulted customer remains a person or business with rights. The objective is to resolve obligations without creating additional harm or misleading records.

Separate recoveries from new revenue and track collection costs. Feed mature outcomes back into underwriting with the original decision context. Do not train only on easy-to-collect accounts and generalize to everyone. Preserve the distinction between a loss caused by poor capacity analysis and a loss caused by a failed collection process.

Close, collect, and learn with care — the flow

1. 01ResolveMaintain accurate obligations and rights
2. 02RecoverRecord value and cost separately
3. 03LearnLink outcomes to original assumptions

Close, collect, and learn with care — the distinction

Gross recovery

• Money collected after loss

Net recovery

• Recovery less relevant costs under the metric definition

Recovery example

Fictional educational excerpt / Not for execution

Recovery example

Illustrative data; not a real customer record or a prescribed policy.

1. 1

   Collected5000 USD

   Gross recovery

2. 2

   Collection costs800 USD

   Relevant example cost

3. 3

   Net recovery4200 USD

   Defined simple difference

Exit is part of the risk lifecycle

Close, collect, and learn with care — control and failure modes

Control design

Use accurate balances and mature outcome feedback. Exit is part of the risk lifecycle.

Failure mode 1avoid

Treat recovered principal as new sales. That misstates the economic event.

Failure mode 2avoid

Ignore collection costs. Gross recovery overstates net benefit.

Failure mode 3avoid

Delete the original underwriting context. The team loses the ability to learn.

This chapter builds on Reserves, limits, and payout policy. Use the glossary for terminology and risk mathematics for formulas and worked calculations.