I am doing paycode integrations with Integration Manager and keep getting errors on the integration when it comes to the Suta state. It is not for every record and it seems random. Has anyone else seen this?
*This post is locked for comments
Yes, the codes are all correct and like the original post from 2012, some records were importing and others weren't. There did not seem to be a pattern to it. I finally resolved the problem by creating a new integration with a single source file which defaulted all fields in the employee master mapping and had no other records imported except pay codes. That took care of it.
Are you using lower case codes in your source data? The field is case sensitive and they should be uppercase.
Here it is 5 years later and I'm experiencing the same problem. Did anyone ever figure this one out?
We have the same problem, but with the state, not the SUTA state. Did you ever find a solution?
I have verified all of this info. Some of the records work and others don't.
Some quick places to check:
1. Validate that employees have SUTA state defined on their card
2. Validate that employee pay code records have a SUTA state. This will populate if you defined the State on the employee card.
2. In your integration, check to see if you are importing the 'Value' for the SUTA state field or if you are using default? If default, it goes to the employee pay code record first, then employee card. If you are a 'One State Only' payroll site, you could put in a constant for that State (for example MI for Michigan). That would elimate the missing of SUTA state records.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (