Changes to improve data quality in April 2027

On 1 April 2027, we will publish a number of changes to data reporting APIs for the Positive credit register to improve the quality of the reported data and prevent incorrect reporting. We are communicating about the upcoming changes this early to enable the lenders using the APIs to start preparing for them in good time. 

The following changes will be made to the APIs in April 2027:

• No dates preceding the loan contract date can be entered in the loan data 
• Error code used for the End-of-Loan API will be clarified
• Several reports related to the same loan cannot be report in the same batch

We will publish technical documentation of the changes on the page Upcoming changes on 2 December 2026. The changes can be tested in the ExtTest2 environment from February 2027. In the following, we will describe each change in more detail. 

Dates preceding the loan contract date cannot be reported

After 1 April 2027, dates relating to loans that occur before the dates of conclusion of the loan contracts may no longer be reported in the APIs. This new processing rule will be added to all APIs in the register. Therefore, in the future, for example, the payment date of a payment transaction, the start and end date of a deferment period or the last due date of a payment plan cannot be earlier than the contract date indicated for the loan. For example, if the loan contract date were reported as 2 April 2027, the API will not accept 1 March 2027 as the last due date of the payment plan. The purpose of the change is to prevent incorrect data from ending up in the register. 

We clarify the error code in the End-of-Loan API

No reports can be submitted in the End-of-Loan API for a loan previously reported as terminated if the report type is “NewReport” (newReport). The current implementation sends the error code E14 in the processing response if the lender tries to give a report in the End-of-Loan API using the wrong report type. This error code notifies the user about the incorrect content of the end-of-loan data but does not direct them to use the correct report type. On 1 April 2027, we will correct the error code used in these situations to E12, which will directly inform the user that the error was made in selecting the report type. The purpose of the change is to clarify the error code and thus assist the API users in selecting the correct corrective action. 

Several reports related to the same loan cannot be in the same batch

From the beginning of April 2027, the data batches submitted to the register’s APIs can only contain one report per loan number. We will add a technical processing rule to the API, which rejects reports related to the same loan within a single batch. Even until now, we have been instructing lenders not to submit more than one report related to the same loan per batch, but this has not been technically prevented. 

The register does not process reports within a batch in the same order in which they were submitted. So, if there are several reports related to the same loan in the same batch, it is coincidental which of the reports is the last to be processed, i.e. which report's data will remain in force in the register. Concurrent reports related to the same loan have also occasionally caused the data processing at the registry’s API to get stuck.

We recommend that you continue to include as many reports as possible in each batch you send. The maximum size of a batch is 10,000 reports. The change only applies to including several reports related to the same loan in the same batch. 

Example: Lender A reports data related to loan 12345678 to the register. The lender tries to include two payment transactions related to loan 12345678 in the same batch on 2 April 2027. The payment transaction API rejects both reports. When the lender requests processing response for the batch, they are informed that the reports were rejected with error code E00: Only one report on the same loan can be submitted in the same batch.