Measuring effectiveness across internal, DCA1, and DCA2 (practical NPV application)

Turn real performance into inputs for NPV-driven decisioning: consistent metrics, timing, cost, and SoR-aligned data.

Why this matters

If you do not measure effectiveness properly, then:

• NPV becomes theoretical
• Strategy decisions become biased
• DCA performance cannot be compared properly
• Internal versus external allocation becomes subjective

Goal: convert real performance data into inputs that improve NPV-driven decisioning.

What “effectiveness” means in practice

Effectiveness is not one metric. It must be measured across:

• Recovery outcome
• Speed of recovery
• Cost efficiency
• Sustainability of outcome
• Operational quality

Core effectiveness metrics (all strategies)

At a minimum, all strategies (internal, DCA1, DCA2) must be measured using consistent definitions. Fix numerator and denominator in policy before comparing.

Gross recovery rate

How much of the refer balance is recovered as cash.

Gross recovery rate = Total cash collected ÷ Refer balance

Express as a percentage when you report. Align “refer balance” with your placement and SoR rules.

Net recovery rate

Recovery after cost. A simple high-level proxy for economic outcome before full discounting:

Net recovery = Cash collected − Cost to collect

This is the closest simple proxy to NPV at a high level when timing is viewed separately.

Time to recovery

How long it takes to collect. Measure at least:

• Average days to first payment
• Average days to full resolution
• Recovery curve over time (cumulative recovery by period)

Cure / resolution rate

Percentage of accounts reaching a resolved outcome. Includes, per your policy: paid in full, settled, and other closed outcomes you treat as terminal for that strategy.

Cost per dollar recovered

Cost efficiency in currency terms:

Cost per dollar recovered = Total cost to collect ÷ Total cash collected

Lower is better when definitions are consistent across strategies.

Roll rate / progression

Movement through stages. Examples:

• Percentage moving from DCA1 to DCA2
• Percentage recalled to internal
• Percentage escalated to legal

Additional metrics specific to DCA models

DCA introduces additional complexity.

Refer performance (R1 vs R2)

Track separately:

• R1 refer balance versus recovery
• R2 refer balance versus recovery

Recall metrics

• Percentage recalled from DCA1
• Percentage recalled from DCA2
• Recall reason distribution
• DCA-requested recalls versus CP-executed recalls

DCA reported versus CP actual

• DCA reported balance versus CP balance
• DCA reported payments versus CP posted payments

This ties directly to Source of Record and controls.

Arrangement performance

• Percentage of accounts on arrangement
• Arrangement success rate
• Broken arrangement rate

Internal versus DCA1 versus DCA2 (comparative view)

You need to compare strategies like for like. The table below is illustrative only: your bank’s numbers and cost definitions will differ.

Interpretation (illustrative). Internal: often higher recovery and higher cost, faster. DCA1: balanced performance, scalable. DCA2: lower recovery and lower unit cost, longer timelines.

NPV insight. Even if DCA2 recovers something, it may still have lower NPV due to delay and lower conversion. Timing belongs in the model, not only in the headline recovery rate.

Recovery curve (critical for NPV)

NPV is highly sensitive to timing. You should not track total recovery alone: track recovery over time.

Insight. Internal often collects earlier; DCA1 is moderate; DCA2 is slower. Earlier recovery increases NPV, reduces risk, and reduces cost exposure in many models.

Linking effectiveness to NPV

To make NPV useful, feed it with recovery rate, timing profile, and cost to collect.

Key insight. Best recovery is not always best NPV. Best unit cost is not always best NPV. NPV balances recovery, timing, and cost.

Required reporting fields (critical for build)

To enable this analysis, capture the right data in operational and reporting stores.

Core fields

• Refer balance (R1 / R2)
• Refer date
• Current balance
• Cash collected
• Cost to collect
• Status

DCA-specific fields

• DCA ID (R1 / R2)
• DCA reported balance
• DCA reported status
• DCA reported arrangement status
• DCA reported recall request reason (where used)

Recall fields

• Recall date
• Recall reason
• Recall balance
• Next strategy proposed
• Next strategy actual

Timing fields

• Days to first payment
• Days to resolution
• Time in strategy

Segmentation matters

Do not evaluate effectiveness at portfolio level only. Break down by balance bands, product type, customer type, age of debt, and prior history.

Example. DCA2 may perform poorly overall but well on low-balance aged debt.

Insight. Strategy effectiveness is segment-dependent.

Common mistakes

• Comparing DCA1 and DCA2 without timing: ignores NPV impact.
• Using gross recovery only: ignores cost.
• Not separating R1 and R2 performance: hides underperformance in one tier.
• Ignoring recall behaviour: masks strategy failure or data issues.
• Not aligning to Source of Record: leads to incorrect reporting and wrong model inputs.

How this feeds back into strategy

Once measured properly, this drives:

• Allocation decisions: which accounts go to DCA1 versus internal
• Recall strategy: when to pull accounts back
• DCA performance management: which DCA to retain or replace
• End-state decisions: when to abandon, when to sell

Final takeaway

Back to pack home · NPV in collections · Cost to collect · Reporting