Pension data declaration

The pension declaration is a complete digital delivery of pension data that requires very little user intervention. Pension data declarations include an overview which shows you the information to be delivered.

In Profit, you can generate and send the pension declaration for Syntrus Achmea, AZL, BeFrank and TKP (Retail).

Description

The pension declaration is based on the wage declaration message from the tax authority, supplemented with a number of additional fields for the pension data.

For the 'Syntrus’ and ‘AZL’ pension data declaration, you use the Profit CLA. In the Profit CLA, wage summaries are available for the pension declaration. You can also use Basic CAO for the BeFrank pension data declaration.

If you process salaries, Profit automatically generates a new declaration line for the relevant period. We recommend you check the wage declaration after processing the salaries. In that case, any errors detected by the check can be resolved before the salary processing is approved.

Process

The pension declaration process is integrated with the wage declaration process. When you check the wage declaration, you automatically check the pension declaration as well. The same applies to preparing and sending. Profit tracks a separate status for the two declarations.

The process looks as follows:

Corrections

The period in which Profit includes the corrections depends on the declaration term. When the declaration term elapses depends on the last possible delivery date. You can find this date in the view in the Declaration cockpit. This process is identical to the RAE entries in the wage declaration.

  • Declaration term has not yet elapsed

    If the declaration term has not elapsed yet and the declaration contains errors, send the corrected declaration as new complete declaration. You process and approve the correction in a correction period. This correction period generates generates the new declaration.

  • Declaration term has elapsed

    If the declaration term has elapsed and the declaration contains errors, send the corrected declaration as a correction declaration. You process and approve the correction in a correction period. This correction period generates generates the new declaration.

Contract end date without an Employment end date

If a contract end date has been specified for an employee but not an employment end date, there will not be a date for the end of the income relationship in the declaration for the relevant period. That means the tax authority and the pension fund are not informed about the employment end. In the next period you no longer process the wage of this employee, meaning that Profit does no longer include the employee in the declaration. The pension fund (Syntrus) detects the missing employee and returns error code S0065, with the following message:

In this time frame there was no declaration for this income relationship, but the income relationship has not been ended.

Profit cannot manage this situation, because the salary processing determines the input for the declaration. As the employee is no longer present in the wage calculation, the employee is not part of the selection for the declaration. If you postpone the final settlement by one period most of the time, this situation could arise. Normally you would complete the Employment end date field in the subsequent period. This creates an RAE entry in the salary processing, which in turn creates a correction to the declaration. That means that you still report the employee's end of employment.

If you do not do this, the pension fund will warn you about this. You then have to complete the Employment end date field with retroactive effect.

For this, you can use the Employee/Check for employment end date without contract end date(Profit) default alert.

Preparation

  • Configure a pension declaration

Procedure

Also see