AML checks can return more than one hit. Each hit is one record from an AML list. During review, record a confirmed match or a false positive on each hit. The check status is calculated from those decisions.
KYC and AML features are available as add-ons to your Rebilly account. To activate, contact Rebilly.
| Hit decisions | Check status |
|---|---|
| At least one hit has no decision yet | pending-review or in-review. A check that inherits the result of an earlier check keeps that result until a reviewer decides a hit. |
| Every hit has a copied decision, but the decisions come from more than one earlier check, or the earlier check was not reviewed, or its set of hits differs | pending-review until a reviewer completes the check |
| Every hit has a decision, and at least one is a confirmed match | confirmed-match |
| Every hit is a false positive | false-positive |
A confirmed-match hit cannot be stored on a false-positive check. For information on inherited results, see AML check inheritance.
Use this process to record a decision on each hit of an unreviewed AML check. The check stays in review until every hit has a decision.
- In the left navigation bar, press Data tables, then press KYC & AML.
- Press AML unreviewed customers, then in the ID column, press an AML check ID.
- On each hit with the Needs review badge, press False positive or Confirm match.
- Optionally, to apply one decision to every hit that still has no decision: In the top right of the page, press False positive or Confirm match.
To change a decision after the check is reviewed, see Change a hit decision.
Use this process to change the decision on a hit of a reviewed AML check. The check status is calculated again from the hit decisions.
- In the left navigation bar, press Data tables, then press KYC & AML.
- Press AML reviewed customers, then in the ID column, press an AML check ID.
- On the hit, press False positive or Confirm match.
A later AML check can return a hit that matches a hit with a decision on an earlier check. The decision is copied onto the new hit. The most recent earlier check of the same customer is read first, then the most recent check of each related customer. A related customer is treated as the same person as the checked customer. A copied decision shows the Copied from prior review badge on the hit. A false-positive result of an earlier check can also be reused as a whole, from the same customer or a related customer. Every hit on the new check then has a copied false-positive decision.
Hits without a decision are left open for review. A later check that only adds new hits keeps the earlier decisions and leaves the new hits open. When two hits on the earlier check have the same identifying details but different decisions, neither decision is copied, and both hits come back open.
When every hit on the later check has a copied decision, the check can still wait for a reviewer. That happens when the earlier check was not reviewed, when the set of hits changed, or when the decisions come from more than one earlier check. To complete it, press False positive or Confirm match at the top of the page, or press a decision on a hit.
A recurring check for a customer named John Smith returns four hits. Two lookalikes were marked false positive on the most recent earlier check, and those decisions are copied onto hits 1 and 2. Hits 3 and 4 are open, with neither False positive nor Confirm match selected. The reviewer presses Confirm match on hit 3. The check stays in review because hit 4 has no decision. The reviewer presses False positive on hit 4. Every hit has a decision, and one is a confirmed match, so the check status is confirmed-match.
When you export AML checks from data tables, the hits column includes the decision on each hit.