Identity theft & disputes
Preserve distinct debt, validation, furnishing, and identity-theft signals; attach the right clocks and restrictions; investigate from evidence; and prove the final response.
“This is not mine,” “your balance is wrong,” “send validation,” and “you furnished the wrong status” are not one generic complaint. One interaction may contain several signals, and LendEasy creates linked matters so each obligation keeps its own policy, deadline, evidence, and closure criteria.
Signal classification
| Signal | Operational question | Typical immediate control |
|---|---|---|
| Debt dispute | Which part of liability, amount, or ownership is contested? | Mark scope; apply configured collection review. |
| Validation request | What information must be provided, and by when? | Track request timing and response eligibility. |
| Furnishing dispute | Which furnished field, period, and destination are disputed? | Preserve source file and investigation deadline. |
| Identity-theft claim | Which account or transactions are alleged fraudulent? | Apply configured fraud/contact/furnishing protections. |
| Payment or balance error | Which intent, return, allocation, charge, or effective date differs? | Open reconciliation and preserve transaction evidence. |
The platform’s rule library can model the FDCPA/Regulation F and FCRA/Regulation V where applicable. Counsel-approved configuration determines scope; the case title is not a legal conclusion.
Lifecycle
Evidence graph
An investigation should be reproducible without trusting a summary note:
customer allegation / bureau notice
├─ identity and authority verification
├─ contract and disclosure snapshot
├─ payment, return, allocation, and charge timelines
├─ statements and delivered communications
├─ furnished values and acceptance records
├─ restrictions and contact decisions
└─ finding → corrections → response evidenceAI may classify documents or summarize differences, but a bounded output cites permitted evidence and follows the configured human-review requirement. It cannot invent a missing payment or close a statutory obligation.
Deadlines and closure
Deadline calculation records jurisdiction, rule version, trigger event, received time, calendar, extensions, and pause conditions. The system blocks closure while a required investigation, correction, response, or delivery artifact remains open.
A corrected loan balance, furnishing record, or identity restriction changes through its owning governed API. The dispute case references those result IDs; it does not overwrite financial or reporting state itself.
Customer communication
Outbound response still requires an eligible channel and appropriate identity/authority assurance. If electronic delivery is not permitted, the obligation remains open or follows configured alternate delivery; the platform never marks a response complete merely because content was generated.