Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
Identify the failure before applying a fix
A payroll, rostering, HR, or time-tracking app does not send employee or timesheet data to Xero, or sends incomplete or duplicated values.
Record the complete message, affected organisation or company, user, date range, and last successful action. A precise symptom is more useful than trying several broad repairs at once.
Workflow map
Reconcile one employee before replaying a pay period
The safest test is the smallest record set that proves identity, mapping, connection ownership, and duplicate protection before payroll is finalised.
- 1
Identity
Match employee IDs, status, email, and pay-calendar assignment across both systems.
Evidence: One unambiguous active employee on both sides.
- 2
Mapping
Compare earnings, deductions, leave, tracking, accounts, units, and rounding.
Evidence: Every code used by the failed record has an approved destination.
- 3
Connection
Confirm the connection owner still has access and preserve the failed queue.
Evidence: A current authorised owner and exportable error evidence.
- 4
Replay
Sync one employee or period and compare hours and payroll inputs before finalising.
Evidence: One draft result, no duplicate employee, timesheet, or pay item.
Checks before changing data
- Confirm the Xero edition and region; payroll features and partner apps vary by country.
- Identify whether one employee, one pay period, or every record fails.
- Do not finalise or file the pay run while source hours and totals are unresolved.
Resolution path
- Compare employee identity fields. Match employee IDs, names, email addresses, employment status, and pay-calendar assignments across both systems.
- Look for duplicate employee records.
- Confirm terminated or archived employees are handled intentionally.
- Review payroll mappings. Check earnings, deductions, leave types, tracking categories, and account mappings used by the integration.
- Map every active code used in the failed period.
- Confirm units and rounding rules.
- Verify the connection owner and app status. Review the app in Xero connected apps and the provider’s admin console.
- Make sure the connecting user still has access.
- Export the failed queue before reconnecting.
- Replay one employee or period. After correcting the cause, sync the smallest possible test and compare source hours, gross pay inputs, deductions, and tracking.
- Check for an existing draft before replay.
- Reconcile totals before finalising the pay run.
Verify the result
A disappearing error is not enough. Confirm the accounting and workflow outcome:
- The test employee or period syncs once.
- Source hours and mapped payroll inputs agree.
- No duplicate employee, timesheet, or draft pay item is created.
What to avoid
- Finalising payroll before source totals reconcile.
- Running a full historical resync as the first test.
- Assuming a Xero connection problem when only the third-party app is failing.
When to involve product support, IT, or your accountant
Stop making changes and escalate when any of these conditions applies:
- A filed or finalised pay run is affected.
- Employee identity cannot be reconciled without merging records.
- The app provider controls the mapping or replay queue.
Bring the exact error, screenshots, affected record IDs, timestamps, product version or region, and a description of every change already attempted. That evidence shortens the support path and reduces repeated or conflicting fixes.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.