Reviewing a match · LendEasy Docs

How a monitoring finding is adjudicated: the field-by-field comparison, the evidence panel for each signal type, and the three decisions available to a reviewer.

Monitoring covers five signals: military service, bankruptcy, mortality, sanctions and disaster. For bankruptcy, death, military service and disaster, protective suppression is applied the moment the finding is recorded — before anyone reviews it. A sanctions finding applies nothing. What the reviewer decides is whether the match is real, and no account change follows from that decision by itself. There is no address-change or employment monitoring.

both records, field by field

What the comparison shows

The customer field, the listed record's field, and a verdict per row
Matches · Partly · Differs · Unknown
Our assessment and the provider's confidence score, kept separate
Absent values printed as "Not on file" or "Not printed"
The full normalised provider record one click away, stamped with observation time and evidence version

by design

What it does not do

Combine the two confidence values into a single score
Render an absent value as an empty cell
Change anything on the account before a decision is recorded

An absent value and an unread one are printed differently, because a blank cell would not distinguish them.

Evidence panels

Each signal type carries its own evidence panel alongside the comparison:

SanctionsName compared word by word, plus a world map of exposurean initial "V" matched by the name "Victor" is flagged on its own — the classic false-positive shape

DisasterA county map with the borrower’s county called outdeclarations are made by county, and borrowers live in one

BankruptcyThe court’s own timeline, and what the stay actually stoppedread from the live case, never assumed from the filing — and a step the court has not reported shows as pending rather than guessed

Military serviceThe rate cap, per loanso the reviewer sees the consequence, not just the status

A death recordA five-step estate checklist, and the precision of the date"July 2026 · month precision" — never rendered as a day nobody reported

Date precision is preserved rather than normalised. A death record reported to the month renders as month precision and carries a warning against reading it as a known day.

Decisions

Nothing on the account changes until one of these is chosen

1Not a matchand quiet this record for a set number of days — a record that changes comes back sooner
2Confirmed matchthe finding is true of this borrower — and even this changes nothing on the account by itself
3Not enough evidencedeliberately leaves the work open rather than forcing a false choice

Confirming completes the review task with the mapped workflow outcome. Applying a hold, capping a rate or stopping contact are separate governed operations with their own permissions.

Each decision requires a written reason. Reviewer identity is taken from the authenticated session rather than the request body. The decision carries the evidence version the reviewer was shown, and a stale version is refused.

The same review runs identically whether opened from the match review list or reached as a task from the work queue.

Findings arrive from the monitoring integrations. What follows a confirmation is the relevant case type’s own workflow.