Minor improvements to the new report design layout

New report design

The PDF reports have been redesigned from scratch, with a new look and layout.

Most information elements are still present in the reports, with exception of the list of signature combinations which previously could take up an unnecessary amount of space in the report. Note that the signature combinations are still available in the JSON API. 

SSN (social security number / fødselsnummer) is no longer a requirement to receive personal information from FREG / Folkeregisteret.

Now an input combination of name and birth date is sufficient for this purpose.

Note that an SSN input might give the search a higher match propability.

Also, note that a valid application for access and delegation is still a requirement in order to receive information from FREG.

More roles are supported in the response. New roles are:

• PARTICIPANT_WITH_SHARED_LIABILITY
• PARTICIPANT_WITH_UNLIMITED_LIABILITY
• MANAGING_OWNER
• OWNERSHIP_COUNTY
• COMPLEMENTARY
• OBSERVER
• JOINT_OWNER

For Norwegian translation see: https://confluence.bankidnorge.no/confluence/pdoidcl/problems-we-solve/aml-and-compliance/aml-services/the-organization-resource/organization-api-implementation-guide/organization-roles

The roles "auditor" and "accountant" are now listed as part of the general roles list. An effect of this is that more than one entity can be listed for any these roles.

The response elements auditor and accountant are marked as DEPRECATED.

Added two numbers to the financial information:

1. sum other financial income
2. sum financial income

Switched to new infrastructure for the entire service. This is a major internal upgrade.

Enhanced information about missing signature rights description in Brreg.

Simplified routine for access to the Norwegian National Registry

Our goal is that the customer should be able to be completely self-served in the process of getting access to information from the Norwegian National Registry.

Previously a specific scope aml_person/NO_NATIONAL_REGISTRY was required. This scope has no longer a valid purpose and is ignored when supplied in the API.

Any customer client is eligible to receive data from the Norwegian National Registry when the following 3 prerequisites are met:

1. Access is granted by Skatteetaten
2. Access is delegated to Vipps AS
3. A request to the API contains expand parameters referring to data elements in the national registry source such as ‘address’

Please encourage the customers to follow our guidelines to fulfill steps 1 and 2: Veiledning for tilgang til folkeregisteret.

Also, make sure to provide the necessary expand parameters in the API requests.

Access rights status information API

A new endpoint has been established in order for the customer to check the status of the access rights to the Norwegian National Registry.

A JSON response containing two boolean flags is returned:

• "granted": true if access has been granted by Skatteetaten (step number 1 above)
• "delegated": true if access has been successfully delegated to Vipps AS (step number 2 above)

We recommend presenting this information in a visual matter in any merchant's customer portal.

The reason to be a beneficial owner is now also returned as part of the JSON API response.

Three new fields are introduced:

1. reason : Enum describing the reason
2. reasonPhrase : Text description of the reason. Same as is presented in the report, in the same language.
3. integratedOwnership: Share of integrated ownership.

In addition, the existing field percentageControl is adjusted to only return a value in cases where the share of control clearly can be described with a number. (Typically this is null when reason is a role or indirect control).

New feature: Reason to be a beneficial owner

The list of beneficial owners in the PDF report now includes a reason column. The reason is a description of why the system has classified the entity as a beneficial owner.

There are six possible reasons:

This information will soon also be available in the JSON response.

Minor layout improvements in the PDF reports.

• improved ordering of subsidiaries
• changed order of some chapter

New feature: The roles of the person

The person service can now return a list of the person's official roles in companies. Note: Include the expand parameter roles in the request to enable this feature.

A number of improvements to the PDF reports, affecting both content and visuals.

• Improved formatting, layout, and other visual improvements, including "smart" page breaks.
• A more detailed description about ownership indicators
• Added a chapter about PEP/Sanctions lists in the optional appendix

Added/changed the "type" property of beneficial owners and shareholders. A beneficial owner can now be recognized as "unidentified" when it is unknown if the entity is a real person or an organization of some sort.

Page breaks are now avoided inside chapters of PDF reports, when possible.

PEP and Sanction results are ordered by match indicator in the PDF reports.

Corrected some typos in the English language organization reports

Switched to T-rank as the source of all ownership information delivered from the organization service:

• Beneficial owners
• Direct owners
• Subsidiaries

This change comes with multiple benefits for the customer:

• Improved data quality
• Calculation of beneficial owners is in accordance with the updated rule set in The Anti-Money Laundering Act.
• All ownership information is now completely in sync with the present ownership indicators calculation

Note that with this release we are also making some changes to the presentation of ownership in the PDF reports:

• The list of owners is limited to the 20 with the biggest ownership.
• All ownership chapters are included even if the listed content is empty.
• Visual improvements

Organization resource: Supplier of official roles has been switched to T-rank

Fixed a bug in handling of some signature rights with specific individuals

Minor bug fixes in the national registry output.

Added support for multiple persons with the same role in the organization response. This upgrade can affect all official roles, but statistics shows that it basically applies to the following set of roles:

• CEO
• Chairman
• Deputy chairman

To benefit from this update, changes must be made to the client's request and response handling as follows:

Request: The expand officialRoles has been deprecated. This must be replaced with the newly introduced expand roles.

XML Response: Furthermore, the element officialRoles in the XML response has been deprecated. A new response element roles has been introduced. This is corresponding to the new expand and contains a different data structure.

PDF Response: The new expand results in a new and different chapter in the PDF reports.

See the API documentation for further details.

Added integration with FREG (The new Folkeregisteret). This new service replaces DSF, and has multiple benefits for the customers of BankID AML, such as a much easier registration process through Altinn. The feature will soon be ready for all customers.

This release includes a major upgrade of an internal framework component.

The first release of the new Organization Async Session API.

In upcoming releases, the asynchronous API will be extended with

• introduction of batch support
• person search support

The asynchronous alternative is the only available option for new integration partners, and existing partners are encouraged to migrate their implementation.

Benefits are improved robustness and quality of delivery, especially under periods of high traffic load.

Have a look at the documentation for more information.

Adjustments to which scenarios the signature rights remark exceptions possible is added to the response.

Changes in the response from the authorizations API of the organization resource: The whole board will now always be included as a valid signature rights option.

The test data has been improved with more representative values for ownership indicators.

Næringskode (NACE) is included in the organization PDF report

Fixed a bug in the report generator sometimes causing the endpoint to return HTTP 404 (Bad Request) before eventually returning HTTP 200 (Ok)

Various improvements to the new "Ownership indicator" pilot feature. (temporarily restricted access)

Fixed a bug causing an invalid return value of housetype: "0"

Added optional parameter showMissingAccessAlerts to the person resource API. The parameter makes it possible to hide the DSF chapter and information about missing access to DSF from the PDF reports.

The property statusCodes in the organization response used to be an array of strings, but is now an array of enums, with the following possible values: BANKRUPT, UNDER_LIQUIDATION, UNDER_COMPULSORY_LIQUIDATION, CLOSED_COMPANY

Improved error handling in cases where one data source is unavailable.

Performance improvements and bug fixes.

The monitor state IMPORT_COMPLETE has been renamed to ACTIVE. See diagram.

Continuous screening: Added an endpoint with the possibility to DELETE an entire monitor

Continuous screening: The GET /monitor endpoint returns more relevant statistics about the persons in the monitor.

• "ordered": Number of people added to the monitor, but not yet confirmed
• "confirmed": Number of people confirmed added to the monitor

The «queryMismatch» response element is now also supported in monitor alerts

Organization: Fixed a bug causing the type of shareholder to be wrong for deleted companies

All signature remarks will now be listed as part of the organization PDF reports

Introducing support for using D-number as search parameter against the person resource

A combination of both the birth date and the SSN (or D-number) may now be included as part of the search parameters against the person resource. This improves support for use cases where the birth date embedded in the SSN is not correct, which is common in D-numbers.

When using this approach:

•  the SSN will be forwarded as parameter against sources where SSN is required (National Registry)

• The explicit birth date will be used against other sources

Introducing real-time status information about the AML services with the new status page: https://bankid-services.statuspage.io/

Organization: variants of signature rights where exactly one board member must sign are now handled as conclusive.

Introducing a timeout of 9 seconds on the person and organization resource endpoints, so all requests can be excepted to give a response within this time limit.

Person report: Sanction results will contain an explicit note when the birth date is different than the search criteria.

In the JSON response, a new data element "queryMismatch" is introduced to inform about the same thing.

Monitor: Introducing a new data element "hitType" on alerts. The enum comes in two variants:

• MATCH: the person has been added to a sanction or PEP list
• REMOVED: the person has been removed from a sanction or PEP list

Person test data: search on date of birth is now possible

Person resource: Removes duplicates in the list of historic addresses.

Person resource: postal code and city were sometimes presented in a mixed and incorrect matter. The values are now cleaned automatically.

Person report: Removed all mentions about fuzziness when the exact mode is enabled.

• Changed the label regarding «search mode».
• In addition, the information about «quality of name match» is now only present the search mode is «fuzzy».

Organization report: Empty chapters headlines are excluded when the specific content is not requested.

Monitor: EuAndUn template is now the default.

Monitor: Introducing «seek pagination» support in the «get alerts API». See API docs.

Monitor: Improved validation and error handling in API.

Monitor: Fixed a bug in the «delete alert» functionality.

Added support for retrievement of the individual's historic names in the person resource. (Note: requires new expand parameter)

Added information elements in organization PDF report:

• status code
• purpose

Introduced new signature rights API element ("authorities") in the organization resource.

• the old "authorizations" node is now deprecated