GP CHE: RAFam - No Storno In Case Of Changed AHV/AVS-Number For A Child - Legal Requirement
(Doc ID 2486380.1)
Last updated on NOVEMBER 23, 2019
Applies to:
PeopleSoft Enterprise HCM Global Payroll Switzerland - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
On : 9.2 version, Reporting
ACTUAL BEHAVIOR
---------------
Even the AHV/AVS number (social insurance number) is a quiet stable information, it can happen that either due to input errors or due to changes in case of chils adoption the AHV/AVS number of a child changes.
In this case the last RAFam declaration needs to be canceled (storno) and a new declaration with the new AHV/AVS number needs to be initiated.
The "caisse" sends error report due to conflicts within the announcement (2 different activ AHV/AVS numbers for the same child).
Actually only the new information ist created within the RAFam file process but the storno record is missing (DEP record).
The same process works in case of changed AHV/AVS number for the employee (BEN record).
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, only the new information will be created within RAFam file process if you`ll cancel last RAFam declaration and will add a new one.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |