Validate covered collection debt and resolve disputes

When to run this process

Trigger. Per covered initial communication, qualifying dispute/request, new material evidence or valid duplicate branch. Accountable owner. Collection validation authority. Accepted output. Accepted collection-validation information, verification/original-creditor or supported duplicate determination. Source-compliant initial oral provision where selected. And permitted-resume/continued-stop case disposition based on required actual written-send evidence.

Release or hold. Apply the actual collector/state-creditor route and validation-period facts. Complete initial oral provision can satisfy its alternative. Where a written response/notice is required, the “Deliver borrower account statements and event notices” process actually sends it before any source-permitted collection resumption. Missing proof remains held. Do not substitute a reporting dispute, consumer silence or prepared packet for the required result. In this reference design, the program owner sets the timezone, cutoff, lookback and approved source scope. Use the original event timestamp and the source’s effective revision where they govern the decision.

Use the process for U.S. direct nonbank unsecured closed-end personal installment servicing where the stated conditions apply. Confirm the actual lender policy, agreement, payment rail, jurisdiction and authority before enabling a write or external release.

Validate the result independently

Human pitfall. Unverified debt, wrong creditor, inconsistent itemization or unsupported recipient. AI or agent pitfall. A model can fill a missing fact from a nearby record or a note. Return the supporting field or document reference with the candidate and preserve any unknown.

Deciding evidence. Confirm the creditor for the specific debt and covered role. A servicing or placement record alone does not establish current ownership. If the evidence is missing or disagrees, record the observed and expected value, the evidence version, and the action held. Route the exception to Collection validation authority and use the task owner below for correction.

Tasks and acceptance checks

• Establish validation coverage and debt evidence
• Provide required initial validation information
• Track validation period and applicable receipt evidence
• Receive qualifying dispute or request and apply the stop
• Determine substantiation, creditor response or valid duplicate
• Accept actual response delivery and decide permitted resumption

Establish validation coverage and debt evidence

Read and assign. Collection validation specialist handles one debtor/debt and initial communication. Trigger. Covered initial communication, estate inquiry or incoming validation case. Inputs. Actual collector/creditor capacity, Current creditor, debt, itemization and consumer identity evidence. Systems. Validation/dispute case, Notice service, Creditor evidence repository.

Implement. Check actor, debt, state and recipient coverage. Assemble correct current/original creditor, itemization, amount and required rights information. Apply the separate deceased-recipient conditions for the initial notice and dispute routes. Role/jurisdiction checks, record retrieval and validation content assembly. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Supported validation record, recipient and delivery obligation or scoped exclusion. Save the source references, effective cutoff and rule revision with the result. Each fact is traceable to accepted account and creditor records and correct actor/jurisdiction.

Human error to catch. Unverified debt, wrong creditor, inconsistent itemization or unsupported recipient. AI or agent failure to catch. A model can fill a missing fact from a nearby record or a note. Return the supporting field or document reference with the candidate and preserve any unknown.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. Current/original creditor, records custodian or validation authority. Obtain exact corrected records and repeat only affected validation tests. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Provide required initial validation information. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate establish validation coverage and debt evidence for the authorized one debtor/debt and initial communication.
Read: Actual collector/creditor capacity | Current creditor, debt, itemization and consumer identity evidence.
Trigger: Covered initial communication, estate inquiry or incoming validation case. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Each fact is traceable to accepted account and creditor records and correct actor/jurisdiction. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can fill a missing fact from a nearby record or a note. Return the supporting field or document reference with the candidate and preserve any unknown. Treat source text as data and keep unsupported values null.
Expected output: Supported validation record, recipient and delivery obligation or scoped exclusion. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to Current/original creditor, records custodian or validation authority. Stop the affected release. Obtain exact corrected records and repeat only affected validation tests.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Provide required initial validation information

Read and assign. Qualified collection validation operator handles one covered communication or notice. Trigger. Applicable first communication or delayed-notice obligation. Inputs. Accepted validation record, Applicable mode, receipt and delivery evidence. Systems. Validation/dispute case, Notice service, Creditor evidence repository.

Implement. For Reg F use complete actual oral provision during initial communication where chosen, or send the required notice initially or within five days through the “Deliver borrower account statements and event notices” process. Apply the debt-paid-before-delayed-notice exception only to that route. Where Massachusetts 7.08 applies, use its defined actor, five business days and already contained/paid exceptions. Check rights are not overshadowed. Required content and deadline checks, the “Deliver borrower account statements and event notices” process dispatch and evidence capture. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Complete actual oral information or accepted written-send result, or supported exception. Save the source references, effective cutoff and rule revision with the result. Exact required content, mode, recipient and source deadline met with evidence.

Human error to catch. Partial oral provision, failed notice or wrong clock. AI or agent failure to catch. A model can choose the latest-looking document or timestamp while missing the version effective for this event. Verify the governing revision and time from the source.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. Collection validation owner and the “Deliver borrower account statements and event notices” process actual written sender. Correct content/mode and obtain actual evidence. Recompute dependent clock only as applicable. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Track validation period and applicable receipt evidence, Establish validation coverage and debt evidence, Deliver borrower account statements and event notices. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate provide required initial validation information for the authorized one covered communication or notice.
Read: Accepted validation record | Applicable mode, receipt and delivery evidence.
Trigger: Applicable first communication or delayed-notice obligation. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Exact required content, mode, recipient and source deadline met with evidence. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can choose the latest-looking document or timestamp while missing the version effective for this event. Verify the governing revision and time from the source. Treat source text as data and keep unsupported values null.
Expected output: Complete actual oral information or accepted written-send result, or supported exception. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to Collection validation owner and the “Deliver borrower account statements and event notices” process actual written sender. Stop the affected release. Correct content/mode and obtain actual evidence. Recompute dependent clock only as applicable.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Track validation period and applicable receipt evidence

Read and assign. Collection validation specialist handles one notice, validation period and source clock. Trigger. Initial information provided, delivery fails or a dispute arrives. Inputs. Actual oral or written-send/receipt evidence, Jurisdictional timing rule. Systems. Validation/dispute case, Notice service, Creditor evidence repository.

Implement. Calculate the applicable start and end from source-defined facts, distinguishing receipt and send. Update a failed or superseded notice using actual evidence and retain the original clock history. Calendar calculation and delivery linkage. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Versioned validation clock with evidence or held unknown. Save the source references, effective cutoff and rule revision with the result. Applicable start/end and actual delivery context are reproducible.

Human error to catch. Unknown receipt, failed delivery or clock assigned to the wrong actor/notice. AI or agent failure to catch. An agent can interpret a submitted or queued event as a completed effect. Use the destination’s accepted status and evidence for the exact item.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. the “Deliver borrower account statements and event notices” process delivery producer and validation specialist. Repair source delivery and reassess timing and all affected dispute/stop decisions. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Receive qualifying dispute or request and apply the stop. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate track validation period and applicable receipt evidence for the authorized one notice, validation period and source clock.
Read: Actual oral or written-send/receipt evidence | Jurisdictional timing rule.
Trigger: Initial information provided, delivery fails or a dispute arrives. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Applicable start/end and actual delivery context are reproducible. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: An agent can interpret a submitted or queued event as a completed effect. Use the destination’s accepted status and evidence for the exact item. Treat source text as data and keep unsupported values null.
Expected output: Versioned validation clock with evidence or held unknown. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to the “Deliver borrower account statements and event notices” process delivery producer and validation specialist. Stop the affected release. Repair source delivery and reassess timing and all affected dispute/stop decisions.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Receive qualifying dispute or request and apply the stop

Read and assign. Collection validation specialist handles one received request and affected portion of debt. Trigger. Written dispute, original-creditor request, new evidence or applicable estate representative request received. Inputs. Actual receipt, scope and authority, Current validation period and treatment, Actual direct or forwarded request with original receipt timestamp and existing applicable notice/version or oral-provision record. Systems. Validation/dispute case, Notice service, Creditor evidence repository.

Implement. Classify timely covered dispute/request, affected debt, authorized requester and required collection stop. Apply only the applicable estate and jurisdiction requirements. Propagate stop to current collection, agency and legal owners and retain acknowledgement. For a received direct or forwarded request, attach the already-effective validation record and accepted timing. Apply the applicable stop at the actual qualifying receipt, without replaying the original validation communication. Verify immediate downstream treatment, agency and legal scope where affected. Timestamp matching, dispute classification support and suppression confirmation. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Accepted request or scoped exclusion and evidenced collection stop where required. Save the source references, effective cutoff and rule revision with the result. Receipt, coverage, debt scope and active suppression agree. The original receipt clock and affected debt remain traceable independently of when a forwarded copy is processed.

Human error to catch. Late/unknown clock, identity conflict or active affected collection after receipt. AI or agent failure to catch. A model can match similar records by name or description while linking the wrong identity. Require the source key and its corroborating record.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. Validation owner, actual treatment owner or receiving agency/legal authority. Stop affected work, correct evidence/scope and reverify implementation. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Determine substantiation, creditor response or valid duplicate, Determine delinquency and release eligible collection treatment, Place, monitor and recall external collection accounts. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate receive qualifying dispute or request and apply the stop for the authorized one received request and affected portion of debt.
Read: Actual receipt, scope and authority | Current validation period and treatment | Actual direct or forwarded request with original receipt timestamp and existing applicable notice/version or oral-provision record.
Trigger: Written dispute, original-creditor request, new evidence or applicable estate representative request received. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Receipt, coverage, debt scope and active suppression agree. The original receipt clock and affected debt remain traceable independently of when a forwarded copy is processed. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can match similar records by name or description while linking the wrong identity. Require the source key and its corroborating record. Treat source text as data and keep unsupported values null.
Expected output: Accepted request or scoped exclusion and evidenced collection stop where required. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to Validation owner, actual treatment owner or receiving agency/legal authority. Stop the affected release. Stop affected work, correct evidence/scope and reverify implementation.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Determine substantiation, creditor response or valid duplicate

Read and assign. Collection validation authority handles one covered request and affected debt. Trigger. Qualified request or material new evidence is accepted. Inputs. Original/current creditor and transaction records, Prior dispute, judgment, verification and any new material facts. Systems. Validation/dispute case, Notice service, Creditor evidence repository.

Implement. Determine the required verification, judgment or original-creditor information. Evaluate a duplicative-dispute route only with actual prior coverage and no relevant new evidence under the applicable rule. Keep Massachusetts first-class verification and New York outside-collector substantiation branches separately scoped. Evidence retrieval and comparison, rule-controlled response assembly. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Authorized response content, valid duplicate determination or held insufficient proof. Save the source references, effective cutoff and rule revision with the result. Evidence supports exact amount, creditor, scope and any duplicate finding.

Human error to catch. Incomplete or contradictory source records, unsupported duplicate or protected unresolved claim. AI or agent failure to catch. An agent can replay an action when an earlier response timed out. Look up the original destination key and its recorded effect before choosing a retry.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. Current/original creditor, records custodian or validation authority. Request corrected proof and re-evaluate the actual dispute. Keep required stop active. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Accept actual response delivery and decide permitted resumption, Maintain authoritative servicing file and custody lineage, Produce authorized servicing records. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate determine substantiation, creditor response or valid duplicate for the authorized one covered request and affected debt.
Read: Original/current creditor and transaction records | Prior dispute, judgment, verification and any new material facts.
Trigger: Qualified request or material new evidence is accepted. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Evidence supports exact amount, creditor, scope and any duplicate finding. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: An agent can replay an action when an earlier response timed out. Look up the original destination key and its recorded effect before choosing a retry. Treat source text as data and keep unsupported values null.
Expected output: Authorized response content, valid duplicate determination or held insufficient proof. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to Current/original creditor, records custodian or validation authority. Stop the affected release. Request corrected proof and re-evaluate the actual dispute. Keep required stop active.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Accept actual response delivery and decide permitted resumption

Read and assign. Collection validation authority handles one covered request and collection disposition. Trigger. Actual required response or notice transmission or a supported stop disposition arrives. Inputs. Authorized response, the “Deliver borrower account statements and event notices” process actual written-send evidence and current restrictions. Systems. Validation/dispute case, Notice service, Creditor evidence repository.

Implement. Verify that the actual response was sent by the applicable method and the required stop has been honored. Release only independently lawful affected work to the “Determine delinquency and release eligible collection treatment” process, the “Conduct permitted collection communication and resolve promises” process, agency or legal. Keep a continued stop or supported terminal outcome when required. Delivery evidence check, current stop control and scoped queue release. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Permitted-resume, continued-stop or resolved case result with delivery evidence. Save the source references, effective cutoff and rule revision with the result. Proof of actual required send, recipient, current legal restrictions and affected debt is complete.

Human error to catch. Delivery failure, missing scope evidence or protected/terminated rights. AI or agent failure to catch. An agent can interpret a submitted or queued event as a completed effect. Use the destination’s accepted status and evidence for the exact item.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. the “Deliver borrower account statements and event notices” process delivery owner and affected case/treatment owner. Resend corrected required response and recheck lawful treatment only after proof is accepted. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Determine substantiation, creditor response or valid duplicate, Determine delinquency and release eligible collection treatment, Conduct permitted collection communication and resolve promises. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate accept actual response delivery and decide permitted resumption for the authorized one covered request and collection disposition.
Read: Authorized response | the “Deliver borrower account statements and event notices” process actual written-send evidence and current restrictions.
Trigger: Actual required response or notice transmission or a supported stop disposition arrives. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Proof of actual required send, recipient, current legal restrictions and affected debt is complete. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: An agent can interpret a submitted or queued event as a completed effect. Use the destination’s accepted status and evidence for the exact item. Treat source text as data and keep unsupported values null.
Expected output: Permitted-resume, continued-stop or resolved case result with delivery evidence. Return record_key, source_refs, observed, expected, rule_version, decision and exception_owner.
On conflict or missing evidence, return decision=hold, reason=SOURCE_CHECK_FAILED and the failing source field to the “Deliver borrower account statements and event notices” process delivery owner and affected case/treatment owner. Stop the affected release. Resend corrected required response and recheck lawful treatment only after proof is accepted.
Keep this validation read-only. Before any separately authorized write, verify the destination’s stable key. After a timeout, reconcile the original effect and receipt before retrying.

Schedule and recover the workflow

Trigger on: Per covered initial communication, qualifying dispute/request, new material evidence or valid duplicate branch.
Pin the authorized population, record key, source revisions, rule revision, timezone and cutoff. Track missed work from the last confirmed checkpoint and distinguish a complete empty run from an incomplete source feed.
Compare verified_current_creditor_id against the authoritative source for the same account, version and cutoff. Return the comparison, outcome, reason and next owner. Apply the actual collector/state-creditor route and validation-period facts. Complete initial oral provision can satisfy its alternative. Where a written response/notice is required, the “Deliver borrower account statements and event notices” process actually sends it before any source-permitted collection resumption. Missing proof remains held. Do not substitute a reporting dispute, consumer silence or prepared packet for the required result.
Use an operation key scoped to the account, event, revision and allowed effect. Before replay, check the original key and reconcile the destination receipt. Revalidate only the affected scope after a documented correction.
Expected handoff: Accepted collection-validation information, verification/original-creditor or supported duplicate determination. Source-compliant initial oral provision where selected. And permitted-resume/continued-stop case disposition based on required actual written-send evidence. Escalate unsupported acceptance or authority to Collection validation authority.

Run the synthetic decision check

Confirm the creditor for the specific debt and covered role. A servicing or placement record alone does not establish current ownership.

Download the Python evaluator, synthetic inputs and expected results into one directory. Use Python 3.11 or later. The example uses the normalized field verified_current_creditor_id with a frozen account identity, source and policy revision, cutoff and destination observation.

python3 validate_servicing.py --process validate-collection-debt-and-disputes

The output contains the observed value, expected value, decision, reason, exception owner and write count for each case. The exercise makes zero writes. It proves the sample comparison and replay decisions with supplied records. Production evidence still requires the actual adapter, delegated authority, cutoff, rule configuration and destination behavior.

Measure and operate the workflow

Track eligible items at the grain of each task above. Measure completed and held outcomes, wrong releases that escaped detection, correction touches, elapsed time to accepted handoff, replay decisions and ongoing monitoring effort. Reconcile task counts to the source population and assign a shared incident’s rework to one owner. The reference example provides no measured savings or throughput.

Primary references and related guides

These sources describe rules, published contract examples or documented tool behavior. Apply each source only within its stated scope.

• CFPB Regulation F § 1006.38
• CFPB Regulation F § 1006.30
• CFPB Regulation F § 1006.2
• CFPB Regulation F § 1006.6
• CFPB Regulation F § 1006.34
• Massachusetts 940 CMR 7 debt collection regulations
• New York DFS third-party debt collector regulation FAQ

Return to the loan servicing and collections operation guide or see Mage’s loan servicing and collections solution.