Enable 7216 Consent Status to Rollfoward Same as All Other Settings

Describe your idea. The more information you provide, the clearer picture of your idea we will have.

Issue:

• Clients have been rolled forward from 2022 to 2023 and the 7216 consent was set to “Yes” in 2022 with expiration date of 12/31/2024
  

• however, after rollover, 7216 consent is set to “No” by default
  

• 7216 information should have been rolled forward / set to “Yes” , as well as unexpired based on settings in 2022
  

• For the interim, we must manually change the setting for the 7216 consent to yes with an expiration date of 12/31/2024 wherever this issue is relevant within 2023

How will this idea help you and potentially others? Understanding how things are done today, where the pain is, and how the idea is beneficial puts us in your shoes.

It will save us from having to update that status manually, which would greatly increase our efficiency.

Who will benefit from this idea? Whether it's specific roles of users, users of a specific product, or certain departments/markets, this helps us know who to talk to when we need more information.

Any firms with 7216 consent as part of their rollforward

How do you envision this idea being implemented at K1x? You're the expert and understanding how you see this working helps kickstart the idea.

Could be implemented several different ways - possibly as a checkbox users could select for "maintain PY 7216 consent status in rollover," or it could just default to doing that automatically and the smaller subset of users who don't want the 7216 to rollover can undo it.

Alternatively, the system could pop up a question that asks the user if they want to maintain PY 7216 status during the rollover process and users could then say yes or no as appropriate.