Resolve loan-owner instructions and servicing conflicts

When to run this process

Trigger. Receipt of an owner servicing instruction or a detected instruction/agreement/law/practices/document conflict. Event grain is the specific instruction/case, not every loan or annual policy cycle. Accountable owner. Servicing owner-instruction authority, functional reference allocation. Accepted output. Documented permissible, rejected, held or no-change individual owner-instruction disposition, controlling priority and required conflict notice, with the affected execution owner identified.

Release or hold. Complete when lawful direction/hold and required notice are recorded with the source-required evidence. Unresolved instructions remain specifically held/escalated. Other lawful unaffected work continues. Source does not establish automatic owner-response acceptance or an invented universal response SLA. 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. Missing instruction, unauthorized sender, wrong owner/pool, conflicted scope. AI or agent pitfall. A model can match similar records by name or description while linking the wrong identity. Require the source key and its corroborating record.

Deciding evidence. Compare the proposed instruction to the actual written direction from the authorized owner. A previously accepted direction cannot resolve a later conflict. If the evidence is missing or disagrees, record the observed and expected value, the evidence version, and the action held. Route the exception to Servicing owner-instruction authority, functional reference allocation and use the task owner below for correction.

Tasks and acceptance checks

• Validate covered owner and written instruction
• Determine controlling individual instruction and permissible action
• Give required conflict notice and hand off the decision

Validate covered owner and written instruction

Read and assign. Servicing owner-instruction authority. Actual Purchaser produces its own written direction handles owner, instruction version and affected loan or pool. Trigger. Receipt of purported owner instruction or identified authority/document conflict. Inputs. Actual owner and contract/delegation evidence, Written instruction, regulatory or supervisory basis, Affected Loan Documents and current practices. Systems. Owner instruction and contract register, Loan/source-document index.

Implement. Validate actual capacity, scope and commercially reasonable written instruction under source conditions. Distinguish covered owner instruction from ordinary consumer request and general policy release. Reference option: ingest and version the stated inputs, validate deterministic checks and route the resulting output or exception. Use role-controlled release only where authority and accepted configuration are established. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Authenticated scoped instruction/case, or owned rejected/held intake. Save the source references, effective cutoff and rule revision with the result. Exact Purchaser/Servicer capacity, covered population, actual written direction or defect, and stated regulatory/supervisory predicate.

Human error to catch. Missing instruction, unauthorized sender, wrong owner/pool, conflicted scope. 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. Actual Purchaser or contract/legal authority corrects affected instruction or scope. Actual Purchaser or contract/legal authority corrects affected instruction or scope . Then reaccept only that case. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Determine controlling individual instruction and permissible action. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. LendingClub Master Loan Servicing Agreement form filed 2020. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate validate covered owner and written instruction for the authorized owner, instruction version and affected loan or pool.
Read: Actual owner and contract/delegation evidence | Written instruction, regulatory or supervisory basis | Affected Loan Documents and current practices.
Trigger: Receipt of purported owner instruction or identified authority/document conflict. 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 Purchaser/Servicer capacity, covered population, actual written direction or defect, and stated regulatory/supervisory predicate. 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: Authenticated scoped instruction/case, or owned rejected/held intake. 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 Actual Purchaser or contract/legal authority corrects affected instruction or scope. Stop the affected release. Actual Purchaser or contract/legal authority corrects affected instruction or scope . Then reaccept only that case.
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 controlling individual instruction and permissible action

Read and assign. Actual Servicer in covered contract. Obtain qualified Legal/Compliance input if unresolved handles exact instruction and affected servicing output. Trigger. Accepted instruction or identified conflict. Inputs. Validated instruction and owner authority, Applicable Law, Accepted Servicing Practices, Loan Documents and Agreement, Current protected account constraints. Systems. Owner instruction case record, Source/rule version index.

Implement. Apply §3.1 hierarchy where applicable. A qualifying written Purchaser instruction controls over the Agreement, subject to Applicable Law first, Accepted Servicing Practices second and Loan Documents third in conflicts. Determine permissible, rejected, held or no-change result and identify actual affected execution owner. Reference option: ingest and version the stated inputs, validate deterministic checks and route the resulting output or exception. Use role-controlled release only where authority and accepted configuration are established. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Recorded controlling priority and scoped decision or hold. Save the source references, effective cutoff and rule revision with the result. Apply actual source priority and source-defined trigger. Retain protected borrower/court rights. A decision does not execute payment, document, report or new general policy.

Human error to catch. Wrong priority, ambiguous source protection or unsupported owner decision. 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. Actual Legal/Compliance/contract source clarifies authority. Actual Legal/Compliance/contract source clarifies authority . Then redo individual decision and recheck previously held effects. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Give required conflict notice and hand off the decision. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. LendingClub Master Loan Servicing Agreement form filed 2020. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate determine controlling individual instruction and permissible action for the authorized exact instruction and affected servicing output.
Read: Validated instruction and owner authority | Applicable Law, Accepted Servicing Practices, Loan Documents and Agreement | Current protected account constraints.
Trigger: Accepted instruction or identified conflict. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Apply actual source priority and source-defined trigger. Retain protected borrower/court rights. A decision does not execute payment, document, report or new general policy. 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: Recorded controlling priority and scoped decision or hold. 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 Actual Legal/Compliance/contract source clarifies authority. Stop the affected release. Actual Legal/Compliance/contract source clarifies authority . Then redo individual decision and recheck previously held effects.
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.

Give required conflict notice and hand off the decision

Read and assign. Actual Servicer for source conflict notice. Other producing process accepts its own work handles purchaser, instruction version, conflict notice and affected output. Trigger. Applicable conflict or accepted permissible decision requiring local execution. Inputs. Controlling priority and exact conflict basis, Actual Purchaser destination, Agreed downstream execution or scope of hold. Systems. Contract communication/audit log, Scoped execution queue.

Implement. Use commercially reasonable efforts to give prompt conflict notice under the source route. Preserve delivery attempt/evidence and outcome without an invented universal response SLA. Route only independently authorized affected work or refer actual new general rule to the “Release applicable servicing policies, delegated authorities and configurations” process. Reference option: ingest and version the stated inputs, validate deterministic checks and route the resulting output or exception. Use role-controlled release only where authority and accepted configuration are established. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Source-qualified conflict notice evidence and scoped execution handoff or documented unresolved hold. Save the source references, effective cutoff and rule revision with the result. Notice recipient, version and actual conflict correctly identified. No owner response acceptance inferred. Work unaffected by conflict continues.

Human error to catch. Wrong recipient, unproved conflict notice or premature instruction execution. 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. Actual Servicer corrects notice or source owner clarifies case. Actual Servicer corrects notice or source owner clarifies case . Then revalidate decision and retransmit affected notice/handoff only. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Determine controlling individual instruction and permissible action, Release applicable servicing policies, delegated authorities and configurations, Review proposed loan transfers and pledges. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. LendingClub Master Loan Servicing Agreement form filed 2020. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate give required conflict notice and hand off the decision for the authorized purchaser, instruction version, conflict notice and affected output.
Read: Controlling priority and exact conflict basis | Actual Purchaser destination | Agreed downstream execution or scope of hold.
Trigger: Applicable conflict or accepted permissible decision requiring local execution. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Notice recipient, version and actual conflict correctly identified. No owner response acceptance inferred. Work unaffected by conflict continues. 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: Source-qualified conflict notice evidence and scoped execution handoff or documented unresolved hold. 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 Actual Servicer corrects notice or source owner clarifies case. Stop the affected release. Actual Servicer corrects notice or source owner clarifies case . Then revalidate decision and retransmit affected notice/handoff only.
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: Receipt of an owner servicing instruction or a detected instruction/agreement/law/practices/document conflict. Event grain is the specific instruction/case, not every loan or annual policy cycle.
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 actual_written_direction_revision against the authoritative source for the same account, version and cutoff. Return the comparison, outcome, reason and next owner. Complete when lawful direction/hold and required notice are recorded with the source-required evidence. Unresolved instructions remain specifically held/escalated. Other lawful unaffected work continues. Source does not establish automatic owner-response acceptance or an invented universal response SLA.
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: Documented permissible, rejected, held or no-change individual owner-instruction disposition, controlling priority and required conflict notice, with the affected execution owner identified. Escalate unsupported acceptance or authority to Servicing owner-instruction authority, functional reference allocation.

Run the synthetic decision check

Compare the proposed instruction to the actual written direction from the authorized owner. A previously accepted direction cannot resolve a later conflict.

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

python3 validate_servicing.py --process resolve-loan-owner-servicing-instructions

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.

• LendingClub Master Loan Servicing Agreement form filed 2020

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