· Yair Knijn
You cleared the fuzzy match. You wrote down nothing. The auditor only sees the second part.
A compliance officer pulls up a screening hit at 9:40 in the morning. The system flagged "Viktor Petrov" against an SDN entry for a "Viktor Petrov" with a different birth year and a different country. Thirty seconds of looking, the officer knows it is a different person, clicks clear, and moves to the next of forty hits in the queue. The decision was correct. The mistake is that the officer wrote down nothing about why.
This is the quiet failure mode of every screening program I have worked inside. The adjudication was right. The record of the adjudication does not exist. And a regulator reviewing the file two years later cannot see your instinct, your experience, or the thirty seconds you spent being correct. They see a green checkmark over a true name match, and a blank.
The difference between dispositioning a match and recording a decision
Dispositioning a match is closing the alert. Recording a decision is leaving behind a thing another human can read and agree with. These are not the same act, and most screening tools only force you to do the first one. You click the disposition, the queue count drops, and the system is satisfied. Nothing asked you for a reason, so you did not give one.
That gap is invisible while you are working and total when someone audits you. The officer who cleared Viktor Petrov knew the DOB was off by eleven years. That fact lived in their head for thirty seconds and then was gone. The case file kept the verdict and threw away the evidence.
What "reasonable care" under 31 CFR 501.701 actually wants to see in the file
OFAC does not publish a checklist that says "write one sentence per cleared hit." What it does is treat your compliance program as a factor in any enforcement outcome, and the Economic Sanctions Enforcement Guidelines at 31 CFR Part 501, Appendix A weigh the quality of your program when they decide what a violation costs you. Contemporaneous documentation is how that quality becomes legible. A program that cleared the right names but cannot show its reasoning looks, on paper, identical to a program that cleared names at random.
The recordkeeping clock is long, too. OFAC extended the retention requirement under 31 CFR 501.601 to ten years, effective in 2025. So the disposition you make in a hurry this morning is discoverable for a decade, and the version of you who has to explain it will not remember this party at all. The file is the only witness, and right now the file says nothing.
The discriminators that make a clearance defensible: DOB, jurisdiction, identifiers
A defensible false-positive call rests on a discriminating data point: a fact about your party that the listed party does not share. The whole job of the written rationale is to name that fact. Vague reassurance is worthless under review. The specific mismatch is the entire defense.
- Date of birth. The SDN entry lists 1961, your insured was born in 1972. Eleven years is not a typo, it is a different person.
- Jurisdiction. The designated party is tied to a sanctioned-region passport, your party is a Dutch national with a Dutch
KvKregistration and no nexus to that region. - Strong identifiers. Passport number, national ID, tax registration. When these are present on the list entry and yours does not match, the match dies on the spot, and that is the cleanest record you can leave.
Write the discriminator down by name. "Cleared, DOB mismatch 1961 vs 1972, no shared identifiers" is a sentence an auditor can verify against the list entry. "False positive" is a sentence an auditor can only distrust.
Capturing rationale at the point of decision instead of reconstructing it under audit
The reconstruction is the part nobody budgets for. When the examiner asks why you cleared a party in March of two years ago, you are not retrieving a memory, you are inventing a plausible story and hoping it matches what you actually did. That is the worst possible posture, because a guessed rationale that turns out wrong is more damaging than an honest blank. The only fix is to capture the reason in the same click as the clearance, while the discriminating fact is still on your screen.
InsureGuardAI is built so the rationale is part of the disposition, not a thing you mean to add later. When an officer clears a fuzzy match in their workspace, the discriminator, the cleared-against list version, and the identity of the decider are written into the case at the moment of the call, alongside the raw match response. The file answers "show me why you cleared this party" before the examiner finishes asking, because the answer was recorded by the person who actually knew it. See how the workspace captures every clearance.