DCA and contingent collections
A training and operating model pack for teams who design, run, govern, or challenge debt collection agency (DCA) programmes, contingent fee models, and post write-off recoveries. Content is grouped into six packages: concepts and flows, operating model, technical blueprint, appendix, canonical DCA Governance documents and samples, and search across the full pack.
Clarity: DCA work can be outsourced without a write-off. This pack still spends material time on written-off allocation because many banks place most contingent volume there, not because DCA implies write-off.
Package 1: Training, concepts, and flows
Teach the topic: vocabulary, major decision points, lifecycle meaning, and how language in the market often diverges from clean theory. Start here if you are onboarding or aligning stakeholders.
Overview: what is a DCA?
BPO vs DCA vs debt sale, pre and post write-off use, contingent economics, recoveries lifecycle, common misunderstandings.
1.2Recoveries decision and treatment paths
Master strategic flow: contingent, internal, sale, waive or abandon, recycle versus end state. Secured recoveries called out as separate.
1.3Source of Record, write-off, charge-off
Benchmark chapter: SoR, GL, CP recoveries, DCA-reported state, why reconciliation matters.
1.4Written-off debt: MoSCoW and journey
Contingent branch after write-off: R1 and R2 as operating constructs, governance for end states.
1.5Allocation strategy and decisioning
Internal vs DCA vs sale vs abandon, NPV and conduct overlays, first versus second placement, strategy over time.
1.6Programme lifecycle
Strategy through exit: overlapping phases, pilots, why contract sign-off is not operating model readiness.
1.7Glossary
Terms aligned to the body of the pack.
Package 2: Operating model
How a credit provider actually runs a DCA model: ownership, cadence, performance, issues, and closure decisions. Use this when you are building run-state discipline, not only reading definitions.
DCA operating model overview
CP, DCA, finance and GL, risk and compliance, vendor management: practical roles.
2.2Controls framework
SoR, allocation, recall, payment, arrangement, reconciliation, credit reporting, ownership, failure patterns.
2.3Recall and reassignment
Recall as control and state transition: compliance and strategic recalls, DCA requests, CP authority, risks.
2.4Governance in practice
Oversight of controls and performance: cadence, escalation, attestation; not the same as controls themselves.
2.5Reporting and performance management
Layer 3 supported by controls; CP authoritative reporting; DCA as challenge data.
2.6OKRs, KPIs, and SLAs
Balanced objectives, conflicting definitions, perverse incentives.
2.7End states and closure decisions
Paid, settled, abandon, forgiveness, waiver, sale, crystallised shortfall: governance and reporting.
2.8Single account worked example
One narrative from recoveries decision through R1, recall, R2, and exit.
2.9Secured recoveries interaction
Short boundary chapter: separate process; shortfall may feed contingent model later.
Package 3: Technical blueprint
How you would build, integrate, reconcile, and audit: data domains, traceability, files, lineage, and implementation checkpoints.
Requirements: interfaces, data, activities, routes
Strategic path versus operational routes, recall fields and capabilities, sequencing, ownership.
3.2R1 / R2 traceability model
Refer, recall request, recall execution, category, balance, proposed versus actual next strategy.
3.3CP / DCA files and reconciliation
Placement, delta, recall and RQT files, SLAs, reconciliation, double-contact risk.
3.4Source of Record architecture
Core, GL, recoveries platform, DCA platform, boundaries and file flows.
3.5Reporting data lineage
Which system drives numerator and denominator, CP versus DCA-reported fields.
3.6Reconciliation and exception management
Balance, status, arrangement, payment breaks, thresholds, ageing.
3.7Onboarding and implementation checklist
Due diligence through go-live sign-off.
3.8COF for DCA
Control Orchestration Framework: state, gates, clocks, trace, credit reporting; CGF, REA, COP.
3.9Controls to COF mapping
Traditional versus engineered controls; maturity progression.
Package 4: Appendix
Reference material that supports multiple layers: issue categories, NPV, activity cost and effectiveness, effectiveness measurement across internal and DCA placements (NPV), exception handling, and alignment to governance logs.
Issue taxonomy and exception management
Categories A to D, ownership, silent leakage into risk.
NPV in debt collections and DCA decisioning
Timing, cost, risk, strategy-specific NPV, sale versus collect, SoR data.
Cost to collect: activity cost and effectiveness
Unit cost, effectiveness, rework, direct and indirect cost, link to NPV.
Measuring effectiveness: internal, DCA1, DCA2 (NPV)
Core metrics, recovery curve, DCA-specific fields, SoR alignment, segmentation.
Package 5: Search
Search across every page and section heading in this pack.
Package 6: Canonical DCA Governance and samples
The complete Qurioux Standardised DCA Governance Framework as shipped in docs/DCA-Governance/: executive HTML for every layer, sample monthly reporting dashboard, monthly review deck, implementation plan, and Markdown sources. Open the hub first, then drill into layers or samples.
DCA Governance hub
Index to all canonical pages: Layers 1 to 6, appendix, samples, rollout plan.
6.2Layer 3 exec (STD-DCA-REPORT-001)
Mandatory monthly pack sections and field definitions.
6.3Sample monthly pack dashboard
Illustrative KPIs and tables for one DCA and month.
6.4Implementation plan
STD-DCA-IMPL-001 phases, workstreams, dependencies, master checklist.
client-training-pack folder and upload to your intranet, SharePoint, or any static web host. Open index.html in a browser. All assets use relative paths so the pack works offline.