Service break for the Incomes Register's stakeholder testing environment on 18 December, 4 pm – 11 December, 8 am.

Do you report data to the Incomes Register via API? Please note the codeset changes taking place in April. Retrieve your processing feedback smoothly, even on congested days

3/6/2024

New codes will be added to the codeset “Applicable collective agreement (CBACode)” in the Incomes Register. At the same time, the validity of the corresponding old codes will end.

The codesets will be used in the technical interface of the Incomes Register. Please check with your software supplier how the codesets are updated in the software you are using.

Use the new codes for reports whose payment date is on or after 1 April 2024. If you use codes in the report that are no longer valid, your report will be rejected.

The following new codes will take effect at the beginning of April:

  • 220 Collective Agreement for Supervisors in Hotel, Restaurant and Leisure industry
  • 221 Collective Agreement for Supervisors in Trade Logistics
  • 222 Collective Agreement for Retail Supervisors
  • 223 Collective Agreement for Employment Industry

The validity period of the codes of the following collective agreements will end at the end of March:

  • 36 Collective Agreement for the Personnel Services Sector
  • 88 Collective Agreement for Tourism, Restaurant and Recreational Services - Supervisors
  • 170 Collective Agreement for Warehouse and Transport Supervisors
  • 185 Collective Agreement for Supervisors in the Retail Trade

You can continue to use expired codes when correcting or submitting reports whose payment date is on or before 31 March 2024.

The changes have already been updated in the technical documentation of the Incomes Register.

Read more about codesets on the Documentation page

Retrieve processing feedback smoothly even on congested days ‒ avoid records containing more than 3 000 reports

When submitting data via the Incomes Register’s API, we recommend that you send records containing a maximum of 3,000 reports to the Incomes Register.

If your record contains more than 3,000 reports, you should split it into several records. This will speed up the processing of your records in the Incomes Register.

Wait five minutes before requesting processing feedback

Always ensure the successful receipt of your record by requesting processing feedback. We recommend that you allow at least five minutes between sending your record and requesting processing feedback.

On the busiest days, we receive over a million reports a day to the Incomes Register. Therefore, the processing of a record can sometimes take several minutes.

If you have not received processing feedback within five minutes, we recommend that you wait at least another five minutes before requesting it again. This will avoid unnecessary requests.

Verify the status of the record through processing feedback

Do not submit the record again until you have successfully received processing feedback. This will avoid a situation where you accidentally resend reports already stored in the Incomes Register.

If you do not receive the processing feedback within two hours even if you waited the recommended five minutes between requests or if you received the message-level (MessageErrors) error code “GEN0010 Unexpected technical error”, please contact us by filling in the observation report.

The error code “GEN0010 Unexpected technical error” is occasionally displayed in the acknowledgement of receipt (AckFromIR) in the deferred Web Service interface. In such situations, we recommend that you wait the recommended five minutes and request processing feedback for the record as normal. In most cases, the error code received in the acknowledgement of receipt is unnecessary and you will receive confirmation of the actual status of the record in the processing feedback.

Please see the documentation on data delivery and read more about the recommendations

Page last updated 3/6/2024