Bankruptcy stay
The moment a filing is recorded, collection outreach is suppressed automatically and the account routes into a bankruptcy case with its own workflow.
Compliance engine
Check servicing actions before they reach a borrower
LendEasy evaluates messages, calls, and payments using current account facts and the applicable rule version. It records the decision, any human approval, and the final outcome in an exportable audit trail.
Proposed action
Outbound call — Collections
Case #C-2417 · consumer installment · evaluated at execution time
compliance gate
Call-frequency policy
Reg F §1006.14(b)(2) · v3
State rule
MA contact cap · v2
Quiet hours
borrower TZ — 2:14 PM local
Consent
on file — voice, cell
Alloweddecision recorded #D-48121
Current rule versions, checked before execution — human or AI
Rule history
Know which rule was used for each decision
Each rule records its source, jurisdiction, effective date, and version history. Past decisions remain linked to the version that evaluated them.
- Named regulation and citation on every rule — federal and state
- Effective-dated versions: updates create history, never rewrite it
- Every decision records the exact rule versions it was evaluated against
Call-frequency threshold — 7 calls / 7 days per debtv3 · active
- Regulation
- Reg F · 12 CFR §1006.14(b)(2)
- Jurisdiction
- Federal · United States
- Effective date
- This version in force since its effective date — predecessors retained
- Applies to
- Consumer debt · voice + voicemail · per debt, not per account
Version history: v1 → v2 → v3, each with its own effective window. Every past decision stays linked to the version that evaluated it, so a reviewer can see which rule version was used for the call.
Before execution
The same policy check for people and AI
Each send, call, or payment is evaluated using current facts when it is about to run. The result is allowed, warning, human approval required, blocked, or missing facts.
Allowed
Every applicable rule passes on current facts. The action executes and the evaluation is recorded.
Warning
Permitted, but worth a human glance — the worker sees why before proceeding.
Human approval required
Policy marks this action for human review. It cannot execute until a person approves it.
Blocked
A hard stop. No override exists — not for a manager, not for an AI agent, not for anyone.
Missing facts
Required information is missing or stale, so the action waits for updated facts.
If required information is missing or too old to support the decision, the action waits for updated facts.
Contact budgets
Call-frequency controls visible before dialing
Set a contact-frequency policy for each program, including Regulation F presumptions, state rules, and lender limits. Workers see the remaining call capacity on the case before dialing.
Example contact budget — this debt
7-day window5 of 7 attempts used · 2 remaining before the configured threshold
- Voicemails and limited-content messages count toward the budget — not just connected calls.
- The budget is re-checked at the moment of dial — a queue built earlier cannot overspend it.
Borrower protections
Turn recorded protections into active controls
A recorded protection can suppress affected outreach, pause configured payment activity, and route the account into the right case workflow.
SCRA protections
A verified military-status signal opens review of the protections that may apply, including rate and enforcement controls, with each action evaluated against the confirmed status.
Cease communications
A potential cease-communication or channel opt-out request is captured immediately, scoped under applicable law and policy, and enforced across affected outreach paths.
Deceased borrower
Outreach stops, the account routes to a deceased-borrower case, and communication shifts to the configured estate process.
Product-specific rules
Keep consumer and commercial rules separate
Each obligation carries a product class, so the engine applies only the rules configured for that type of lending.
Consumer credit
Applicable Regulation F call-frequency presumptions, Regulation Z disclosures, Regulation E autopay notices, and state consumer-collection rules for installment and BNPL obligations.
Merchant advance
Commercial-financing rules and disclosure regimes apply here, keeping consumer and commercial treatment separate.
The audit trail
Build the examiner record as work happens
Each decision records the facts and as-of times used, rule versions evaluated, approvals, and outcome. Linked, hash-chained records make later changes visible and support search and export.
Queryable by design
Search contact attempts by account, date, outcome, and the rule versions used.
Tamper-evident
Each record commits to the hash of its predecessor. An after-the-fact edit breaks the chain — visibly.
Exportable review record
Export decisions, rules, approvals, and outcomes for litigation or examination review.
Overrides
Some actions allow approval. Others remain blocked.
Configure which controls are non-overridable and which allow a recorded exception with an approver, reason, evidence, and expiry.
Non-overridable controls
Automatic-stay restrictions, applicable cease-communication restrictions, and other controls your policy marks non-overridable. No permission level, manager, AI agent, or API key has an application-level bypass.
Recorded exceptions
Where policy allows discretion, an override captures the approver, the reason, supporting evidence, and an expiry — and becomes part of the audit trail.
FAQ
What compliance leaders ask first
Each rule has an effective date and version history. An update creates a new version without rewriting past decisions. Because the source regulation and jurisdiction are recorded, reviewers can identify which rules and decisions a change affects.
Turn your rulebook into execution-time controls
Choose one policy and see how the platform evaluates a real action, records the decision, and explains the outcome.