Determine and implement military servicing protections

When to run this process

Trigger. Per eligible service/request/verification, status correction, retroactive recalculation or relief expiry. Accountable owner. Military benefits authority. Accepted output. Supported relief/denial/held determination with forgiven excess interest, actually returned excess paid amounts and revised installments/restrictions.

Release or hold. Do not defer forgiven interest or accelerate principal to offset it. Departure from cap requires applicable court relief. Preserve evidence and court-action handoff. 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/contradictory service proof, incorrect account or unverified representative. 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. Preserve the verified service date used by the applicable protection and review the exact obligation and request before a release. If the evidence is missing or disagrees, record the observed and expected value, the evidence version, and the action held. Route the exception to Military benefits authority and use the task owner below for correction.

Tasks and acceptance checks

• Accept service evidence and preserve notice clock
• Determine protected debt, relief and exceptions
• Direct distinct relief effects and accept implementation evidence
• Close, correct or expire protection case

Accept service evidence and preserve notice clock

Read and assign. Military benefits authority handles one request, service period and affected loan set. Trigger. Military request, eligible independent verification or representative evidence arrives. Inputs. Actual service notice, orders/other indicators or permitted DMDC facts, party/representative proof, account identifiers. Systems. Military-benefit case, Service verification, Loan recalculation.

Implement. Record actual request/notice and qualifying proof or permitted independent DMDC route. Apply source-specific representative proof, and preserve dates of call to active duty and termination/release. Distinguish Upstart procedure, lender enhancements and actual DMDC coverage. For an actual covered Upstart submission, retain the original submission timestamp and route a safely identified insufficient-proof case to the “Determine protected debt, relief and exceptions” step for a supported response disposition. Preserve a hold on uncertain authority or an unverified recipient. Capture notice, verify authorized evidence route and compute candidate eligibility dates. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Accepted military proof/route and period evidence, or owned missing-evidence hold The original request/clock remains available on an incomplete branch. Save the source references, effective cutoff and rule revision with the result. Validate identity, service dates, permissible evidence and statutory request limit of no later than 180 days after termination/release when required. Do not assume all service appears in DMDC.

Human error to catch. Missing/contradictory service proof, incorrect account or unverified representative. 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. Servicemember/representative or actual verification source. Benefits intake reaccepts. Request exact missing facts, use approved independent route where applicable, recheck only affected coverage. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Determine protected debt, relief and exceptions. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate accept service evidence and preserve notice clock for the authorized one request, service period and affected loan set.
Read: Actual service notice, orders/other indicators or permitted DMDC facts | party/representative proof | account identifiers.
Trigger: Military request, eligible independent verification or representative evidence 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: Validate identity, service dates, permissible evidence and statutory request limit of no later than 180 days after termination/release when required. Do not assume all service appears in DMDC. 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: Accepted military proof/route and period evidence, or owned missing-evidence hold The original request/clock remains available on an incomplete branch. 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 Servicemember/representative or actual verification source. Benefits intake reaccepts. Stop the affected release. Request exact missing facts, use approved independent route where applicable, recheck only affected coverage.
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 protected debt, relief and exceptions

Read and assign. Military benefits authority handles one debt/party and supported effective service period. Trigger. Service proof result or safely identified incomplete submission, effective period change, or actual court order. Inputs. Accepted service facts, loan incurrence history, rates/fees and party, relevant orders/benefit policy, Original submitted-request ID and timestamp, recipient authority and any specific documentation gap. Systems. Military-benefit case, Service verification, Loan recalculation.

Implement. Apply 50 USC §3937 to qualifying interest-bearing pre-service debt, including qualifying joint spouse scope, for nonmortgage service period. Determine 6% cap/forgiveness, actual effective start and applicable rate/fee changes. Only actual §3937(c) court relief may vary statutory cap under its test. Keep Upstart/FNBO or other enhancements within their own products. For an actual covered Upstart submission with a supported denial or insufficient proof, send the authorized reason or exact evidence request to the “Prepare source-qualified specialist communications” step at determination. Do not trigger recalculation, posting or refund from this disposition. Reconcile dates, rate/fee categories and benefit eligibility against effective source rules. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Supported entitlement, denial/incomplete hold or court-referral decision with effective period For a covered Upstart adverse/incomplete result, release the qualified response instruction and retain the open response evidence check. Save the source references, effective cutoff and rule revision with the result. Document actual debt dates, coverage and source authority. Keep 10-day Upstart response operator-specific, mortgage extra year outside this scope and court route separate. The source describes response within 10 days of submitting the request. A later proof check or case reopen does not reset the original submission anchor.

Human error to catch. Wrong pre-service or period determination, mistaken enhancement or missing court order. 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. Benefits authority and counsel/court for actual exception. Repair loan/service data and reassess affected period only. Refer supported creditor exception to the “Authorize legal recovery and administer accepted court outcomes” process/court without treating request as relief. Correct the adverse/incomplete reason or missing proof basis at the “Determine protected debt, relief and exceptions” step. Retry a delivery-only defect at the “Deliver borrower account statements and event notices” process on the authorized payload. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Direct distinct relief effects and accept implementation evidence, Close, correct or expire protection case, Authorize legal recovery and administer accepted court outcomes. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate determine protected debt, relief and exceptions for the authorized one debt/party and supported effective service period.
Read: Accepted service facts | loan incurrence history, rates/fees and party | relevant orders/benefit policy | Original submitted-request ID and timestamp, recipient authority and any specific documentation gap.
Trigger: Service proof result or safely identified incomplete submission, effective period change, or actual court order. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Document actual debt dates, coverage and source authority. Keep 10-day Upstart response operator-specific, mortgage extra year outside this scope and court route separate. The source describes response within 10 days of submitting the request. A later proof check or case reopen does not reset the original submission anchor. 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: Supported entitlement, denial/incomplete hold or court-referral decision with effective period For a covered Upstart adverse/incomplete result, release the qualified response instruction and retain the open response evidence check. 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 Benefits authority and counsel/court for actual exception. Stop the affected release. Repair loan/service data and reassess affected period only. Refer supported creditor exception to the “Authorize legal recovery and administer accepted court outcomes” process/court without treating request as relief. Correct the adverse/incomplete reason or missing proof basis at the “Determine protected debt, relief and exceptions” step. Retry a delivery-only defect at the “Deliver borrower account statements and event notices” process on the authorized payload.
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.

Direct distinct relief effects and accept implementation evidence

Read and assign. Military benefits authority handles one approved debt-period version, including each actual dependent effect. Trigger. Benefit decision approved or retroactive correction/expiry occurs. Inputs. Authorized relief terms, historical posted/accrued amounts and payment history, requested actual response. Systems. Military-benefit case, Service verification, Loan recalculation.

Implement. Send accepted effective scope to the “Maintain contractual balances, accruals, fees and due state” process for recalculation/reduced installments, the “Apply, reverse and adjust loan payment entries” process for actual posting when triggered, the “Return borrower credit balances and remedy payments” process for actual return of eligible excess paid and the “Deliver borrower account statements and event notices” process for applicable actual response. Distinguish excess accrued from amounts paid. Require forgiveness and no principal acceleration to offset reductions. Source-specific Upstart most-borrower bank refund applies only where established. The the “Determine protected debt, relief and exceptions” step adverse/incomplete response has a distinct communication-only path. An approved/corrected determination can be communicated from the “Direct distinct relief effects and accept implementation evidence” step when otherwise due without waiting for unrelated effects. Claim an implemented effect only with its actual evidence. Generate versioned effect instructions and reconcile calculated, posted, refunded and sent evidence. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Accepted recalculated/posted protected state, actual applicable refund/response and unresolved effect list. Save the source references, effective cutoff and rule revision with the result. Reconcile cap, affected interest/fees, corrected installments and actual refund evidence. Do not treat pending deposit, approval or net rate as proof of returned funds. Keep any actual response independent of cap, state, posting or refund acceptance and send its result to the “Close, correct or expire protection case” step.

Human error to catch. Wrong period, interest deferred, installment not reduced, missing issued refund or unavailable response. 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 ledger/posting/refund/communication owners correct their effects. Benefits authority reaccepts. Return exact discrepancy to effect producer and replay only affected period/version. Escalate no supported effect or missed response. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Close, correct or expire protection case, Maintain contractual balances, accruals, fees and due state, Apply, reverse and adjust loan payment entries. Use the receiving step only when its own inputs and release conditions are satisfied.

Copyable validation instruction

Validate direct distinct relief effects and accept implementation evidence for the authorized one approved debt-period version, including each actual dependent effect.
Read: Authorized relief terms | historical posted/accrued amounts and payment history | requested actual response.
Trigger: Benefit decision approved or retroactive correction/expiry occurs. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Reconcile cap, affected interest/fees, corrected installments and actual refund evidence. Do not treat pending deposit, approval or net rate as proof of returned funds. Keep any actual response independent of cap, state, posting or refund acceptance and send its result to the “Close, correct or expire protection case” step. 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: Accepted recalculated/posted protected state, actual applicable refund/response and unresolved effect list. 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 ledger/posting/refund/communication owners correct their effects. Benefits authority reaccepts. Stop the affected release. Return exact discrepancy to effect producer and replay only affected period/version. Escalate no supported effect or missed response.
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.

Close, correct or expire protection case

Read and assign. Military benefits authority handles one benefit case and effective period/version. Trigger. Required effects return, service/authority changes or actual protection expires. Inputs. Accepted military determination and effect evidence, updated service/court facts or scheduled expiry, Actual the “Reconcile communication evidence and return failure” step response result for covered denial, incompleteness or approval/correction communication. Systems. Military-benefit case, Service verification, Loan recalculation.

Implement. Confirm actual cap, forgiveness, adjusted payment, returned excess where applicable and source-required response. Maintain collection/legal restrictions as actual law or order requires. Reopen newly affected period or resume only after accepted effective expiry or correction. Reconcile the scoped actual response even when no relief implementation applies. Preserve the incomplete/held status while material proof remains outstanding. Reconcile current status and dates, flag residual requirements and protect against duplicate refund. Use the lender’s documented authority for approval and release. Keep unsupported approvals and permissions unresolved.

Save and verify. Accepted relief/denial/held/expired case with validated downstream status. Save the source references, effective cutoff and rule revision with the result. Review chronology, applicable current restriction and residual refund/response. Keep the “Authorize legal recovery and administer accepted court outcomes” process sworn filing and court-appointed counsel/stay/judgment separate. For covered Upstart requests, validate actual response on the correct version, recipient, permitted route and original submission clock. A requested or failed send is an owned open response, and does not complete the communication branch.

Human error to catch. Stale status, protected default litigation attempt, missing adjustment/refund or wrong resumption Treat missing, wrong-version or late response evidence as its own issue. 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. Benefits authority, servicing effect owner, and the “Authorize legal recovery and administer accepted court outcomes” process/court for actual legal action. Return precise change to eligibility or affected output owner. Preserve prior service-period history and outcome before new version. Use the “Deliver borrower account statements and event notices” process for delivery-only failure and the “Determine protected debt, relief and exceptions” step for a changed determination. Do not send an adverse or incomplete disposition through the “Direct distinct relief effects and accept implementation evidence” step's financial-effect repair. Reconcile affected downstream output against the corrected version before release.

Possible handoffs. Determine protected debt, relief and exceptions, Direct distinct relief effects and accept implementation 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 close, correct or expire protection case for the authorized one benefit case and effective period/version.
Read: Accepted military determination and effect evidence | updated service/court facts or scheduled expiry | Actual the “Reconcile communication evidence and return failure” step response result for covered denial, incompleteness or approval/correction communication.
Trigger: Required effects return, service/authority changes or actual protection expires. Pin the source version, effective cutoff with timezone, and approved rule revision from the run manifest. Return hold if those are missing.
Deciding check: Review chronology, applicable current restriction and residual refund/response. Keep the “Authorize legal recovery and administer accepted court outcomes” process sworn filing and court-appointed counsel/stay/judgment separate. For covered Upstart requests, validate actual response on the correct version, recipient, permitted route and original submission clock. A requested or failed send is an owned open response, and does not complete the communication branch. 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: Accepted relief/denial/held/expired case with validated downstream 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 Benefits authority, servicing effect owner, and the “Authorize legal recovery and administer accepted court outcomes” process/court for actual legal action. Stop the affected release. Return precise change to eligibility or affected output owner. Preserve prior service-period history and outcome before new version. Use the “Deliver borrower account statements and event notices” process for delivery-only failure and the “Determine protected debt, relief and exceptions” step for a changed determination. Do not send an adverse or incomplete disposition through the “Direct distinct relief effects and accept implementation evidence” step's financial-effect repair.
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 eligible service/request/verification, status correction, retroactive recalculation or relief expiry.
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_service_end_date against the authoritative source for the same account, version and cutoff. Return the comparison, outcome, reason and next owner. Do not defer forgiven interest or accelerate principal to offset it. Departure from cap requires applicable court relief. Preserve evidence and court-action handoff.
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: Supported relief/denial/held determination with forgiven excess interest, actually returned excess paid amounts and revised installments/restrictions. Escalate unsupported acceptance or authority to Military benefits authority.

Run the synthetic decision check

Preserve the verified service date used by the applicable protection and review the exact obligation and request before a release.

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_service_end_date with a frozen account identity, source and policy revision, cutoff and destination observation.

python3 validate_servicing.py --process apply-military-servicing-protections

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.

• 50 USC 3937 current interest limit
• DOJ SCRA sixpercent creditor duties
• SCRA default judgments
• Upstart SCRA procedure
• SCRA interest cap

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