Problem: Users can change their tax id after submitting it to Treasury and accessing their calendar, but we have not developed an intentional experience for if the user deletes or changes their tax id. If the user changes their tax id, they would be interacting with the roadmap in a way that did not intend, swapping between tax calendar for multiple businesses or multiple business locations.
Scope
Determine where/design for any tool tip(s) needed once tax id is locked (after validating their tax id with Treasury)
Determine where/design for any tool tip(s) needed once EIN is locked, which should happen for non-sp/gp after validating their tax id with Treasury - (EIN# are the first 9 digits of a users tax id for non-sp/gp)
Determine where/design for any tool tip(s) needed once business name or dba name is locked, which should happen for non-sp/gp after validating their tax id with Treasury
Problem: Users can change their tax id after submitting it to Treasury and accessing their calendar, but we have not developed an intentional experience for if the user deletes or changes their tax id. If the user changes their tax id, they would be interacting with the roadmap in a way that did not intend, swapping between tax calendar for multiple businesses or multiple business locations.
Scope