· Yair Knijn
Your team blocked a real customer because a raw name match was treated as a confirmed hit
A claims operations director gets a flag on a claimant mid-payout. The screening provider returned a name match against a sanctions list, the file says HIT, and the director does the responsible-sounding thing: freezes the payout and treats the case as a confirmed designated party. The claimant is a different person who shares a very common name with someone on the OFAC list. Nobody adjudicated anything. The provider returned a candidate, and the operation converted a candidate into a verdict.
This is the mirror image of the failure everyone talks about. Under-blocking lets a designated party through; over-blocking freezes a clean customer. Both are compliance and conduct failures, and over-blocking is not a safe default you reach for when you are unsure.
Match status versus adjudicated outcome: two different things the system shows you
A provider match is a probabilistic statement: this name, with this fuzzy-matching configuration, resembles a list entry closely enough to surface. A confirmed true positive is a determination that the party in front of you is the designated entity, made after comparing the identifiers the list actually gives you, date of birth, nationality, passport or registration number, known aliases. Those are different states, and the screen has to render them as different states. FATF has been explicit that common names and ambiguous identifiers are a recognised source of false positives, and it expects the private sector to filter them out rather than treat every name collision as a match worth acting on. A score crossing a threshold is the start of a decision, not the decision itself.
The cost of over-blocking: customer harm, conduct exposure, and unblock workload
Freezing a legitimate claimant is not a quiet internal event. The customer waiting on a payout experiences a denial of service, and in most lines that lands squarely inside fair-treatment and conduct obligations. A real customer who later proves they were the wrong James O'Brien does not file a service complaint. They file a regulatory one, and the file you hand over shows you took irreversible action on a raw match with no adjudication recorded.
There is an operational tax on top of that. Every wrongful freeze becomes an unblock case someone has to investigate and reverse, with the relationship already damaged. False positives are the overwhelming majority of screening alerts, so auto-converting them into actions just turns queue volume into customer harm.
Adjudication as the mandatory bridge between a score and an action
Adjudication is the step that sits between detection and decision, and it is not optional. Before any irreversible action, the workflow has to force a disposition, cleared or escalated or confirmed, against the secondary identifiers rather than the name alone. Three things have to be true for it to function:
- No payout-affecting action fires on a raw match. It is gated on a recorded disposition, not on the presence of a
HITtoken. - The reviewer sees the list entry's identifiers next to the claimant's, so a date-of-birth or nationality mismatch clears the alert on its face.
- The decision and its reason are captured as structured data, and a genuine partial match reaches a senior reviewer rather than being silently cleared or silently actioned.
Recording both the raw match and the disposition so the file shows the whole story
The case file has to hold two things, not one. Keep the raw provider response exactly as it came back, score, matched fields, list source, list version, and keep the disposition that resolved it. When the regulator asks why you froze a real customer, the answer has to be in the file already. "The system said hit" is not a defensible record. "We surfaced a partial match on name only, the date of birth and nationality did not match the listed individual, reviewer cleared it on those grounds at this timestamp" is.
InsureGuardAI is built around that split. Each workspace separates the provider match from the adjudicated outcome, gates payout-affecting actions behind a recorded disposition rather than a raw score, and keeps both the original match response and the reason it was cleared or confirmed, so the case file answers the regulator's question before they finish asking it. That detection-to-decision step is where you start.