Tanda Virtual Assistant: rosters to template, timesheets reconciled to actual

Nobody searches “tanda virtual assistant” for fun. You search it because the roster, the timesheets and the export to payroll all live in Tanda, and the person building the week, reconciling the clock-ins and getting it clean before the pay cut-off is you, somewhere between the lunch rush and lock-up. Tanda does the heavy mechanical work, the award engine, the clock, the wage tracker, but the system still needs a person to drive it, and that person keeps being the owner.

A Tanda VA is the person who drives it instead. Not someone who decides your award rules or sets a pay rate, those stay exactly where they should, but someone who builds the roster to your template and your budget, works the timesheet exceptions every day, triages leave, and hands your bookkeeper a clean export instead of a mess to unpick.

The daily rhythm a VA runs in your Tanda

It starts with the roster. Each week your VA opens the Rosters screen, copies forward the template that fits the trading pattern, and drops shifts onto the right teams and areas. The whole time, Tanda’s live wage tracker is running, showing labour cost as a number and a percentage as shifts are added. Your VA builds to the wage-cost target you set rather than guessing, holds the draft, and brings it to you for sign-off before it publishes to staff phones through MyTanda. If you’re short, they create the open shifts; if someone’s flagged unavailable, the roster respects it because the availability is kept current.

Then through the week, the real Tanda work: roster versus actual. This is the screen Tanda is built around and the one that eats an owner’s morning. Staff clock in and out on the Time Clock tablet or the MyTanda app, and on the Timesheets screen Tanda lines up what each person was rostered against what they actually worked. Your VA works the gaps. A shift that ran forty minutes long gets a reason or a query. A missing clock-out gets chased with the staff member before it’s resolved, not guessed. An unrostered punch gets explained. Early starts, no-shows, split shifts, all surfaced and worked one by one, so by the time anything is approved it reflects what actually happened on the floor.

While that runs, the award engine is talking. Tanda interprets the award as the roster and timesheets are built, throwing warnings for breaks not taken, overtime triggered, minimum-engagement breaches and shift-spacing problems. A lot of owners click past these because there’s no time. Your VA reads every one. If it’s a genuine roster error, a break scheduled wrong, a shift that needs trimming, they fix it. If it looks like a real award interpretation question, they escalate it to you with the context attached rather than approving over it.

Leave and availability sit alongside. Requests land in the Leave screen, and your VA triages them: checks the balance, flags any clash with the published roster, and queues each one with context for your approve-or-decline call. The decision stays yours; the legwork that makes it a two-second decision doesn’t have to be.

Then export prep. Once the exceptions are cleared and the week reconciles, the VA checks the timesheets line by line and readies the payroll export Tanda generates, the file that flows into Xero, MYOB, KeyPay or whatever payroll platform you run. The point is that your bookkeeper opens a clean export and sends it, instead of opening a half-reconciled one and spending an hour working out why the hours don’t match.

And around the edges, the reporting. Tanda’s Live Insights and reports hold the numbers that actually run a venue, wage cost against sales, hours by department, clock-in compliance, no-shows, and your VA pulls them so you start the week looking at the figures rather than digging them out on a Sunday night.

The discipline that ties all of this together is the wage budget. A roster that looks fine on Tuesday can quietly blow your labour percentage by Saturday if nobody is watching the number while shifts get added. Because Tanda shows projected wage cost live as the roster is built, your VA can hold the build to the target you set rather than discovering the overspend in next month’s report. The same instinct runs through the timesheet review: a roster built to 28 per cent that gets approved at 34 because shifts ran long and nobody queried them is the single most common way labour leaks, and the roster-versus-actual work is where it gets caught. That is the practical value of the VA, not just data entry, but a person watching the gap between what you planned to spend and what you actually spent, every week, while you run the floor.

There is also a rhythm to the week worth naming. Early in the cycle it is roster build and publish. Mid-week it is daily exception clearing on the timesheets as shifts are worked, so the reconciliation is never a single mountain on pay day. Leave and availability get handled as they land. Then the day before the pay cut-off it is the final pass and the export prep, with everything already reconciled so the close is a check rather than a scramble. Spread across the week like that, the whole Tanda cycle stops being the thing you dread on a Sunday night and becomes background admin that is simply handled.

The honest bit

A few things Tanda genuinely will not do, no matter who you put on it, so the page reads true.

Tanda interprets the award; it does not write your award rules. The interpretation is only as good as the configuration behind it, the pay rates, the penalty and overtime setup, the allowances mapped to the right award. If that configuration is wrong, Tanda will confidently produce wrong numbers, and no VA fixes that by clicking around the roster. Getting the setup right is a payroll and compliance job for you or your bookkeeper, and it sits behind admin settings a VA’s role does not open.

The clock only captures what staff actually do. If people forget to clock in, clock a mate in, or punch from the car park, Tanda records it faithfully and someone still has to query it. The VA chasing missing and odd punches is doing necessary work, not patching a flaw, because no system invents a clock-in that never happened.

And Tanda is not your payroll authority. It prepares the export beautifully; it does not decide that the pay run is correct or send it on your behalf as a final act. That sign-off is a decision, and it stays a decision.

One more honest note on the integration. Tanda exports cleanly into Xero, MYOB, KeyPay and the rest, but the mapping between a Tanda team or position and the right pay item or account in your payroll system has to be set up correctly once, and that mapping is a finance decision, not roster admin. If it is right, the export flows. If it was never set up properly, the export will be tidy and still land in the wrong place, and a VA reconciling rosters has no business changing it. We flag the difference rather than blur it: the VA prepares the export inside a mapping you and your bookkeeper own.

What stays with you

Two lines we keep bright, because they protect you.

The first is award and pay configuration. Tanda automates award interpretation, and that’s exactly why a VA must not touch the setup. Your pay rates, your award rules, your penalty, overtime and allowance configuration are a payroll and compliance decision that stays with you or your bookkeeper. The VA works inside what is already configured. When Tanda throws a break, overtime or minimum-engagement warning, they read it, fix a genuine roster error, and escalate anything that smells like a real award question to you. They never guess at compliance, and they never set a rate. The VA’s role is scoped so those settings are not even reachable.

The second is final approval and the pay run. The VA chases, reconciles and readies the timesheets, but most owners keep the last approval click and the actual export-send for themselves. That isn’t a limitation, it’s the right division: the VA removes the hour of reconciliation legwork so your decision takes two minutes. Where you run more than one site, the VA’s role is scoped to the single venue they support, so it never reaches your other locations.

What it costs and where to start

Tanda admin sits on the admin tier, $12-17 AUD an hour excl GST, typically 10-15 hours a week for a single-venue or small-multi-site operator, covering roster builds, the roster-versus-actual timesheet review, leave triage and export prep. If the VA also keeps your booking and staff calendars straight or hands a clean file to your Xero bookkeeping workflow, fold that into the same hours. Placement takes 7-10 business days, with 5-7 days supervised inside your Tanda before any solo work, a 30-day recalibrate-or-replace guarantee, and no lock-in beyond 14 days notice.

If you want the industry view, the hospitality page goes deeper on venue admin, and the VA cost guide lays out the full pricing picture. Otherwise book a discovery call with Jenn, who has placed 87+ VAs into Australian businesses since 2024 and will tell you straight if your venue isn’t ready for one. Bring last week’s roster and your current timesheet screen with its unresolved exceptions. We’ll find the hours.