Preventing duplicate contacts (dependents, beneficiaries)
Summary:
Preventing duplicate contacts (dependents, beneficiaries)
Content (required):
Hi, we see multiple issues with the duplicated contacts (dependents have been entered more then once with the same SSN) or the Employee chooses effective start date in the future then does not see this contact in Oracle as of today and reenters the same contact again.
It causes a lot of manual correction effort as we have the back out the life event and then delete the contact.
An way we can prevent the dups?
- Identify it by the SSN, like it is implemented for workers.
- Freeze the effective start date as an enterprise hire date preventing entering the contact as a future start date
0