Changelog

With edit entities, you can now edit the information in the dashboard for all the businesses and individuals you connect to or with.

We have released the first version in a limited scope and will continue to expand the edit functionality in the coming weeks.

With custom properties, you can create company-specific properties that do not exist in Bits' data model. You can use these properties to tag and group your customers, and the properties can be reused across different industries, customer segments, and countries. With this update, Bits data model goes from static to fully dynamic and adaptable to your needs.

You can now select and close multiple case items at once.

Here's an example: if you have two possible PEP matches in one case, and you see both of them are false positives, you can now click "Select all" and make a multi-decision at once. This will save you and your colleagues a huge amount of time.

With risk score breakdown, you can clearly see how and why a risk score was calculated. Based on the risk score model you've set up, you'll now be able to see how each organization has gained their accumulated risk score based on the factors it has had a "hit" on.

You can now view all questionnaires an individual or organization has connected to their entity. Compare questionnaires against each other to quickly and easily see if and how their answers have changed over time.

We've released a comletely overhauled, improved and expanded version of our API reference. It's built with Scalar, so EVERYTHING will be included, documented and referenced in our new API reference. It's accessible within the dashboard.

We've released basic User Management settings. Invite team members in the new "Account" in our dashboard. You can invite multiple at once, and have a list to see who's been invited, joined and pending to accept invitation. More to come.

We've integrated AIS with GoCardless to offer the service to let your users add their bank account information automatically; such as your sort code, account number, IBAN, BBAN, account type and account balance.

Our Account Information solution is available in all European Economic Area countries that are subject to PSD2 regulation. We've also built a manual flow for the end-user if their country is not eligible for the PSD2 regulation to be able to add their account information.

New feature: Save Filters
Now, when you add filters in any table view (e.g., the Workspace page), you’ll see a new "Save Filters" button. Here’s how it works:

1. Apply your filters.

2. Click "Save Filters", give your filter group a name, and save.

3. Next time, just select your saved filters from the "Filters" dropdown—no need to set them up again. You can browse between multiple Saved filters that you create. (And you can always edit or remove saved filter groups as needed.)

Monitoring just got a lot(!) of new features and capabilities. We've made the monitoring configuration customizable to suit any specific needs. We've made it possible to configure your monitoring lists, set properties and build custom rules. Here's a little bit more information of these three new configuration possibilities:

Lists

It is now possible to select the specific lists you want to monitor against. Browse thousands of lists for the areas you want to monitor; PEP, Sanctions and Adverse media. More type of lists are coming soon.

Properties

It is now also possible to set up your custom preferences regarding which properties you want to monitor. Properties are the fields that will be used to match listed records for a category. By enabling more properties, matching will be more explicit and less likely to match unintended records. Property fields can be set to one of the following states:

Disabled: The property will not be used when monitoring.

Optional: Used if the property is available, but not required to start monitoring.

Required: The property is required to start monitoring an entity.

Custom rules

All properties are monitored by default. Create rules to specify the entities and properties to be excluded from monitoring. This means that you might want to monitor Owners, but not individuals or organizations that owns less than perhaps <10% of an organization you're monitoring.