SecurePoint USA
SecurePoint USAEnterprise Compliance
Book Demo
Back to Compliance Academy
Visitor
Trade
Education
Third-Party Monitoring
Front Desk
Compliance Manager
Admin

"True hit, but not relevant to our business" — and how to document it

A disposition for a confirmed (real) match that does not apply to your line of business — recorded with the agency, the denied-party (DPL) category, and a detailed explanation.

Last Reviewed: 2026-06-02Plain-English reference · not legal advice

Plain-English Summary

Sometimes a screening match is genuinely the listed party (a true hit), but the listing has no bearing on what your organization actually does — for example a designation tied to an industry or activity you are not involved in. This is dispositioned as "true hit, not relevant to our business" (code 62). It is different from a false positive: the match is real; only its relevance is not. To use it defensibly you must record the agency/source, the denied-party (DPL) category, and a detailed explanation.

Why This Matters

Clearing a real match as if it were a false positive misstates the record and can look like you ignored a true hit. The "not relevant" disposition lets you proceed while honestly documenting that the listing does not reach your business — but only if the rationale is captured. That written basis is your evidence of reasonable care if the decision is ever questioned.

Visual Guide

Explanation Depth

Concept Explanation

Sometimes the alert really is the listed person or company — it is a true match — but the reason they are listed has nothing to do with what your business does. In that case you do not call it a false alarm (it is real); you mark it "true hit, not relevant to our business." To do that properly you must write down which agency listed them, the category of the listing, and a clear explanation of why it does not apply. If it might apply, you escalate instead.

When You'll See This in SecurePoint

In SecurePoint, selecting the "true hit, not relevant" disposition requires entering the agency, DPL category, and detailed remarks before the case can be closed; the entry is written to the immutable audit log. False positives use a separate disposition, preserving the distinction between "not a match" and "a real match that does not apply."

What You Should Do Next

First confirm it really is a true match (identifiers align), not a false positive. Then assess relevance: does the listing actually restrict what your organization is doing? If it does not, select the "true hit, not relevant" disposition and record the agency/source, the DPL category, and a clear, specific explanation in the Remarks field. If the listing could restrict your activity — or you are unsure — escalate instead.

What Can Go Wrong

Two errors: mislabeling a true-but-not-relevant hit as a "false positive," which corrupts the audit trail; and using the "not relevant" disposition without recording the agency, DPL category, and explanation, leaving no basis for the decision. Either makes the record hard to defend. And "not relevant" is never the right call when the listing actually reaches your business — that is an escalation.

Need structured workflow compliance?

SecurePoint USA builds these checks, watchlists, approvals, and immutable logs directly into your daily operations.

"True hit, but not relevant to our business" — and how to document it | Compliance Academy | SecurePoint USA | SecurePoint USA