Sage 100

Running into an issue running W2s for a client that has a MI employee. For some reason it thinks there's local taxes and we can't figure out why. Aatrix says it's being triggered by Sage. Sage can't figure out where the problem is. Has anyone with MI employees run into this?

Did you check PR3 for a record?

It must in a record somehow in the PR_40 or PR_41 tables. Have you entered bogus information to get through, to identify the employee?

It looks like someone accidentally entered FE in the Local tax code box in Tax Table Maintenance. Did you check there?

Diana - we don't see anything odd in PR3. Michelle - both Sage and I have combed through PR_40 and PR_41 and don't see anything odd there. Dawn - Local tax reporting isn't even turned on so there's no place to enter a local code. I've entered bogus info and taken it through the grid and don't see anything strange anywhere. No local codes or taxes show up in the grid and nothing prints on any of the W2s. It's the weirdest thing!

Try tuning Local codes on and then check. The PR3 record would be MIFE as part of the key

Tried that. Unfortunately nothing like that in PR3.

I experienced this also. I made all of the local code setups match in this State and Local Tax screen setup window and then everything worked fine. I also connected with Sage and we could not find anything. I informed Alec with Sage of my workaround in hopes it would be published for others to know.

Thank you, Michele!