Describe your idea. The more information you provide, the clearer picture of your idea we will have. |
On the account management side there is a field for engagement code. At EY the engagement code changes from year to year. The account set up information does not. We use what is called a Client Code. Please rename this field in EYTSEO to Client Code. |
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. |
Engagement code does not help any EY user in EYTSEO. In fact the engagement code changes from year to year. The account set up information should be the same and not change. We are respectfully asking this field be renamed to Client Code for EYTSEO. The Client Code allows us to find it at a glance. The client code is invaluable to EY users in many other EY applications to finding other important client information. The client code does not change from year to year at EY. |
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. |
We are only asking this be changed in EYTSEO please. Not globally for all of Ctrac. |
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. |
Please update the field name from Engagement Code to Client Code. |