The Deputy Xero integration connects a Deputy location to your Xero organisation so approved Deputy timesheets export into Xero Payroll, ready for a pay run. It also imports or syncs employee details between the two and can sync leave balances. You connect it from Deputy's Integrations page, and it only works cleanly when names, emails, pay items and the pay period match exactly in both systems.

Most of the pain people search about comes from that last part. The connection itself takes a few clicks. The fiddly bit is getting Xero set up the way Deputy expects, every pay run, for every employee.

The setup in one go: make Deputy the source of truth for pay rates and timesheets, and Xero the source of truth for super, deductions and the final pay run. Create the draft pay run in Xero first, with the same dates you'll pick in Deputy. Export as Timesheets, check them in Xero, then approve. Most failed exports trace back to a name, an email, a pay item or a date that doesn't match.

What does the Deputy Xero integration actually do?

Deputy's help centre lists three main things the connection is for. You can import your employees from Xero into Deputy when you first set up, and keep their details in sync after that. You can export Deputy timesheets to process payroll in Xero. And you can sync employee leave balances between the two.

Xero's own app store listing for Deputy, checked on 19 November 2026, shows it listed since May 2016. It describes employees as shared both ways, timesheets as shared from Deputy to Xero, and pay items as shared from Xero to Deputy.

What it doesn't do matters just as much. Deputy's setup guide says plainly that superannuation is processed through your payroll provider: "Deputy does not set up pay items with super. This is all handled within Xero." Deputy also doesn't create the pay run for you. You make the draft pay run in Xero, and Deputy fills it.

Deputy has a second, smaller Xero link that a lot of people miss. If your staff bill their time to customers, Deputy can export approved timesheets as invoices into Xero using its Xero Time Billing option, with a markup percentage on the employee's hourly rate. That's useful for cleaning, security and labour hire businesses, though most hospitality and retail employers only need the payroll side.

What syncs between Deputy and Xero?

This table is built from Deputy's help centre and Xero's app listing. It's the quickest way to see which system owns what before you switch anything on.

DataDirectionHow it runsWorth knowing
EmployeesXero to Deputy at setup, then either wayBulk import at setup, then optional add-onsWith Auto sync employees on, Deputy becomes the source of truth and overwrites existing details in Xero. You also can't edit Payroll IDs in Deputy.
New startersXero to DeputyOptional add-on that invites the new employee to DeputyAdd-ons run once a day at midnight in your Deputy account's time zone, unless you run them by hand.
TimesheetsDeputy to XeroManual export from Deputy's Export Timesheets pageGoes into a draft pay run you've already created in Xero. Dates must match exactly.
Pay ratesDeputy to Xero (with the pay rule library)Created in Xero on first exportDon't rename these earnings rates in Xero afterwards, or later exports can't match them and may create duplicates.
Leave balancesBetween the twoOptional add-onIf you've synced Xero pay rates into Deputy, Deputy assumes Xero manages leave.
Paid leave takenDeputy to Xero (Australia)Exported on the timesheetDeputy's leave export codes must match the Xero leave types.
Super, tax, deductionsStays in XeroNot syncedHandled in the employee's pay template in Xero.

One more limit to plan for. Xero's developer documentation sets a limit of 60 API calls a minute and, for apps above its starter tier, 5,000 calls a day for each connected organisation. Deputy's troubleshooting page says that if your account hits Xero's daily limit, the only fix is to try again the next day. A normal pay run won't get near it, but repeated re-exports of a big team on pay day can.

How do you connect Deputy to Xero?

Before you start, Deputy says you need Location Manager, System Administrator or Advisor access in Deputy, and Standard or Advisor access in Xero, with Xero payroll settings already set up. Exporting timesheets also needs an active Xero Payroll subscription and the right Xero payroll roles.

  1. In Deputy, open the menu under your name at the top right and click Integrations.
  2. Select Xero, then click Connect add-on.
  3. Pick the Deputy location you want to connect and click Connect.
  4. Log in to Xero, check the organisation name, and click Allow access.
  5. Back in Deputy, click Configure to turn on the add-ons you want, or connect your other locations.

If you run several venues or clinics, think about this step. Deputy lets you connect different Xero organisations to different Deputy locations, but it doesn't recommend connecting more than one Xero organisation to a single location, because that can cause sign-in problems.

How to get a clean timesheet export every pay run

Deputy's export guide lists the conditions that have to be true in both systems. In plain terms, this is the checklist:

  1. Names and emails match exactly. Deputy matches each timesheet to a Xero employee by email first, then by first and last name. Deputy warns that a blank space after a name in Xero is enough to break the match, and a mismatch can create a duplicate employee in Xero.
  2. Each employee in Xero has an ordinary earnings rate, a payroll calendar and every earnings rate they'll need on their pay template.
  3. Pay items are named the way Deputy expects. On standard hourly rates, a Deputy "Saturday" rate needs a Xero earnings rate called "Saturday". With Deputy's pay rule library, Deputy creates the earnings rate in Xero for you the first time it's used.
  4. A draft pay run exists in Xero, with start and end dates that exactly match the dates you'll select in Deputy.
  5. No timesheets for that period are already approved in Xero. If they are, revert them to draft first.
  6. Timesheets are approved in Deputy before you export. Deputy's export guide says to export your approved timesheets.

If you pay staff under an Australian award in Xero, Deputy points you to its separate guide on exporting with the pay rule library. Read that one rather than the standard hourly guide, because the setup is different.

Salaried staff are the other trap. Deputy says that for salaried team members only leave, and any extra pay rates such as overtime, go across. Their fixed salary stays in Xero. If a re-export goes wrong, Deputy also warns that exporting every timesheet again overwrites the previous export, so re-export only the ones that failed.

Should you export as Timesheets or Payslips?

Deputy gives you both options on the export screen, and its help centre says most customers choose Timesheets. Export as Timesheets if you still want to add allowances or deductions in Xero. Each timesheet lands in Xero for you to check, and once you approve it, the hours move into the draft pay run against the matching earnings rates.

Export as Payslips only if you're happy with the rates Deputy applied and don't need to change anything. Payslips go straight into the pay run. For most small teams, Timesheets is the safer habit because it gives a person one last look before the pay run.

Why do Deputy exports to Xero fail?

Deputy keeps a list of the common Xero export errors. These are some of the errors on that list a small employer is likely to meet, with the fix Deputy gives for each.

Error you seeUsual causeFix
Employees Not FoundName or email differs between Deputy and Xero, or the connection droppedMake names and emails match exactly, then export again
Timesheet is not a Draft TimesheetTimesheets for that period are already approved in XeroRevert them to Draft in Xero, then export again
No Payroll Calendar foundNo calendar, calendar not on the employee, or another pay run already openCheck the calendar dates and employee assignment, and delete any active pay run
Invalid Leave PeriodXero's pay calendar doesn't match the dates picked in DeputyUse the same pay period in both
Pay Element not foundThe employee has no proper ordinary earnings rateSet an Ordinary Time Earnings rate, paid per unit in hours, on the Employment tab
Add Pay Items FailedA pay item in Xero has no expense account, including inactive onesGive every earnings line an expense account
Superannuation ErrorNo super on the employee's pay template in XeroAdd super to the pay template in Xero

Deputy's advice when an export partly fails is sensible: check the pay run in Xero to see who came across and who didn't, fix that person, and export only their timesheets.

Worked example: a three-venue cafe group

Say a hospitality business in Geelong runs three cafes with 28 staff, mostly casuals, paid fortnightly. They roster and clock in with Deputy, and pay through Xero Payroll. Each Deputy location is connected to the same Xero organisation.

Before they tidied things up, pay day went like this. The bookkeeper made the draft pay run in Xero, exported from Deputy, and got "Employees Not Found" for two new starters whose emails had been typed differently in each system. One cafe's manager hadn't finished approving timesheets, so those hours were missing. She fixed the emails, chased the manager, reverted the timesheets that had gone across to draft, and exported again.

After the tidy-up, the routine is short. New starters are only ever added in Xero, and the add-on invites them to Deputy, so the emails always match. Managers have a set cut-off to approve timesheets the day before pay day. The bookkeeper creates the draft pay run with the fortnight's exact dates, exports as Timesheets, checks the hours against the roster for anyone with overtime or a public holiday, adds any allowances in Xero, approves and runs the pay.

Nothing here needs a custom build. It's the same two systems, set up the way Deputy's guides describe, with one owner for each piece of data. That's where I'd start for most cafes, shops and clinics.

If you're not sure whether payroll is where your team loses the most time, the free AI readiness check takes about 3 minutes and shows where automation would save the most time across the whole business.

What stays with a person

Even with a clean integration, some payroll decisions should stay with someone who knows your staff and your award.

  • Approving timesheets. A manager should look at missed breaks, early clock-ins and odd hours before anything is approved for payroll.
  • Checking the award setup. Deputy's pay rule library applies the rules you've chosen. Whether those are the right rules for each employee is a person's call.
  • Approving the pay run in Xero, and anything unusual like back pay or a final pay.
  • Paying super on time. Super stays in Xero. The Fair Work Ombudsman says that from 1 July 2026, under Payday Super, employers pay super at the same time as wages so it reaches the fund within 7 business days, with some exceptions.
  • Keeping records. Fair Work says employers have to keep time and wages records for 7 years, including overtime hours and start and finish times, and hours worked by casual and irregular part-time staff paid by the hour. Deputy and Xero hold most of this, but someone should know where it lives if Fair Work or a staff member asks.

This page isn't legal, payroll or tax advice. For what your business must do, check the Fair Work Ombudsman, the ATO, or your bookkeeper or accountant.

When does a custom build on top make sense?

If you have one location, a handful of staff and an easy award, Deputy's own Xero integration is enough. Set it up properly and leave it alone.

A small build on top starts to earn its place when pay day keeps breaking in the same ways. Both systems have APIs, so the checks a bookkeeper does by hand can run by themselves before and after the export:

  • A check the day before pay day that lists timesheets still waiting for approval, by venue and manager. Deputy's API separates timesheets that are approved from ones approved for payroll export, so it can catch the ones that look done but aren't.
  • A match check that compares every active Deputy employee with Xero for name, email, trailing spaces and payroll calendar, so "Employees Not Found" is fixed before the export, not after.
  • An after-export check that totals hours per person in Deputy and in Xero's draft timesheets and flags anyone who doesn't match.
  • A weekly labour report per venue that puts Deputy hours next to your sales. Our guide to AI automation for hospitality covers more of the admin behind a venue.

That kind of glue between tools you already pay for is what our workflow automation service builds, usually in n8n, in your own accounts. If your CRM or booking system also needs to talk to Xero, that sits under CRM integration. And if you want to know what Xero now does by itself before adding anything, read what Xero and JAX automate in 2026.

NDIS providers have different shift and pay rules. We've built a rostering and invoicing system for an NDIS provider, and our NDIS rostering and Xero guide covers it.

If pay day still eats your bookkeeper's afternoon after all this, book a free call. I'll look at how you roster and pay, and tell you straight whether a fix in your settings is enough.

Sources

Facts checked 19 November 2026.

Pay day still a fight between Deputy and Xero? Tell us how you roster and pay. We'll show you what to fix in your settings first, and whether anything needs building at all. Book a free call.