About acceptance checks
When a task is configured, it can be assigned one or more check variants as Acceptance checks.
When the task is on a profile's product application, it's automatically marked as Passed when the most recent Acceptance check passes.
If the task has multiple Acceptance checks, only one needs to pass for the task to pass.
Acceptance checks are tied to task versions. If the task gets a new version, the latest Acceptance check on that version must pass for the version to pass automatically.
Some checks return a Completed state instead of a Passed state, for example, the Company ownership check. We do not recommend adding these checks as Acceptance checks. Learn why some checks return Completed.
In the case of PEPs, sanctions, and adverse media tasks, the task passes automatically when the latest Acceptance check does not return any potential matches and the profile has no outstanding potential matches returned from an earlier check.
PEPs, sanctions, and adverse media tasks don't autocomplete when matches are resolved manually. If any matches are discovered during the check or ongoing monitoring, the check must be passed manually. You can also configure check variants to run automatically. Learn more about all task configuration options.
Where to view a task's acceptance checks
To view a task's acceptance checks, you need Read-only access for the smart policies permission.
A task's Acceptance checks can be found in . Select the task you want to see. Any check variants that will cause the task to pass automatically are listed in Acceptance checks.
To add or remove Acceptance checks, contact our Client Service team.
To learn when your checks pass, see the configuration instructions for your data provider.