claude connector super
The Xero MCP connector currently exposes accounting data only — invoices, bills, aged reports, P&L, balance sheet, bank transactions. There is no access to payroll: no pay runs, no employees, no super payment batches, no super payment status or due dates.
This matters more since payday super commenced 1 July 2026. Contributions must now be received by the employee’s fund within seven business days of the pay date, rather than 28 days after quarter end. The compliance window is short enough that it needs monitoring between pay cycles, not just at quarter end.
Without payroll endpoints, any automated check has to be reconstructed as a proxy from the general ledger — comparing movement in Wages & Salaries and Superannuation accounts against an assumed pay calendar, and watching the bank feed for outgoing payments. That proxy is unreliable in both directions. It cannot see a super batch sitting in Processing, cannot distinguish submitted from received, and cannot see the date the fund actually received the contribution, which is the binding fact for the deadline.
Specifically requested:
Super payment batches with status (Processing, Completed, Failed), submission date, and per-fund disbursement dates where available.
Pay runs with pay period, pay date, and posted status.
The calculated super due date per pay run under payday super rules.
Extension of the existing payroll tool coverage to the AU region, which the open-source MCP server currently limits to NZ and UK.
Read-only access would be sufficient. The use case is monitoring and early warning, not making changes to payroll.
Thanks for submitting your idea on Xero Product Ideas. We appreciate you taking time to let us know how we could improve Xero for you.
Your feedback will soon be reviewed by our Community team, and in the meantime this can begin to build support with votes from other community members.
If you're interested to see recent releases or get a pulse on what's coming soon see The Long and Short of it. 🙂