How To Fix HRPAYDEE2703 - 552020402 refDatumAG is not after the stored refDatumAG

HRPAYDEE2703 - Overview

• Message type: E = Error

• Message class: HRPAYDEE2 - Message Class ELStAM Procedure

• Message number: 703

• Message text: 552020402 refDatumAG is not after the stored refDatumAG

What causes this issue?

The entire procedure note from the clearing house is as follows:
<LS>552020402 Ref. date ER is not after the stored ref. date ER of the
work relationship for which the registration is to be changed. [Ref.
date ER = $datum]</>
This is a rejection at employee level.
The clearing house returns this error message if the date of the change
of registration is not after the registration date.
This situation can occur only if <LS>Force Change of Registration</> was
selected.

System Response

The clearing house rejected the change of registration for the employee.
The master data for the <LS>Fiscal Data D</> infotype (0012) was not
updated.

How to fix this error?

Change the registration at a later key date.

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 HRPAYDEE2703 - 552020402 refDatumAG is not after the stored refDatumAG ?

  The SAP error message HRPAYDEE2703 with the description "552020402 refDatumAG is not after the stored refDatumAG" typically occurs in the context of payroll processing in the SAP Human Capital Management (HCM) module. This error indicates that there is an issue with the reference date (refDatumAG) used in the payroll calculation, specifically that the date being processed is not after a previously stored reference date.
  
  Cause:
  
  Incorrect Reference Date: The reference date being used for the payroll run is earlier than or the same as a previously stored reference date. This can happen if there are overlapping payroll periods or if the payroll data has been incorrectly entered or processed.
  Data Consistency Issues: There may be inconsistencies in the payroll data, such as incorrect entries in the infotypes or payroll results that do not align with the expected sequence of dates.
  
  Configuration Issues: The payroll configuration may not be set up correctly, leading to issues