Skip to main content
Level 5
January 23, 2026
Solved

2025 Quick Employer Forms

  • January 23, 2026
  • 3 replies
  • 10 views

Is anyone experiencing Quick Employer Forms not allowing a business profile address to be updated?

 

Best answer by Kathi_at_Intuit

@sjrcpa Obvs. I replied to it. Still not fixed on Monday.  Its an address field! 


Hello! While a permanent fix is not yet in place, we do have a workaround that has helped some users and may help populate the Business Details page for you as well:

 

Steps:
1. Navigate to the "Update Business" page, click on the "Contact Info" section, and populate all empty fields with temporary values. Save the changes.
2. Re-edit the "Contact Info" section, remove the temporary values added in Step 1, and proceed to make the necessary updates to the business details.

 

Please let us know if this resolves the issue after trying the steps above. We appreciate your patience while we continue working on a full resolution.

3 replies

TKMCPA
Level 2
January 23, 2026

YES. I'm trying to call support and its so frustrating!  I called Pro Series Support....  holding to see if they can change the employer address on the back end...  they can't fix it at the moment ... they are working on it actively, they said try to update the address over the weekend...

Kathi_at_Intuit
Moderator
January 24, 2026

Hi @ClintCPA great to see you in the Community and thanks for posting about Quick Employer Forms not allowing a business profile address to be updated. We appreciate you taking the time to let us know about this. We have checked and see that it has been reported and is being reviewed by Development. 

**Click the 👍Thumbs up icon to say thanks on a post, and click Best Answer to mark the post that answered your question.**
TKMCPA
Level 2
January 24, 2026

I JUST TRIED AT 1:00P EST SATURDAY, STILL NOT WORKING...  

sjrcpa
Level 15
January 24, 2026

@TKMCPA Did you even read Kathi's post?

The more I know the more I don’t know.
Level 2
January 28, 2026

I just tried again today and it has now been corrected!!