How To Fix HRPAYNLLA447 - Leper &1 Was Terminated in Period &2, but Ext. Data in Period &3

HRPAYNLLA447 - Overview

• Message type: E = Error

• Message class: HRPAYNLLA - Notifications for Wage Return NL

• Message number: 447

• Message text: Leper &1 Was Terminated in Period &2, but Ext. Data in Period &3

What causes this issue?

You have used the <ZK>Wage Return: Last Possible Tax Return Period</>
(NLLA4) feature to indicate that no current wage tax returns can be
created for legal person &1. Nevertheless, employer results exist in
period &3, whereas period &2 is the last period for which the legal
person in question can submit a wage tax return. This could lead to
errors in the wage tax return, if the termination of a legal person is
cancelled retroactively.

System Response

If you wish to retroactively terminate a legal person, be aware of the
fact that if you have already reported results for the wage tax return
for the legal person in question, you can still retroactively terminate
this legal person. This is subject to the condition that as from the
termination via the NLLA4 feature no payroll results are created for the
closed periods and no employer data is created via the <ZK>Wage Return:
Update Collective Employer Data (</>RPUTAEN0_UPDATE).
For example: You have created a wage tax return for legal person 1
until October 2007. You then retroactively terminate legal person 1 in
wage tax return period 11, making August 2006 the last wage tax return
period. This means that as from wage tax return period 11 (in-period)
payroll results for legal person 1 can only exist for period 8 or
previous periods. If payroll results for later periods are entered, an
error message is returned. In case of a retroactive termination, IRs
that were reported in earlier closed periods are not reversed and you
must contact the tax authorities.
It is possible to retroactively cancel the retroactive termination of a
legal person. Note that after the cancellation, the IR's status at the
time of the cancellation applies.

How to fix this error?

Check whether the <ZK>Wage Return: Last Possible Tax Return Period</> (
<DS:HRDS.DSYSLO_ECI549B_NLLA4AAAAAAAAAAAAAAA___0VVV>NLLA4</>) has been
set up correctly. Use the <ZK>Wage Return: Display Collective Employer
Data </> (<DS:RE.RPUTAEN0_DISPLAY>RPUTAEN0_DISPLAY</>) report to also
check if you have entered the employer data in the correct period. If
necessary you can use the <ZK>Wage Return: Change Collective Employer
Data</> (<DS:RE.RPUTAEN0_DISPLAY>RPUTAEN0_UPDATE</>) report to carry
through changes.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYNLLA447 - Leper &1 Was Terminated in Period &2, but Ext. Data in Period &3 ?

  The SAP error message HRPAYNLLA447 indicates a discrepancy in the employee's termination status and the external data (such as payroll or benefits data) for the specified periods. Specifically, it means that the employee was terminated in a certain period, but there is still external data (like payroll results) that exists for a different period, which can lead to inconsistencies in the payroll processing.
  
  Cause:
  
  Termination Date Mismatch: The employee was terminated in a specific period, but there are records or data entries that still reference the employee in a subsequent period.
  Incorrect Data Entry: There may be incorrect or incomplete data entries in the payroll or HR modules that do not align with the termination date.
  External Data Issues: External systems or integrations may still be sending data for the terminated employee, leading to conflicts.
  
  
  Solution:
  
  Review Termination Date: Check the employee's termination date in the HR master data. Ensure that it is correctly set and