Periodic verification offers the ability to automatically conduct ongoing due diligence for KYC and KYB applicant checks, which minimizes compliance risks and streamlines daily operations. Periodic verification conditions are based on 3 main parameters:

• Applicant data
• Timeframes
• Actions applied to the selected applicants

This ensures organizations can stay compliant while reducing manual effort and scaling their operations with confidence.

How periodic verification works

You can set rules based on any applicant’s parameter available at Sumsub like registration date, residency, verification status, geography, risk level, and more.

• For instance, for KYC, regulations may require applicants to periodically resubmit PoI or PoA documents, or complete a Liveness check after X days of registration or starting for the review date, after a specific action completion, once a document expires and many more.
• For KYB customers, automated periodic rechecks help reduce compliance risks by confirming that the business address is still valid, company information is up to date, and UBOs are not on sanctions lists.
• For the Travel Rule, periodic verification helps enforce deadlines by triggering actions after a certain time period has passed. For instance, automatically rejecting or returning funds if no response is received within the required timeframe.

Easily manage and configure periodic verification via rules: one rule represents a single scheduler logic, giving you a simple way to control all your recheck scenarios.

📘

Note

Once configured, the scheduler runs automatically every day at 00:00 CET, applying recheck logic only to approved applicants.

Set up periodic verification

The following is a sequence of steps to be taken to set up the conditions for the periodic verification.

Step 1: Create custom rule

To create a rule for the periodic verification, do the following:

1. In the Dashboard navigate to the Transactions and travel rule section.
2. Go to the Rules page and click Create rule.
3. Give your rule a preferred name and optional description.
4. In the Rule behavior, select the Trigger scheduled event option.
5. In the Affect applicant section, define what action should be applied to the applicants who met the criteria of the scheduler.

Step 2: Configure scheduler conditions

First, define the criteria for which applicants should be included in the periodic check.

• Select Time since a level was completed, if you want the system to re-evaluate all applicants who passed a specific level after a certain period of time. To do this, you will also need to specify the number of days after the applicant completed the level and level itself.
• Select A custom condition, if you want to filter applicants by custom logic. In the Timer condition field, you can specify those parameters (applicant country, source key, applicant tag and so on).

If needed, you can optionally apply the scheduler only for applicants created from the specific date by checking the Activation scope box.

In the Affect applicant section, add actions as described here. Additionally to the default settings, you are able to reset steps for a current or new level. To do so, check the Reset box next to the step of your interest.
If you want to add more actions, click Add action.

Step 3: Test configuration

You can test a rule during editing, without saving it, by clicking the Trigger event immediately button. The system will then display sample applicants who meet the condition.

Step 4: Save changes

After completing the setup, click Create rule in the top-right corner.

📘

Note

If you go live, the event will not trigger right away, but at 00:00 CET of the next day.

Step 5: View results

You can see scheduled events on the Transactions table in the Dashboard by applying the Type filter and selecting the Scheduled event. They will appear for each applicant who meets the conditions.