End states and closure decisions

Terminal outcomes, reasons, and why governance matters for closure

Purpose. End states are where the recoveries story stops for an account or batch. This page aligns language for training and control design. Credit reporting and legal outcomes vary by jurisdiction and product: confirm wording with your legal and policy teams. This content is not legal advice.

Agreed position in this pack: abandon and forgiveness are both terminal states for collection purposes. The difference is usually why the CP stopped pursuit, not a different operational “button” in every system. Abandon is generally driven by economics, risk, or proportionality (“not worth pursuing”). Forgiveness is more often policy-led, remediation, or customer-harm driven. Operational closure may look similar; evidence and approvals differ.

Paid in full or substantially per policy

Customer pays amounts required to close the debt under contract and policy. Reporting should show cash matched to account, DCA fees calculated, and any write-back or recovery posting to finance completed. This is the cleanest closure for reconciliation.

Settled

A negotiated outcome short of full balance: lump sum or instalments with defined closure. Settlement must sit inside delegated authority bands, with documentation suitable for audit. Credit reporting may show settled or partial settlement depending on local rules and bank policy; do not assume “paid in full” on credit files.

Waiver

Policy or commercial decision to waive part of the obligation or fees as part of a controlled closure. Distinct from informal “we will not pursue the rest” without documentation. Waivers often need dual approval when above threshold.

Abandon

Terminal decision to stop active collection because pursuit is not economical, too operationally risky, legally uncertain, or otherwise not worth marginal effort. It is not “we forgot about it.” Good governance records reason codes, population scope, and any cooling-off before re-open if policy allows.

Forgiveness

Terminal decision driven more often by policy, remediation, or identified customer harm than by raw NPV. Operationally you may still cease collection and close the operational record similarly to abandon, but the approval chain and evidence usually differ, and regulatory reporting may apply.

Debt sale as exit

Receivable transfers per sale agreement; CP must complete final feeds, recall from DCA, and handoff within contract. Customer notices and buyer rules apply. This is not the same as contingent closure inside CP ownership.

Crystallised shortfall

After secured recovery or asset realisation, a remaining balance may exist as an unsecured shortfall. That shortfall may then enter the contingent or written-off paths described elsewhere in this pack. See Secured recoveries interaction.

Credit reporting (orientation only)

Markets differ on whether “settled,” “paid,” or other codes apply. Often credit reporting is updated to settled rather than “paid in full” when closure was not full balance. Exact wording must follow bank policy and legal advice.

Why governance matters for end states

Silent closure in a DCA platform without CP authoritative update is a classic defect. End states should drive CP recall, suppression, finance posting, and reporting cohorts in one coherent timeline. If not, you will double-count recoveries, mis-state active placements, or contact customers who should be closed.