The AML resource server is running as a separate service and has its own release cycle different from the rest of the OIDC platform.

Changes in V75

Release date: 2022-09-12

No	Changes
1	High risk industry sectors are now highlighted in the reports
2	Improved error messages for the Norwegian Population Registry

Changes in V74

Release date: 2022-08-10

No	Changes
1	Preparations to switch the supplier-based integration against The Norwegian National Registry from Vipps AS to BankID BankAxept AS. More information and updated delegate routines will be provided for merchants and customers soon.
2	The report language parameter now supports additional values `nb` and `nn`. Valid options are now: `no\|nb\|nn\|en\|NO\|EN\|NB\|NN` (two letters ISO 639-1)
3	Added mapping of previously unknown organization types
4	Added test persons from Sweden, Denmark and Finland

Changes in V73

Release date: 2022-07-05

No	Changes
1	Added support for BankID authentication input to the asynchronous person search API
2	The organization search against Sweden, Denmark, and Finland is available by default to any customer, and manual access request for this purpose is no longer necessary.
3	Added a danish test company to the Current environment
4	Bug fixes in the handling of webhooks in the asynchronous APIs

Changes in V72

Release date: 2022-06-22

No	Changes
1	The Beneficial Owners report service will now deliver a positive response with a PDF report even when the customer has no access to the Norwegian National Registry. The information elements citizenship and birthplace will be missing in this case.
2	Removed information about fuzzy mode from the Person PDF report.
3	Changed to the improved name searching algorithm against Norwegian National Registry also to requests with the usage of the date of birth instead of ssn. This name matching can return successful results even for inputs consisting of initials or name parts not present in the registration.
4	Fixed a bug causing duplicate error messages about roles in the Person PDF report.

Changes in V71

Release date: 2022-06-08

No	Changes
1	Added support for organization search against Denmark. See further documentation about: Data sources Information elements supported Organization Async Session API implementation guide
2	Added information about missing response elements in the PDF reports when an error occurs. This optional error message can be present in any chapter.
3	Changed the validation pattern for Swedish SSN in the person search. The standard ÅÅMMDD-XXXX format is now supported. Note that the special variant ÅÅMMDD+XXXX is currently not supported. Also added validation of SSN (NO, SE, DK, FI) in the monitor API.

Changes

Added support for organization search against Denmark.

See further documentation about:

Added information about missing response elements in the PDF reports when an error occurs. This optional error message can be present in any chapter.

Changed the validation pattern for Swedish SSN in the person search. The standard ÅÅMMDD-XXXX format is now supported. Note that the special variant ÅÅMMDD+XXXX is currently not supported.

Also added validation of SSN (NO, SE, DK, FI) in the monitor API.

Changes in V70

Release date: 2022-05-20

No	Changes
1	Improved the name matching algorithm in searches against the Norwegian population registry. The name matching can now return successful results even for inputs consisting of initials or name parts not present in the registration.

Changes in V69

Release date: 2022-05-12

No Changes

No	Changes
1	Fuzzy mode is now enabled as default on all PEP and sanction searches. Removed the parameter `matchMode=<exact/fuzzy>` Added new optional parameter `nameMatchThreshold=<number from 0.0 to 1.0>` (default 0.85) See updated description about how to interpret the person search results Note that this change of request parameters is backward compatible, and a change on a client is not mandatory.
2	Removed the optional appendix (documentation) from PDF reports. Equivalent documentation is available online. The corresponding request parameter `addPdfAppendix` is no longer available.

Fuzzy mode is now enabled as default on all PEP and sanction searches.

Removed the parameter matchMode=<exact/fuzzy>
Added new optional parameter nameMatchThreshold=<number from 0.0 to 1.0> (default 0.85)
See updated description about how to interpret the person search results
Note that this change of request parameters is backward compatible, and a change on a client is not mandatory.

Removed the optional appendix (documentation) from PDF reports. Equivalent documentation is available online. The corresponding request parameter addPdfAppendix is no longer available.

Changes in V68

Release date: 2022-05-09

No	Changes
1	Added support for organization search against Sweden and Finland. See further documentation about: Data sources Information elements supported Organization Async Session API implementation guide
2	The first release of a new Person Async Session API. This will be the preferred integration alternative going forward.
3	Added a new address information element to roles and owners in the Norwegian organization search.
4	Structural and visual improvements to the PDF reports.
5	Added testdata companies 845936862 (DA Norway) 556628-1234 (Sweden) 2292844-0 (Finland)
6	Added some roles to the 613838465 testdata company.

Changes in V67

Release date: 2022-03-23

No	Changes
1	Minor improvements to the new report design layout
2	Added the role PROPRIETOR to test company 8741477372
3	Other bugfixes and internal improvements

Changes in V66

Release date: 2022-03-16

No	Changes
1	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.
2	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.
3	Corrected the Norwegian translation of some company roles.

Changes

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.

Corrected the Norwegian translation of some company roles.

Changes in V65

Release date: 2022-02-01

No Changes

No	Changes
1	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
2	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.
3	Added two numbers to the financial information: sum other financial income sum financial income

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:

sum other financial income
sum financial income

Changes in V64

Release date: 2022-01-26

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

Changes in V63

Release date: 2021-11-10

No	Changes
1	Enhanced information about missing signature rights description in Brreg.
2	Fixed a bug causing bad behavior in the signature rights options algorithm.
3	Fixed a bug where the reason to be a beneficial owner was incorrect in some rare special case.
4	Fixed a bug causing missing query mismatch statements in the continuous screening service.

Changes in V62

Release date: 2021-10-18

No Changes

No	Changes
1	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: Access is granted by Skatteetaten Access is delegated to Vipps AS 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.
2	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.
3	Improvements to information about ownership in company test data.

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:

Access is granted by Skatteetaten
Access is delegated to Vipps AS
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.

3 Improvements to information about ownership in company test data.

Changes in V61

Release date: 2021-10-04

No	Changes
1	The reason to be a beneficial owner is now also returned as part of the JSON API response. Three new fields are introduced: `reason` : Enum describing the reason `reasonPhrase` : Text description of the reason. Same as is presented in the report, in the same language. `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).
2	Improved support for AML search after persons with nationality other than Norwegian. the input parameter `ssn` now supports national ID number for the countries Norway, Sweeden, Denmark, and Finland. if a Swedish nationality is given, a Sanction/PEP result with match quality of 500 (full ssn match) is possible. The input parameter `countryOfSsn` is deprecated and replaced with the more syntactically correct parameter `country. B`oth parameters are supported and have the same effect. Note that if an `ssn` is not present, an input consisting of only the `name` and `dateOfBirth` parameters are sufficient. This can lead to PEP/Sanction match results for any international person. Information from national registers, such as an address, is still only available for Norwegian citizens. Similar support will be added for other Nordic countries in a future release.
3	Beneficial owners are described with an address when the information is available. (both PDF and JSON)
4	Unidentified beneficial owners are described with a country when that information is available. (both PDF and JSON)

Changes in V60

Release date: 2021-09-16

No Changes

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:

Reason	Description
Direct ownership	The person has direct ownership of a certain percentage above 25%
Indirect control or ownership	The person has control of the company through indirect ownership or control through multiple steps. For each step control of at least 25% is required. Note that ownership of some specific share class may lead to greater control than the actual ownership percentage, and this aspect is taken into account in the calculation.
Direct role in the foundation	The organization of interest is a foundation. Major roles in such foundations are classified as beneficial owners.
Indirect control through role in some foundation	The person has a major role in some foundation which in the next step has great ownership (25% each step) of the organization of interest.
Voting rights	The person has direct ownership of some specific share class giving voting rights greater than 25%.
Both voting rights and direct ownership	The person has direct ownership of some specific share class giving voting rights greater than 25%. The direct ownership percentage in itself is also large enough to classify the person as a beneficial owner.

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

New feature: Continuous screening of organizations BETA

At this stage only alerts about sanctions are supported. In future releases, this feature will be extended to support alerts about other changes in the organizations.

Note that this feature is in a beta stage, and is currently only available to some customers.

3 The three-year financial history numbers are now presented side-by-side on a single page.

4 Continuous screening of persons: Added support to present a queryMismatch remark in monitored person alerts with a match indicator of 155

5 Links to information about PEP/Sanction results in the PDF reports are no longer clickable. A restriction in the PDF/A standard (PDF for archiving purposes) caused the hyperlinks to be corrupt in some cases. Instead, the links are now presented as pure text.

Minor layout improvements in the PDF reports.

improved ordering of subsidiaries
changed order of some chapter

7 Removed the time-of-day component in the lastChanged response element.

Changes in V59

Release date: 2021-08-23

No Changes

No	Changes
1	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.
2	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
3	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.

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.

Changes in V58

Release date: 2021-07-01

No	Changes
1	Page breaks are now avoided inside chapters of PDF reports, when possible.
2	PEP and Sanction results are ordered by match indicator in the PDF reports.
3	Fixed a bug where signature rights were missing from a company of type sole proprietorship.
4	Fixed a bug where the webhook URL of a continuous screening monitor was not returned from the information endpoint.
5	Minor visual improvements in testdata reports.

Changes in V57

Release date: 2021-06-23

No	Changes
1	Corrected some typos in the English language organization reports
2	Support for the upcoming OIDC domain change. As described here: https://bankid-services.statuspage.io/incidents/ps6xdc0pccs5
3	Fixed a bug where clients in the Current environment did not have access to test data from FREG (Folkeregisteret).

Changes in V56

Release date: 2021-05-26

No	Changes
1	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

Changes

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

Changes in V55

Release date: 2021-05-04

No	Changes
1	Organization resource: Supplier of official roles has been switched to T-rank
2	Some minor text improvements in the PDF reports
3	Fixed a bug in handling of some signature rights with specific individuals
4	Fixed a bug causing duplicate "roles" chapters in the reports
5	Fixed a bug in the continuous screening service where the description of a 175 match indicator was wrong in some cases

Changes in V54

Release date: 2021-04-20

No	Changes
1	Minor bug fixes in the national registry output.

Changes in V53

Release date: 2021-04-14

No Changes

No	Changes
1	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.
2	Improvements in error handling.

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.

2 Improvements in error handling.

Changes in V52

Release date: 2021-04-07

No	Changes
1	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.
2	Text improvements in the PDF reports regarding the sources used in the sanction and PEP searches.
3	Better validation of the dateOfBirth parameter.

Changes in V51

Release date: 2021-03-16

No	Changes
1	Continuous screening: Fixed a bug causing duplicate webhook signals
2	Continuous screening: Adjustments to what time of day alerts are being delivered. Previously alerts used to be ready in the evening at 20:00, but now they also can be delivered earlier during the day when available.
3	Continuous screening: Improvements to the monitor statistics. Deletion of alerts will give a more immediate effect to the number of "active alerts".

Changes in V50

Release date: 2021-03-04

No	Changes
1	A better description of the sanction- and PEP lists being used in PDF reports
2	Support for the OFAC sanction list in organization search. Use the new scope `aml_organization/OFAC` (restricted access)
3	Improved performance while generating PDF reports
4	Fixed a bug in the continuous screening alert delivery service

Changes in V49

Release date: 2021-02-22

No	Changes
1	This release includes a major upgrade of an internal framework component.
2	The ownership indicators feature no longer require specific access (the scope `aml_organization/ownership.indicators` is no longer required)
3	A bug causing bad scrolling behavior in the API documentation when using the Chrome browser has been fixed.
4	Fixed a bug in the monitor service causing incorrect matchindicator

Changes in V48

Release date: 2021-01-27

No	Changes
1	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.
2	Improved description of some ownership indicators in the PDF reports
3	Minor improvements in the API documentation

Changes

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.

Improved description of some ownership indicators in the PDF reports

Minor improvements in the API documentation

Changes in V47

Release date: 2021-01-11

No	Changes
1	Fixed a bug in the monitor statistics calculation causing an HTTP 500 error from the GET monitor endpoint in some cases.

Changes in V46

Release date: 2021-01-06

No	Changes
1	The first release of the new Organization Session API BETA
2	The GET report endpoint now returns an HTTP 500 error immediately for failing reports, preventing clients from polling the endpoint for a long time in such cases.
3	Minor bugfixes

Changes in V45

Release date: 2020-12-09

No	Changes
1	Information about BankID identification has been enhanced with more information about the related BankID certificate. In the PDF report the following elements are presented: Timestamp (time of authentication) Certificate serial number (serial number of the BankID certificate) Organization (Issuer of the BankID certificate) Organizational Unit (Organization number of the issuer) The following elements are added to the JSON response: originator (complete originator String, similar to the one delivered as part of the ID Token) serialNumber (BankID serial number, similar to bankid_altsub in the ID Token) Example originator string CN=BankID Bankenes ID-tjeneste Bank CA 2, OU=988477052, O=Bankenes ID-tjeneste AS,* C=NO;OrginatorId=9775;OriginatorName=Gjensidige Bank RA 1
2	Fixed a bug in continuous screening which caused an error when adding persons.
3	The lifespan of PDF reports has been increased to 30 minutes (from the previous 10 min). This is the deadline for when all reports must be downloaded before they are deleted from the server.
4	Changes to the terms used in PDF reports regarding the organization types General Partnership and General Partnership with shared liability. "Aksjonærer" is renamed to "Deltakere" (English: Partners). Also, the percentage of ownership is removed from General Partnership.
5	Adjustments to which scenarios the signature rights remark exceptions possible is added to the response.

Changes in V44

Release date: 2020-11-23

No	Changes
1	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.
2	The test data has been improved with more representative values for ownership indicators.
3	The organization type is written in Norwegian in the PDF reports when Norwegian language has been selected.
4	Continuous screening: nationality parameter is only mandatory in conjunction with the SSN parameter.

Changes in V43

Release date: 2020-11-05

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

Changes in V42

Release date: 2020-11-03

No	Changes
1	Fixed a bug in the report generator sometimes causing the endpoint to return HTTP 404 (Bad Request) before eventually returning HTTP 200 (Ok)
2	Correcting a rounding error in the ownership indicators

Changes in V41

Release date: 2020-10-28

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

Changes in V40

Release date: 2020-10-21

No	Changes
1	Fixed a bug causing an invalid return value of `housetype: "0"`
2	Fixed a bug causing an error when searching after some specific organizations
3	Minor visual improvements in PDF reports

Changes in V39

Release date: 2020-10-07

No	Changes
1	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.
2	Minor text change in signature rights remark.
3	Stability improvements.

Changes in V38

Release date: 2020-09-22

No	Changes
1	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
2	Introducing a warning message in the beneficial owner's section of the PDF report when the beneficial owner's can not be detected because of the ownership structure.

Changes in V37

Release date: 2020-09-08

No	Changes
1	Stability improvements in the PDF report generator. Introducing a fallback mechanism in the integration with a timestamp server.
2	Additions have been made to the list of situations causing a SERVER_ERROR to be reported as part of the "`response_warnings`" response element.
3	Corrections in the API documentation examples - all role names are CAPITAL LETTERS.

Changes in V36

Release date: 2020-08-24

No Changes

No	Changes
1	The new parameter `caseReference` is required when requesting information from the National Registry. Read more about this parameter in the Person resource. Note that for access to information from the National Registry the customer must first apply for access and sign an agreement with Skatteetaten. Vipps will help the customer through this process. After the application is approved, the client will be granted access to the scope `aml_person/NO_NATIONAL_REGISTRY`
2	A deleted company will now be returned with the statusCode "`Avviklet`"

The new parameter caseReference is required when requesting information from the National Registry. Read more about this parameter in the Person resource.

Note that for access to information from the National Registry the customer must first apply for access and sign an agreement with Skatteetaten. Vipps will help the customer through this process.

After the application is approved, the client will be granted access to the scope aml_person/NO_NATIONAL_REGISTRY

2 A deleted company will now be returned with the statusCode "Avviklet"

Changes in V35

Release date: 2020-08-10

No	Changes
1	Improved error handling in cases where one data source is unavailable.
2	Introducing the new response element "`response_warnings`" in the Organization resource. This is a list of warnings about specific response elements that could not be delivered for some reason. At the moment, the only notable reason is that a necessary data source is unavailable. Example: "response_warnings":[ { "property":"keyInformation", "type":"SERVER_ERROR", "message":"National Registry service is unavailable" }]
3	Sanction results with a match indicator of either 125 or 155 might now be delivered with a note about the birthdate when this is different than the search criteria.
4	The "expands" parameter now affects the content of PDF reports in the test environments.
5	Fixed a bug where a search on a deleted company resulted in an error response.
6	Fixed a bug causing historic name to be excluded from PDF reports.
7	Improved reliability of the reports download service.
8	Performance improvements and bug fixes.

Changes in V34

Release date: 2020-06-09

No	Changes
1	The monitor state IMPORT_COMPLETE has been renamed to ACTIVE. See diagram.
2	The monitor states UNKNOWN and DEACTIVATED were unused and has been removed
3	Corrected the error message when missing parameter 'countryOfSsn'
4	Fixed a bug causing some role persons without birthdate to be missing from the report

Changes in V33

Release date: 2020-05-26

No	Changes
1	Continuous screening: Added an endpoint with the possibility to DELETE an entire monitor
2	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
3	Organization: The signature description "Styrets medlemmer hver for seg" is handled as CONCLUSIVE.
4	The quality of the test data is improved. This includes a change of SSN for most of the persons to a new valid one. Note: The old test data with existing SSN will still work for a time period.

Changes in V32

Release date: 2020-05-04

No	Changes
1	The «queryMismatch» response element is now also supported in monitor alerts
2	Organization: Fixed a bug causing the type of shareholder to be wrong for deleted companies
3	All signature remarks will now be listed as part of the organization PDF reports

Changes in V31

Release date: 2020-04-16

No	Changes
1	Introducing support for using D-number as search parameter against the person resource
2	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
3	A couple of textual improvements in the PDF reports
4	Some bugfixes in the expression of organization signature rights

Changes in V30

Release date: 2020-03-24

Changes

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.

Citizenship has been added as a new return value on sanction results

Signature rights now may come with a list of remarks (both in JSON and PDF report).

There are three categories of remark:

EXCEPTIONS_POSSIBLE	There are known exceptions to the rule. A common example is that there exist deputy board members that could sign on behalf of the main board members.
SUPPLEMENTED	The signature rights text is overridden by the system. A common example is if the registered text in Brreg is empty.
INCOMPLETE_DATA	The signature rights text could normally be handled as CONCLUSIVE, but the roles described are not documented. The service will instead return IN_CONCLUSIVE as a fallback.

This feature is new and slightly experimental. We might need to make changes in this area after customer feedback.

Fixed a bug in the validation of organization number ending with '0'.

Changes in V29

Release date: 2020-03-10

No	Changes
1	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.
2	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.
3	Invalid organization number is handled as HTTP 400 bad request
4	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
5	Person test data: search on date of birth is now possible
6	Organization test data: purpose is returned

Changes in V28

Release date: 2020-03-03

No	Changes
1	Person resource: Removes duplicates in the list of historic addresses.
2	Person resource: postal code and city were sometimes presented in a mixed and incorrect matter. The values are now cleaned automatically.
3	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».
4	Organization report: Empty chapters headlines are excluded when the specific content is not requested.
5	Organization report: Fixed a bug causing a chapter to be missing in some rare cases.
6	Monitor: EuAndUn template is now the default.
7	Monitor: Introducing «seek pagination» support in the «get alerts API». See API docs.
8	Monitor: Improved validation and error handling in API.
9	Monitor: Fixed a bug in the «delete alert» functionality.

Changes in V27

Release date: 2020-01-30

No	Changes
1	Signature rights referring to an undefined role are now marked as inconclusive
2	Cases of missing signature rights in Brreg is more precisely described as "Signaturrett er ikke oppgitt i Brreg"
3	The name of the role "Styreformann" is changed to "Styrets leder" in PDF reports

Changes in V26

Release date: 2020-01-20

No	Changes
1	All PDF reports have been redesigned with a new look
2	Added "instant alert" feature in continuous screening test simulator
3	The old person API is marked as deprecated
4	Fixed a bug leading to missing addresses from Posten in some rare cases

Changes in V25

Release date: 2020-01-07

No	Changes
1	Fixed a bug leading to missing financial data returned from the organization resources in some cases.
2	Improved performance in the organization api.
3	Continuous screening: The "import all customers" step is no longer a requirement for initialization of a new monitor
4	Minor design improvements in the organization pdf report

Changes in V24

Release date: 2019-12-16

No	Changes
1	Added support for retrievement of the individual's historic names in the person resource. (Note: requires new expand parameter)
2	Minor design improvements in the organization pdf report
3	The pdf report from the new Person API now contains a note about BankID authentication
4	More signature rights are handled as "conclusive"

Changes in V23

Release date: 2019-12-04

No	Changes
1	More signature rights are handled as conclusive in the organization resource.
2	Presents a physical description of sanctioned persons in the PDF report.
3	Improved organization test data.

Changes in V22

Release date: 2019-11-19

Changes

Organization test data in the "Current" environment. Production data is no longer available.

Added information elements in organization PDF report:

status code
purpose

Changes in V21

Release date: 2019-11-11

No	Changes
1	Added support for person search against The Office of Foreign Assets Control (OFAC) sanction list.
2	Introduced new signature rights API element ("authorities") in the organization resource. the old "authorizations" node is now deprecated
3	Introduced the "identity" API element in the person resource.
4	New hard-coded test data in the test environment
5	Added support for more official roles in the organization resource.
6	A collection of small improvements in the organization resource.

Changes in V20

Release date: 2019-10-16

No	Changes
1	Test simulator support in the continuous screening service
2	Support for name and birthdate request parameter in the continuous screening service
3	Support for DUNS number request parameter in the organization resource
4	Improvements in the person resource PDF reports

Changes in V19

Release date: 2019-09-23

No	Changes
1	Person API v2 (pilot)

Changes in V17

Release date: 2019-08-13

No	Changes
1	Continuous screening (pilot)

Changes in V10-V11

A collection of PDF report improvements and other minor improvements.

Changes in V9

No	Changes in 2019-03-28 V9 (AML)
1	Added support for an accounting firm as part of organization resource
2	Bugfixes

Changes in V8

No	Changes in 2019-03-27 V8 (AML)
1	Bugfix in monitor

Changes in V7

No	Changes in 2019-03-25 V7 (AML)
1	Added match indicator description in Sanction / Pep PDF report
2	Added SSN (when used as a search parameter) in Sanction / Pep PDF report
3	Added dummy PDF report in organization resource for testing purposes

Changes in V6

Changes in 2019-03-12 V6 (AML)

New Organization resource with support for

key information
address
sanction search result
official roles in the company
ownership (shareholders etc)
signature rights
key financial figures
auditor and accountant company
credit score (limited access)

The previous scope aml_person/noauthentication has been removed from the scopes list, and it is no longer a requirement to request the "no authentication" variant of the service. Scope aml_person/basic is now the only requirement.

Browser not supported