Product context is educational relevance, not a feature-status or compliance claim.
Confirmed identity match, but does the source-specific restriction apply?
An internal disposition that should be used only when the party is correctly identified but the specific source restriction does not apply to the contemplated activity; it is not a safe harbor from an applicable government prohibition.
Plain-English Summary
Why This Matters
The question is whether the source-specific restriction reaches the contemplated activity, not whether the listing feels related to the organization’s business. Legacy labels such as 'true hit, not relevant' invite the second reading, which is why the applicability question has to be asked explicitly. Different screening sources have different scopes, so the reviewer has to identify the source, confirm identity, read the restriction, analyze the contemplated activity against it, and document why the rule does or does not apply.
Visual Guide
- 1Confirm identity
Identifiers align with the source record
- 2Identify the source and program
Which list produced this, under what authority
- 3Read the source-specific restriction
What that source actually prohibits or requires
- 4Analyze the contemplated activity
Does this restriction reach the contemplated activity?
- 5Document the rationale
Source, restriction, activity, and conclusion
- 6Disposition: restriction not applicable
Internal workflow outcome only, logged
Not the same as a false positive. The match is real; the open question is whether the source-specific restriction reaches the contemplated activity.
Explanation Depth
Concept Explanation
Sometimes the screening system correctly identifies the listed person or company, but the specific list governs a type of government program or activity that is not involved in this case. The reviewer has to read that list’s rule and compare it against the activity being contemplated before recording the restriction as not applicable. A real sanctions block cannot be ignored because it feels unrelated to the business.When You'll See This in SecurePoint
Where a product or an organization still carries a legacy label such as 'true hit, not relevant', treat it as an internal workflow name and not as a legal status: the reviewer must still document the source, the restriction, the activity analyzed, and the rationale. An internal disposition must not be used to bypass an applicable OFAC block, export restriction, SAM exclusion effect, health-care exclusion consequence, or other source-specific rule.
What You Should Do Next
Work the six steps in order. First, confirm identity. Second, identify the exact source list or program that produced the result. Third, read the source-specific restriction that source imposes. Fourth, analyze the contemplated activity against that restriction. Fifth, document the rationale so a later reader can follow it. Sixth, follow any applicable prohibition, blocking rule, rejection requirement, license requirement, exclusion, reporting obligation, or other consequence the source imposes. A restriction-not-applicable disposition is available only when step four genuinely shows the rule does not reach the activity.
What Can Go Wrong
Sources & References
Related Terms
Need structured workflow compliance?
SecurePoint USA builds these checks, watchlists, approvals, and immutable logs directly into your daily operations.