Deputy-Xero Payroll Bridge
Key Facts
- Current state: Deputy (rostering/time tracking) and Xero (payroll) are disconnected — manual export by Tom Nguyen takes 2–3 hours per pay cycle
- Native integration exists but is semi-automated: requires manual trigger, timesheets do not auto-flow on approval
- Strategic partnership: Xero invested USD $25M in Deputy (April 2024) and made Deputy the exclusive embedded rostering partner for Australian Xero customers (March 2026)
- Xero App Store rating: 3.96/5 from 146 reviews — mixed; 1-star reviews describe integrations that never worked
- Award complexity: 6 different bartender pay rates under HIGA, plus full-timers on individual contracts
- Structural limitation: Salaried employees cannot be exported; pay rate dollar amounts do NOT transfer — only hours and categories
- Risk factors: Double handling, reconciliation risk, 14 documented export error types, dependency on undocumented process
Strategic Context
Xero invested USD $25M in Deputy (April 2024), subsequently retired competing Planday in Australia, and made Deputy the exclusive embedded rostering partner for Australian Xero customers (March 2026). The partnership is deep and growing — Deputy’s integration is built and maintained by Deputy, not a third party.
However, reliability is mixed. The Xero App Store rating of 3.96/5 from 146 reviews includes multiple 1-star reviews from users whose integrations never worked. The integration performs well for simple hourly structures but is brittle for complex award configurations like the HIGA.
See Deputy for the comprehensive platform assessment.
The Problem
Pride of Our Footscray uses Deputy for rostering and time tracking, and Xero for payroll processing. Without direct integration, payroll data must be manually transferred from Deputy to Xero each pay cycle. This creates:
- Double handling: Data entry in two systems
- Reconciliation risk: Hours in Deputy may not match amounts processed in Xero
- Process risk: Payroll depends on an undocumented spreadsheet or process that only Tom Nguyen understands
- Audit trail: No automated log of what data was transferred and when
Integration Architecture
Native Workflow Steps
The Deputy–Xero export is semi-automated — a manager must manually trigger it. Timesheets do not flow to Xero automatically on approval.
- Draft pay run in Xero with exact matching date range
- Approve timesheets in Deputy for the period
- Export from Deputy: select location, date range, employees
- Import to Xero via API (no CSV step)
- Review and adjust in Xero — add manual allowances, leave loading, casual loading
- Process pay run in Xero
14 Documented Export Error Types
The most critical for Pride:
| Error | Impact | Pride Risk Level |
|---|---|---|
| Employee name/email mismatch | Export fails for mismatched records | HIGH — high casual turnover means frequent onboarding |
| ”Pay element not found” | Xero earnings rates don’t match Deputy config | MEDIUM — complex HIGA rate structure |
| API rate limit (5,000 calls/day, 60/min) | Failed batches with no same-day fix | LOW–MEDIUM — staff count is small |
| Duplicate timesheet conflicts | Overlapping records block export | MEDIUM — split shifts common |
Structural Limitations
- Salaried employees cannot be exported — hourly/award-rate only
- Cannot selectively sync employees — all-or-nothing
- Pay rate dollar amounts do NOT transfer — Xero applies its own earnings rates to exported hours; only hours and categories cross the bridge
HIGA Award Interpretation Gaps
Deputy automates the following under the Hospitality Industry General Award (MA000009):
- Base hourly rates
- Weekend penalties (Saturday 1.25x FT/PT, 1.20x casual; Sunday 1.50x/1.40x)
- Public holiday penalties (2.25x/2.00x)
- Daily overtime tiers
- Evening penalties (+$2.81/hr M–F)
- Split shift and delayed meal break penalties
Deputy does NOT automate (requires manual adjustment in Xero every pay run):
- Leave loading (17.5%)
- Casual loading (25%)
- Loaded rates
- Annualised wage outer limits testing
- Overnight stay penalties
- Most allowances: meal, first aid, laundry, travel, supervisor
- Part-time overtime thresholds (Enterprise plan only)
Every pay run at Pride will require manual Xero adjustments for these gaps regardless of integration setup.
Risk Mitigation
Timesheet Preflight (January 2025)
Deputy’s Timesheet Preflight feature flags employee record mismatches before export — directly addressing Pride’s highest-risk error type given high casual turnover. Should be enabled as part of Step 1 optimisation.
Deputy Payroll Add-on (June 2025)
At $5/user/month, Deputy Payroll eliminates the Xero integration entirely by processing payroll within Deputy. This is the long-term simplification path but the product needs 6–12 months of maturity. Revisit Q3 2026.
Alternative Platforms
If the native Deputy–Xero integration proves unreliable after optimisation, evaluate in this order:
| Platform | Xero App Store Rating | Est. Cost (20 staff/mo) | Strength |
|---|---|---|---|
| Tanda + Xero | 4.47/5 (51 reviews) | ~$290–$350 | Best-rated alternative; real-time award interpretation during rostering; live labour cost visibility Deputy lacks |
| KeyPay (Employment Hero Payroll) | 4.32/5 (34 reviews) | ~$120 | Eliminates integration layer entirely; strongest award engine |
| Microkeeper | 4.4/5 (~$4–6/employee/month) | ~$120 | Budget pick; full HIGA support, STP compliant, Australian-built |
| RosterElf + Xero | 4.88/5 (90 reviews) | ~$140 + Xero | Highest Xero App Store rating; Fair Work awards built in; smaller user base |
Custom Development
If zero-touch automation is required and no commercial platform meets requirements:
| Option | Cost Range | Notes |
|---|---|---|
| Australian agency (Hello People, Dcode Group) | AUD $6k–$17k | Local support, familiar with HIGA |
| Offshore development | AUD $3k–$12k | Lower cost, timezone/context risk |
| AWS Lambda custom architecture | ~$0–5/month running cost | Batch export with webhook buffering |
No middleware can replicate the native export. Zapier and Make process events individually with no Australian award awareness — useful only for supplementary notifications. Workato is enterprise-priced ($10k+ USD/year) and overkill for this use case.
Recommended Pathway
Per Deputy Xero Integration Research:
- Step 1 (now): Optimise native integration — audit employee records for exact name/email match, enable Timesheet Preflight, configure native integration, build per-pay-run manual checklist for leave loading, casual loading, and allowances
- Step 2 (if native remains unreliable): Evaluate alternatives — Tanda → KeyPay → Microkeeper in that order
- Step 3 (only if zero-touch automation required): Custom development — AWS Lambda batch architecture
Related Pages
- Deputy — comprehensive platform assessment and operational context
- Deputy Xero Integration Research — source: full research report (April 2026)
- Xero — payroll/finance platform
- Tom Nguyen — subject matter expert for current manual process
- Tech Stack Optimisation — strategic technology planning
- Labour Cost Structure — HIGA penalty rate exposure and award interpretation gaps