Passfort clients can now benefit from a new T-rank data provider that helps to identify beneficial owners.

T-rank uses advanced methods to identify the most powerful shareholders in a company, even when dealing with complex ownership structures such as circular ownership. T-rank’s unique power index reveals who the powerful owners are, and supports combining T-rank’s voter power approach with an integrated ownership approach.

The T-rank integration will be recognizable to users of Orbis.

How it works

• The T-rank data provider makes use of T-rank’s beneficial ownership product.
• The data provider uses the company data check template.
• Beneficial owners are returned within the assess company ownership task. In contrast to the Moody’s Analytics Orbis integration, no other roles are returned by the data provider.
• The beneficial owners identified by T-rank can be added to a verification list using automation and can also be added to the verification list manually within the Passfort portal or API.
• The user can click on the ownership visualization link in the check result and see the organizational structure of the onboarded company in T-rank’s visualisation tool.
• Thresholds for the percentage ownership required before a shareholder is considered a beneficial owner can be configured in the data provider, and the client can choose whether or not they want to include beneficial owners identified through their voter power.

The check result for the T-rank data provider within the assess company ownership task, including the Ownership visualisation link that takes you to T-rank’s interface

The T-rank interface that opens in a new window when you click on the Ownership visualisation link

Out of scope

• Data from other T-rank products
• T-rank data appearing in Passfort’s native org chart

Using the new T-rank integration

If you’d like us to set this up for you, contact us.

Useful links

From T-rank

• Documentation for the T-rank data provider for Passfort
• A marketing page on beneficial ownership discovery
• A whitepaper on beneficial ownership discovery
• Documentation on integrated ownership
• Documentation on shareholder power
• General T-rank documentation

From Passfort

• Help docs on the assess company ownership task
• Help docs on verification lists
• General Passfort documentation

We are postponing our plan to limit the size of the application flag history you can retrieve to the 100 most recent entries.

We previously reached out about upcoming changes to how you can retrieve flag history details from the API. These changes were initially planned for June, but we have postponed the release to later this year. 

We will get in touch ahead of time to notify you of when we will release these changes.

You can now visualize videos and proof of address documents submitted by the customer to the Intelli idbox portal when running Document verification (service collects multiple) checks.

Customers submit their documents to the Intelli idbox portal and, if required, have a videocall with a qualified Intelli idbox agent. The documents, any videos, and the verification results are brought into Passfort’s portal where you can see everything in one place.

To run these checks, you need to have a direct agreement with Intelli idbox.

Contact us to get started, or learn more about our Intelli idbox integration.

Passfort’s portal now supports translations for Spanish and German. These are now selectable in the dropdown menu in the navigation bar

You can track progress in our roadmap portal here

Additional information

Find out more in our help site article here

Help site

The help site is also being translated to match the supported languages, these will be released over the next few months

Support

Our support process will continue to be in English

Out of scope

Note, some text isn't supported for translation such as:

• Fixed Passfort terms will remain in English, such as 'Policy Builder'
• User-generated values (Custom fields, task/product/etc. titles)
• Check results and data returned by third-party providers
• API documentation
• Notification emails

We are planning to limit the size of the application flag history you can retrieve via API to the 100 most recent entries.

Currently, you can retrieve the entire application flag history in the v4 API using the flag_history array documented here. However, this can have significant performance issues for profiles with large numbers of associates. As a result, we will limit the number of returned entries you can retrieve by API in the flag_history array to the 100 most recent entries. Note that we will still store the entire application flag history in the database. This change will be released in June. 

We are notifying customers as, although this is unlikely to impact you, it is a backwards-incompatible change to the v4 API.

If your integration relies on the application flag history array, please get in touch with support@passfort.com by the 26th May if you have any concerns.

Clients using Orbis data for company data checks can now see the source data for those checks in the Orbis portal at the click of a button. This means you can carry out deeper manual investigations without searching for the company again in Orbis.

What’s changed?

When completing a task that is powered by an Orbis company data check you can now click on a link in the check result banner to view the source data.

This will open a new browser tab displaying the relevant company profile in the Orbis portal. You can view all of the source data for the check within the Orbis portal, along with any additional data Orbis holds about the company.

Authentication

To view the data using the new source data link each user will need an Orbis username and password or single sign-on (SSO) access to the Orbis portal.

You may be asked to log in when you click the link. You will be redirected to the relevant profile once you have logged in.

Where you can find the source data link

The new source data link will appear within tasks that use the company data check.

Supported data providers:

• Bureau van Dijk Orbis
• Moody’s Analytics Orbis

Supported tasks:

• Verify company details
• Verify company address
• Identify officers
• Assess company ownership (new Moody’s Analytics Orbis data provider only)
• Assess financials (new Moody’s Analytics Orbis data provider only)

Limitations

PassFort checks contain a snapshot of the company data taken at the time when the check was run. There may be a difference between the data in the check result and the data in Orbis if you view them at a later time. You can manually run the check again in PassFort to see the most up-to-date information in PassFort.

The option to view data in Orbis won’t be available if the check returns an error or no matching company was found in Orbis.

What you need to do

You don’t need to take any action to enable this feature. The new source data link is available for all PassFort users running company data checks with Orbis. You can find out more in the PassFort help docs. If you have any questions, just get in touch with Support.

You can now share saved filtered views with the other users in your institution.

Getting started

The shared views feature is available now. If you have any questions, just get in touch with Support or read more about it in the help documentation.

The Australian Government's Document Verification Service (DVS) has made the driver's license card number a mandatory field when verifying a driver's license.

The driver's license card number is unique to each new driver's license card that is issued. It is distinct from the driver's license number, which does not change when a new card is issued. The Australian Government says this change will help reduce identity fraud and impersonation by ensuring that only the most recently issued driver's license card can be used in a verification check.

Some of PassFort's data providers, such as Equifax Australia, use the Australian DVS to verify driver's licenses. Equifax say these changes are "particularly relevant for those affected by the Optus breach" in which some Australian driver's license numbers were exposed.

What's changed?

When an Australian driver's license is added via the PassFort portal, the card number can be added to the new driver's license card number field. When it's added via the API, the card number can be sent in the new issue_number field.

We pass the driver's license card number to the Equifax Australia integration as the driver's license card number. This improves automation rates for applications in PassFort when using Equifax Australia's IDMatrix.

Adding driver's license details using the PassFort portal

When PassFort collects document details, you've always been asked to enter a document number. For driver's licenses, this is the permanent driver's license number.

If you have chosen the option of adding an Australian driver's license, we will now also ask you to enter the driver's license number and the new driver's license card number.

Adding a driver's license using the PassFort API

We now accept an optional issue_number in the documents_metadata section of the PassFort API.

The driver's license card number should be provided in the new issue_number field. As before, the driver's license number should go in the number field.

For example:

"documents_metadata": [
  {
    "document_type": "DRIVERS_LICENSE",
    "country_code": "AUS",
    "number": "The driver's license number",
    "issue_number": "The driver's license card number", // the new optional field
    "issuing_state": "VIC"
  }
]

Limitations

• PassFort currently only supports this additional field for Australian driver's licenses.
• Only the Equifax Australia integration has been updated to make use of the new field.

What you need to do

If you process Australian driver's licenses using Equifax's PassFort integration, begin collecting the driver's license card number from your customers.

Enter these numbers in the driver's license card number field of the PassFort portal as shown above, or submit them in the issue_number field of the documents_metadata in the PassFort API.

You can find out more in the PassFort help docs and our API docs. If you have any questions, just get in touch with Support.

Clients using ComplyAdvantage can now opt to send them the PassFort customer reference field.

Customer reference is a profile field that lets you store an internal ID for your customer within PassFort. ComplyAdvantage refers to this field as the client reference. This reference can be used within the data provider’s own systems for actions such as searching, whitelisting, and tracking searches.

You can find out more in our help documentation.

Limitations

ComplyAdvantage only supports client reference fields that are:

• 255 characters or less
• Only contain the following character types:
  • Alphanumeric characters
  • Spaces
  • Hyphens
  • Underscores

PassFort does not update its customer reference if the corresponding client reference is updated in ComplyAdvantage, nor does PassFort backfill any missing customer reference entries that may be set in ComplyAdvantage.

How to configure

The Send customer reference checkbox must be enabled on the ComplyAdvantage data provider configuration screen.

If you’d like us to set this up for you, contact us.

Soon we will be releasing the ability to share saved filtered Views with all the other users in your institution. Views are combinations of filters, columns and sorting of the profiles list.

Please note, the ability to reorder filtered Views will be replaced by favouriting Views, which will appear at the top of the list in a new section. Your existing Views will be ordered alphabetically unless they are favourited.

Getting Started

When released, you will immediately be able to start sharing Views.