Service break in the Incomes Register on Saturday, 22 June from 6 pm to 8 pm. See the service break schedule

News on accuracy of information for data users

On this page, we have compiled information on the changes.


Responsibility of the Incomes Register for the accuracy of data will extend in 2027

A new legislative amendment entering into force next year will grant data subjects – i.e. private individuals – new rights.

Following the amendment, a private individual may ask the Incomes Register to investigate any errors or omissions in their data. They will also have the right to request the correction of data, the restriction of processing, or both. The requests do not suspend or prevent the disclosure of data to data users.

The payer is still obliged to report and correct the data. If the payer does not correct or report the data despite requests to do so, the Incomes Register Unit may impose a conditional fine to ensure compliance with the reporting requirement.

Data users will only be informed of the request if a private individual requests a restriction on the processing of data and if the request concerns data that the data subject is entitled to receive from the Incomes Register.


Ensure that your organisation can receive and react to triggers and disputation flags

The organisations using the Incomes Register data must themselves determine how they react to trigger and disputation entries in the reports.

Entries can only be included in earnings payment reports or benefits payment reports. Because an employer’s separate reports are not specific to an income earner, requests concerning them cannot be lodged.

How is the request visible to the organisations utilising the data?

After a private individual sends us a request to restrict the processing of their data and the request has been saved in the Incomes Register, we will also inform data users of the request.

In such cases, a trigger and disputation flags will be generated for the earnings payment report or benefits payment report being disputed. The organisations using the Incomes Register data must themselves determine how they react to triggers and disputation flags in the reports.

A trigger in the report indicates that the income earner has flagged a piece of information in the report as incorrect or missing. The information in question, such as personal data, reported income or employment relationship information, will be marked with a disputation flag.

Data users can only see those triggers and disputation flags linked to data that the data users are authorised to receive from the Incomes Register.

The triggers are automatically shared with data users in the API and the e-service.

  • If the data user retrieves the data from the Incomes Register via the API, the organisation can determine whether the details are always included in extractions or extracted separately based on triggers.
  • If the data user retrieves data from the Incomes Register’s e-service, triggers and disputation flags will be visible in each report.

When a payer has corrected a disputed piece of information, the Incomes Register Unit makes a decision on the correction request. If the correction is sufficient, the disputation flag is removed entirely.

In certain situations – for example, if the payer cannot be reached at all – the Incomes Register Unit can also correct data. In such cases, the data are permanently flagged as having been corrected by the Incomes Register.

If a private individual's request to restrict the processing of data concerns reports that are missing entirely from the Incomes Register, the request is distributed in the Missing earnings payment report or Missing benefit payment report data in the API. Data can also be retrieved from the e-service.


More on this topic

The controller’s responsibility will be extended in 2027: Private individuals will have the right to request the correction of their personal data

Read the technical instructions: the responsibility of the Incomes Register for the accuracy of data will be extended in 2027


Page last updated 6/17/2026