Entry Dates

[pmacduff]

Relius 7.1 - I have a plan with no eligibility requirements. I have "0" coded in the Plan Entry Requirements Specs for hours, no years or months of service, no age, etc. I do, however, have 1000 hours in the "vesting" hours fields. Under entry dates, I have "date of event" coded. I ran elig as of 01/01/02 and 06/30/02 (semi-annual val dates). I have an employee hired 01/02/02 and after I run elig and transactions, it says that she is ineligible. When I check the employee census data, it says "fails service requirement". Am I crazy? I thought I saw prior threads saying that I shouldn't have to enter elig transactions for each entry date and, in this case, I couldn't feasibly enter 183 entry dates anyway! Any guidance is appreciated.

[Archimage]

I think you need to run an eligibility transaction each time a new participant enters the Plan. Relius needs the eligibility transaction ran in order to tell that this participant is now eligible. Just run an eligibility transaction every time you post a contribution.

[pmacduff]

I did that. I have two eligibilities posted, 01/01/02 and 06/30/02 and the contribution for the 6 months posted as a 06/30/02 contribution transaction. It is not working this way.

[Archimage]

The 1/1 eligibility wouldn't pick him up but the 6/30 one should. Are your contribution transaction effetive dates earlier than 6/30? If so you might need to rerun eligibility effective the day before you do the contribution. If that is not it I recommend calling Relius support.

[rcline46]

Also remember to let the elig transaction calculate prior entry dates.

[Guest DottleC2]

You definitely don't have to enter elig transactions for each entry date, there's no reason to 'enter 183 entry' dates either. An odd exception like an employee who works part time in a 'Year of Service' plan may need an override, but as long as an eligibility transaction is run some time _Coincident or After_ a participant enters the plan, the system will correctly evaluate entry. This doesn't appear to be the root of the problem though, since you have immediate entry.

I tried to duplicate your problem with the Jan 2 hire, and could only come up with a few suggestions on what to look for; also, I would make sure that there isn't a field that is unintentionaly set, like 'date elig met' for your Jan 2 person, then check the following:

Do a quick review of sourse level elig specs using: Account Definitions / Source Tab . Then check these against plan level specs (most of the time there is no need for source level specs but the boxes need to be unticked)

Do a quick review of the service fields at different points after running eligibility :Personal Data /Dates/Age/Service.

Make sure the 'month wait' is set to 0 to reflect immediate entry.

Having always run 'estimate entry' transactions, I'm not sure what would happen if this were not set - or if this is your situation - but if you're not using 'estimate entry', then you may want to check with Relius support to see if there's some logic underneath the hood that is causing an exception.

Make sure the 'Entry dates' are set correctly on both the plan level eligibility and the source eligibiliity specs, if you are using source level eligibility. (this is more for continuity, but it's interesting that source level specs will supersede plan level eligib. specs.)

In trying to force a sample plan to reflect the problem that you described, I could duplicate the situation by setting an incorrect plan specification on the plan level screen of '12 month wait' or using an incorrect entry - but I couldn't duplicate the problem using intentionally incorrect _source_ level changes. Then of course things like ADP testing would be affected by an errant Deferral level eligibility spec, but this doesn't appear to be your situation either.

You may want to check that the participant is not participating in another plan - and check the dates are okay on the first Plan Specs screen. I'd be interested to hear how it works out.

[pmacduff]

I am embarassed to say, (although it was only 4 days ago), I cannot remember how I eventually fixed this issue! The plan is working fine now. There are no source eligibility issues, as the only contributions are deferral $. I think for some reason I may have had "1" hour coded in the elig requirements in specs, and since I only entered payroll for 06/30, Relius thought she didn't have any hours yet. Thank you for your time and input, it is always most helpful.

[Guest DottleC2]

That's interesting, I have the same explanation when asked how I came up with vesting svc overrides, etc... "well, I don't really recall how I got there, but having arrived in the right place.."

Since there is no separate 'vesting service' override field, and the process of overriding is simply a matter of changing the service fields, the only trail of what has been overridden is an internal report showing eligibility, accrual, and vesting. Edited fields are circled on the report to indicate overrides.

For backup I store the overrides in an Excel file and import, but this file is essentially ignored when the report is reviewed.

Bill