Solutions · Bankruptcy & protected borrowers
When a bankruptcy notice lands, the clock is already running. LendEasy opens the case, applies the stay, pauses autopay, suppresses outreach, and cancels every scheduled contact — automatically, with evidence for each one. The same machinery protects SCRA, cease-communications, and deceased borrowers.
The stay, enforced
System
Bankruptcy notice arrives — case auto-opens
Compliance Gate
Automatic stay applied as a governed action
System
Autopay paused, outreach suppressed — in minutes
Human
Communications route to counsel of record
Each pause, suppression, and cancellation recorded individually — full walkthrough below
The scenario
Follow one filing through the system. The restriction is applied before anything else can happen, the consequences fan out in minutes, and each one leaves its own evidence record.
Bankruptcy notice arrives — or a data-source match fires
Whether the trigger is a mailed notice your team logs or an automated match from a bankruptcy data source, the same machinery starts immediately.
Evidence: The triggering notice or match, with source and timestamp.
Case auto-opens with the petition details
Chapter, filing date, case number, and the borrower's full servicing context — snapshotted at open, so everyone who touches the case works from the same facts.
Evidence: Petition details and context snapshot pinned to the case.
Automatic-stay restriction applied as a governed action
The restriction is not a note on the account — it is an enforced rule the compliance gate evaluates before every future action on this borrower.
Evidence: The restriction, its legal basis, scope, and effective time.
Autopay paused, outreach suppressed, every scheduled contact cancelled
All of it happens in minutes, as one coordinated consequence of the stay: no debit against a stayed debt, no letter in the mail room, no call sitting in tomorrow's dialer queue.
Evidence: Each pause, suppression, and cancellation recorded individually — provable one by one.
Communications route to counsel of record
Attorney-only routing takes over. Agents see the restriction in context the moment they open the account, so nobody learns about the filing mid-call.
Evidence: Routing rule and every subsequent contact decision.
Discharge or dismissal handled when the case resolves
Restrictions adjust to the outcome: what must survive survives, what should lift lifts — as governed actions, not manual cleanup.
Evidence: The disposition, the restriction changes it drove, and the full hash-chained history.
Protected states
Different laws, different triggers — the same pattern: detect, restrict through a governed action, enforce at the gate on every subsequent action, and record everything.
Notice or data-source match auto-opens a case with petition details. What auto-happens:
An active-duty match flips the borrower into a protected state. What auto-happens:
Borrower language detected in any channel — a call, a reply, a letter. What auto-happens:
Notification of a borrower's death starts respectful handling immediately. What auto-happens:
Why minutes matter
Intent is not a defense. A single debit against a stayed debt, one letter that was already in the queue, one call from a dialer list refreshed yesterday — each is a violation regardless of how good your policy memo was.
The exposure window is the gap between the filing and the last system that finds out about it. In a manual process, that gap is measured in days and inboxes. Here, the restriction is applied once and enforced everywhere — because every action, from autopay debits to AI follow-ups, passes the same gate before it executes.
Manual process
Days of exposure: notice → mailroom → analyst → each downstream system, one inbox at a time.
One gate, applied once
Minutes: the restriction is enforced at the gate every action already passes — nothing downstream to chase.
Illustrative comparison of process shape, not a measured benchmark.
The restriction model
A protection you cannot enforce precisely is a protection you cannot prove. Restrictions here are first-class, scoped, and evaluated by the gate on every action.
A restriction can cover everything, or exactly what the law and the borrower's request require — calls but not mail, one debt but not another. Enforcement matches scope precisely.
Restrictions carry effective windows and respond to events — a dismissal, a discharge, a rescinded request — adjusting through governed actions rather than manual edits.
Closing the bankruptcy case does not quietly drop the protections that must outlive it. The restriction lives on the borrower, enforced at the gate, independent of any case's lifecycle.
The evidence trail
When a trustee or examiner asks what happened after the filing, the answer is not a policy document — it is the record: the match, the restriction, each cancelled contact, each suppressed action, hash-chained and exportable.
FAQ
In minutes from notice or data-source match: the case opens with petition details, the stay restriction is applied as a governed action, autopay is paused, outreach is suppressed, and scheduled contacts are cancelled. Because the compliance gate re-checks every action at execution time, enforcement does not depend on anyone reading an email first.
We will run a bankruptcy scenario live: the match, the restriction, the cancellations, and the evidence export — with the founding team.