Excluding a contact from checks
Overview. Sometimes you do not want IdentityCheck to act on a particular client at all: you have already verified them elsewhere, they are out of scope, or you simply do not want a bulk or automatic run to pick them up. On Xero Practice Manager (XPM) and FYI you can mark that client as Excluded, which deliberately stops any check from being triggered on them. Exclusion never deletes the record or any checks already done. It is a per-client opt-out you turn on, and can turn off again later.
What "Excluded" does
The Excluded status is a signal on the client record that tells IdentityCheck to skip that client. When a client is marked Excluded:
- Ticking the KYC Command or AML Command field on them does not start a check.
- Automatic and scheduled runs pass over them rather than sending a request.
- Their existing history is untouched. Any verification or risk assessment already completed stays on the record as evidence.
This is why "nothing happened" after ticking a command box is sometimes simply an Excluded client rather than a fault. See You set the AML trigger but no check appeared.
How to exclude a client
On XPM and FYI, set the client's status field to Excluded on the client record. [VERIFY: exact field name and location on the XPM/FYI client record used to set Excluded status, e.g. the KYC Status or AML Status field vs a dedicated field.]
On the next sync (XPM and FYI run on an hourly background sync), IdentityCheck reads the status and leaves that client alone. You do not need to change any account-level setting to exclude a single client; it is set on the individual record.
[VERIFY: whether a contact can be excluded from inside the IdentityCheck app itself (for example from the dashboard) for clients that are not managed through XPM or FYI, or whether Excluded is only available on those two integrations.]
When to use exclusion
Exclusion is useful when you want a client to stay in your practice system but out of the checking flow. Common cases:
- Already verified elsewhere. You have identity evidence for this client from another process and do not want a duplicate check.
- Out of scope. The client does not require a check for the service you provide. For help deciding what is in scope, see Designated services under Tranche 2.
- Protecting a bulk or automatic run. You are about to trigger checks across many clients and want specific records left out.
Exclusion is a deliberate choice, so use it where you have a clear reason and can point to it later. It does not change the client's obligations; it only stops the platform acting on them.
Bringing a client back in
Exclusion is reversible. Remove the Excluded status from the client record, and on the next sync the client can be checked again in the normal way. Nothing about their earlier history is affected by turning exclusion on or off.
Frequently asked
How do I stop a client from being checked? On Xero Practice Manager and FYI you can set the client's status to Excluded. An Excluded client is deliberately skipped by IdentityCheck, so ticking a command field on them never starts a check. It is the clean way to exempt a client you have already verified elsewhere or who is out of scope.
When should I exclude a contact? Use it for clients you do not want the platform to act on: someone you have already verified through another process, a client who is out of scope for your obligations, or a record you do not want a bulk or automatic run to pick up. Exclusion is a deliberate opt-out you control per client.
Does excluding a client delete their record or past checks? No. Exclusion only stops new checks from being triggered on that client. Any verification or assessment already completed stays on the record as evidence. If you exclude a client and later change your mind, remove the Excluded status and they can be checked again.
Nothing happened when I ticked the command box. Is exclusion the cause? It can be. An Excluded client is skipped on purpose, so check the client is not marked Excluded before treating it as a fault. Work through the other common causes in You set the AML trigger but no check appeared.