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
Compliance that runs before the action, not after the report
Most platforms report collections compliance after the fact. LendEasy decides what is allowed to happen next: every rule traces to a named regulation, every send and dial is checked at the moment of execution, and every decision lands in tamper-evident evidence you can hand to an examiner.
Proposed action
Outbound call — Collections
Case #C-2417 · consumer installment · evaluated at execution time
compliance gate
Call-frequency cap
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
Version-pinned rules, checked at the moment of execution — human or AI
Rule-to-regulation traceability
Every rule answers for itself
A rule in LendEasy is not a row in a vendor's settings table. It carries the regulation it implements, the jurisdiction it covers, the date it took effect, and its full version history — pinned, so past decisions are always judged by the rule that was actually in force.
- 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 cap — 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 pinned to the version that evaluated it — so “which rule version was in force when this call was made?” is always answerable.
The pre-execution gate
Checked at the moment it matters — for humans and AI alike
Every send, every dial, every action is evaluated at execution time against current facts — not when the campaign was planned, not in a nightly batch. The gate returns one of five outcomes, and only one of them reaches a borrower.
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.
Approval required
Policy marks this action sensitive. It routes to a distinct approver before anything happens.
Blocked
A hard stop. No override exists — not for a manager, not for an AI agent, not for anyone.
Missing facts
The engine cannot establish the action is permitted — so it is not. Missing facts never permit.
The posture is deliberate: missing facts never permit. If the engine cannot prove an action is allowed, the action waits — it is never waved through on a gap in the data.
Contact budgets
Frequency limits your workers can see before they dial
Reg F's seven-calls-in-seven-days presumption is computed per debt, in real time. Remaining capacity is visible on the case before anyone picks up the phone — so the limit is a guardrail in the workflow, not a finding in next month's audit.
Contact budget — this debt
7-day window5 of 7 attempts used · 2 remaining before the cap
- 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.
Protected-borrower states
When a protection applies, the platform reacts — not a memo
Protected states suppress outreach automatically and route the account into the right case workflow, with the suppression enforced by the same gate that checks every other action.
SCRA protections
Servicemember protections apply across rate, fees, and outreach — flagged once, enforced everywhere the engine evaluates.
Cease communications
A cease request shuts the affected channels immediately, and the engine blocks every future attempt on them — human or AI.
Deceased borrower
Outreach stops, the account routes to a deceased-borrower case, and communication shifts to the estate process — with dignity built into the workflow.
Product-class awareness
Consumer rules stay consumer. Commercial rules stay commercial.
A merchant cash advance is not a consumer installment loan, and the engine never pretends otherwise. Every obligation carries its product class, and rules apply only to the classes they were written for — neither silently over-restricting your commercial book nor under-protecting your consumer one.
Consumer credit
Reg F contact limits, Reg Z disclosures, Reg E autopay notices, state consumer-collection rules — enforced on installment and BNPL obligations.
Merchant advance
Commercial-financing rules and disclosure regimes apply here — and consumer-only restrictions never silently bleed across the boundary.
The evidence graph
Answer the examiner in hours, not weeks
Every decision — human and AI — is written to a hash-chained, tamper-evident record: the facts seen, their freshness, the rule versions evaluated, approvals, and the outcome. The records link into a queryable graph, not a pile of logs.
Queryable by design
"Show every contact attempt on this debt in March, with the rule versions in force" is a query, not a quarter-long project.
Tamper-evident
Each record commits to the hash of its predecessor. An after-the-fact edit breaks the chain — visibly.
One-click export
Litigation and exam packages export in one click: decisions, rules, approvals, and outcomes, ready to hand over.
Overrides
Some lines need a signature. Some can't be crossed at all.
An override system is only as strong as its weakest exception — so LendEasy draws the line structurally.
Hard stops — never overridable
Bankruptcy stays, cease-communication requests, statutory frequency limits. No permission level, no manager, no AI agent, no API key can push past them. The override does not exist to be misused.
Soft overrides — governed, never casual
Where policy allows discretion, an override captures the approver, the reason, supporting evidence, and an expiry — and becomes a record in the evidence graph. Discretion leaves a trail, and the trail expires on schedule.
FAQ
What compliance leaders ask first
Rules are versioned with effective dates, so an update is a new version that takes force on its date — the old version remains in the history, still answering for the period it governed. Because every rule names its regulation and jurisdiction, reviewing coverage against a regulatory change is a query over the rule book, not an archaeology project.
Bring your rule book. We'll show you it running.
Pick the regulation that worries you most and watch the engine evaluate a real action against it — version-pinned, at execution time, with the evidence record to prove it.