Module · Roster & timesheets

Where to find it in the app

• Use it: Time & pay → Roster & timesheets
• Turn it on/off: your business name (top-left) → Settings → Modules → Time & pay → Roster & timesheets

Plan: Solo and Business · Module group: Your team · Navigation: Time & pay → Roster & timesheets

1. Overview

Purpose. Build the weekly staff roster, let staff clock in/out, and turn the result into timesheets you can approve and export for payroll. It understands regular shift patterns, days off, business closures and casual shifts, and it respects approved leave.

The time clock is shift-aware: clock-ins are checked against the rostered shift, so you can capture lateness, no-shows and blocked attempts, and the app can auto-close a clock-out someone forgot. The clock is a separate on/off switch from this module (see §6a), you can run the roster without the clock, and you do not turn the clock off by turning the Roster module off.

2. When to use it

• To schedule who works when, by role.
• To capture worked hours and prepare payroll.

3. Required permissions

• View the roster (roster.view).
• Build / edit the roster (roster.manage).
• View timesheets (timesheets.view).
• Edit / approve timesheets (timesheets.manage).

4. Navigation path

Time & pay → Roster & timesheets

5. What you'll see

• A weekly grid of staff × days, with This week and week navigation.
• Shift blocks showing the role; regular patterns appear automatically, with day-off overrides and business closures marked.
• Controls to add a casual shift (including a typed name for a one-off).
• A timesheets view to review worked hours, approve the week, adjust any single day (or a whole week in one press), and Export payroll CSV.
• An attendance read in Timesheets: on-time %, lateness, no-shows and blocked clock-in attempts for the week, plus a Time in lieu (TOIL) running balance per person. Auto-closed clock-outs are flagged for you to confirm.

6. Turning it on

Settings → Modules → Your team → Roster & timesheets. Set your staff up in Team → Staff list; their regular patterns and any closures flow into the grid.

6a. The time clock is a separate switch

The clock in/out feature has its own on/off switch, separate from this module: Settings → the "Team" tab → the "Time clock" card → "Use the time clock".

• Turn the clock off there if you don't track hours this way, the roster still works. Turning the Roster module off is not how you turn off clocking, and is a common mix-up.
• Solo (one-person) accounts hide the clock automatically.
• Just below the toggle are the clock-in rules, see §7b.

7. Step-by-step tasks

7a. Build the roster

1. Open Time & pay → Roster & timesheets and pick the week.
2. Add or edit shifts per person, setting the role (e.g. Floor, Kitchen).
3. Regular patterns pre-fill; use a day-off override where someone isn't working, and add casual shifts as needed.
4. Business closures (e.g. a public holiday or training day) block the day.

A closure is whole days, for the whole business. It also tells the roster you are shut. To hold back one room, one thing you offer, or part of a day while the team keeps working, block it out on the Calendar instead. See Calendar.

Changing somebody's standard week changes the roster ahead of it. Regular hours flow into the roster as many weeks ahead as you choose at the top of the Regular hours tab. When you edit somebody's standard week, the shifts already sitting on those upcoming weeks are re-made to match, and the save tells you how many moved. Three things are deliberately left alone:

• Today and anything past. It may already be worked, and paid.
• Any shift you have edited by hand. Once you change one day's hours, move it, or hand it to somebody else, it is yours, and no change to the standard week will overwrite it.
• Casual shifts and days off. They were never made from a standard week.

If a week you already published changes, publish it again. The save says when that has happened, and the roster keeps saying "Changes have been made. Re-publish to let them know" until you do. Re-publishing reaches only the people whose own shifts moved, so a change to one person's standard week does not email the whole team. See §7a-iv.

With auto-fill set to Off (manual), nothing is added or removed: the roster is yours to build, so saving a standard week leaves the upcoming weeks exactly as they are.

Availability warnings. The grid knows each person's stated weekly availability plus any date-specific casual exceptions (a casual marking a particular day off or open), and it flags a shift you drop on a time someone said they can't work, so you can rethink it or go ahead. Casuals set their date-specific availability with a per-business notice period you configure at Settings → Team.

7a-i. Somebody calls in unwell (personal leave)

You don't need them to fill anything in. Open their shift on the roster and press Record personal leave, then confirm. One action does the whole phone call:

• their personal leave is recorded on their behalf (under your business's own personal / carer's leave type, paid or unpaid by their employment type), marked as entered by you,
• their shift is cleared for that day, they drop off the kiosk's clock list, and their day closes to new bookings,
• any customer bookings with them that day are listed right there, each with a Reassign button offering only colleagues who genuinely have that time free. Moving several across different times or days? The link underneath opens their calendar day, where Move day refits the whole list for you,
• and they get one calm email saying it's recorded and there's nothing they need to do.

The paid personal leave then flows through to pay on its own: the Timesheets grid shows the day as LV with the hours it covers, the weekly total says "incl leave", and the payroll export carries it as its own earnings line (for example "Personal / carer's leave, 8.00") so your bookkeeper keys it at the right rate. A leave day pays the hours the roster knows about, the shift it displaced or the person's regular hours; a week you have adjusted by hand is never changed behind your back.

If they had already requested that day off, the button approves their request instead of double-recording it, and a day already covered by approved leave is left alone. It needs both the approve leave and manage roster permissions, so owners and managers have it out of the box.

7a-ii. Publish the week, and add a note to the team

When the week is ready, press Publish & notify team. A short panel opens before anything is sent, telling you how many people are on the roster this week; each of them gets an email with their own shifts, and nobody sees anybody else's.

Add a note to the team. Tick the box and write anything you would normally put in a separate email: "Hey team, here's the roster for the week, the coffee delivery moves to Tuesday…" It goes at the top of their email, above their shifts, exactly as you typed it. A preview underneath shows how they will read it before you send.

• Nobody sees the note in isolation. It also appears on the roster for that week and on each person's My work, so somebody who reads the app instead of their inbox still gets it. Anybody with no email address on their team card will only ever see it there.
• People with no shifts that week hear nothing unless you ask. When you add a note, a second tick offers to send it to the team members who are not on this week, which is what you want when the note is about a meeting rather than the shifts. They get the note on its own, with no shift list.
• The two emails read differently, and the preview shows both. The people on the week get "Your roster for 17 to 23 Aug", your note, and then their shifts. The people who are not on it get "Frank's note to the team, 17 to 23 Aug", headed A note from Frank, and their first line says plainly that they have no shifts this week before handing over to your note, so nobody is left hunting for shifts that are not there.
• Reuse last week's words with one press when the note is a standing message. It is offered as a button rather than filled in for you, so a week-old note can never go out by accident.
• Re-publishing re-sends, and replaces the note with whatever is in the box. Publish with the box unticked and the previous note is cleared.
• The note holds up to 2,000 characters. If you go over, the app says by how much and refuses to send rather than quietly cutting the end off.

7a-iii. On call: not rostered, but ring me

Somebody who is not working a day but is happy to be phoned if you get stuck goes on the roster as on call. It is not a shift: it is never hours worked, never reaches a timesheet, and never touches their pay.

To put somebody on call, press the + in their empty day, switch the top of the panel from Working shift to On call, and press Put on call. That is it. Nothing has to be set up first: it works for anybody on your team list, including people with no login at all.

• All day unless you say otherwise. Tick "Only for part of the day" and set a From and To if they are only around in the morning.
• It shows on the roster as a dashed On call marker in that day, so you can see at a glance who to ring on Saturday. Hover it and press ✕ to take it off.
• Nothing is added to the hours, theirs or the day's total.
• They are told when you publish, exactly like a shift: they appear on the re-publish list as "Sat 29 Aug added, On call". Their email marks the day "Sat, 29 Aug · ON CALL" next to the hours (or "All day"), with a highlighted box above the list that says "On call means you are not rostered on for that day, but we may ring you if we get stuck", so nobody reads it as a shift with the times missing. Their My work says the same thing.
• Somebody folded away as "not on this week" comes back the moment you put them on call, because they are now part of the week.
• Anyone who can build the roster can do it, so an owner, a manager, a supervisor, or whoever you have given the roster permission to.

On call is not the same as availability. Availability is a standing statement your team make about themselves in My work: which days they can work at all, and between what hours. The roster warns you when you drop a shift on a day somebody said no to, and it never blocks you. On call is you saying, for one day, that this person is your backup.

7a-iv. Changing a week the team already has

Publishing is the only thing that sends anything. Change a shift on a week you have already published and nobody is emailed on the spot. The roster says so, in orange, next to the button:

Changes have been made. Re-publish to let them know.

Press Re-publish and the panel lists only the people whose own shifts have changed, by name, with what changed beside each one, and a tick you can clear:

2 people have had a change since you published on 22 Aug. Only they hear from you. The other 7 people on the week are left alone.

☑ Murray Wells, Sat 29 Aug added, 8:30am to 1:00pm ☑ Sarah Kidd, Wed 26 Aug now 8:30am to 1:00pm

Nothing goes out until you press the button, and the button says exactly who it reaches: Publish & email 2 people.

Everything counts as a change, not just adding a shift: new times, a new day, a different role, handing a shift to somebody else (both people are listed), removing one, marking somebody off the day, and the bulk fills. Change something and change it back, and nobody appears on the list at all, because nothing about their week is different.

Clear a tick and that person is left out on purpose. Their row says so, and they stay on the list next time, because a change nobody has heard about is not finished. Use it when you have already rung them.

A note goes to whoever is being emailed, and the box says who. With one person on the list it reads "Add a note for Murray", and underneath, "Only Murray Wells will read this". So "Sorry Murray, I forgot you couldn't make it that day, so I have changed it" reaches Murray and nobody else. With everyone on the list it is the note to the team, as in §7a-ii.

Somebody with no login is listed but has no tick, because there is nowhere to send them anything. Their row says "No login yet, so you will need to tell them yourself."

They get a change in the app as well as by email: on the bell and on their phone if they have notifications turned on. That is the one that always arrives, which matters for casuals with no email address on their card.

"Send the whole week to everyone on the roster again" is a tick on the same panel, off by default, with the number on it. Use it when the week has changed a lot and you would rather the whole team had it fresh.

Nothing is sent for a week you have not published yet. While you are still building a roster, moving shifts around tells nobody. The first press of Publish is what starts the conversation, and it reaches everybody who is on.

7b. Clock in / out (staff)

Where staff clock in:

• From "My work" in the top nav (their own page, clock in/out + this week's hours + their roster), or
• From a paired tablet kiosk set up as a Staff kiosk. Setting one up is a QR you scan with the tablet's camera, see Kiosk (a tablet on the counter).

Worked time builds their timesheet, and who's currently clocked in shows on the dashboard (On shift).

Clock-in rules (Settings → the "Team" tab → Time clock, under Clock-in rules), these only bite where you use the Roster module:

• Only clock in with a rostered shift, no shift now → clock-in is blocked, the person is told why, and the attempt is logged for you (see attendance in §7d). Owners/managers can always clock in, just flagged if there's no shift.
• Clock-in opens N min before the shift starts.
• Late after N min grace, past that, the clock-in is recorded as late.
• Max shift length, used as a backstop for forgotten clock-outs.

On-site (GPS) check, optional. You can require staff to be at the workplace to clock in: turn on Location check on clock-in (Settings → Team, shown when the Roster module is on), pin your workplace and set a radius.

• A self-service clock-in from outside the radius is flagged on the timesheet, or blocked if you make the check required (the person is told how far off-site they are). Clock-outs are checked too, so an off-site clock-out is flagged for you.
• The kiosk is exempt, a paired tablet is already on site.

Kiosk identity, name vs PIN. On a shared kiosk, choose how a person proves who they are at Settings → Kiosk → "How staff clock in" (full guide: Kiosk (a tablet on the counter)):

• Tap your name, simplest, but a colleague could tap your name.
• Personal PIN, each person types their own PIN, so no one can clock a workmate in or out. Use this to stop "buddy-punching". PINs are set per-person on the same Kiosk tab (managers only), stored encrypted and never shown.

7b-ii. Breaks, and how one reaches the timesheet

The clock is start work / stop work. There is no "start break" button. So a break gets onto a timesheet one of three ways, and it is worth knowing which one your business is using, because it decides what people are paid.

1. Someone punches out and back in. The gap between the two punches is simply not worked time, so it is unpaid automatically with nothing to type. Coming back is treated as coming back: it is not recorded as a late arrival, your team is not told anyone was late, and it counts as one shift rather than two on the attendance figures.
2. You type it on the timesheet. Each clocked row has a break box in minutes on the Timesheets tab. Whatever you type is taken off the paid time for that row, and the change is recorded in your activity log with the old and new value. Do not use both at once. If somebody already punched out and back in, the gap is out of their pay, so typing those minutes in the box as well takes them off twice. The box is for the days nobody punched anything.
3. An automatic rule. On the Timesheets tab, open the settings control and turn on Unpaid breaks: "deduct N minutes from any shift longer than H hours". By default that rule applies only to rostered hours, not to clocked ones. A separate tick, Also apply to clocked time, extends it to the clock.

Before you turn on the automatic rule, read this. It deducts a break whether or not the break happened. If a busy Saturday means nobody got their 30 minutes, that rule still takes 30 minutes off their pay. An amount you typed for a row always wins over the rule, including a deliberate zero, so you can correct any day the rule got wrong.

Paid rest breaks are not this. Several awards give a short paid rest break as well as the unpaid meal break, and paid ones must not be deducted at all. The break box and the automatic rule are for unpaid breaks only, so leave paid rest breaks out of both.

Nobody outside the payroll seat sees a break figure. The break box is on the Timesheets tab, which needs the timesheets permission. A casual who clocks in at the tablet and has no login never sees what was deducted, so if you type breaks in by hand it is worth telling people that is how it works.

7d. Attendance & auto clock-out

• The Timesheets tab summarises the week's punctuality, on-time %, who was late (and by how long), no-shows (a rostered shift with no clock-in) and blocked attempts. Punctuality counts one shift per shift: someone who punched out for lunch is one arrival, not two, so taking a break never flatters or damages their record.
• Forgot to clock out? If someone forgets, the app closes it for them, at their rostered shift end plus the auto clock-out grace, or the max shift length if they had no shift. It's marked auto clock-out · check, left unapproved for you to confirm, and never paid automatically. The grace is set at Settings → the "Team" tab → Time clock → "Forgot to clock out?".

7c. Approve & export timesheets

1. Open the timesheets view.
2. Review hours; adjust any day that needs it (below).
3. Approve week when correct.
4. Export the approved hours for payroll, as a CSV, or as a Printable summary: one page per person to read from while you enter hours into Xero, QuickBooks or MYOB.

7c-i. Rostered vs clocked, and the ⚠ flags

Each person's row shows what they were rostered, what they clocked, and what the week will pay. A day where the clock disagrees with the roster carries a small ⚠. Click that day to answer it, one click each:

• Rostered pays the rostered hours for that day (the extra time was not work, or the early finish is forgiven).
• Clocked pays what the clock recorded (the extra time was real, approved work; a late start is docked).
• Or type any figure in between.

Answering a day clears its flag. The two buttons on the row (Rostered / Clocked) do the same thing for every day of the week at once, and the week's total is always the sum of its days. Reset puts the week back to the default (the clock, for people who clock).

7c-ii. Round to roster (stop tidying 2-minute differences)

If your team clocks a few minutes either side of their shift and you just pay the rostered time, turn on Settings → Round to roster (on the timesheets view). A punch within the grace (10 minutes unless you change it) of its rostered start or finish counts as the rostered time automatically: nothing to click, no flag, and 3 minutes early or late never changes anyone's pay in either direction.

Differences bigger than the grace are real, so they pay the clock and carry the ⚠ flag for you to accept, decline or adjust as above. The attendance record is untouched either way: the punch is stored exactly as it happened, and late arrivals still show as late. Rounding changes what is paid, never what is recorded.

You can always see and pay the real minutes. Open a person's row and each punch is listed with the times exactly as clocked next to the hours it pays, so a 9:00am to 5:06pm day shows those times beside its 8h 0m. Hovering the day on the grid says the same thing ("clocked 8h 6m, rounded to 8h 0m"), and clicking that day offers Clocked 8h 6m as a one-click choice if you would rather pay the extra six minutes. Rounding is a default, never a lock.

Your payroll system gets the paid hours. The CSV, the printable summary, the Xero timesheet push and a locked pay period all read the same figures as the screen, so what you approve is what payroll receives. A week you have already locked keeps the hours it was locked with: changing this setting afterwards cannot move a finalised week, and if the live hours and the frozen ones drift apart the screen says so and asks you to unlock and re-lock.

What the export is (and isn't). This is an hours export for manual entry or CSV import. HappierBiz never runs pay or lodges STP; your payroll software stays the source of truth for pay. One exception saves the retyping, below.

7c-iii. Send timesheets straight to Xero payroll (optional)

Xero Payroll has no timesheet file to import, so instead HappierBiz sends the hours in over the same Xero connection as draft timesheets, one per person for the pay period, for you to approve in Xero.

Set up, once:

1. Set your payroll system to Xero (the Timesheets settings menu on this page), and connect Xero at Finance → Accounting export (see Accounting export, 7d). If you connected before this existed, click Connect Xero once more so it can add payroll access; your settings are kept.
2. Go to Time & pay → Pay prep & export. In the Send timesheets to Xero card, match each person to their Xero employee (names that match are suggested for you) and your pay categories to Xero earnings rates. Ordinary hours is the only one you must set; weekend and public-holiday hours fall back to it.
3. Select Save matches.

Each pay run: finalise (lock) the weeks, then press Send N timesheets to Xero. You get a line per person saying what happened.

What to expect:

• Always a button, never automatic. Hours never ride the six-hourly accounting sync, because pay should only move when you decide the period is finished.
• Locked weeks only. If a week isn't finalised the whole run is refused, and if one person's hours changed since locking, only they are held back, by name.
• Drafts. Nobody is paid until you approve the timesheet in Xero, and re-sending updates the same draft rather than adding another. A timesheet you have already approved in Xero is left alone.
• Paid leave is not on it, by design. Leave is entered in Xero as leave, not as timesheet hours, so it can't be paid twice. ⚠️ Which means the other half of the job is yours: after the send, the card lists Leave still to enter in Xero, naming anyone with approved leave in the period and how many hours. Book that leave in Xero (Payroll, then Leave) or they are paid for the days they worked and nothing for the days you approved them to be away.
• The period must match their Xero pay calendar. If it doesn't (say they're on a fortnightly calendar and you sent a single week), the line says so and names the fix. Weekly, fortnightly and four-weekly calendars are supported; monthly is not.
• Needs Xero Payroll, which is a paid add-on in Australia, with a pay calendar and employees already set up in Xero.

Two-step sign-off (optional). If your business has turned on two-step approvals, a submitted timesheet takes two approvals: the submitter's direct manager confirms the hours first (this writes nothing to pay), then a Payroll Officer does the final sign-off, and only then do the hours flow into the export. A timesheet part-way through shows a "Payroll sign-off" tag. Turn it on and read the full flow in Approvals & payroll sign-off. With it off (the default), approving a timesheet is a single decision, exactly as described above.

Pay public holidays. A toggle in the timesheet settings: when it's on, a public-holiday closure pays the rostered hours, and public-holiday hours are tagged separately on the timesheet and the export, so you can apply penalty rates in payroll.

7f. Finalise (lock) a pay period

Once a week's hours are right, you can finalise (lock) it. Locking freezes that week's payable snapshot, so a later change to a setting or the roster can't quietly move numbers you've already signed off, and it blocks edits to that week's overrides, breaks, approvals and TOIL. The week shows as locked with who locked it and when.

• Finalise & export locks the whole period you choose in one go. Set the Period (this week, fortnight or four weeks) and click Finalise & export: it lists every week with its people and hours so you can check what's being frozen, then freezes them all and downloads one file for the span. You no longer have to lock each week separately.
• If a week still has hours waiting for approval, finalising stops and tells you which weeks to approve first, so you never freeze someone's hours at zero. Approve them in the Timesheets tab or the Approvals inbox, then finalise.
• If payroll needs to correct a locked week, unlock (re-open) it, fix it, and finalise again.
• Exporting records an exported-at stamp on each week, so a re-export is visible and you can see the week was already sent to payroll.
• Finalising, re-opening and exporting all need Edit / approve timesheets, and each is written to the business Activity Log.

7f-ii. Set up the MYOB export so it imports cleanly

MYOB only accepts a timesheet row if its pay code (the Activity ID) and the employee code already exist in your MYOB company file, spelled the same, in capitals, up to eight characters. HappierBiz can't know your MYOB codes, so it gives you a quick one-time setup and sensible defaults.

1. Choose MYOB in the Payroll dropdown on the Finalise & export card, then open MYOB pay codes.
2. Each pay type (ordinary, overtime, public holiday) and each leave type you use shows an editable code, pre-filled with a tidy default (for example Annual leave becomes ANNUAL). Change any to match the exact pay code you have in MYOB, then Save codes. Copy list for MYOB copies the whole list so you can set the same codes up on the MYOB side.
3. Employee codes. The panel lists everyone in the file with the code they'll export as, and flags anyone matched only on their surname (which can go wrong) or sharing a code with someone else. For a reliable match, put each person's MYOB Card ID in their Team profile (Team, open the person, the employee ID field); the export uses that when it's set.
4. In MYOB, turn on timesheets, make sure each pay code above exists and is linked to each employee, then import via File, Import Data, Timesheets and map the columns. MYOB imports the rows that match and lists any it can't, so you can fix a code and re-import.

Note: only MYOB AccountRight (desktop or browser) can import timesheets; MYOB Business online can't, so there you key the hours in by hand from the file.

7e. Time in lieu (TOIL)

TOIL is a per-person balance of time owed for extra hours worked: positive = banked (you owe them time), negative = used. The running balance sits in the balances panel on the Leave page (Time off & shifts → Leave), and each staff member now sees their own balance in My Work.

Banking time (four ways):

1. Log it by hand, in the balances panel, pick a person, enter the hours and a note. This is the quick "you worked back two hours on Tuesday" case.
2. Bank a timesheet variance, on a clocking person's timesheet row, the Bank to TOIL button banks the difference between clocked and rostered hours.
3. Staff bank it on their own timesheet, when a set-hours person confirms their week, they can tag part of a day Bank to TOIL; it lands when you approve the week.
4. Auto-accrual (optional), turn on "Auto-bank over-roster hours" in the timesheet settings and, whenever you approve a timesheet, any hours above the roster that weren't tagged as overtime bank to TOIL automatically. Your approval is the gate, nothing accrues without it.

Using time (taking a TOIL day off). Staff take TOIL as time off by requesting leave of the "Time off in lieu" type (or whichever leave type you choose in the TOIL settings). Approving that request draws the balance down by the hours off, blocks the roster and bookings for those days like any leave, and emails the staff member. Cancelling it hands the hours back. Staff can't request more TOIL than they have, the app stops the request with the exact figures.

Guardrails. Set an optional cap so a balance can't grow past, say, 40 hours, and the app won't let TOIL be overdrawn (used below zero). Every change is logged in the business Activity Log.

8. Examples

• Beginner (café): roster Floor and Kitchen for the week; staff clock in; approve and export Friday.
• Real-world (gym): trainers' regular patterns auto-fill; add a casual to cover a sick call; a public-holiday closure blocks the day.
• Advanced (multi-role venue): roster across Floor/Parties/Setup roles, fix a miskeyed clock-out on the day it happened, then export approved hours.

9. Reports & exports

• Timesheets per week, approvable.
• Payroll CSV export of approved hours (hours only, for manual entry or CSV import into your payroll software; no pay runs or STP from here). With the Xero connection, the Pay prep & export page can instead send the period to Xero payroll as draft timesheets.
• Printable summary, one page per employee, to read off while entering hours into Xero, QuickBooks or MYOB. Public-holiday hours are tagged separately when Pay public holidays is on.
• On shift (clocked-in now) shows on the dashboard.

10. Common mistakes

• Exporting before approving, approve the week first so payroll gets final numbers.
• Forgetting closures, mark business closures so days aren't rostered or counted.
• Using a closure to hold back one room, that shuts the whole business for the day and tells the roster you are closed. Block it out on the Calendar instead, which stops the bookings and leaves the team working.
• Editing a pattern vs a single day, use a day-off override for one-offs; change the pattern for ongoing changes.
• Assuming a standard-week change only affects future weeks you have not looked at yet. It reaches every upcoming week that was auto-filled, which is the point. If you want one week different, change the shifts on that week instead: a shift you edit by hand is never touched again by the standard week.
• Expecting a note to reach the whole team on its own, the roster email goes to the people who are ON the week. If the note is about a meeting or a change everybody needs, tick the second box so the people with no shifts get it too.
• Ignoring leave clashes, approved leave blocks bookings, but check the roster reflects who's actually off.
• Turning the Roster module off to stop clocking, that's the wrong switch. The clock has its own toggle at Settings → the "Team" tab → Time clock. Turn that off; leave the Roster module as you need it.
• Paying an auto clock-out without checking, auto-closed entries are an estimate. Review and approve them before the payroll export.

11. Troubleshooting

12. Error messages

Roster edits and approvals confirm inline (e.g. "Week approved"). The payroll export is disabled until there are approved groups to export.

Related: Approvals & payroll sign-off · Leave · Shift requests · Calendar · Kiosk (a tablet on the counter)