Pocket HRMS vs Tanda

Tanda ships near-daily and most of it is workforce-management plumbing for AU/NZ operators: new pay run statuses so a failed run names the affected payslips instead of failing silently, no-show marking with reasons that flow into the Shift and Attendance reports, Beam super batches restricted to the bank accounts actually configured for them, and the Nurses Award phase-three wage increases handled inside the managed template with no customer action. Running alongside that is a page-by-page visual conversion — Locations and Teams, Stat Types, a new Sales page, a dedicated Roster Ratios page — most of it rolling out gradually per account.

Two things are happening at once. The visible one is a long UI migration, shipped in slices behind gradual rollout, which is why so many entries say functionality is unchanged. The one that matters is that AI is being placed at the decision points: applicants are now automatically tiered against criteria the employer writes in plain language, and the roster validation page consolidates Roster Agent instructions with custom natural-language validations. Tanda is not marketing an AI product; it is putting a scoring layer inside the screens managers already use.

Expect the same criteria-and-explanation pattern to spread to other decisions Tanda already automates — rostering suggestions and timesheet approvals are the obvious candidates, given the Roster Agent already takes natural-language instructions. The POS revenue-splitting work also flags more integrations to come, since the entry says so explicitly.