How MatchAudit standardizes inputs, supports multilingual names, finds candidates, and scores confidence—so your decisions stand up to banks, auditors, and regulators.
/public/sanctions-lists.Covered jurisdictions and update cadence are listed in Coverage & Credence.
Before matching, we standardize both inputs and list values:
This reduces false mismatches caused by formatting while preserving informative tokens.
Practical tip: when possible, search with the most complete legal name plus any known local-language spelling.
We search across multiple name fields and aliases using Fuse.js with a strict threshold:
name, primaryName, wholeName, firstName, secondName, thirdName, lastName, surname, familyNamealiases, aliasName, nameAliases.wholeName, nameAliases.firstName, nameAliases.lastNamematch.score (0 = perfect). We convert to confidence as 1 − score.No phonetic algorithms are used by default; this reduces over-broad hits and keeps rationales transparent.
We parse and attach contextual fields to help you disambiguate candidates:
Each candidate receives a confidence value (0–1, shown as %) and label:
Labels reflect the current implementation; future tuning may add a distinct “High” band.
If the API is unavailable, we fall back to the last snapshot and mark the source in the result.
MatchAudit does not provide human reviewers or manual adjudication services. You and your team are responsible for reviewing candidates and making final decisions per your policy.
Screening reduces risk but does not eliminate it. Always follow your internal due-diligence procedures.
Screening outputs are risk indicators, not legal determinations. MatchAudit provides timestamps, list versioning, and rationales to support audit readiness; responsibility for final decisions remains with you.
Effective date: 2025-12-06. We update this page as thresholds and sources evolve.