census report

[Tom Poje]

unlike your office, where everything is entered correctly all the time, I had to come up with a way of checking data, which over the years, well, is just not correct.

this census report will print messages under the following conditions: (its getting out of control, but it does catch things!)

(after eligiblity has been run- some message make no sense if you run the report before eligibility is processed)

1.ee term prior year but has comp this year hint:must be rehire or maybe its just the last paycheck that showed up in the new year.

2. ee is Age 70 1/2 (actually age 69 1/2 but what the heck, I like to know a year ahead of time)

3. Bad date of birth (this came about because the import didn't include the century, so the year imported as 2048 rather than 1948)

4. 0 comp but active (ee must have quit but no one told you)

5. ee is inactive or ineligble and no reason provided (probably as a result of takeover and ee wasn't coded properly. I think this could play mind games with the 5500 participant count)

6. ee is inactive but has no term date (don't ask me how I ended up with this, different users with different abilities and multiple over-rides over the years, anything is possible.)

7. number of break in svc if > 3 (just in case he should forfeit at 5 and Ididn't run a forfeiture transaction)

Since I don't use home e-mail address, I put secret messages in there such as "ee paid out in 2009" just cuz.

[Jim Chad]

Tom

This report is AWESOME!!!!!

Thank you very much for sharing it.

[Tom Poje]

dang, I should have traded the report for some cooler weather!

days above 90 degrees:

JACKSONVILLE 46 DAYS (RANK 1ST) JULY 8TH TO AUGUST 22ND

PREVIOUS RECORD OF 44 DAYS FROM JUNE 30TH TO AUGUST 12TH 1992

and more of the same all this week

but I'll settle for the compliment assuming you really find it that useful.

Jim - hope to see you at the ASPPA Conference in October.

[pmacduff]

Be careful what you wish for Tom. I was camping in the Adirondack Mtns. this past weekend and the low on Friday night was 30 degrees...YIKES! Saturday night was a balmy 62, but it rained all night.

And if anyone was wondering - I was in a tent [not a trailer or cabin ]

Who thinks of that in August even up here?!!?!

[Tom Poje]

assuming you folks have a minimum of ability in Crystal, added another data check field, this one for normal retirement age.

I'm not going to attach the revised report just for this one item, hopefully it's easy enough to add at your end.

it's a formula

if {PLANDYN.MINAGENRYRS} >{PLANEE.NRAGE} then "Check retirement date"

in other words, if an employee's normal retirement age is less than the plans retirement age, it implies the date of birth was changed at some moment in time and the normal retirement age needs to be reset.

this happens when a fake date of birth is entered and eligibility has been run. in a later year, a correct date of birth is entered. unless you delete the normal retirement date (or set eligibiility to recalc normal retirement date), the system will never make someon's retirement date worse than what it was.

(Of course, if the plan was amended to a later retirement age this will generate an error message that is bogus.)

[Guest Brenda Schachle]

Discovered another HUGE problem with using Fake Birthdates -- pulling a Catch up Elgible report in Relius the report shows many folks eligible this year who are obviously not eligible -- we had used a 1/1/1960 fake date in 2007 (which set the catch up eligible date to 2010 for THAT YEAR). Corrected date in 2008 and in 2009 the catch up date in census shows the correct date but the Relius crystal report is using the OLD DATE from 2007 that says this guy is eligible 2010! -- It took Relius's help to find it but the fix is going to be alot of work -- unless you have some bright ideas

[Tom Poje]

is that a hint?

never used that report before, my first attempts at generating anything resulted in no names appearing on the report. shows you how much I know about that report. Then I found out additional selections the year showing was 2010 instead of 2009, so once I set that to 2009 it pulled names.

what you could do to the catch up elig report is to add the following formula

if ({RPTEE.METCATCHUPELIGREQDATE}-{RPTEE.BIRTHDATE})/365.25 < 49 then "Check catch up date"

this will take the catch up date and subtract off the birth date and give a warning if it less than 49. I manually changed someone to give a bogus catch up date in an earlier year and it actually produced a warning message. Have to use 49 instead of 50 because the catch up date is set to the beginning of the plan year (when the person is still 49) rather than the actual date someone turns 50. That's about the best I can do off the top of my fool head.