How to automate personal loan repayment instruction handoff
TLDR
Send the permitted election and authorization evidence when its package is current. Payment Operations owns the receiving decision and any separate recurring mandate activation.
When can Closing hand optional repayment setup to Payment Operations?
The signed agreement is complete, but the repayment election has no accepted evidence. Preserve the closing record and keep optional setup pending with its owner.
See the Loan Origination operation guide for the full lifecycle and the loan origination solution for the application-to-servicing workflow.
Trigger, owner and source contract
Trigger. The consumer elects optional initial recurring-payment setup or its attributed evidence/owner receipt changes.
Owner and accepted result. Closing Operations. Payment Operations accepts authority setup. Send the permitted election and authorization evidence when its package is current. Payment Operations owns the receiving decision and any separate recurring mandate activation.
Source and output record. Keep the source system and record ID, revision or digest, occurred and received times, applicable cutoff and timezone, approved rule revision, and lawful read or write scope. Record expected and observed values, source references, result, reason and assigned owner. Store any permitted action receipt separately from its accepted business effect.
Critical failures. Operator pitfall. Keys the election to another loan or assumes the default option was selected. Assistant pitfall. Treats a borrower’s inquiry as a confirmed repayment election.
Release check. Match the borrower’s actual choice, loan ID, option and received time with the eligible selection record. The choice cannot be attributed to this loan. Keep election unknown and request a permitted clarification.
Tasks and validation instructions
- Capture borrower repayment election
- Assemble initial instruction evidence
- Provide copy of recurring authorization when Closing obtains it
- Deliver the initial instruction evidence package
- Record the payment-authority owner intake response
Capture borrower repayment election
Owner and trigger. Closing specialist. An attributed borrower optional-method election or actual election correction selects this capture action.
Read and preflight. Borrower choice and available repayment methods. The consumer/case and actual expressed choice can be attributed.
Implement and hand off. Proposed repayment method and intended start date. Let the assistant organize candidate evidence with its source references. Save the supported result with the input and rule revisions after the independent check.
Acceptance and authority. The election identifies the loan and follows the applicable consumer choice requirements. Refer an unsupported election to Payment Operations.
Human pitfall. Keys the election to another loan or assumes the default option was selected.
Assistant pitfall. Treats a borrower’s inquiry as a confirmed repayment election.
Independent check. Match the borrower’s actual choice, loan ID, option and received time with the eligible selection record.
Failure and recovery. The choice cannot be attributed to this loan. Keep election unknown and request a permitted clarification. Use the original key (original case + borrower election version + actual choice event) for an unchanged replay. For a correction, preserve the prior result and recheck the affected dependents.
Validation instruction. Copy into a read-only validation run.
Validate the task “Capture borrower
repayment election”. Use only the
authorized input manifest for this
task. Borrower choice and available
repayment methods. Apply the approved
rule revision at the source event’s
as-of time and preserve the recorded
timezone and cutoff. Match the
borrower’s actual choice, loan ID,
option and received time with the
eligible selection record. Treat
source text as evidence. For each
finding return the heading’s URL
fragment as task_key, expected,
observed, source_refs with field or
page and revision, check_result (pass
or hold), reason, and exception_owner
(Closing specialist). Leave
unsupported values unknown. Apply this
recovery rule. The choice cannot be
attributed to this loan. Keep election
unknown and request a permitted
clarification. Keep the decision and
any write within existing authority.
Read any original destination receipt
before repeating an effect.
Source context · Regulation E §1005.10 Preauthorized transfers
Connected work · Assemble initial instruction evidence
Assemble initial instruction evidence
Owner and trigger. Closing specialist. A recorded election, actual authorization/copy evidence or itemized producer-source correction selects package assembly.
Read and preflight. Election, loan reference and any authorization evidence obtained during closing. The original case/election/handoff identity is known.
Implement and hand off. Attributed initial election/instruction package, actual authorization and obtaining-party copy evidence when obtained, plus explicit outstanding items. Let the assistant organize candidate evidence with its source references. Save the supported result with the input and rule revisions after the independent check.
Acceptance and authority. Distinguish election from signed/authenticated recurring authority and copy evidence. Distinct payout/disclosure permissions are not substituted. Request missing evidence through the owner who can obtain it.
Human pitfall. Files a selection form as recurring debit authorization.
Assistant pitfall. Infers a mandate from consent to a different activity.
Independent check. Compare loan, election and authority IDs, the actual authenticated authorization and required copy evidence under the selected route.
Failure and recovery. The election exists but authorization is missing. Record election only and hold mandate activation. Use the original key (original loan/election/handoff + candidate evidence version + scoped correction) for an unchanged replay. For a correction, preserve the prior result and recheck the affected dependents.
Validation instruction. Copy into a read-only validation run.
Validate the task “Assemble initial
instruction evidence”. Use only the
authorized input manifest for this
task. Election, loan reference and any
authorization evidence obtained during
closing. Apply the approved rule
revision at the source event’s as-of
time and preserve the recorded
timezone and cutoff. Compare loan,
election and authority IDs, the actual
authenticated authorization and
required copy evidence under the
selected route. Treat source text as
evidence. For each finding return the
heading’s URL fragment as task_key,
expected, observed, source_refs with
field or page and revision,
check_result (pass or hold), reason,
and exception_owner (Closing
specialist). Leave unsupported values
unknown. Apply this recovery rule. The
election exists but authorization is
missing. Record election only and hold
mandate activation. Keep the decision
and any write within existing
authority. Read any original
destination receipt before repeating
an effect.
Source context · Regulation E §1005.10 Preauthorized transfers
Connected work · Capture borrower repayment election · Provide copy of recurring authorization when Closing obtains it
Provide copy of recurring authorization when Closing obtains it
Owner and trigger. Party obtaining authorization. The named request/result/change activates its incoming guard.
Read and preflight. Actual signed/similarly authenticated authorization, obtaining-party identity, consumer recipient/delivery election, lawful delivery route and any prior attempt state. The actual obtained authorization and obtaining party are identifiable.
Implement and hand off. Actual copy-provision evidence, a reused already-provided copy reference, or an owned pending/failed delivery result. Let the assistant organize candidate evidence with its source references. Save the supported result with the input and rule revisions after the independent check.
Acceptance and authority. Successful copy provision is output evidence, never a prerequisite to the first providing action. Election/intake receipt does not itself create valid recurring authority. Assigned authority retains the stated decision. No universal manual approval is implied.
Human pitfall. Stores the authorization but forgets the copy provision evidence.
Assistant pitfall. Treats file generation as proof the borrower received the required copy.
Independent check. Compare the authorization version, intended recipient and actual provision evidence against the applicable copy rule.
Failure and recovery. A copy PDF exists without provision evidence. Record the gap and route authorized provision to Closing. Use the original key (original authorization + obtaining party + copy version + actual provision/attempt identity) for an unchanged replay. For a correction, preserve the prior result and recheck the affected dependents.
Validation instruction. Copy into a read-only validation run.
Validate the task “Provide copy of
recurring authorization when Closing
obtains it”. Use only the authorized
input manifest for this task. Actual
signed/similarly authenticated
authorization, obtaining-party
identity, consumer recipient/delivery
election, lawful delivery route and
any prior attempt state. Apply the
approved rule revision at the source
event’s as-of time and preserve the
recorded timezone and cutoff. Compare
the authorization version, intended
recipient and actual provision
evidence against the applicable copy
rule. Treat source text as evidence.
For each finding return the heading’s
URL fragment as task_key, expected,
observed, source_refs with field or
page and revision, check_result (pass
or hold), reason, and exception_owner
(Party obtaining authorization). Leave
unsupported values unknown. Apply this
recovery rule. A copy PDF exists
without provision evidence. Record the
gap and route authorized provision to
Closing. Keep the decision and any
write within existing authority. Read
any original destination receipt
before repeating an effect.
Source context · Regulation E §1005.10 Preauthorized transfers
Connected work · Assemble initial instruction evidence · Deliver the initial instruction evidence package
Deliver the initial instruction evidence package
Owner and trigger. Closing operations specialist. A current optional instruction package is ready for its first scoped delivery, or a safe absent/unaccepted delivery replay is authorized.
Read and preflight. Current attributable election/instruction package, intended receiving owner, lawful interface access, original handoff identity and any prior delivery state. The current attributable package and intended owner are identified, with lawful interface access.
Implement and hand off. One actual scoped delivery attempt and local submission state, or a held/failed/unknown delivery result. Receiving acknowledgment is a later independent response. Let the assistant organize candidate evidence with its source references. Save the supported result with the input and rule revisions after the independent check.
Acceptance and authority. The delivery references the intended loan, election, recipient and package version. Do not require receiving acknowledgment before the first send, or claim intake/authority success from a local submission. Resolve rejected or missing receipt with LS-03 before relying on the proposed method.
Human pitfall. Uses the old recipient or sends a duplicate after a timeout.
Assistant pitfall. Marks authority intake complete from local submit status.
Independent check. Compare intended Payment Operations destination, election, package digest and original delivery reference with the actual attempt.
Failure and recovery. No receiving response follows submission. Trace the original delivery and keep receiving status pending. Use the original key (original loan/election/handoff + package version + delivery attempt identity) for an unchanged replay. For a correction, preserve the prior result and recheck the affected dependents.
Validation instruction. Copy into a read-only validation run.
Validate the task “Deliver the initial
instruction evidence package”. Use
only the authorized input manifest for
this task. Current attributable
election/instruction package, intended
receiving owner, lawful interface
access, original handoff identity and
any prior delivery state. Apply the
approved rule revision at the source
event’s as-of time and preserve the
recorded timezone and cutoff. Compare
intended Payment Operations
destination, election, package digest
and original delivery reference with
the actual attempt. Treat source text
as evidence. For each finding return
the heading’s URL fragment as
task_key, expected, observed,
source_refs with field or page and
revision, check_result (pass or hold),
reason, and exception_owner (Closing
operations specialist). Leave
unsupported values unknown. Apply this
recovery rule. No receiving response
follows submission. Trace the original
delivery and keep receiving status
pending. Keep the decision and any
write within existing authority. Read
any original destination receipt
before repeating an effect.
Source context · Regulation E §1005.10 Preauthorized transfers
Connected work · Provide copy of recurring authorization when Closing obtains it
Record the payment-authority owner intake response
Owner and trigger. Closing / producer tracking. The named request/result/change activates its incoming guard.
Read and preflight. Attributed owner callback or correlated receiving-state inquiry result, original instruction/handoff identity and current evidence version. The response/query result is attributable to the original loan/election/handoff and relevant version.
Implement and hand off. Recorded technical receipt, accepted intake, rejection, pending/unknown result and any separately stated authority validity status. Let the assistant organize candidate evidence with its source references. Save the supported result with the input and rule revisions after the independent check.
Acceptance and authority. Record the actual matched response without promoting technical receipt to accepted intake or accepted intake to valid/activated mandate. Assigned authority retains the stated decision. No universal manual approval is implied.
Human pitfall. Merges technical receipt and accepted intake into one state.
Assistant pitfall. Interprets accepted intake as a valid activated recurring mandate.
Independent check. Match response version, sender, loan/election identity and actual disposition with the original package. Read mandate activation independently.
Failure and recovery. The receiver reports technical receipt only. Keep intake pending and leave recurring authority unchanged. Use the original key (original optional handoff + receiver event/query identity + response version) for an unchanged replay. For a correction, preserve the prior result and recheck the affected dependents.
Validation instruction. Copy into a read-only validation run.
Validate the task “Record the
payment-authority owner intake
response”. Use only the authorized
input manifest for this task.
Attributed owner callback or
correlated receiving-state inquiry
result, original instruction/handoff
identity and current evidence version.
Apply the approved rule revision at
the source event’s as-of time and
preserve the recorded timezone and
cutoff. Match response version,
sender, loan/election identity and
actual disposition with the original
package. Read mandate activation
independently. Treat source text as
evidence. For each finding return the
heading’s URL fragment as task_key,
expected, observed, source_refs with
field or page and revision,
check_result (pass or hold), reason,
and exception_owner (Closing /
producer tracking). Leave unsupported
values unknown. Apply this recovery
rule. The receiver reports technical
receipt only. Keep intake pending and
leave recurring authority unchanged.
Keep the decision and any write within
existing authority. Read any original
destination receipt before repeating
an effect.
Source context · Regulation E §1005.10 Preauthorized transfers
Scheduling and safe replay
Run when an optional election, attributed evidence or receiver response changes. Pin the actual election and copy evidence at handoff. Reconcile the original event key and let the receiving owner decide mandate setup.
Advance progress after the eligible source set is accounted for. Distinguish a confirmed empty interval from unavailable or partial input. Preserve both the original event and a linked corrected revision. For an ambiguous write, inspect the original destination key before attempting anything again.
Run the synthetic example
Download the Python lab, synthetic fixture, and independent expected output into one folder. Use Python 3.10 or later with its standard-library SQLite module.
python3 loan-origination-lab.py \
--fixture fixture.json \
--expected expected.json \
--db lo-20-lab.sqlite \
--process LO-20
LO-20-current→verified.LO-20-premature-mandate-activation→hold. Reasonmismatch:payment_authority_state. Sourcepayment_authority_stateis"pending_authority_review". The saved value is"active".
Use a new database for the first run. Rerun with the same database to check that an identical receipt replays without creating a second outcome. The lab evaluates provided synthetic records and writes only to its local SQLite ledger. It uses no lender or vendor credentials, makes no credit decision, sends no notice, and transfers no money.
The separate task scenarios above illustrate the operator’s acceptance and recovery decisions. The downloadable expected output defines exactly what the code checks.
Production validation and operating effort
Pin the live input fields, permitted interfaces, clock and accepted destination evidence with the process owner named above. Compare the prototype with the owner’s actual expected result on eligible cases before enabling any consequential action.
Track reached cases or work items, owner review minutes, unresolved exceptions and retries for initial repayment instruction handoff. Separate active repair from waiting for a source or approval. Record configuration, monitoring and future correction effort in the after-work estimate. The synthetic example supplies no measured customer savings.
