DCA operating model overview
Purpose. Translate concepts into day-to-day ownership. A DCA programme fails when everyone agrees on the contract but nobody agrees on who moves the balance, who accepts a recall request, or who attests the monthly pack. This page names the usual first-line and second-line roles and what “good” looks like in handoffs.
Controls and rhythm. Operating model design must embed controls (SoR, recall, reconciliation, credit reporting) and clear recall authority. Where the bank adopts a Control Orchestration Framework, governance meetings shift toward validating engineered execution rather than manually catching every breach; see COF for DCA.
Executive sponsor and CP ownership
The credit provider owns the customer relationship, the receivable (until sold), regulatory accountability, and the authoritative ledger for balance and payments. Sponsorship sits typically with the head of collections or recoveries with clear backing from risk and finance for incentive design and material strategy shifts.
Ownership includes publishing segmentation rules, approving exceptions to placement, signing off recalls that carry legal or conduct sensitivity, and ensuring the recoveries book remains the operational source of truth for placement state. See Source of Record.
DCA role: delivery, not truth
The DCA executes collection activity within contract, discloses appropriately, logs contact and outcomes, requests recalls when required, and remits funds. It does not replace CP balance truth. Dual-state reconciliation exists precisely because the DCA must work from timely CP feeds while also reporting what it believes it is collecting against.
Account managers on the DCA side should have a defined path into CP operations for file defects, SLA misses, and conduct issues. Informal chat is not a substitute for logged issues categories. See Issue taxonomy.
Finance and general ledger
Finance cares about correct recognition of recoveries, fee accruals, impairment movements, and period close. They are not running dialler campaigns, but they need confidence that operational numbers in Layer 3 tie to GL postings and that contingent fees do not drift from contract mechanics.
Typical failure: operations celebrates cash collections while finance finds fee disputes or mis-posted recoveries because DCA remittance lines and CP cash allocation use different definitions.
Risk, compliance, and legal
Second line sets appetite, tests controls, and challenges incentive design. Compliance interprets conduct rules, fair treatment expectations, and credit reporting obligations in your jurisdiction. Legal advises on settlements, litigation handoffs, bankruptcy, and debt sale documentation.
In mature models, these functions receive the same monthly pack definitions as first line, not a parallel spreadsheet. Misaligned definitions between risk and operations is a red flag.
Vendor management
Procurement onboards the DCA, manages contract change, tracks performance against SLAs, coordinates exit, and maintains business continuity when a vendor fails a checkpoint. Vendor management should not “own” customer outcomes alone; they coordinate with collections operations and risk.
Healthy programmes treat vendor scorecards as joint artefacts: CP operations confirms data quality issues, DCA confirms remediation plans, risk tracks conduct metrics.
Cross-functional rhythm
Weekly operational forums focus on breaks, recalls, and SLA recovery. Monthly forums interpret Layer 3 trends. Quarterly forums test whether incentives and policies still match risk appetite. Annual review reconnects contract, fees, and panel strategy.
Details sit in Governance and Programme lifecycle.
One-page RACI-style view
| Topic | CP collections / recoveries | Finance | Risk / compliance | DCA |
|---|---|---|---|---|
| Authoritative balance | Accountable owner of recoveries book | Validates GL tie-out | Challenges material breaks | Consumes feeds; reports dual state |
| Placement and recall | Decision and execution | Informed on material $ | Escalations on conduct | Executes stop work |
| Monthly pack | Produces CP-controlled sections | Uses for P&L narrative | Second line review | Inputs and attests vendor sections |
| Issues and incidents | First line ownership | Notify on financial materiality | Category B and C escalation | Root cause and fix plans |