Deputy ↔ Xero Integration: Comprehensive Research Report for Melbourne Hospitality
Prepared: April 2026 Context: Small hospitality business, Melbourne, Australia (10–30 staff) Award: Hospitality Industry General Award (HIGA) [MA000009]
Executive Summary
The Deputy–Xero integration is in its strongest strategic position ever. Xero invested USD $25 million in Deputy in April 2024, retired its competing Planday product in Australia, and as of March 2026 made Deputy the exclusive, officially embedded rostering solution for Australian Xero customers. The native integration is free, handles core timesheet-to-payroll export, and received a notable quality update in early 2025 (Timesheet Preflight validation).
However, the integration has well-documented pain points — particularly for hospitality businesses with complex award structures. Leave loading (17.5%), casual loading, loaded rates, most allowances, and annualised wage outer limits are all not automated by Deputy under HIGA. The export is semi-automated (requires a manual trigger), employee matching is brittle (exact name/email required), and customer support quality is a persistent complaint across review platforms.
For a small Melbourne hospitality business, the recommended path is: use the native integration as the primary solution, accept that some manual reconciliation is required each pay run, and evaluate alternatives only if the manual burden becomes unsustainable. Tanda + Xero and KeyPay (Employment Hero Payroll) are the strongest alternatives for businesses needing deeper award automation.
1. Native Deputy–Xero Integration: Current State (2025–2026)
Strategic Context
The integration is built and maintained by Deputy, not a third party. Key milestones:
- April 2024: Xero invested USD $25M for a minority stake in Deputy and retired Planday in Australia (shutdown 30 September 2024)
- January 2025: Timesheet Preflight validation launched — a pre-export check system that prevents duplicate employees, corrects missing earning rates, and blocks re-exporting approved timesheets
- March 2026: Deputy officially launched as Xero’s exclusive embedded solution for Australian SMBs — discoverable, triallable, and subscribable directly inside Xero
The Xero App Store lists Deputy at 3.96/5 from 146 reviews, listed since May 2016.
Reliability Assessment
Mixed. The integration works well for businesses with simple hourly pay structures and consistent employee data. It is brittle for businesses with complex award configurations, legacy employee records, or non-standard setups.
Positive evidence: Multiple users report payroll processing dropping from hours to minutes — “once we approve the hours submitted by the team, we simply click export to Xero” (Xero App Store).
Negative evidence: Multiple 1-star Xero App Store reviews from Australian users describe integrations that never worked. An April 2026 Reddit post reported timesheets resetting to “pending” on export. A Trustpilot reviewer spent 5 months trying to fix a Xero sync issue through Deputy support with only escalation promises and no resolution.
Known Limitations (14 Documented Error Types)
Deputy’s own troubleshooting guide documents these recurring export errors:
| Error | Common Cause |
|---|---|
| Validation Exception | Unpaid leave export; leave name mismatch; hire date after pay period |
| Employees Not Found | Name/email mismatch between Deputy and Xero |
| Wrong rates exported | Employee syncing to old/archived Xero profile |
| Pay Element not found | Earnings rate misconfigured in Xero |
| Superannuation Error | No super in employee’s Xero pay template |
| Daily API rate limit reached | >5,000 Xero API requests/day — no same-day fix |
| No Payroll Calendar found | Calendar not assigned to employees in Xero |
| Timesheet already exists | Employee submitted a timesheet directly in Xero |
Structural Limitations
- Salaried employees cannot be exported — hourly/award-rate only (Deputy Help)
- Cannot selectively sync employees — all-or-nothing (Deputy Help)
- Gender field required by Xero — sync fails if missing in Deputy
- Negative leave balances do not sync (Deputy Help)
- Pay rate dollar amounts do not transfer during timesheet export — Xero uses its own rates (Deputy Help)
- Initial setup for 12+ employees can take hours due to API throttling
2. Data Fields That Transfer Between Deputy and Xero
Employee Data (Bidirectional)
| Direction | Fields Synced | Frequency |
|---|---|---|
| Deputy → Xero (Auto Sync ON) | First/last name, mobile, gender, DOB, address, hire date | Every 15 minutes |
| Xero → Deputy (add-on) | Name, gender, mobile, DOB, hire date | One-time per employee (daily check) |
| Deputy Onboarding → Xero (AU only) | All personal details + bank account (BSB, account number) + super fund (USI, ABN, member number) + TFN + tax declaration | Manual trigger (“Sync and Approve”) |
Source: Deputy Help — Sync Employee Info, Deputy Help — Onboarding Sync
Timesheet Data (Deputy → Xero Only)
Exported fields: employee name, date, start/end times, unpaid break duration, total hours, pay rate category (weekday/Saturday/Sunday/PH/overtime tiers), area/location code, leave type. Dollar amounts are NOT sent — Xero applies its own earnings rates to the hours.
Leave Balances (Xero → Deputy)
Syncs annual leave, personal/carer’s leave, compassionate leave, community service leave, long service leave, and TOIL. Runs once daily at midnight. Positive balances only. Source: Deputy Help — Leave Balance Sync
What Does NOT Sync
- Superannuation (handled entirely in Xero)
- Leave loading (must be added manually)
- Casual loading (must be baked into base rate)
- Most allowances (meal, first aid, laundry, travel)
- Unpaid leave timesheets
- Salaried employee timesheets
The Actual Pay-Run Workflow (Step by Step)
- In Xero: Create a draft pay run with exact matching dates
- In Deputy: Approve all timesheets for the period
- In Deputy: Go to Export Timesheets → select location, date range, employees
- Choose export format — Timesheets (allows Xero-side adjustments) or Payslips (direct to pay run)
- Click Export — Deputy pushes data to Xero via API (no CSV step)
- In Xero: Review imported timesheets per employee, add manual allowances
- In Xero: Approve timesheets → process pay run
The export is semi-automated — a manager must manually initiate it. Timesheets do not flow to Xero automatically on approval. Source: Deputy Help — Export to Xero
3. HIGA Award Interpretation: What Deputy Automates vs. What It Doesn’t
Automated by Deputy (Premium Plan)
| Condition | Rate |
|---|---|
| M–F Ordinary | Base hourly rate |
| M–F 7pm–12am | Base + $2.81/hr |
| Saturday | 1.25x (FT/PT) / 1.20x (Casual) |
| Sunday | 1.50x (FT/PT) / 1.40x (Casual) |
| Public Holiday | 2.25x (FT/PT) / 2.00x (Casual) |
| M–F Daily OT (first 2 hrs) | 1.50x |
| M–F Daily OT (after 2 hrs) | 2.00x |
| Delayed meal break | 1.50x–2.75x depending on day |
| Split shift allowance | $3.53–$5.34/day |
Source: Deputy Help — HIGA MA000009
NOT Automated (Manual Adjustment Required)
| Condition | Status |
|---|---|
| Leave loading (17.5%) | Must be manually added to each timesheet |
| Casual loading (25%) | Must be included in base hourly rate manually |
| Loaded rates | Not supported (Enterprise plan required) |
| Annualised wage outer limits (post-Sept 2022) | “Not currently supported — please send feedback” |
| Overnight stay penalty rates | Not automated |
| Most allowances (meal, first aid, laundry, travel, supervisor) | Not automated |
| Part-time OT threshold (agreed hours, not 38h) | Enterprise plan only |
| Penalty rates for partial hours | Full hours only — no pro-rating |
Source: Deputy Help — HIGA, Deputy Help — Award Updates FAQ
4. Common Pain Points and Workarounds
Top 5 Pain Points (from user reviews and forums)
1. Employee mapping errors — The integration matches by exact full name + email. Any spacing, capitalisation, or email discrepancy causes export failures or duplicate records. This is the single most common complaint across Xero App Store reviews and Deputy’s own troubleshooting docs.
Workaround: Audit names and emails in both systems before each pay run. Rename or delete archived Xero profiles that share names/emails with active employees.
2. Award interpretation gaps — Leave loading, casual loading, allowances, and loaded rates require manual payroll adjustments every pay run. One Reddit user reported a persistent ~7-hour/fortnight discrepancy between Deputy and payslip hours.
Workaround: Build a checklist of manual additions needed per employee type. Add these in Xero after each timesheet import.
3. Customer support quality — Offshore (Philippines) first-level support with timezone mismatches and language barriers. One Trustpilot reviewer spent 5 months trying to resolve a Xero sync issue. An Xero App Store reviewer was charged $1,800 for a year’s subscription after failing to get the integration working.
Workaround: Request escalation to Australian team explicitly. Document issues thoroughly via email for paper trail.
4. Connection drop-outs and setup failures — Multiple 1-star reviews describe integrations that never connected. Token expiry requires manual reconnection. Source: Deputy Help — Connecting to Xero
Workaround: Ensure only one Xero organisation per Deputy location. Verify Xero user has Payroll Administrator permissions.
5. API rate limit (5,000 calls/day) — Can block large exports entirely with no same-day remedy. Source: Deputy Help — Troubleshooting
Workaround: Export in smaller batches. Schedule exports early in the day.
5. Third-Party Middleware Options
Comparison Table
| Option | Monthly Cost | Can Replace Native Export? | AU Payroll Aware | Best For |
|---|---|---|---|---|
| Native integration | $0 | N/A (is the native export) | Yes (via Deputy) | Primary solution |
| Zapier (Professional) | ~$20 USD | No — event-by-event only | No | Supplementary notifications |
| Make (Core) | ~$10 USD | No — cannot batch export | No | Better-value supplementary |
| Workato | ~$10,000+ USD/yr | Yes (if built) | Partial | Enterprise only — not for SMBs |
| n8n (self-hosted) | Free + VPS hosting | Partial (needs dev work) | No | Only if you have a developer |
Source: Zapier Deputy-Xero page, Make Deputy integration
Key Finding
Neither Zapier nor Make can replicate the native Deputy → Xero batch payroll export. They process events individually and have no understanding of Australian awards. They are useful only as supplements — for example, sending a Slack notification when an employee is late, or auto-creating a Xero contact when a new employee joins Deputy.
If supplementary automation is needed: Make at ~$10 USD/month offers substantially more operations and deeper Deputy module access than Zapier at ~$20 USD/month. Source: Make Deputy modules, Capterra Zapier Pricing
6. Deputy API Technical Capabilities
Webhooks: Fully Supported
Deputy supports webhooks across all plans at no extra cost, with events for timesheets (created, updated), employees (created, updated, deleted), leave requests, and schedules. Source: Deputy Developer Docs — Webhook Overview
There is no dedicated “timesheet approved” event — approval triggers a timesheet update event where the TimeApproved field changes to true. This is sufficient for building real-time notification or buffered export workflows.
API Architecture
| Feature | Deputy | Xero Payroll AU |
|---|---|---|
| API type | REST v1/v2 | REST v1.0/v2.0 |
| Auth | Permanent token or OAuth 2.0 | OAuth 2.0 only |
| Webhooks | Yes — timesheets, employees, leave, schedules | Contacts and Invoices only (no payroll events) |
| Rate limits | Not publicly documented (unlikely issue for SMBs) | 60 calls/min, 5,000/day |
| Timesheet write | Full CRUD | Full CRUD (must link to Draft Pay Run) |
| Official SDKs | None (community PHP wrapper available) | Node, Python, PHP, Ruby, .NET, Java |
Source: Deputy Developer Portal, Xero Payroll AU API
Recommended Custom Architecture
For a small hospitality business, the recommended approach is batch export with webhook buffering: Deputy webhooks capture timesheet approvals in real-time into a queue, then a scheduled job (or manual trigger) pushes approved timesheets to Xero under the active Draft Pay Run. This is simpler than full real-time sync and aligns with Xero’s period-based payroll model. Hosting on AWS Lambda would cost ~$0–5/month. Source: Deputy API Documentation
7. Custom Integration Development Costs
Cost Estimates by Route
| Route | Year 1 Cost (AUD) | Year 2+ (AUD/yr) | Risk Level |
|---|---|---|---|
| Native integration (free) | $0 | $0 | Low |
| Zapier / Make | $400–$1,600 | $165–$1,280 | Low |
| Australian freelancer/agency | $6,000–$17,000 | $1,300–$4,200 | Medium |
| Offshore developer (Upwork) | $3,100–$11,700 | $800–$3,100 | Medium-High |
| Switch to all-in-one platform | $0–$5,000 (migration) | Platform fees | Low |
Source: Hello People — Xero Integration Pricing, Upwork API Developer Rates, Aalpha — AU Dev Costs
Named Xero Developer Partners in Australia
| Partner | Location | Notes |
|---|---|---|
| Hello People | Perth / AU-wide | Explicitly lists Deputy; AUD $5,000–$15,000 for single integration |
| Dcode Group | Melbourne | Xero Developer Partner; custom integrations; open-source Laravel Xero timesheet sync on GitHub |
| ISH Technologies | AU-wide | Xero App Developer; 6–12 week delivery |
| Sprint Digital | Brisbane | Xero + finance automation |
Build vs. Buy Verdict
Custom development is not recommended for most small hospitality businesses. The native integration covers the core workflow at zero cost. Custom builds are justified only if the business needs fully automated (zero-manual-trigger) payroll sync, has non-standard award rules beyond what Deputy handles, or must integrate with additional systems.
8. Alternative Rostering-to-Payroll Systems for Australian Hospitality
Comparison Matrix
| Platform | Type | HIGA Award Depth | Est. Cost (20 staff/mo) | Xero Integration Rating | Best For |
|---|---|---|---|---|---|
| Deputy + Xero | 2-system | Partial (gaps documented above) | ~$200–$250 | 3.96/5 (146 reviews) | Simple setups; Xero-embedded experience |
| Tanda + Xero | 2-system | Strong (real-time cost visibility) | ~$290–$350 | 4.47/5 (51 reviews) | Award-heavy hospitality; live labour cost control |
| Employment Hero Payroll | All-in-one | Strong (55+ awards, auto-updates) | ~$120–$160 | 4.32/5 (34 reviews) | Single platform for HR+payroll |
| KeyPay (EH Payroll standalone) | All-in-one | Industry-leading | ~$120 | Highly rated (journals to Xero) | Best award engine; accountant-friendly |
| Humanforce | All-in-one | Enterprise-grade (120+ awards) | Custom (high) | N/A | 50+ staff, multi-site — overkill for small ops |
| foundU | All-in-one | Strong, highly configurable | Min $400/mo | N/A | True end-to-end; 25+ staff minimum to justify cost |
| Microkeeper | All-in-one | Full Modern Awards | ~$120 | N/A | Budget-conscious; from $4/employee/month |
| RosterElf + Xero | 2-system | Built-in Fair Work awards | ~$140 + Xero | 4.88/5 (90 reviews) | Affordable; highest Xero rating |
Standout Alternatives
Tanda + Xero is the most direct upgrade path for a business wanting to stay on Xero. Tanda’s award interpretation engine shows live wage costs as rosters are built (Deputy doesn’t do this), and its Xero integration is rated higher than Deputy’s. Leave loading still requires manual handling in Xero. Source: Tanda Xero Integration
KeyPay / Employment Hero Payroll is the strongest option for eliminating integration friction entirely. It handles rostering + payroll natively, posts payroll journals automatically to Xero (no Xero Payroll subscription needed), and has the deepest award interpretation engine in the Australian market. The trade-off is the rostering module is consistently criticised as less polished than Deputy or Tanda. Source: KeyPay Xero page
Microkeeper is an under-discussed sleeper pick for budget-conscious operators — Australian-built, full HIGA interpretation, STP compliant, all-in-one, from $4–6/employee/month. Rated 4.4/5 across 115 Trustpilot reviews. Source: Capterra — Microkeeper
Decision Framework by Business Profile
Small café/restaurant, 10–15 staff, mostly casuals, tight budget: → Microkeeper ($80–$120/month all-in) or Employment Hero Payroll ($100/month minimum)
Pub/hotel, 20–30 staff, complex HIGA, need labour cost visibility: → Tanda + Xero (best real-time award interpretation during rostering) or KeyPay standalone (built-in payroll + rostering)
Existing Deputy user wanting better payroll compliance without switching rostering: → Deputy + KeyPay (keep Deputy’s rostering UI; replace Xero Payroll with KeyPay’s award engine; KeyPay posts journals to Xero for accounting)
9. Recommendations
For Most Small Melbourne Hospitality Businesses
Step 1: Optimise the native Deputy + Xero integration.
The built-in integration handles the core workflow at zero additional cost. Take these steps to minimise friction:
- Audit employee names and emails for exact match between both systems
- Use Deputy’s paperless onboarding to create Xero employee profiles (avoids data entry duplication)
- Enable the Timesheet Preflight feature to catch errors before export
- Set Deputy as source of truth for employee data; enable Auto Sync
- Build a per-pay-run checklist of manual additions needed (leave loading, allowances)
- Export as “Timesheets” (not “Payslips”) to allow Xero-side adjustments
Step 2: If the manual burden is unsustainable, evaluate alternatives in this order:
- Tanda + Xero — if you want to stay on Xero but need better award interpretation
- KeyPay (Employment Hero Payroll) — if you want to eliminate the integration layer entirely
- Microkeeper — if budget is the primary constraint
Step 3: Custom development only if:
- You need fully automated zero-touch payroll sync
- You have non-standard award rules beyond what any platform handles
- Budget: expect AUD $5,000–$15,000 for initial build via a Xero-certified Australian agency like Hello People or Dcode Group (Melbourne-based)
Key Risk to Monitor
Xero introduced new tiered API pricing effective March 2026. As a major Xero partner, Deputy should be insulated, but this represents a background ecosystem risk for any third-party or custom integrations consuming Xero’s API.