This Lesson 24 package translates “tax debt recovery” into a repeatable, auditable, legally safe operating system for practitioners. Because the jurisdiction is unspecified, the toolkit is built as a comparative reference model anchored to: (i) United States IRS statutory “collection due process” and codified tools (installment agreements, compromise, lien/levy, strict confidentiality), (ii) UK HMRC operational manuals and modern enforcement routes (Time To Pay, Taking Control of Goods framework, Direct Recovery of Debts safeguards, a statutory Charter and confidentiality code), (iii) Canada CRA collections policies and statutory powers (payment arrangements; “Requirement to Pay” third‑party garnishment; defined 10‑year collection limitation; strong confidentiality), and (iv) civil‑law examples emphasizing formal administrative procedure and rights of defense (e.g., Germany AO §91 hearing/right to be heard; France SATD administrative third‑party seizure).

The core teaching idea is that effective debt management combines: segmentation + service and payment facilitation + proportionate escalation + rigorous documentation + compliance controls. The OECD’s compliance risk management (CRM) approach supports this systems view, and OECD debt-management work highlights the value of differentiating debtors and addressing payment issues earlier in the cycle.

Deliverables included below: clear learning objectives; a step‑by‑step end‑to‑end workflow with mermaid diagrams; SOP templates (intake, triage, contact, payment plans, escalation, field safety); standardized document and evidence checklists; compliance checklists (due process, data protection/confidentiality, evidence preservation/chain‑of‑custody discipline); risk scoring and vulnerability flags; common legal pitfalls with mitigation and illustrative cases; classroom case studies; assessment questions with answers; KPIs for performance and program evaluation; and prioritized reading links to statutes, manuals, and official guidance.

Learning objectives. By the end of Lesson 24, learners can:

Build and run a debt recovery workflow from case intake through closure, including segmentation, communications, payment plans, monitoring, and proportionate enforcement escalation.

Identify and correctly use core enforcement documents and decision points (e.g., notice and demand, lien notices, final levy notice/hearing rights; third‑party garnishment requirements; “notice of enforcement” before taking control of goods).

Apply compliance controls: due process requirements, confidentiality/data protection rules, identity/authorization validation, and defensible documentation that supports review/appeal or litigation.

Use risk segmentation and escalation triggers to allocate effort and select the least intrusive effective intervention, consistent with OECD CRM principles and leading debt-management practice.

Recognize and mitigate common legal pitfalls: statute-of-limitations errors, improper notice/service, ultra vires concessions, procedural fairness failures, privacy breaches, and unlawful seizure/levy.

Suggested session plan (2.5–3 hours). Use the workflow as the spine: (a) 35 minutes concept briefing (workflow + constraints), (b) 70 minutes lab (templates + case file simulation), (c) 35 minutes “pitfalls + cases” clinic, (d) 25 minutes assessment/debrief. Publication 594 is a practical “collection lifecycle” overview for U.S. anchoring; adapt structure to the learners’ jurisdiction.

Practitioner workflow as an operating system

The workflow below is jurisdiction-neutral, with reference-jurisdiction “hooks” at each gate (U.S./UK/Canada/civil-law examples).

Why this structure is defensible: - “Rights + due process” gates exist because statutes often require prescribed notices and hearing opportunities before intrusive enforcement (e.g., U.S. lien notice hearing rights under §6320 and levy hearing rights under §6330; Canada’s “collections restrictions” delaying certain legal actions in the first 90 days after assessment; UK’s minimum “notice of enforcement” period before taking control of goods). - “Segmentation” is explicit because OECD CRM and OECD debt-management work emphasize differentiating debtors and selecting the most effective treatments accordingly. - “Documentation + audit trail” is explicit because operational manuals (e.g., IRS Field Collection guidance) embed case-history expectations and governance/controls around contact and actions.

Use an escalation ladder that is proportionate (least intrusive effective intervention) and legally gated (no jumping over required notices/hearings).

Reference jurisdiction guardrails for Stage 5 (“notice gate”). - U.S.: assessment is followed by “notice and demand” (§6303), lien arises after demand if unpaid (§6321), and specific notice/hearing rules apply for lien-filing and levy pathways (§6320; §6330). - UK: if enforcing via Taking Control of Goods, regulations require a notice of enforcement and a minimum of 7 clear days before control is taken. - Canada: CRA states it generally cannot start listed legal actions (including court proceedings, Federal Court certification, and “Requirement to Pay” third‑party demands) until 90 days after sending an assessment/reassessment notice, subject to specified exceptions. - Civil-law examples: administrative acts often require formalized “right to be heard” safeguards (Germany AO §91) and/or codified rights of defense (EU Sopropé).

Comparison table: enforcement tools, timelines, and legal thresholds

Because jurisdiction is unspecified, the table intentionally uses reference jurisdictions and flags where thresholds vary.

This section provides templates for operational use. Replace with your jurisdiction’s approved forms/letters where required; templates are pedagogical but aligned to reference-jurisdiction practices.

SOP template for case intake and legal status check

SOP: Case Intake (Collections) Purpose: - Create a clean, legally compliant case file that can support escalation or litigation. Steps: 1) Open case file and assign unique case ID; log source (return assessment, audit assessment, self-assessment, third-party report). 2) Identity verification: - Confirm taxpayer legal name, TIN/ID, business number, registered address(es), authorized contact(s). - Confirm representative authorization (POA/agent authorization) before discussing case. 3) Pull account profile: - Tax type(s), periods, assessment dates, balance components (tax/interest/penalties), prior actions. 4) Legal status check: - Is there an active dispute/appeal window, hearing request, or statutory collections restriction? - Insolvency/deceased/under administration? (Route to specialized unit). - Statute-of-limitations / limitation clock: compute remaining time and any tolling/restarts. 5) Data governance: - Apply confidentiality and data protection rules; restrict access; log disclosures. 6) Documentation: - Create “Case Summary Page 1”: debt snapshot; risk flags; immediate next action; deadlines.

Reference anchors: - Canada’s ITA §222 defines/limits collection actions by a limitation period and lists restart/tolling mechanisms—important at intake to avoid time‑barred action. - Identity/authorization validation is explicitly emphasized in CRA collections policy (“confirm the identity and authorization… before release”). - IRS Field Collection IRM on taxpayer contacts includes “case histories” expectations and governance controls around contact and documentation.

SOP template for triage and segmentation

SOP: Triage & Segmentation Objective: - Match intervention to taxpayer risk and likely responsiveness. Inputs: - Debt size/age; compliance history; prior broken arrangements; asset signals; vulnerability indicators; safety indicators. Segmentation outcomes (choose one): A) "Can pay / will pay" -> fast digital/self-serve resolution B) "Can pay / won't pay" -> structured escalation with tight deadlines C) "Can't pay / will pay" -> payment plan or hardship pathway D) "Can't pay / won't pay" -> verify facts; enforce key safeguards; consider insolvency referral E) "Disputed/uncertain" -> route to dispute resolution; pause enforcement where required Mandatory outputs: - Segment label - Next best action and channel - Deadlines (response date; review date) - Escalation trigger(s) - Documentation checklist completed

SOP template for taxpayer contact scripts and documentation

SOP: Contact & Case History Recording 1) Pre-contact checks: - Verify authorization/POA status. - Identify required disclosures and prohibited disclosures. - Confirm whether additional notice requirements apply (e.g., third-party contacts). 2) First contact script (service-forward): - Confirm identity. - State purpose and amount, period(s), and due date(s). - Explain rights/review options in plain language. - Offer menu: pay in full; payment plan; hardship; dispute pathway where eligible. - Confirm next step and deadline. 3) Documentation requirements (same day): - Record contact attempt type (phone/letter/portal/in-person). - Record taxpayer statements relevant to ability-to-pay, dispute, vulnerability. - Record documents requested and deadlines. - Record warnings/rights notice delivered. - Record next scheduled action and escalation trigger.

Reference anchors: IRS IRM 5.1.10 (Taxpayer Contacts) is explicitly designed to guide actions “prior to, during and following” taxpayer contact and includes a “Case Histories” section, reinforcing the need for disciplined case notes.

SOP template for payment-plan processing

SOP: Payment Plan Processing (Installment / Time-to-Pay / Arrangement) 1) Eligibility gate: - Confirm debt is enforceable. - Confirm no legal restriction requires pause (appeal/dispute/collection restriction). 2) Ability-to-pay verification: - Request standardized financial statement (income, expenses, assets, liabilities). - Apply reasonableness and verify key items (bank statements, payroll, leases). 3) Proposal design: - Select plan type: short-term arrangement; long-term installment; direct debit; payroll deduction. - Define: payment frequency, due dates, method, review clause, default and cure rules. 4) Documentation: - Written agreement summary + taxpayer acknowledgment. - Calendar monitoring schedule and automated reminders. 5) Monitoring: - Missed payment => contact within X days, assess cause, cure plan or escalate. - New debt incurred => enforce “stay current” policy; re-segment.

Reference anchors: - U.S. installment agreements are statutory (IRC §6159) and regulated; this supports a formal “eligibility + terms + monitoring” SOP. - HMRC Time To Pay is described as tailored to what customers can afford; this aligns with ability-to-pay verification and individualized terms. - CRA payment arrangements require supporting documentation to prove income/expenses/assets/liabilities and may postpone payment during hardship, consistent with a verified arrangement pathway. - Standardized financial statements exist in IRS practice (Form 433‑A and guidance on how to complete it).

SOP template for enforcement escalation and approvals

SOP: Escalation to Enforcement 1) Confirm “notice gate” compliance: - Required notices sent? hearing/opportunity-to-be-heard met? - Required waiting periods met? 2) Confirm proportionality rationale: - Why lesser steps failed (no contact, repeated default, asset dissipation risk, strategic nonpayment). 3) Tool selection: - Third-party action (bank/wage/offset) - Security (lien/charge/registration) - Seizure/taking control of goods / levy - Court step (judgment/certification) or insolvency referral 4) Approvals and legal check: - Ensure internal approvals documented; verify exemptions/restrictions. 5) Execution: - Serve documents correctly; maintain evidence of service. 6) Post-action: - Update balances; issue release/withdrawal where required; log all actions.

Reference anchors: - IRS levy process includes “pre-levy actions and approvals” and “restrictions on levy,” supporting a structured escalation checklist. - Canada explicitly lists “Requirement to Pay” and Federal Court certification as collection actions subject to timing restrictions, reinforcing the need for a “notice gate” compliance check. - UK Taking Control of Goods regulations include a minimum notice period before control of goods is taken, reinforcing waiting-period discipline.

SOP template for field visit safety

SOP: Field Visit Safety & Security Pre-visit: - Check safety flags in system (threats, prior incidents). - Consider non-contact observational visit first if appropriate. - Plan visit time/day; share itinerary with supervisor; confirm check-in protocol. - Verify address/occupancy; avoid high-risk situations (isolated locations) without safeguards. During visit: - Keep distance and maintain safe exit path. - Use identity/credential protocol. - De-escalate; end visit if threatened. - Avoid prohibited third-party contact settings (jurisdiction policies vary). Post-visit: - Record events immediately: date/time, participants, statements, safety observations. - File any threat reports per employee protection program.

Reference anchors: IRS IRM 5.1.3 is dedicated to “Safety, Security, and Control” for field collection; IRS also maintains a Potentially Dangerous Taxpayer (PDT) program in IRM 25.4.1 to manage safety risks.

Core “universal” documents (adapt by jurisdiction):

Insolvency-oriented “proof-of-debt” forms (include because collections often intersects with insolvency): - U.S. Bankruptcy Official Form 410 (Proof of Claim). - England & Wales Insolvency Rules 2016 r14.4 proof-of-debt framework and Insolvency Service template. - Canada OSB Form 31 Proof of Claim (new version effective for estates filed Sept 16, 2024 and after).

Evidence preservation and chain-of-custody discipline

Jurisdictions vary on formal evidentiary rules for administrative records, but litigation and review risk is universal. Use a disciplined “chain-of-custody mindset” for documents, recordings, and digital extracts.

Practitioner evidence checklist (jurisdiction-neutral): - Maintain immutable originals (scanned PDFs with hash or secure repository); keep redacted public copies when required. - Record “who/what/when/how obtained” for each critical document (bank statements, property checks, employer confirmation) to rebut authenticity challenges. - Preserve service evidence: mail logs, delivery confirmations, screenshots of portal delivery, call recordings metadata (where lawful). - Maintain case history notes that tie actions to statutory authority and escalation rationale.

Why this matters (examples): Canada’s statutory scheme explicitly uses court-facing steps such as Federal Court certification (referenced in CRA policy) and defines “actions” and limitation periods in ITA §222, increasing the importance of accurate records and timestamps. IRS Field Collection manuals emphasize structured contact procedures and case histories, reinforcing “document as you go” discipline.

Use a simple scoring matrix for consistent decisioning and quality review.

Escalation triggers (examples): repeated missed payments without contact; new debt incurred during arrangement; refusal to provide financial evidence; evidence of asset dissipation; approaching limitation expiry; and credible safety threats.

This section is framed as “pitfall → why it fails → how to prevent,” with case illustrations where available.

“Why documentation is a legal control,” not paperwork

In contested collection environments, the file becomes the institutional memory. IRS field collection guidance explicitly frames taxpayer contact procedures as serving taxpayer rights, employee safety, and effective case resolution, and includes a case-history discipline. Similarly, CRA collections policy stresses consistent/fair application and confirms that legal action will include some debt details, reinforcing careful disclosure boundaries and recordkeeping.

Classroom activities and case studies

Case study scenario A: “Broken payment plan, nearing limitation.” Students receive a file: taxpayer had an arrangement, defaulted twice, and the collection limitation is approaching. They must: compute limitation-risk, re-segment, choose an intervention, draft the required notices, and justify escalation choices. Use U.S. §6502 and Canada ITA §222 as reference templates for the “time-to-limit” logic and restart rules.

Case study scenario B: “Third-party garnishment decision under uncertainty.” A wage garnishment/bank levy is proposed but there is uncertainty about ownership of funds (joint account or third-party holding). Students must choose whether to proceed, what evidence is required, and how to notify parties. Use National Bank of Commerce as an illustration of legal disputes arising from levy execution.

Case study scenario C: “UK-style enforcement journey.” Students apply a UK enforcement path: Time To Pay attempt → Notice of Enforcement → Taking Control of Goods after the minimum period, ensuring the “7 clear days” rule is met and documented.

Assessment questions with model answers

Question: In the U.S. reference model, what is the purpose of the §6303 “notice and demand,” and what timing constraint applies? Answer: It initiates formal collection by notifying the taxpayer of the assessed amount and demanding payment; §6303 requires notice “as soon as practicable” and within 60 days after assessment.

Question: What statutory provisions anchor “notice and opportunity for hearing” before levy and after filing a lien notice in the U.S. model? Answer: Levy: IRC §6330; lien notice filing: IRC §6320.

Question: Under Canada’s ITA §222, when does the limitation period generally begin and end, and what events can restart it? Answer: It generally begins 90 days after the last relevant notice is sent/served and ends 10 years after it begins; it restarts upon written acknowledgment or payment, commencement of an action, or certain assessments against persons related to the debt.

Question: In England & Wales, what is the minimum notice period before an enforcement agent can take control of goods? Answer: Notice of enforcement must be given not less than 7 clear days before taking control of goods (subject to specified exceptions).

Question: Give one example of a case illustrating that agencies cannot grant extra-statutory concessions that contradict statute. Answer: Wilkinson (House of Lords) illustrates limits on administrative “care and management” powers to extend tax benefits not authorized by statute.

Question: Name one primary confidentiality statute for each of the U.S., UK, and Canada reference models. Answer: U.S.: IRC §6103; UK: CRCA 2005 s18; Canada: ITA §241.

KPIs and program metrics for practitioners and program evaluation

A practitioner toolkit must measure both effectiveness and legality/quality. The table below combines widely used debt indicators with “quality and rights” indicators.