Application reports
Use reports to analyze your compliance processes.
What are the application reports?
These are the reports for applications:
Conversion rate
Time to decision
Straight through processing (STP)
To view a report, go to the tab, select , and select the report you want to see.
By default, all reports show data for profiles who are prospects and/or customers. To view the data for company associates, change the options for the Profile type filter criterion. To learn more about when your data refreshes, how data is displayed in the graph and table, and more, see Using reports.
Conversion rate
The Conversion rate report shows the percentage of product applications that have been approved each week.
There are three metrics:
Created: The number of applications created that week.
Approved: The number of applications created that week that have been approved since then.
% Approval rate: The percentage of applications created that week that have been approved since then.
In the preceding example, 10 applications were created the week of September 23. Of those 10 applications, three have been approved since, which makes the approval rate 30%. They may have been approved at any time.
Time to decision
The Time to decision report shows the amount of time it took for a percentile of applications to be decided (approved or rejected) each week.
There are three metrics:
50th percentile: The amount of time it took for 50% of the applications approved/rejected that week to be decided.
80th percentile: The amount of time it took for 80% of the applications approved/rejected that week to be decided.
95th percentile: The amount of time it took for 95% of the applications approved/rejected that week to be decided.
In the example preceding, 50% of the applications approved/reject the week of July 22 were decided in 21 hours or less. 80% of applications approved/rejected that week were decided in two days or less. 95% of applications approved/rejected that week were decided in three days or less.
This report shows the time to the first application decision. For example, if an application was initially approved, then later rejected, the Time to decision report only shows the amount of time before the application was approved. If the Time to decision report shows 0 seconds, there is no data for that plot point. For example, if the 50th percentile of applications in a given week were decided in 0 seconds, there were likely no applications decided that week.
Straight through processing (STP)
The Straight through processing (STP) report shows the percentage of applications decided that week that did not have any manual intervention during the date range. Learn more about how STP is determined.
There are three metrics:
Decided (all): The number of applications decided that week, including those decided with STP and those decided with manual intervention.
Decided with STP: The number of applications decided that week that did not have any manual intervention.
% decided with STP: The percentage of applications decided that week that did not have any manual intervention.
In the preceding example, 10 applications were decided the week of November 18. Of those 10 applications, three were decided with STP, which means that 30% of all applications decided that week were decided with STP.
This data shows the time to the first application decision. For example, if an application was initially approved, then later rejected, the STP report only shows the amount of time before the application was approved.
How is STP determined?
An application is decided with STP when it goes from created to approved or rejected automatically, with no manual intervention.
The following actions do not affect whether the application is decided with STP:
Creating the profile.
Viewing the profile.
Adding/deleting a task note.
Adding/removing a tag.
Adding a comment to the application.
Downloading an audit file.
Downloading an audit report.
Automated actions by an API integration.
If any of the following actions take place between the time the application is created and first decided, the application is not decided with STP:
Application is updated manually, for example, a user runs a check.
Profile is updated manually, for example, a user adds profile data, even if that data does not affect the outcome of the application.
Company associate is updated manually, such as a user runs a check on the associate or adds data to the associate's profile.
Another application the profile has open at the same time is updated manually, for example, a user runs a check on that application or updates a company associate who is being verified for that application.
Application is escalated for approval.
Data you can filter
You can choose from any of the following criteria and only the data from applications that meet your criteria are displayed:
Application status (current): The status of the application. Possible statuses are: Applied, meaning that the application has not yet been approved or rejected for the first time, Approved, Canceled, In Review, and Rejected.
Application status (at first decision): Whether an application was initially approved or rejected. Note that the decision may have changed since, for example, the first application decision was Approved but the current state of the application is Canceled. To see applications that haven't been approved or rejected yet, select .
Product: The product the application is for.
Profile type: The type of profile. The options for this filter are INDIVIDUAL_CUSTOMER, individuals applying for your product, COMPANY_CUSTOMER, companies applying for your product, INDIVIDUAL_ASSOCIATED, company associates who are individuals, COMPANY_ASSOCIATED, company associates who are companies.
Country of incorporation: The profile's country of incorporation. To see applications from profiles with no country of incorporation: all individual profiles, plus any company profiles with no data for this field, select .
Country of current address: The profile's country of address. To see applications from profiles with no country of address: all company profiles, plus any individual profiles that have no data for this field, select .
Country of nationality: The profile's country of nationality. To see applications from profiles with no country of nationality: all company profiles, plus any individual profiles that have no data for this field, select .
Risk level (current): The current risk level of the application. To see applications that do not have a risk level, for example, a risk level won't be assigned because there's no risk model for that product, select . To see applications with a risk level that could not be calculated, select . Note that this criterion is only displayed if you're using Risk. Equally, the option is only available if at least one application has a risk level that could not be calculated.
Risk level (at first decision): The risk level of the application when it was initially approved or rejected. Note that the risk level may have changed since then, for example, an application might have been initially evaluated low risk, but a sanctions match could be later discovered and cause the risk level to be re-evaluated as high risk. To see applications with a risk level that could not be determined, select . Note that this criterion is only displayed if you're using Risk. Equally, the option is only available if at least one application's risk level could not be calculated.
Assignee type: The type of application assignee, this will be a Team, an individual User or unspecified No data.
Assignee user: The name of the user assigned to an application.
Associate role: The company associate's role, for example, beneficial owner or director. Note that applications for associates are created once per role, so if an associate has multiple roles at the same company, they'll have multiple applications. To see profiles that are not company associates, select .
Decided with STP: Whether the application was first decided with STP. To see applications that have not yet been decided, plus any applications that were created before 24 July 2019, select .
Last decision made: User type: The type of user that made the most recent decision on an application. This will be an API user, a smart policy user, or a User (portal). This information can only be retrieved from 24 Jul 2019 onwards.
Last decision made: User name: The name of the user that made the most recent decision on an application. This information can only be retrieved from 24 Jul 2019 onwards.
To learn how to apply or remove a filter, see Using reports.
Data you can export
You can export the following data.
Standard profile data:
Application date: The date and time the application was created. Note that the date and time are determined using UTC.
Application decided with STP: Indicates whether the application was decided with straight through processing. If the application hasn't been approved or rejected yet, this is blank. This data corresponds to the Decided with STP filter.
Application ID: The application's ID in Passfort.
Application first decision date: The date and time that the application was initially approved or rejected. If the application hasn't been approved or rejected yet, this is blank. Note that the date and time are determined using UTC.
Application first decision week: The week, starting on Monday, that the application was initially approved or rejected. If the application hasn't been approved or rejected yet, this is blank.
Application status (current): The status of the application at the time the data was exported. This data corresponds to the Application status (current) filter.
Application status (at first decision): Indicates whether the application was initially approved or rejected. If the application hasn't been approved or rejected yet, this is blank. Note that this may be different from Application status (current). This data corresponds to the Application status (at first decision) filter.
Application week: The week, starting on Monday, that the application was created.
Assignee type: The type of application assignee, this will be a Team, an individual User, or unspecified No data.
Assignee user: The name of the user assigned to an application.
Assignee ID: The user ID or the team ID for the people who have been assigned to work on an application.
Associate role: If the profile is a company associate, this column displays the associate's role. If the profile is a customer or prospect, this is blank. This data corresponds to the Associate role filter.
Associate shareholdings: If the profile is a company associate, this column displays the percentage of shares that the associate holds in the company and any other entities in the ownership structure. The data shows the ID of the entity, followed by a dash, then the share percentage, for example, a2e7545b-cb67-7a0e-7108-a444461891a9-35. If the profile has multiple shareholdings, each one is separated with a semicolon. If the profile is a customer or prospect, this is blank.
Company name: The name of the company.
Company number: The company's registration number.
Company branch address: If the profile is a company, this is the country in which the company branch is located. If the profile does not have a branch address or if the profile is an individual, this is blank.
Company contact address: If the profile is a company, this is the country of the contact address. If the profile does not have a contact address or if the profile is an individual, this is blank.
Company head office address: If the profile is a company, this is the country where the head office is located. If the profile does not have a head office address or if the profile is an individual, this is blank.
Company registered address: If the profile is a company, this is the country where the company is registered. If the profile does not have a registered address or if the profile is an individual, this is blank.
Company trading address: If the profile is a company, this is the country of the trading address. If the profile does not have a trading address or if the profile is an individual, this is blank.
Country of current address: If the profile is an individual, this is the country of residence. If the profile does not have a country of residence or the profile is a company, this is blank. Note that the country is provided as an ISO3 code. This data corresponds to the Country of address filter.
Country of incorporation: If the profile is a company, this is the country in which the company is incorporated. If the profile does not have a country of incorporation or the profile is an individual, this is blank. Note that the country is provided as an ISO3 code. This data corresponds to the Country of incorporation filter.
Country of nationality: If the profile is an individual, this is the country of nationality. If the profile does not have a country of nationality or the profile is a company, this is blank. Note that the country is provided as an ISO3 code. This data corresponds to the Country of nationality filter.
Customer reference: An optional profile field that can be used to add a unique identifier for the profile, for example, the unique identifier from your CRM.
Date of birth: If the profile is an individual, this is the date they were born. If the profile does not have a date of birth or the profile is a company, this field is blank.
Date of incorporation: If the profile is a company, this is the date it was incorporated. If the profile does not have a date of incorporation or if the profile is an individual, this field is blank.
Display name: The name of the profile or associate profile.
Email: If the profile is an individual, this is their email address. If the profile is a company, this is the information provided as an email contact.
Entity type: The type of corporate structure. This will be one of the following: trust, partnership, association, company, sole proprietorship, or other.
First name(s): If the profile is an individual, this is their given name.
Gender: If the profile is an individual, this is their listed gender. If the profile does not have a gender or the profile is a company, this field is blank.
ID type [document name]: The document’s unique identifier in Passfort. Each ID type can be selected for export and is shown in its own column
Individual address (current): If the profile is an individual, this is their current address. If the profile does not have a current address or if the profile is a company, this is blank.
Last decision made: User type: The type of user that made the most recent decision on an application. This will be an API user, a smart policy user, or a User (portal). This information can only be retrieved from 24 Jul 2019 onwards.
Last decision made: User name: The name of the user that made the most recent decision on an application. This information can only be retrieved from 24 Jul 2019 onwards.
Last decision made: User auditee ID: The unique ID of the user that made the most recent decision on an application. This information can only be retrieved from 24 Jul 2019 onwards.
Legal Entity Identifier (LEI): For corporate profiles, this will be a 20-character, alpha-numeric code that provides the unique identification of legal entities participating in financial transactions.
Liability: The type of liability, for example, limited or non-limited liability.
National identity number: If the profile is an individual, this is their country code and national identity number, for example, GBR-012345678. If the profile does not have a national identity number or if the profile is a company, this is blank.
Phone number: If the profile is an individual, this is the phone number that was provided for that individual. If the profile is a company, this is the information provided as a contact number.
Product: The product that the application is for. This data corresponds to the Product filter.
Profile creation date: The date the profile was created. Note that the date and time are determined using UTC.
Profile ID: The profile's ID in Passfort.
Profile type: Indicates whether the profile is an individual or a company and whether the profile is an associate or not. This data corresponds to the Profile type filter.
Risk level (at first decision): Indicates the risk level when the application was first approved or rejected. This data corresponds to the Risk level (at first decision) filter. Note that this column is only displayed if you're using Risk.
Risk level (current): The application's risk level when the data was exported. This data corresponds to the Risk level (current) filter. Note that this column is only displayed if you're using Risk.
Risk score (current): For corporate profiles, this is the current calculated risk score at the time of the report's creation.
Shares: For corporate profiles, this indicates whether the shares are publicly traded or private.
Screening events: Adverse media count (confirmed): The number adverse media matches for the profile have been confirmed.
Screening events: Adverse media count (ignored): The number of adverse media matches for the profile that have been ignored.
Screening events: Adverse media count (potential): The number of adverse media matches for the profile that haven't yet been confirmed or ignored.
Screening events: PEP count (confirmed): The number of PEPs matches for the profile that have been confirmed.
Screening events: PEP count (ignored): The number of PEPs matches for the profile that have been ignored.
Screening events: PEP count (potential): The number of PEPs matches for the profile that haven't yet been confirmed or ignored.
Screening events: Referral count (confirmed): The number of risk matches for the profile that don't fit into the PEPs, sanctions, or adverse media categories, for example, a criminal record, that have been confirmed.
Screening events: Referral count (ignored): The number of risk matches for the profile that don't fit into the PEPs, sanctions, or adverse media categories, for example, a criminal record, that have been ignored.
Screening events: Referral count (potential): The number of risk matches for the profile that don't fit into the PEPs, sanctions, or adverse media categories, for example, a criminal record, that haven't yet been confirmed or ignored.
Screening events: Sanctions count (confirmed): The number of sanctions matches for the profile that have been confirmed.
Screening events: Sanctions count (ignored): The number of sanctions matches for the profile that have been ignored.
Screening events: Sanctions count (potential): The number of sanctions matches for the profile that haven't yet been confirmed or ignored.
Surname: If the profile is an individual, this is their last name.
Tags: The profile's tags. If the profile has multiple tags, each one is separated with a semicolon. If the profile does not have any tags, this is blank.
Ultimate parent display name: If the profile is an associate, this is the name of the product application that their application is contributing to. If the profile is not an associate, this is blank.
Ultimate parent profile ID: If the profile is an associate, this is the ID number of the profile that made the original product application. If the profile is not an associate, this is blank.
Website: This is the company's web address.
Custom fields:
This category contains any custom fields you have.
Decision reasons:
Application decision reasons (at first decision): Indicates the first decision reason that was assigned to the application.
Application decision reasons (current): This shows the most reason decision reasons assigned to an application.
Comments: Free text comments that were added while accepting or rejecting an application.
If a profile is initially created via the API as an INDIVIDUAL_CUSTOMER or COMPANY_CUSTOMER and then manually linked to another profile as an associate, it will retain its INDIVIDUAL_CUSTOMER or COMPANY_CUSTOMER profile type.
In some cases, an associate profile may have more than one parent. If an individual or company is an associate of multiple companies, by default, one application is created for every role the individual or company has. However, it's possible for users to merge the profiles into a single profile as part of the resolve possible duplicates feature. When this happens, there will be one profile with a parent for every company that it's an associate of.
To learn more about screening events, see the PEPs and sanctions screening for individuals and the Sanctions and adverse media screening for companies.
To learn how to export report data, see Using reports.