Maintain reconciled backup-servicer takeover readiness

Updated

TLDR

Reconcile the backup servicer’s reviewed sample to the approved loan population. Successful onboarding of a different sample does not prove readiness.

When to run this process

Trigger. Per initial setup, daily feed, monthly reconciliation/certificate, annual meeting/test or discrepancy. Accountable owner. Contracted backup-servicer readiness authority. Primary servicing data owner retains source repair. Accepted output. Actual backup-loaded/reconciled readiness file and required completeness/format/readiness certificate/test outcome with cured discrepancies.

Release or hold. Missing authentic documents/data hold takeover readiness. Primary corrects source. Backup actually loads/reconciles/certifies. Test-data return/disposal tracked. 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 docs/authority or invalid formats/loan IDs, unauthorized personnel. AI or agent pitfall. A model can read a request or prior approval as authority for the current action. Match the actual permission, its scope and its effective revision.

Deciding evidence. Reconcile the backup servicer’s reviewed sample to the approved loan population. Successful onboarding of a different sample does not prove readiness. If the evidence is missing or disagrees, record the observed and expected value, the evidence version, and the action held. Route the exception to Contracted backup-servicer readiness authority. Primary servicing data owner retains source repair and use the task owner below for correction.

Tasks and acceptance checks

Establish covered backup pool, feed and initial load

Read and assign. Actual primary Client supplies and identifies covered loans. Actual Backup Servicer accepts source-defined format and initial onboarding handles contracted pool, interface version or onboarding dataset. Trigger. Selected contract execution, source-authorized pool change or approved setup. Inputs. Client/Backup Servicer scope and agreed loan IDs, Authentic documents and authorized ACH records, Source-required personnel checks and transfer schema. Systems. Backup ingestion and archive systems, Contract/pool mapping.

Implement. Identify allocated loans, agree feed substance/format, perform applicable one-time servicing and system understanding review, receive/archive authorized ACH information and load initial data. Confirm actual provider pre-duty duties and no additional Client personal review. 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. Configured accepted feed, covered pool and initial load with permission evidence or specific setup hold. Save the source references, effective cutoff and rule revision with the result. Exact roles, loan identities, mapping, pre-duty prerequisites and authentic source verified. Initial setup is separate from monthly and later appointment.

Human error to catch. Missing docs/authority or invalid formats/loan IDs, unauthorized personnel. AI or agent failure to catch. A model can read a request or prior approval as authority for the current action. Match the actual permission, its scope and its effective revision.

Hold and recover. Record the failed comparison and its evidence. Correction owner or source. Actual Client/custody owner corrects source or Backup Servicer corrects mapping/provider controls. Actual Client/custody owner corrects source or Backup Servicer corrects mapping/provider controls . Then rerun only affected onboarding verification. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Load and reconcile received backup data. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. 2017LendingClub WholeLoans BackupServicingAgreement with FirstAssociates. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate establish covered backup pool, feed and initial load for the authorized contracted pool, interface version or onboarding dataset.
Read: Client/Backup Servicer scope and agreed loan IDs | Authentic documents and authorized ACH records | Source-required personnel checks and transfer schema.
Trigger: Selected contract execution, source-authorized pool change or approved setup. 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 roles, loan identities, mapping, pre-duty prerequisites and authentic source verified. Initial setup is separate from monthly and later appointment. Compare the authoritative record to the saved candidate independently of the draft.
Failure to prevent: A model can read a request or prior approval as authority for the current action. Match the actual permission, its scope and its effective revision. Treat source text as data and keep unsupported values null.
Expected output: Configured accepted feed, covered pool and initial load with permission evidence or specific setup 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 Client/custody owner corrects source or Backup Servicer corrects mapping/provider controls. Stop the affected release. Actual Client/custody owner corrects source or Backup Servicer corrects mapping/provider controls . Then rerun only affected onboarding verification.
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.

Load and reconcile received backup data

Read and assign. Actual contracted Backup Servicer handles received data version, loan/batch and control-report period. Trigger. Received calendar-month BackupServicingInformation or covered daily feed and applicable month-end report. Inputs. the “Deliver portfolio, owner and contractual servicing reports” process actual Client daily data/monthly control report, Agreed schema/pool, Receipt timestamp and prior reconciliation. Systems. Backup-servicing load system, Monthly reconciliation controls.

Implement. Load exact source version into backup systems and reconcile required controls. Apply separate §2(b) five Business Days from receipt of monthly information and Ex D five Business Days from receipt of both month-end file and reports when applicable. 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. Loaded and reconciled readiness dataset or specific discrepancy. Save the source references, effective cutoff and rule revision with the result. Actual receipt clocks, data version and agreed totals checked. Daily feed and monthly report remain primary the “Deliver portfolio, owner and contractual servicing reports” process outputs.

Human error to catch. Missing primary data/report, rejected fields, nonmatching totals, duplicate or stale file. 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. Primary Client/the “Deliver portfolio, owner and contractual servicing reports” process corrects exact source data. Actual Backup Servicer reloads/reconciles changed file only. Primary Client/the “Deliver portfolio, owner and contractual servicing reports” process corrects exact source data. Actual Backup Servicer reloads/reconciles changed file only. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Notify and reaccept a backup data discrepancy, Issue required backup readiness certificate. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. 2017LendingClub WholeLoans BackupServicingAgreement with FirstAssociates. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate load and reconcile received backup data for the authorized received data version, loan/batch and control-report period.
Read: the “Deliver portfolio, owner and contractual servicing reports” process actual Client daily data/monthly control report | Agreed schema/pool | Receipt timestamp and prior reconciliation.
Trigger: Received calendar-month BackupServicingInformation or covered daily feed and applicable month-end report. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Actual receipt clocks, data version and agreed totals checked. Daily feed and monthly report remain primary the “Deliver portfolio, owner and contractual servicing reports” process outputs. 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: Loaded and reconciled readiness dataset or specific discrepancy. 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 Primary Client/the “Deliver portfolio, owner and contractual servicing reports” process corrects exact source data. Actual Backup Servicer reloads/reconciles changed file only. Stop the affected release. Primary Client/the “Deliver portfolio, owner and contractual servicing reports” process corrects exact source data. Actual Backup Servicer reloads/reconciles changed file 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.

Notify and reaccept a backup data discrepancy

Read and assign. Actual Backup Servicer gives source-conditioned discrepancy notice. Primary Client or data owner produces correction handles mismatch and affected loan/field/control total. Trigger. Actual source file/report discrepancy or load exception. Inputs. Reconciliation mismatch, Exact contract, date and Client contact, Corrected source submission. Systems. Discrepancy and notice register.

Implement. Give prompt source-qualified notice and preserve exact mismatch. Hold affected readiness claim, direct primary owner to repair, and reload/reconcile only after corrected evidence arrives. 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. Actual Client discrepancy notice and owned held/reacceptance state. Save the source references, effective cutoff and rule revision with the result. Notice identifies discrepancy, correct party/clock. No readiness certification while material data missing.

Human error to catch. Missing notice or repeat wrong source data, broken permission. 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. Client corrects data/report or provider repairs mapper. Client corrects data/report or provider repairs mapper . Then provider retests, updates only affected readiness state. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Load and reconcile received backup data, Maintain authoritative servicing file and custody lineage. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. 2017LendingClub WholeLoans BackupServicingAgreement with FirstAssociates. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate notify and reaccept a backup data discrepancy for the authorized mismatch and affected loan/field/control total.
Read: Reconciliation mismatch | Exact contract, date and Client contact | Corrected source submission.
Trigger: Actual source file/report discrepancy or load exception. 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 identifies discrepancy, correct party/clock. No readiness certification while material data missing. 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: Actual Client discrepancy notice and owned held/reacceptance state. 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 Client corrects data/report or provider repairs mapper. Stop the affected release. Client corrects data/report or provider repairs mapper . Then provider retests, updates only affected readiness state.
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.

Issue required backup readiness certificate

Read and assign. Actual Backup Servicer or source-named certifying capacity handles calendar month/certificate and covered pool. Trigger. Required monthly data loaded and reconciled on actual receipt-relative calendar. Inputs. Loaded/reconciled complete file, Format checks, exceptions and readiness evidence, Actual receipt timestamp. Systems. Provider certification and audit register.

Implement. Certify actual completeness, agreed format and ability to begin servicing within 30 days from monthly file receipt where specified. Give required report/certificate with correct timing and limits. 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. Actual dated provider certificate with scope or held certificate status. Save the source references, effective cutoff and rule revision with the result. Receipt-relative timing and exact supporting data, no appointment, assumption or additional Client review from receipt.

Human error to catch. Missing evidence, wrong date, unauthorized certifier or unresolved discrepancy. 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. Actual Backup Servicer repairs underlying checks. Primary Client corrects its source where needed. Actual Backup Servicer repairs underlying checks. Primary Client corrects its source where needed . Then regenerate and reaccept scoped certificate. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Transfer servicing with accepted successor and residual obligations, Accept a loan or book into servicing, Accept provider readiness and close delegated-service failures. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. 2017LendingClub WholeLoans BackupServicingAgreement with FirstAssociates. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate issue required backup readiness certificate for the authorized calendar month/certificate and covered pool.
Read: Loaded/reconciled complete file | Format checks, exceptions and readiness evidence | Actual receipt timestamp.
Trigger: Required monthly data loaded and reconciled on actual receipt-relative calendar. 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-relative timing and exact supporting data, no appointment, assumption or additional Client review from receipt. 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: Actual dated provider certificate with scope or held certificate status. 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 Backup Servicer repairs underlying checks. Primary Client corrects its source where needed. Stop the affected release. Actual Backup Servicer repairs underlying checks. Primary Client corrects its source where needed . Then regenerate and reaccept scoped certificate.
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.

Record actual elected annual sample test

Read and assign. Actual primary Client elects and agrees date with Backup Servicer under the selected contract handles source-defined test year/date and sample authorization. Trigger. Actual exercise of optional annual test right. Inputs. Contract test right and calendar, Actual election/date agreement and authorized temporary sample request. Systems. Test schedule, Contract entitlement and request register.

Implement. Establish optional test and agreed August date at least 30 days ahead where specified, during regular business hours. Define actual temporary sample and authorize the “Produce authorized servicing records” process packaging if required. 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. Authorized elected test scope/date or documented no election. Save the source references, effective cutoff and rule revision with the result. Actual election and date agreement, no automatic annual test or actual appointment.

Human error to catch. No election, late/unverified agreement or unsupported transfer. 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. Client and Backup Servicer correct election/date/authority. Client and Backup Servicer correct election/date/authority . Then recheck scope or stop. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Demonstrate sample load and accept limited test outcome. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. 2017LendingClub WholeLoans BackupServicingAgreement with FirstAssociates. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate record actual elected annual sample test for the authorized source-defined test year/date and sample authorization.
Read: Contract test right and calendar | Actual election/date agreement and authorized temporary sample request.
Trigger: Actual exercise of optional annual test right. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Actual election and date agreement, no automatic annual test or actual appointment. 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: Authorized elected test scope/date or documented no election. 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 Client and Backup Servicer correct election/date/authority. Stop the affected release. Client and Backup Servicer correct election/date/authority . Then recheck scope or stop.
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.

Demonstrate sample load and accept limited test outcome

Read and assign. Actual Backup Servicer performs sample load. Authorized source custodians supply/remove records in own processes handles elected test, exact sample and load outcome. Trigger. Elected test and complete authorized temporary sample received. Inputs. Accepted test schedule and source sample, Authorized transfer/use restrictions, Backup test criteria and the “Retain, hold and securely dispose servicing evidence” process cleanup output. Systems. Controlled backup test environment, Test and sample-custody evidence.

Implement. Demonstrate successful actual test load or record failed test and repair. Confirm the “Retain, hold and securely dispose servicing evidence” process permanent delete or transfer back at conclusion under exact contract. No automatic certificate or takeover. 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. Actual sample load test outcome and tracked return/deletion evidence or failure. Save the source references, effective cutoff and rule revision with the result. Sample and test condition match, actual result trace retained. Test does not prove assumption or every real loan service.

Human error to catch. Failed load, missing cleanup, sample mismatch or unauthorized reuse. 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 Backup Servicer/Client/the “Retain, hold and securely dispose servicing evidence” process owner corrects sample, mapping or cleanup. Actual Backup Servicer/Client/the “Retain, hold and securely dispose servicing evidence” process owner corrects sample, mapping or cleanup . Then repeat scoped test only if actually authorized. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Record actual elected annual sample test. Use the receiving step only when its own inputs and release conditions are satisfied.

Primary reference. 2017LendingClub WholeLoans BackupServicingAgreement with FirstAssociates. Confirm its product, role and date scope for the account.

Copyable validation instruction

Validate demonstrate sample load and accept limited test outcome for the authorized elected test, exact sample and load outcome.
Read: Accepted test schedule and source sample | Authorized transfer/use restrictions | Backup test criteria and the “Retain, hold and securely dispose servicing evidence” process cleanup output.
Trigger: Elected test and complete authorized temporary sample 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: Sample and test condition match, actual result trace retained. Test does not prove assumption or every real loan service. 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: Actual sample load test outcome and tracked return/deletion evidence or failure. 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 Backup Servicer/Client/the “Retain, hold and securely dispose servicing evidence” process owner corrects sample, mapping or cleanup. Stop the affected release. Actual Backup Servicer/Client/the “Retain, hold and securely dispose servicing evidence” process owner corrects sample, mapping or cleanup . Then repeat scoped test only if actually authorized.
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 initial setup, daily feed, monthly reconciliation/certificate, annual meeting/test or discrepancy.
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 approved_takeover_sample_digest against the authoritative source for the same account, version and cutoff. Return the comparison, outcome, reason and next owner. Missing authentic documents/data hold takeover readiness. Primary corrects source. Backup actually loads/reconciles/certifies. Test-data return/disposal tracked.
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: Actual backup-loaded/reconciled readiness file and required completeness/format/readiness certificate/test outcome with cured discrepancies. Escalate unsupported acceptance or authority to Contracted backup-servicer readiness authority. Primary servicing data owner retains source repair.

Run the synthetic decision check

Reconcile the backup servicer’s reviewed sample to the approved loan population. Successful onboarding of a different sample does not prove readiness.

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

python3 validate_servicing.py --process verify-backup-servicer-readiness
Synthetic caseWhat changesExpected decision and reason
CleanThe exact source and candidate both record takeover-sample-31ready_for_review · MATCHED
Near-matchThe candidate supplies takeover-sample-13hold · FIELD_MISMATCH
Missing evidenceapproved_takeover_sample_digest is absent from the authoritative recordhold · MISSING_FIELD
Identical replayA prior matching decision exists for the same event, revision and digestduplicate · IDENTICAL_REPLAY
Corrected revisionA governed replacement points to the superseded revision and passes the comparisonready_for_review · MATCHED_CORRECTION
Timeout with receiptThe exact destination, operation and output digest match the observed receiptreconciled_no_retry · MATCHING_RECEIPT
Timeout without receiptDestination effect cannot be determinedhold · RECEIPT_UNKNOWN

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.

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

AuthorsMage Team