Changelog

More advanced settings when setting up your PEP, Sanction and Adverse media monitoring.

For PEP, you can now configure:

Remove equivalent names

Disables default behaviour for equivalent names. Examples when enabled: Jon ≠ John Rob ≠ Robert

Remove homophones

Disable matching on homophones but leaves all other aspects of the default equivalent name matching logic enabled. Examples when enabled: Steven / Stephen

Remove weak alias

Do not match on AKAs listed by a source as being weak.

Remove legacy entities

Remove legacy data. Removes matches to older, less complete profiles which are steadily being deprecated and generally do not contain enough information to make a remediation decision about.

Remove out of office PEP entities (1 year)

Remove PEP entities that have been out of office for at least one year.

Remove out of office PEP entities (5 years)

Remove PEP entities that have been out of office for at least five years.

Visit the dashboard to see the settings for Sanctions and Adverse media.

New step added to the Workflow builder: Set application status.

Add this step and assign a status to the application at the end of a workflow to automatically assign a status. Less manual work, more automation!

It's now much easier to get an overview of all the governing members, ultimate owners, financial oversight and Signatory combinations in the dashboard. Get the names, roles and checks (if they're monitored) in an overview and unfold to deep dive if needed.

The dashboard is great and shows all the data, but sometimes, just sometimes, you might need the good ol' PDF. So here you go! You can now export any application or entity as a PDF, and select which data to export in it.

We've just released an update to our relationship tab. The relation between entities are much easier to explore. The release makes it much easier to understand and navigate the connections between entities. You can now:

• Build out complete ownership and relationship networks with much less effort.

• Clearly see how different entities are connected and interact with each other.

• Identify when multiple relationships exist between the same entities, giving a much clearer view of complex structures.

Simply double-click on a node to load more relations for that entity.

• The green node is your starting entity/node.

• If an organisation node is beige it means you haven't loaded its relations.

• If an organisation node is black it means you have loaded its relations.

• If an individual node is beige it means you haven't loaded its relations.

• If an individual node is white it means you have loaded its relations.

Ongoing Due Diligence. This feature allows you to schedule your customers to renew their data/answers to questionnaires etc. In simple words this is how it works:

1. Schedule name - For each schedule that you are creating it need to have a name. The recommendation is to set a name that is descriptive of what it is for. E.g., High-risk.

2. Risk score model(s) - As describe above you’ll need to decide and configure to which risk score model(s) the schedule should apply to. Meaning that only entities that have a risk score using these models will have this scheduling applied. E.g.., Customer Risk Score

3. Risk score interval - Select the range of the risk score that this schedule will apply to. E.g., Greater than or equal to 3 and Less than or equal to 4 (meaning your customers with the highest risk).

4. Monitored properties - Select the properties of your customers that should be monitored to ensure that you have up-to-date information about your customers. E.g., address, organization status, questionnaire answers to 3 questions.

5. Refresh frequency - Decide how often/how old the data in the monitored properties can be. E.g., 12 months.

6. Advanced notice - Decide how far in advance you want to be notified regarding the expiring monitored properties.

We are excited to announce the launch of Risk Analyze, our new product designed to give you deep insight before you publish an updated version of your risk scoring model for your customer base. With Risk Analyze you can:

• Review changes from your previous model version and see how they compare to the proposed new model.

• Visualize a detailed histogram of how risk is distributed across your customer base.

• Track how ve between risk segments under the proposed changes - for example, how many move from low to medium risk, medium to high, or vice-versa.

• Ensure that the updated model’s output aligns with your risk policy and desired outcome rather than producing unintended concentration or escape of risk segments.

• Particularly valuable if you have a large or complex customer base with sophisticated risk-scoring requirements - Risk Analyze helps you validate that your model changes will behave as expected and remain in line with policy.

TLDR; before you publish your model update, you’ll get a clear, visual view of how the change will impact your customer base and risk distribution - helping you move forward confidently and in control.

You can now create smarter, more dynamic workflows with the new Split Condition feature. This lets you design user journeys that adapt in real time—gathering only the data you need while keeping the process lean, effective, and tailored to each case.

Set up multiple conditions and branch paths based on user input. Whether you’re using pre-built properties, custom fields, or risk scores, you can guide users down the most relevant path and reduce unnecessary steps. The result: more precise data collection, faster decisions, and a smoother experience.

This makes your workflows not only more powerful, but also more compliant and user-friendly—helping you focus on what matters most: accurate decisions, less friction, and better outcomes.

What data will be available to build conditions?

You will have access to all entity data for making the decision. This includes:

• Bits properties and data

• Custom properties

• Risk score

Conditions logic

• Each condition results in one new path. A split condition must have at least one condition.

• There will always be a default path called "Otherwise". This is the path that will be taken if the other conditions created are not met.

Re-ordering steps

With this new feature, it is now also possible to re-order nodes in the workflow. You can link and unlink nodes and move them around in the workflow.

Multiple steps of the same type

It is now also possible to add multiple steps of the same type. You can i.e. add multiple questionnaires. This allows you to ask relevant questions based on data you gather along the user journey.

This update includes a cleaner layout and improved navigation to help you find key information more efficiently. You’ll now find the governing body, UBOs, and other related representatives under the new Representatives tab.

Hey! We've been busy working during the summer, and here's a list of new features and other improvements to current features, and more:

• The Account Information verification flow in our No-code has received som UX improvements: account name is now optional, and Financial institution (which is the more technical term used for AIS services) is now labeled "Financial instituations/Bank name" for the end users. We've also made improvements to the confirm account page. We've added a spinner and added more helpful texts on the loading pages so the end-user is continuously updated when adding their account, if it's taking longer time than expected.

• (Custom) Properties has received som more UX love as well. The "Allow multiple values" settings are now under Type. Scroll has been improved for associated countries/markets as well. What was written out as "Value" is now more technically written as "Value name" to be consistent. We're now also displaying the display name under values as well.

• We've added Financial oversight relation when viewing relations for organizations.

• When reviewing a user journey that went through Veriff, we now show more detailed error messages, if there were any.

• Monitoring has received some clearer copy to clarify that the custom rules are "exclusion rules" (what do you NOT want to monitor) and not "inclusion rules". We've also added a custom monitoring rule type: by entity ID, allowing you to create custom rules for specific entities.

• There's a new guide! Properties! It's a great read, we promise. You'll learn everything you need to now about Properties and will master the platform after the read.