ACA Offers - Life Events that are not Offers

Hello,

There have been some posts on this; Life Events come from EMSS, with BN10x processing etc. (and if you don't use EMSS for Open Enrollment like us) you don't get them. If you run BN729 and don't have EMSS, Life Event is "BN729".

So, for the initial load I'm wondering if I need Life Event, andor either way need to identify records that are not really "Offers". So, if someone is enrolled and they just change coverage, that's not really an offer, correct? Is anyone else concerned about this, and if so, how are you handling?

I could right a routine using dates of enrollments, HR History etc. to set Life Event "defaults". Or, just load what I have, but it would overstate offers (but as long as there is one Offer, have more than one may not really be an issue for this year).

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

I don't think you need to worry about having "extra" offers. Each time and employee has benefit elections a BN29 record will be created. But, in the end, the data will be converted into the affordability and coverage offer codes.

We use EMSS but we are still on 9.0 so the life events don't populate.

unknown

Margie,

So, I'm assuming this means the BN229 and or BN297 will perform some type of consolidation, or have logic to select the most relevant plan to report on the 1095c? In looking at the targeted December CTP, I guess the BN97, 197, etc. will also play a part in this. For now I guess we just create the data as best we can, then see how these forms and reports set it up and process it for year end.

Thanks.

sriman-shivakoti

Yes.

Copyright © 2025 Infor. All rights reserved.