News for software developers - 3/2025

New version of Ilmoitin.fi has released on 3 June 2025

• CRS/DAC2 / New check routines:
  • If self-certification has been received (Self-Certification == CRS972), then the date of birth is required (The check routine concerns Individual account holders).
  • If the account is new (AccountTreatment == CRS982), information on self-certification is mandatory (Self-Certification CRS971 or CRS972).
  • If an undocumented account has been reported (UndocumentedAccount == true), then you cannot report that self-certification has been received (Self-Certification == CRS972).
• DPI (DAC7)
  • New check routines:
    • Ilmoitin will check that ReportableSeller/Entity is not 0000000-0 or ReportableSeller/Individual is not 000000-0000.
    • Ilmoitin will check that the ReportableSeller structure has been reported if MessageTypeIndic is DPI401 or DPI402.
  • New notification if data is reported in the Taxes element:
    • You are reporting taxes that the platform operator has collected from the seller in the Taxes element. Make sure you do not include value added tax, for example, in taxes.
• KELA / eSARA
  • Kela will stop accepting eSARA files sent through the Ilmoitin.fi service on 30 September 2025.
  • Kela recommends that all employers who use eSARA files to apply for Kela benefits should start using other e-services instead as soon as possible.
    • The Incomes Register is recommended for large employers,
    • while smaller employers can use either the Incomes Register or the daily allowance and reimbursement service for employers.
  • Read more about the change.

News about Vero API

• Please note that starting from May 12, 2025, all REST API calls to the Vero API test environment (apitest.vero.fi) will require the following common headers: User-Agent, Content-Type, and Accept.
• In the production environment (api.vero.fi), these headers will become mandatory on September 15, 2025. This change enhances security and compatibility. Please ensure that your software includes these headers in all API calls. The production environment's header requirements can be updated in the software immediately.
• It is recommended to include the following details in the User-Agent header:
  • Application name: Helps identify which application is making the request.
  • Version: Indicates the version of the application, allowing the server to distinguish between different versions.
  • Operating system: Provides information about the OS the application is running on.
  • Example: User-Agent: MyApp/1.0 (Windows NT 10.0; Win64; x64)
• Read more: Technical Guidelines for Vero API Interfaces - vero.fi

Tax Administration Certificate Service 

• Tax Administration’s certificate service – a description of the PKI system and APIs the document includes technical clarifications related to the RSA key length.
• Quick guide to certificate creation - includes technical clarifications related to the RSA key length.
• The example of certificate renewal has been separated from the document  into a dedicated subpage on the Certificate service’s webpage
• Using the certificate service – organisations and natural persons from other countries
• Obtaining production certificates for foreigners who do not have a Finnish identification token

How to contact us or make enquiries

• Intended for those who work with IT development at commercial software vendor companies
• Designed to give guidance and support to IT development
• Not at all for error processing
• Instead, if you detect an error or become aware of a technical problem, always use the observation form to inform the Incomes Register Unit of it.