Troubleshooting

Common issues seen when setting plans up with Payroll Integrations

Onboarding

If using one login for multiple divisions, must create an alternative user for each division; otherwise the system will not know which divisions' payroll data to grab. Instructions on how to do so can be found here.
Deduction codes can be set up by plan sponsors using these instructions. Loan codes are slightly different.
Requires two codes per deduction type. One for flat dollar amounts and one for percentage amounts.
If the sponsor ever has trouble accessing the ADP Marketplace try having them clear their cache and cookies and/or try this direct link to the marketplace. Last resort they can open the link in an incognito window to try as well.

Match

The employer match in ADP Run calculates on the individual code not the total of the two. So if an employee contributes to both Roth and Pretax the match will calculate on both separately. (Say someone is contributing 5% Roth and 5% Pretax and their company match is 100% of the employees first 5%, that employee will get 10% match because it’s separating the two deduction types). Please have the sponsor reach out to ADP about this as the more people that bring this up the more likely they are to change it.
- The only work around that we have found is for the plan sponsor to set up a new deduction named “Employer Match %” and assign that to the employees contributing Roth for the correct percent. They will also need to remove the match calculation from the Roth deduction code itself. It’s not ideal as it requires the PS to go in and change the Roth match amount if that employee changes their Roth deferral but it’s the only workaround we have found thus far.

Loans

Loan goals cannot be entered by our system if their payroll is not in the “open” status. Our system will add the loan repayment amount no matter what. If the loan goal was not entered by us, we will reach out to the contact listed in our system to let them know they need to add the loan goal the next time they run payroll.

Codes

Payroll Register is a good resource for amounts that have come out of employee paychecks but the codes listed are only the flat dollar codes as the percentages have already been converted to dollar amounts at that point. If the plan sponsor doesn’t know what their percentage code is, they should look at an individual employee pay profile in ADP to see what code is assigned to that percentage.
Requires two codes per deduction type. One for flat dollar amounts and one for percentage amounts.
Plan sponsors cannot set up codes themselves, they must reach out to ADP to have them do it.

Pricing

Only payroll platform that our fee is for total number of employees not per division.

Access

Plan sponsors sometimes (only if they have done the regular consent manager and our system is still saying they need provider permissions) need to go into their settings and grant us permission to “ALL” in order for ADP to allow us to edit their employee data. They can do so by following these instructions: Setup > Security > Access Permissions > Manage profiles > Marketplace Data Connector Application Profile (make sure this is active) > "Select all" > Save
If the sponsor ever has trouble accessing the ADP Marketplace try having them clear their cache and cookies and/or try this direct link to the marketplace. Last resort they can open the link in an incognito window to try as well.
ADP offers a feature to clients where they can put all of the employee benefits in the same place for employees to review and change at their convenience. If they have their 401k listed in the ADP Benefits Portal, ADP blocks our system from being able to update employee deferral amounts. When this happens we try to reach out to the plan sponsor within 48 business hours of receiving the error from ADP to ask them to remove the 401k information from the Benefits Portal. ADP should be able to do this for them fairly quickly.

Before Onboarding

iSolved requires the plan to get information on their direct integration before they can request our integration.
They do charge their own fee on top of our monthly fee so make sure the client reaches out to iSolved so they know what the fees will be beforehand.

After Onboarding

Plan sponsor needs to reach out to their iSolved rep and ask to start an “API” integration. It is a separate department than the regular integration department.
Takes 6-8 weeks for set up to be complete.

Set Up and Codes

Multiple divisions at recordkeeper need to be on separate Paychex ID’s
Requires one code per deduction type. Can be marked all in our system.
Plan sponsors cannot set up codes themselves, must reach out to Paychex to have them do it.
If codes are unknown they can use the payroll journal or an employee pay stub to see what codes are being actively used.
Match has to be assigned to employees in order to calculate.
- Suggestion is to have Paychex assign the match to all employees even if they are not currently participating in the 401k. That way when our system adds the deduction to their profile the match starts automatically calculating.
- Also suggest having Paychex select the setting that adds the match to new employees automatically so that the same thing happens.

Pricing

180 integration only
Plan Sponsor must reach out to their Paycom rep and let them know they would like to set up and integration with Payroll Integrations Inc. and that we can be reached at implementation@payrollintegrations.com
Takes 6-8 weeks for set up to be complete.

Pricing

Paylocity charges their own fee for API integrations so make sure the client reaches out to them so they know what they are getting into payment wise.

Set Up

Plan Sponsor must fill out the PADE form which we have linked on our website or they can find in their Paylocity online account and submit online. If they do the one on our website they need to email it to their Paylocity rep and copy implementation@payrollintegrations.com
Takes 2-3 weeks for set up to be complete.

Codes

Codes don’t show up in our system until they have been applied to an employee in Quickbooks. Can be applied to an employee and then removed and will allow us to see them.
Does not calculate matches in deduction codes, must still be done manually via a separate code in Quickbooks and assigned to each individual employee. Our system does not update match amounts in Quickbooks.
Codes cannot be named the same thing as any other code. Solution for this:
- If the codes are actively assigned to an employee, the plan sponsor can open that deduction in the employee's profile and rename it so that it is not exactly the same as the other code that was causing the error.
- If the code is not actively assigned to an employee but still a usable code they can reach out to Quickbooks and have them remove the deductions from their account. (NOTE: QBO does not use the term “code” for these; they just call them deductions and/or contributions).
- If the codes are not assigned to an employee and also not usable we will have to put in a ticket with our PI Developers to hard code the deduction codes to the correct buckets
Requires one code per deduction type. Can be marked all in our system.
Quickbooks match code shows up in our system as a “deduction” , map it over to any bucket and mark it as “forbid updates” then map the “Retirement Match” code in earnings to the correct match bucket.
Plan sponsors can set up their own codes using these instructions.

Set Up

Can only integrate with UKG Pro not UKG Ready
Plan Sponsor must reach out to their UKG rep and let them know they would like to set up and integration with Payroll Integrations Inc. and that we can be reached at implementation@payrollintegrations.com
Takes 6-8 weeks for set up to be complete.