Error
| Type | Feature | Error Description |
|---|---|---|
| Import conflict | Pay Schedule | Pay schedule does not exist in QuickBooks Online |
Explanation
The error occurs if the pay schedule does not exist within your QuickBooks Online platform because of this, Employment Hero automatically disables the pay schedule, causing this issue.
Solution
Adding the pay schedule to your QuickBooks Online platform and then re-syncing the two platforms will resolve this issue.
- Log in to QuickBooks Online platform.
- Click the Employee menu.
- Click the Payroll Settings submenu.
- Click the Pay Schedules button.
- Click the Add button.
- Complete the following fields:
- Name.
- Frequency.
- Weekly.
- Fortnightly.
- Monthly.
Important
Selecting the monthly frequency option will display the Monthly Payment Mode option. This is used to calculate an average number of hours per month for employees with advanced standard work hours setup, as opposed to paying for the specific hours per month based on the number of days in the month.
- Included employees.
- Pay slip message.
- Pay run warnings.
- PAYG payments.
- Account Name.
- BSB.
- Account Number.
- Reference.
- Click the Save button.
- Log in to your Employment Hero platform.
- Click the Settings menu.
- Click the Pay Schedules submenu.
- Click the Update From Payroll button.
Helpful Hint
The Pay Schedule page will now show a grey Updated button. It means Employment Hero has successfully imported your pay schedules from your QuickBooks Online platform.
Author recommended
So you have now resolved your QuickBooks error and you are now wondering, what next can I do. There are two recommendations I would make on this front and they are:
- Leave balance visibility | HR Guide This guide walks you through how to customise your employee's leave balance visibility in your Employment Hero platform.
- Common QuickBooks Import Conflicts This section contains a range of error resolution articles that cover common import conflicts our clients run into when syncing their QuickBooks data.
Comments
Article is closed for comments.