I have created a Claim (Reimbursement) type benefit. I've added a custom field Receipt Date. However, there is a loophole to this and I'll need to add some sort of validation. The issue is that the employee could have a past dated Receipt and claim for it once they are eligible.
For example:
- Receipt: 01 Dec 2024 -> Employee is not yet eligible for claims yet as of this date
- Claim Date: 01 Jan 2025 -> Employee becomes eligible (based on eligibility rule) and claims the 01 Dec 2024 receipt on this date. This scenario is not allowed and a validation check must be in place.
I have to add a validation that the receipt must be on or after the employee's actual eligibility date.
What i did so far:
- Added a custom field in Job Info to auto-populate via a rule, with the event date that the employee becomes eligible. The eligibility rule only relies on job info data for eligibility criteria.
- This works for new hires/rehires.
- For existing employees, this field must be auto-populated. However, there can be multiple records already for the employee.
- Ex. Employee has 5 job info records. After the hire record (2nd record), the employee becomes eligible. So the 2nd record must be auto-populated first before the succeeding records. To refresh the rules, it must be from oldest to newest record. We cannot update the 5th record first as it will take that date instead of the 2nd record's date.
Is there another way to add a validation to this scenario?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.