-
Type:
Enhancement
-
Status: Production Complete
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Export
-
Reported by:White Label
-
Item State:Production Complete - Closed
Hi all - please below and original email attached.
I looked everywhere and can’t locate an email identifying the issue. We first realized this was an issue with UVU this past July. Essentially the issue at hand will impact any employee whose termination date reflects the end of the Policy Year (e.g. December 31st) and either has been defaulted into new coverage and/or actively elected new coverage during their OE.
The system wasn’t sending the employee termination as the OE term as never effective was trumping the employee termination. This impacted roughly 30 employees on UVU and would imagine a fair amount of exposure will be experienced this renewal if not corrected since the bulk of our business renews in January.
Please let us know if this issue was ever resolved. If not, please provide an ETA on release.
The above issue is verified on production. Please check.
Hi all - the above seems to be in regards to an OAD which was another issue that UHC brought up. But the initial issue was in regards to employees terming and the terms not going over as it was seeing their benefits as termed as never effective due to OE elections. Example - I switch from the HMO to the PPO during OE in November with a 1.1.16 effective date. I then term in December but my term doesn't go over as the system sees that my plan was already termed (because I have new plans elected for 1.1.16)
Priya DhamandePlease update.
Hi Jennifer,
Yes, the initial issue mentioned by you related OE is also fixed on production.
Let us know if you have any queries on this.
Hi Jennifer,
This will be deployed on production in Tomorrow's patch.