Payroll pattern — Tanda is the AHG payroll system of record
Context
Aspire Hospitality Group's 3 venues (Chanya Thai, Venice Albany, Six Degrees) share payroll infrastructure via Tanda. Each venue has its own rosters and timesheets but a shared payroll pipeline. New ops staff need to know the single source of truth for "what's my pay" and "how do I record hours."
Detail
Tanda is the source of truth
Tanda (my.tanda.co) is the AHG-wide rostering + timesheet + leave + payroll platform. Per-venue rosters live in Tanda, employee identity is unified across venues, and the payroll run feeds Xero (per-venue org) for the actual money movement.
Flow
Venue manager builds roster in Tanda
↓
Staff clock in/out via Tanda (mobile or kiosk)
↓
Timesheets aggregate per-venue, per-fortnight
↓
Payroll cycle (typically fortnightly) — manager reviews + approves
↓
Tanda → Xero (per venue: chanyathai / venice / sixdegree orgs)
↓
Xero issues pay run + ATO STP reporting
↓
Bank file → bank → employees paidWhat lives WHERE
| Data | Where |
|---|---|
| Rosters | Tanda |
| Timesheets | Tanda |
| Leave balances + requests | Tanda |
| Award interpretation (penalty rates, weekend loadings) | Tanda |
| Pay rates | Tanda (synced from Xero pay items) |
| Bank file generation | Xero |
| STP reporting to ATO | Xero |
| Super calculations | Xero |
| PAYG | Xero |
| Bonus / one-off payments | Xero (run manually) |
MCP integration
- Tanda MCP wired in Claude Desktop + Code — can query rosters, timesheets, leave balances programmatically
- Xero MCP per org — chanyathai / venice / sixdegree / ahg / adg
Cross-venue staff
Some staff work at multiple venues (e.g., AHG-level cooks, casual front-of-house). Tanda handles this via:
- One employee record (single identity)
- Per-venue location assignments + roles
- Per-venue timesheet allocation
- Per-venue cost-coding for accounting
Payroll cadence
- Fortnightly for most AHG staff
- Casual rates include relevant penalties per fair-work award
- Public holiday rates automatically applied via Tanda award rules
Generic flags + alerts
- Unapproved timesheets older than X days → manager email + Telegram (via
sendTelegramMessagepattern per telegram-bot-pattern) - Roster gaps before opening shift → manager alert
- Leave requests pending approval → manager dashboard
What this DOESN'T cover
- ZeeHost AI workflows (different system)
- Customer-facing booking/staff visibility
- Cross-org payroll consolidation (each venue's payroll stays in its own Xero org)
Open questions
- Should AHG-level recruiting use Tanda's ATS, or a separate tool?
- When do we adopt Zinga's payroll/HR module (Phase 0+) to start replacing Tanda? Probably not until Zinga has feature parity.
- Cross-venue cost allocation when a staff member works multiple venues in the same fortnight — currently per-venue based on time worked.
Related
- multi-venue-ops-model — the 3-venue ops layer
- aspire-mcp-ecosystem — Tanda + Xero MCPs are wired
- telegram-bot-pattern — payroll alerts use this notification pattern
- zinga-suite — future replacement plan
🔗 Relationships
graph LR
payroll_via_tanda["payroll-via-tanda"]:::self
payroll_via_tanda --> telegram_bot_pattern["telegram-bot-pattern"]
payroll_via_tanda --> multi_venue_ops_model["multi-venue-ops-model"]
payroll_via_tanda --> aspire_mcp_ecosystem["aspire-mcp-ecosystem"]
payroll_via_tanda --> zinga_suite["zinga-suite"]
classDef self fill:#715EE3,color:#fff,stroke:#291F50;