i) Error: Number of Pay Periods is required
ii) Error: Unable to update timesheet, Uploading timesheets is is progress
iii) Error: Employee has already been paid
iv) Error: Incorrect users being imported
v) Error: No users found when importing
vi) Error: No records were found when importing entitlement balances
vii) Error: Operation timed out
viii) Error: Leave adjustment is more than total leave taken. Please enter manual credit
ix) Error: There are problems with the payroll categories or pay elements in this pay run
x) Error: Employee's start date is after the paid to date
xi) Error: Cost centre is required
xii) Error: Employee does not have hours on timesheet template
xiii) Error: Rate must be blank or zero for Unpaid Leave
xiv) Error creating new payroll: The payroll could not be opened because the pay day da...
xv) Error: Employee does not have the correct pay frequency
xvi) Error: There are invalid employees in this pay run
xvii) Error while communicating with CloudPayroll
xviii) Export employee timesheets - Access is denied, FORBIDDEN
i) Re-exporting payroll
ii) Missing user from the CloudPayroll payroll
iii) Resolve incorrect user mapping
🔍 RELATED ARTICLES
CloudPayroll | Integration Information
CloudPayroll | Initial Setup + Sync
1) Error handling
Some errors may occur during the export process. Known errors and their resolutions are listed below (click on th error to expand).
i) Error: Number of Pay Periods is required
The cause of this error is a payroll code in Easy Employer that is exporting to a pay element in CloudPayroll that is set as a bonus type allowance.
To resolve this issue, change the payroll code in Easy Employer that is exporting to a pay element in CloudPayroll from a bonus type allowance to another allowance type.
ii) Error: Unable to update timesheet, Uploading timesheets is in progress
This error has occurred because a payroll period has not been opened in CloudPayroll. This must be done before exporting data from Easy Employer.
To resolve this issue, open the payroll period in CloudPayroll before attempting to export. Please follow the steps below.
- Open CloudPayroll and log in.
- Open the required organisation/company (only required if group login is used).
- Click payroll > open.
- Click the "Cancel" button in to top right.
- Open the payroll period following CloudPayroll documentation/processes.
Once the payroll period has been opened in CloudPayroll, the payroll report can be exported from Easy Employer.
iii) Error: Employee has already been paid
Please contact CloudPayroll support to resolve this issue. No action can be taken in Easy Employer to fix this error.
iv) Error: Incorrect users being imported
If there are users showing on the "import users review screen" from a different CloudPayroll organisation, it means that the connection was established to the wrong CloudPayroll login. This can happen if the wrong CloudPayroll login was used to authorise the connection. CloudPayroll requires that specific organisation logins are used for the API connection. This is necessary as CloudPayroll does not support group logins authorising the connection for more than one payroll entity.
To resolve this issue, the connection needs to be re-established to ensure the correct login is used.
- Open CloudPayroll and log in with the group login.
- Take note of the organisation ID.
- Multiple browser sessions could be used to do this using incognito browsers or multiple browsers. - Ensure CloudPayroll has been logged out in the browser that will be used to open Easy Employer.
- Open Easy Employer and log in.
- Click Organisation.
- Click Organisation Structure.
- Select the Payroll entity that is to be connected .
- Click Settings.
- Click Disconnect under CloudPayroll.
- Click Connect under CloudPayroll.
- Log in to CloudPayroll and ensure the details a specific for the organisation that is being connected.
- Do not use the CloudPayroll group login details.
Once re-connected, perform a user import and review user on the review screen (display toggles will assist with this process). Ensure that the correct users are included in the import.
v) Error: No users found when importing
This error can be resolved by disconnecting CloudPayroll and then reconnecting again. The steps to do this are below.
- Open Easy Employer.
- Click Organisation.
- Click Organisation structure.
- Click on the Payroll entity.
- Select Settings.
- Click Disconnect.
- Click Connect.
- Follow the prompts to reconnect CloudPayroll.
vi) Error: No records were found when importing entitlement balances
This error can be resolved by disconnecting CloudPayroll and then reconnecting again. The steps to do this are below.
- Open Easy Employer.
- Click Organisation.
- Click Organisation structure.
- Click on the Payroll entity.
- Select Settings.
- Click Disconnect.
- Click Connect.
- Follow the prompts to reconnect CloudPayroll.
vii) Error: Operation timed out
This error can occur when the CloudPayroll API connection has timed out. To ensure that all data was exported successfully it is recommended that the Re-exporting payroll process be followed. Re-open the payrun in CloudPayroll and then re-export the Easy Employer payroll report.
If you have tried again and are still experiencing the issue, please speak to CloudPayroll support.
viii) Error: Leave adjustment is more than total leave taken. Please enter manual credit
This error occurs when an employee has taken more leave hours than they will accrue in CloudPayroll. To resolve this error, follow the steps below:
- Open the CloudPayroll organisation.
- Locate the user linked to the ID shown in the error message (for example, user 17).
- Open the payroll report in Easy Employer.
- Locate the same user from step 2.
- Click the timesheet link under the employee's name.
- Adjust the leave shifts so the employee does not go into negative entitlement value.
- Finalise the payroll report.
- Export for payroll processing.
ix) Error: There are problems with the payroll categories or pay elements in this pay run
This occurs when a user included in the payroll export has not been assigned to an award pay group. All users being exported to CloudPayroll need to be assigned to an award pay group so they are using payroll coding that is supported by CloudPayroll.
To resolve this issue, user/s will either need to be assigned to an award pay group or they will need to be excluded from the payroll export.
x) Error: Employee's start date is after the paid to date
This occurs when there is at least one user in the Easy Employer payroll export that already exist in CloudPayroll, but their start date is set to after the period end date of the payroll export. Multiple users could be the cause of this error.
To resolve this issue, update the employee's start date in CloudPayroll. The date needs to be set to a date before the exporting payroll period's end date.
xi) Error: Cost centre is required
This occurs if there are pay records in Easy Employer with no cost centres assigned and you have not assigned a default cost centre to the user in CloudPayroll.
To resolve this issue you will need to update the configuration in Easy Employer so that the cost centre is generating and/or assign the default cost centre to the user in CloudPayroll. If you are assigning a cost centre to a user in CloudPayroll we would recommend referring to their help documentation if you are unsure of this process and what other affects this could have in CloudPayroll.
xii) Error: Employee does not have hours on timesheet template
The error "Employee does not have hours on timesheet template" is caused by a setting in CloudPayroll.
To resolve it, access your CloudPayroll account and make the following change:
- Once the existing payroll is closed, open the next payroll manually, and make sure the timesheets setting (displayed below the dates; Timesheets - Only copy timesheets with hours) is unticked.
- When this payroll is closed, the setting will be remembered, and you will be able to open future payrolls using the API.
xiii) Error: Rate must be blank or zero for Unpaid Leave
The error "Rate must be blank or zero for Unpaid Leave" can be due to a paid leave type being incorrectly set up as unpaid leave.
To resolve it, crosscheck all leave being taken in the payroll period to the corresponding pay element leave types in CloudPayroll, and ensure that paid leave types are not set as unpaid.
xiv) Error creating new payroll: The payroll could not be opened because the pay day da...
To resolve the "Error creating new payroll: The payroll could not be opened because the pay day da..." you will need to contact CloudPayroll support. Investigation and resolution of this issue will be handled by CloudPayroll.
xv) Error: Employee does not have the correct pay frequency
This error means that an employee in CloudPayroll (with the ID number displayed right before the error message), has the wrong pay frequency and needs to be corrected in CloudPayroll. Please contact CloudPayroll support if you are unsure of what to fix.
xvi) Error: There are invalid employees in this pay run
When this error displays, but the employee(s) shown are present in both CloudPayroll and Easy Employer, the error could be due to a mismatch of the employee's ID between the two systems.
To resolve this issue please perform the following steps:
- Open the payroll report
- Run the export checks
- Note the user ID that the system provided for the users presenting the error
- Open CloudPayroll, and check the employee's ID in CloudPayroll
- Open Easy Employer, and check the integration IDs assigned to the profiles of the user(s) presenting the error
- Remove the ID stored in the wrong profile
- Perform a user import and re-map users to ensure the active profile is mapped
Example
Smith, John
This user's ID in CloudPayroll was changed from 950 to 1500, and when the import of users was done, it was attached to the terminated profile in Easy Employer. To resolve it, import the users again, changing the mapping on the import users review screen to match the active profile instead.
xvii) No payroll found
To resolve the "no payroll found - at leas one payroll should exist" you will need to open the first pay run in CloudPayroll
xviii) Export employee timesheets - Access is denied, FORBIDDEN
To resolve the "no payroll found - at leas one payroll should exist" you will need to open the first pay run in CloudPayroll
To resolve this issue, the connection needs to be re-established:
- Open Easy Employer and log in
- Click organisation
- Click organisation structure
- Click the apyroll entity
- Click settings
- Click disconnect at the bottom
- Click connect and authorise the connection again.
Once done, try again.
Please contact CloudPayroll support if you need further information as to why the original user account used to connect the systems is no longer able to export employee timesheets.
2) Troubleshooting
i) Re-exporting payroll
If a pay run needs to re-exported, the payroll in CloudPayroll needs to be re-opened. Please follow the steps below.
- Open CloudPayroll and log in.
- Open the required organisation/company (only required if group login is used).
- Click payroll > open.
- Click "Change dates".
- Ensure dates are correct and then click "Open a new payroll".
Once the payroll has been opened, the Easy Employer payroll report can be exported again.
ii) Missing user from the CloudPayroll payroll
If users are missing from the CloudPayroll payroll, the first thing to check is if the user has been included in the payroll export in Easy Employer.
- Open the Easy Employer payroll report.
- Find the user.
- Set "Include user in payroll export" to "Yes".
- Repeat steps for other users.
The pay run can be exported once a user has been set to be included in the payroll report. Please follow the instructions outlined above in the "Re-exporting payroll" section.
iii) Resolve incorrect user mapping
If a user has been mapped incorrectly (more than one profile exists for the same user, or the user has the incorrect details), remove the incorrect mapping that has been imported then perform an import to bring in the correct users details:
- Open the users profile that has been incorrectly imported over.
- Click integrations.
- Remove the incorrect integration mapping.
- Perform the user import.