Hi Jennifer Leugers,

Currently, there's no validation on ER Coverage, It'll get in even if you give value greater than the max as per customization.
When the another ticket: WT-618 will be completed, Yes the records with ER exceeding the limit in customization will be kicked out.

Hi all - here are UHC comments on the attached document

Sorry for the delay on this! I was able to review the attached and am unsure what we should be commenting on. It looks like from the screen shots the system would continue to operate as it does today with exception that once new functionality is released we will be able to load both EE & ER contributions.

Is the question pertaining to the import allowing greater values than identified in customization chart for EE and/or ER contributions to be successfully imported? If that is the case – then yes our preference would be to have any records error that exceed the threshold identified in the customization chart.

Hi Jennifer Leugers,

In WT- 568 we have allowed to add / update ER coverage using election import. There is no validation on coverage amount as per the age bands. Because of time constraint, we pushed it as it is and created new ticket 618 to provide validations on age bands.
You can use the functionality to add update ER coverage but you have to give exact amount of coverage like we give in other cases.

I will look through the enhancement 618 but I'm still confused on what was deployed to Stage. Per the comments I received from Rakesh, it was tested and verified on our local environment and was supposed to deploy on Monday January 15. So what was deployed?
Rakesh Roy

Jennifer Leugers
Hi Jennifer,

Kindly, Go through the attached Document HSA_Age_Wise_Coverage_Amount
For Enhancement Jira ticket 618.
Let us know if you need more information.

Thanks & Regards,
Rashmita