How To Fix HRPAYDEE2421 - ID no. from ELStAM procedure and infotype &1 are different

HRPAYDEE2421 - Overview

• Message type: E = Error

• Message class: HRPAYDEE2 - Message Class ELStAM Procedure

• Message number: 421

• Message text: ID no. from ELStAM procedure and infotype &1 are different

What causes this issue?

The ID number from the ELStAM notification &V2& with the valid-from date
&V1& differs from the ID number &V3& defined in the infotype <LS>Fiscal
Data D</> (0012).

System Response

The ELStAM notification does not update the infotype data.

How to fix this error?

Check why the two ID numbers are different. If the ID number &V2& in the
ELStAM notification is correct, transfer it to the infotype and use the
report <LS>ELStAM Procedure: Update Master Data Using ELStAM Procedure
</> (RPCE2VD0_IN) to import the ELStAM notification again.

Procedure for System Administrators

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 HRPAYDEE2421 - ID no. from ELStAM procedure and infotype &1 are different ?

  The SAP error message HRPAYDEE2421 typically occurs in the context of payroll processing when there is a mismatch between the data in the ELStAM (Elektronische Lohnsteuerabzugsmerkmale) procedure and the data in the specified infotype (e.g., Infotype 0002 for personal data, Infotype 0003 for payroll status, etc.). This error indicates that the employee's tax data as per the ELStAM procedure does not align with the information stored in the specified infotype.
  
  Cause:
  
  Data Mismatch: The most common cause is that the employee's tax data in the ELStAM system does not match the data in the relevant infotype in SAP. This could be due to changes in the employee's tax status, marital status, or other relevant information that has not been updated in SAP.
  Incorrect Configuration: There may be issues with the configuration of the ELStAM procedure or the infotype settings.
  Timing Issues: If the ELStAM data was updated after the payroll run was initiated, the