What AIMA sanctions screening guidance covers
Fund sanctions screening needs evidence that the right parties were screened against the relevant lists, that alerts received a reasoned decision, and that changes triggered a fresh review. A fund board should be able to follow that evidence from an investor record to the reviewer’s decision.
The Alternative Investment Management Association (AIMA) provides a useful starting point. Its public sanctions screening foreword and outline cover risk assessment, policies and responsibilities, information quality, fuzzy searching, false positives and false negatives, screening tools, frequency, positive identification, testing and training.
Authored by AgentKYZ. Source review: 13 October 2026. This article reviews the public foreword and contents linked to AIMA’s March 2022 Guide to Sound Practices for Sanctions Screening. The review covers those public sources, rather than the restricted full guide. Check AIMA’s official resource for current access and edition information; the linked edition is not a claim that no later edition exists.
AIMA describes its guidance as jurisdiction-neutral. The operational suggestions below are AgentKYZ’s own commentary on the public topics, not a reproduction of the guide or a statement of AIMA requirements. All examples are fictional and illustrative; they are not customer cases, actual designations or prescribed thresholds. AgentKYZ does not claim AIMA endorsement, affiliation or certification. No restricted guide text or templates are reproduced here.
Define the fund’s screening scope
Start with the fund’s structure, investor base, investment activity and payment routes. Identify applicable sanctions regimes with qualified advisers, taking account of the fund, manager, administrator and other relevant parties. Document the legal basis for list selection and any additional lists used under policy. A vendor’s default list bundle does not establish which laws apply.
Separate investor and connected-party screening from screening of investments, counterparties and payments. An administrator’s investor KYC mandate may not cover portfolio issuers or redemption payment instructions. Record the owner of each activity and reconcile the population supplied for screening to the fund’s source records.
Name matching is only one control. Sanctions can restrict activity involving unlisted entities because of ownership or control, or because of restrictions on a jurisdiction, sector or transaction. Assess those risks separately. For a specific US example, OFAC FAQ 401 explains its 50 Percent Rule and indirect ownership. Do not apply that rule as a universal ownership or control test across jurisdictions.
Illustrative scope gap: an administrator screens a subscribing company but receives neither its ownership chart nor the identities required under the fund’s policy. A clean company-name result leaves a coverage gap. The reviewer requests the ownership evidence, records the missing population and escalates any unresolved restriction before the relevant activity proceeds under the fund’s procedures.
For the broader onboarding workflow, use our investor AML screening checklist for private funds. It connects sanctions checks with PEP and adverse-media reviews, source-of-funds evidence and investor approval.
Improve data quality before matching
Collect enough reliable information to distinguish the party from a listed person or entity. Depending on the party and lawful collection requirements, that can include full names, aliases, original-script names, dates of birth, nationality, registration numbers, addresses and ownership relationships. Preserve the source documents and original values when normalising data for the screening tool.
For the wider investor-file process, use our AIMA customer due diligence guide alongside these screening controls. Identity and ownership evidence collected during CDD supplies the information a reviewer needs to investigate a match.
Check the import as well as the file. Truncated names, misplaced date fields, missing connected parties and dropped records can prevent detection even when the source documents are complete. Compare expected and processed record counts, investigate rejects and retain the run’s exception report. Collect and retain personal information under applicable data-protection and recordkeeping rules.
Illustrative data-quality failure: a feeder’s file contains a beneficial owner’s full name, but the screening export contains only initials. The workflow should identify the incomplete record, obtain the full value and re-screen it. “No alerts” from the initials-only run is not evidence that the owner was adequately screened.
Test matching rules and screening tools
Exact matching can miss spelling differences, aliases, transliterations and reordered names. Fuzzy matching can identify candidates that an exact comparison misses, but broader matching also produces more alerts for unrelated parties. AIMA’s public outline explicitly includes fuzzy searching and both false positives and false negatives.
Ask the screening provider which fields and aliases it uses, how it handles scripts and transliterations, how list updates reach the tool, and what audit evidence it retains. Record the configuration version used for each test. There is no transferable “safe” score: the same numeric threshold can behave differently across products and datasets.
Illustrative matching test: create a synthetic list entry for “Nadia Kareem,” then submit the exact name, “Nadia Karim,” a reordered version, and an unrelated person with a similar name. Define the expected candidate alerts before running the test. Review whether the tool finds the intended variants and supplies enough information to investigate the unrelated person. An alert is a candidate for review, not a finding that the person is sanctioned.
Approve configuration changes against documented test results. Raising a threshold just to reduce a queue can hide genuine matches. Compare detection of known test cases as well as alert volume, and re-test after changes to the data feed, matching configuration or provider.
Resolve false positives with evidence
A false positive is an alert concerning a different person or entity from the sanctions target. A false negative occurs when the process misses a target it should detect. Clearing a large share of alerts does not show that the process catches the right targets.
For each alert, retain the screened record, the full list entry and identifiers, the relevant list and date, the comparison evidence, the reviewer’s rationale, the decision and any required approval. OFAC FAQ 5 describes comparing the complete listing against available information and gathering further evidence where needed. That is US guidance; use the procedures and legal requirements applicable to the fund.
Illustrative false-positive review: a fictional investor and a synthetic list record have similar names. Reliable documents show different dates of birth and identity numbers, and the other available attributes support a different identity. A reviewer documents the comparison and obtains the approval required by policy. A different address alone would not justify the same conclusion: addresses change and may be shared.
Where identifying information is missing or contradictory, record an unresolved alert and escalate it. Do not label uncertainty a false positive to meet a turnaround target. If the tool suppresses previously resolved alerts, define the scope and review triggers so a changed list entry or changed investor information does not inherit a stale clearance.
Set re-screening and escalation triggers
Document when screening runs: at onboarding, after relevant list updates or changes in ownership and identity, and at applicable transaction stages. Assign responsibility for detecting each trigger, running the process, reviewing failures and handling alerts. A periodic KYC refresh is not a substitute for responding to a new designation.
The timetable must satisfy applicable law; a low investor risk rating does not waive a sanctions prohibition. This article sets no universal daily, monthly or annual interval. For Cayman-specific context, see the CIMA AML Rule guide’s sanctions section; keep those jurisdictional obligations separate from AIMA’s industry guidance.
Define an urgent escalation path to the designated sanctions/compliance officer, MLRO and legal advisers as appropriate, with deputies and transaction controls that work outside ordinary review cycles. Distinguish an unresolved candidate from a confirmed match, and assign authority for decisions. The procedure must not allow internal sign-off delays to postpone a legally required freeze or report.
Illustrative escalation: a redemption is pending when a new list entry closely matches a beneficial owner. The analyst records the alert and immediately escalates it, while the authorised team applies the relevant controls to prevent prohibited activity. The decision record identifies the applicable regime, the identity and ownership analysis, and the action required. Returning the money automatically could itself involve a prohibited transfer.
A valid match does not produce the same response under every regime or list. Applicable law determines whether to freeze or block, reject or refrain from activity, report to an authority, or consider an available exemption or licence. OFAC FAQ 5 explains these distinctions for US sanctions. Check the relevant rules and deadlines with qualified advisers; commercial approval cannot authorise a prohibited transaction.
Test detection, decisions and follow-through
AIMA’s public outline includes testing, monitoring and training. A useful fund test follows a record from its source through screening, investigation and the required action. Testing only closed alerts cannot reveal records that never reached the tool.
Use an isolated test environment and synthetic cases. Define expected results independently of the tool, including:
- a known exact match and relevant alias or transliteration variants;
- an unrelated near-name match that requires a documented review;
- incomplete input and a rejected record that must appear in an exception queue;
- a newly added test designation that triggers re-screening;
- an ownership-related restriction requiring analysis beyond a name search;
- an urgent escalation with the primary decision-maker unavailable.
Measure population coverage, update-to-screening delay, unresolved alert age and the quality of closure evidence. Record expected versus observed outcomes, assign an owner and deadline to each defect, and re-test the correction. A low alert rate alone measures neither detection nor compliance.
Train reviewers using those failures. For example, ask them to distinguish a missing identifier from a conflicting identifier, or to explain why a previously cleared alert needs another review after an ownership change. Include administrators and other delegated teams in the relevant escalation exercises.
Ask the administrator for fund-specific evidence
For fund administrator due diligence or an AIMA DDQ response about sanctions controls, ask what evidence supports the answer. An investor’s DDQ assesses the manager; investor KYC assesses the subscribing investor. The two processes can use related control evidence, but they serve different purposes.
Request an evidence pack tied to your fund and the review period:
- The scope, applicable-regime assessment, policy version and allocation of responsibilities.
- The screened population reconciled to source records, including import rejects and exclusions with reasons.
- List-update and screening-run records, with the configuration used.
- Alert decisions, supporting evidence, approvals and outstanding escalations.
- Test findings, remediation owners, target dates and re-test results.
Use the AIMA DDQ AML/KYC evidence checklist to connect this screening evidence with the wider control records behind your response.
Agree access, confidentiality and lawful handling of investor data before transferring files. Record the board’s challenge and follow-up. A provider-wide assurance report can inform oversight, but it does not by itself show what happened to your fund’s investor records.
Close file gaps or test delegated work
AgentKYZ’s Shadow KYC service independently reviews administrator-held investor files against an agreed scope and the fund’s policy. Screening results, hit dispositions and evidence of re-screening can form part of that review. The output is traceable file findings and remediation evidence for your authorised team and board. Use those records to support oversight and inform the separate programme-wide AML audit. Screening-engine testing requires its own defined test scope.
If the immediate problem is missing ownership evidence, unresolved screening rationale or overdue investor reviews, managed KYC for Cayman funds supports onboarding and remediation. Managers can also explore Hong Kong KYC services or Singapore KYC services for work under their approved policies.
The regulated entity retains compliance responsibility and the client MLRO retains approval. To scope a review, bring the relevant policy, an overview of the investor population, your administrator’s responsibilities and a description of the evidence gaps. Agree secure file access before sending investor records.