Ansicht
Dokumentation

PAY_DE_DT_200 - Special Features: Germany

CPI1466 during Backup Addresses (Business Address Services)
This documentation is copyright by SAP AG.

In this unit you find out

which wage types you have to transfer

the significance of the time of transfer (cumulated or period-specific)

and which special features of notification procedures must be considered.

CAUTION: You must transfer the payroll account before carrying out the first payroll run.

The master data must have been transferred before the payroll account transfer. For more information, see Data Transfer Workbench: HR. Master Data.

Specify which wage types you would like to transfer.
Sample entries are stored in Customizing for Payroll: International under Payroll Periods (table T558B) and Wage Types (table T558D) under personnel number 00000000. For more information, see the following sections:
Perform the payroll account transfer as described under Payroll Account Transfer

Tables T558B and T558D contain model entries for the payroll account transfer. Depending on the transfer time, (on the 1st January of the year or during the year), there are model entries for periods 12 or 03 of a year.

December 31st of the previous year and March 31st of the current year are entered as dates here. As the dates are insignificant, they are not updated.

The following provides an overview of when to use each sample entry:

1. Wage types for general payroll

1.1. Payroll account transfer when starting in January

The following wage types should be transferred from December of the previous year for the DEUEV and the correct use of the March clause for the calculation of contributions (social insurance contributions for HI, PI, CPS and NI), as well as for the management of semiretirement value credit:

List of Wage Types

1.2. Payroll account transfer when starting during the year

In the case of a mid-year transfer, take note of which areas should be supplied with the payroll account transfer. Transfer all wage types that are necessary for payroll, for DEUEV, correct update of the payroll account, the employment tax statement, the annual employment tax declaration, the statistical evaluations and so on.

For the March clause in the SI contributions, you must distinguish whether you start payroll in February or March or in April.

In the first case, you must transfer the SI income threshold deficits from the previous year and the SI income threshold deficits for the current year.

2 for employment tax certificate

List of Wage Types

2. Wage types for the customer-specific averages calculation

You can either transfer the payroll account in cumulated form or for a specific period.

For customer-specific average calculations, you must transfer the average bases specific to the period for the appropriate number of previous months.

That means that if a 3 month average is used for calculation, you must transfer the average bases for October, November and December of the previous year when starting in January.

The wage types for standard average calculation are:

/204,,Average Bases Amounts
/207,,Average Bases Days
/208,,Average Bases Hours

DEUEV

Cumulated Transfer

In the case of a cumulated transfer, note that you cannot create any correct DEUEV notifications for employees with interruption times in the transfer period. For a partial year live start with cumulated transfer in the legacy system, we therefore recommend that you create a DEUEV deregistration reason 36 (system switch) for all employees. This way, remuneration accrued up until the HR launch are reported by the legacy system. By doing so, you ensure that remuneration accrued up until the HR launch are reported by the legacy system. In the SAP system, a DEUEV registration reason 13 is generated via infotype DEUEV Start (0341). The annual report created by the SAP system comprises the time period starting from the live start.

Period-Specific Transfer

If you execute a period-specific payroll account transfer for the whole year until the live start as a result of the DEUEV annual notification, remember to record additional absences using the time data maintenance. These absence periods must be transferred before the payroll account transfer.
In this case, you can create infotype DEUEV Start (0341) as of January 1 of the year of the live start. A deregistration reason 36 in the legacy system is not required. The annual notification in the SAP system covers the whole year of the live start.

Cluster RD

Wage types from the T558D are entered in table RT. Depending on the coding of the wage types in Processing Class 30, tables CRT and SCRT are filled simultaneously. Tables WPBP, ST, SV, are DUV filled from the master data. This means that the master data for the periods for which you are carrying out a payroll account transfer must be fully maintained.

In order to create DEUEV notifications correctly, it is absolutely necessary that tables SV and DUV are filled from Cluster RD in the month before the date of the DEUEV start (infotype 0341).

Parallel payroll in the first productive month in the legacy system

Remember that there is a calendar month deadline for absences that lead to an interruption in PI (for example, sickness that goes beyond continued pay).

It is possible that the calendar month deadline for an employee has not yet passed in the last payroll month of the legacy system. Instead, this calendar month deadline is not passed until the first productive payroll month in the new system. In this case, create a DEUEV interruption notification with an end date on the last day before the start of the interruption. This end date lies before the date of the DEUEV start, which means that you may not create this interruption notification in the new system.

We therefore recommend that you run payroll for employees for one additional month, that is, the first productive month of the new system, and create a DEUEV notification. The violation of the calendar month deadline should then also be recognized in the legacy system. The missing interruption notifications are created in the legacy system.

Example:

An employee stops receiving continued pay on 12/15/2016. A system switch occurs on January 1, 2004. There is a change of system on 1/1/2017.

The calendar month deadline for the PI interruption is passed in the payroll month of January 2017, meaning that there no interruption notification reason 51 with an end date of 12/14/2016 is created.

The notification cannot be created in the new system since neither the start date of the notification nor the total remuneration is known. The month of January, 2017 have its payroll run in the legacy system so that the violation of the calendar month deadline is recognized.

The same problem occurs with the transfer of legacy data midyear.

Reporting for a professionals' pension organization

When legacy data is transferred for members of a professionals’ pension organization, the start of automatic notification for the PPO contribution survey must be entered in the system.

Start report Start Date of SI Notifications (RPUSVMD0_START) and choose the first date of the month as the start date from which notifications should be created. Choose PPO Contribution Statement to Pension Scheme (BEA) as the notification type.

Paying Office Notification Procedure (ZMV)

When legacy data is transferred from pensioners with statutory pension insurance with regular pension payments, the start of automatic reporting must be specified in the system to allow a start notification to be created and transferred to the health insurance fund. End notifications must have been created in the old system and transferred to the health insurance funds.

Start report Start Date of SI Notifications (RPUSVMD0_START) and choose the first date of the month as the start date from which notifications should be created. Choose Paying Office Data Exchange with Health Insurer (ZAV) as the notification type.

Employment tax statement (ETStmt)

Cumulated Transfer

In the cumulated payroll account transfer from a legacy system, a new starting point is necessary for the employment tax statement (ETStmt). You must, therefore, create the employment tax statement in the legacy system. You may not transfer a notification that can be found in the transfer process (or in the transfer to the tax authorities). You must therefore complete all notification processes in the legacy system before carrying out the general payroll account transfer. A new Statement Period must start in infotype Tax Data Germany (0012) with the live start. Using feature DTXPP Live Start Employment Tax Statement with ELSTER, you can specify the period in which the wage statement should be created with ELSTER wage.

Employment tax notification (ETNotif.)

For the employment tax notification, you have to recreate the notification data for a payroll area when transferring a payroll account. The registration period is usually the payroll period.

Electronic Employment Tax Deduction Features (ELStAM)

In accordance with the technical requirements, you have the following options for transferring a payroll account for ELStAM:

Change of Registration

You can create a change of registration. Note the documentation of report ELSTAM: Create Registrations and Deregistrations (RPCE2VD0_OUT). You may only change the registration within the current month or as of the first day of the following month. You may not change the registration during the period for the creation of the month lists since this affects the assignment of the employees to the change lists provided.

Deregistration and registration

You can deregister the work relationships on the old system and register them on the new system from the following day. For more information, see the Customizing documentation under Specify Actions for Registrations and Deregistrations and the documentation for report RPCE2VD0_OUT. The system creates deregistrations for the following employees:

Employees that are registered under the employer tax number on the date of the registration.

Employees that are stored for the company office for employment tax under Process Data of Reporting Personnel Area.

Note that the system does not deregister any employees who are excluded from the procedure via the Fiscal Data D infotype (0012) on the date of the notification.

ROGBILLS - Synchronize billing plans Addresses (Business Address Services)
This documentation is copyright by SAP AG.

Length: 13071 Date: 20240523 Time: 194511 sap01-206 ( 234 ms )