Open Enrollment - BN32 Stop Dates

Hi,

I'd like to make sure I understand. Are you saying that when a BN32 record is created, Lawson automatically puts an end date on the record? Regardless of whether it's during open enrollment or whether it's entered mid-year by somone on your benefits staff?

Or is it something unique to elections made by employees durign the open enrollment period?

It will place an end date on the existing or previous record when adding a new BN32 record.

When you pend, it does put one on the current record. I don't believe that prevents employees from making changes during the open enrollment period. In fact, it makes it nicer because they can then select the benefits they want to change without having to go through every benefit again.

There is not a way to prevent the stop date being added to BN32.1 when you are allowing employee to go thru Annual Enrollment (or at least one that I am aware of and I have been doing annual enrollment for some time now).

The system automatically enters an end date... I have opened a ticket about this in the past because it creates major data issues when bn32 shows that a benefit was terminated and there is no new benefit in the table yet. (I tried to explain to infor that companies would be using the benefit table for file feeds to vendors but the told me they were not looking to change this so you will need to work around it. )

The end dates will update if the employee makes changes to their elections during the OE period. I usually handle the file issue by suspending files during OE, and submitting any life status changes to the vendor(s) manually. I think it depends on your size and if that's a workable solution for you.

Ditto for everything others said in previous comments. Regarding the vendor file issue... We send only full files vs changes only and we inform our vendors that end dates will be coming on the files during open enrollment period.  They set their system to ignore future end dates and we send them true benefit terms separately.