This is the task, start to finish. For what every button and tab on the page does, see Payroll Hub — this page is the walkthrough, that one is the reference.
Where to start — Payroll & Billing → Payroll Hub. The progress strip across the top is the list below. It lights up as you go, the highlighted step is the one you're on, and clicking any step jumps straight to it.
Before you start — check the pay cycle selector at the top is showing the period you mean to pay. Everything on the page is scoped to it, except Ready to process, which lists draft runs in every cycle.
The cycle, start to finish
- Timesheets submitted (crew) — crews enter their own days. The count sits under Awaiting Approval.
- Approvals complete (supervisors) — supervisors sign off in Team Approvals. This step won't tick while anything is still Submitted.
- Pay setup resolved (you) — everyone with hours needs a pay level. Missing ones show under Exceptions.
- Work collected (automatic) — nobody builds a pay run. The first approval in a cycle opens Run #1, and every approved timesheet after it joins that run by itself, usually within the hour. Leave and work-order days join the same way.
- Runs reviewed (you) — open the run, read it line by line, then click Mark Reviewed. Travel and nights away are confirmed here. If anything is collected or changed after you review, the run asks to be reviewed again before it will finalise.
- Runs finalized (you) — Finalize Pay Run freezes the figures. It does not pay anyone. Finalising before the cycle's last day asks you to acknowledge that; anything approved afterwards goes into a later run for the same cycle.
- Processing recorded (you) — download the Worksheet (CSV) or export the payroll file, key it into your payroll software, then click Record as Processed and enter the pay run reference from MYOB. The cycle is done when this is recorded.
Late work, held pay and amendments
Late work gets its own run. A timesheet approved after Run #1 is finalised opens Run #2 for the same cycle, and payroll is notified once. The Ready to process panel on the Hub lists every open draft, oldest first, so a late run for an earlier week is finalised in the same sitting as this week's. Run #2 only pays what Run #1 did not — a day, a salary or a travel allowance is never paid twice.
Hold what must not be paid yet. Holds replace removing timesheets from a run:
- Hold from pay on a timesheet keeps that one day out of every run until someone releases it — a disputed day, a missing docket.
- Hold an Employee on a draft run keeps a person's period pay for the cycle (salary, day rate, travel allowances) out of every run in that cycle — the only way to hold back someone who files no timesheet.
A hold needs a reason, and holds never block finalising — the rest of the crew is paid as normal. Release a hold and the pay joins the cycle's draft run automatically.
Open amendments hold their original back. While a revision of an approved timesheet is in progress, the original stays out of every run. If nobody is going to finish the amendment, Discard revision draft puts the original back into its run. A rejected amendment does the same on its own.
Work from before automatic pay runs started is never paid automatically. It is listed under Before automatic pay runs on the Hub until you have marked each day as processed externally, confirmed unpaid or unresolved.
Finding one person's timesheet
Two places, and they answer different questions.
| Where | Scope | Use it for |
|---|---|---|
| Payroll Hub → Timesheets tab | the selected cycle only | What's holding this run up? |
| Payroll & Billing → Timesheets | full history, all filters | Find me that timesheet |
The standalone Timesheets page has one-click tabs for Not in a pay run and Flagged, so you don't set the same filters every week.
Search takes the name you actually use. Typing Milly finds Amelia Lucre — you don't need the full name off their employee file. The Employee filter lists the short names too.
Reading the hours on a timesheet
Click View on any row. The Hour Buckets panel splits the day by what each hour is paid at. Every hour worked lands in exactly one bucket, and the buckets always add up to the total hours.
| Bucket | Typical rate | When it fills |
|---|---|---|
| Ordinary | 1.0x | Standard hours on a weekday |
| OT 1.5x | 1.5x | Past the ordinary cap on a weekday |
| OT 2.0x | 2.0x | Past the time-and-a-half cap |
| Saturday | 1.5x | Saturday work, up to the tier set on the pay level |
| Sunday | 2.0x | Any Sunday work |
| Public Holiday | 2.5x | Any hours on a gazetted holiday |
| Night OT | varies | Overtime on a night shift |
| Onsite | — | Total hours on site. Not a pay rate — a coverage figure |
Rates come from the employee's pay level, so check there if your workspace differs.
A Saturday reads across two buckets. Seven hours on a Saturday shows as 2.00 under Saturday and 5.00 under OT 2.0x — the first two hours at time-and-a-half, the rest at double time. That is the shift priced correctly, not a split that has gone wrong.
Below the buckets, Travel & Allowances shows how the person got to site, what they claimed, and any note they left. If payroll has changed someone's travel answer, it is badged payroll override with the reason recorded.
When the Hub says blocked
A red panel means the cycle can't go to payroll yet. Resolve blockers takes you to the list.
- No pay level — someone worked without one, so no rate, template or allowance can resolve. Assign a level, or set them excluded from payroll if they're paid outside this system.
- Unconfirmed nights away — a distant job needs travel-in and travel-out dates before the nightly allowance can be priced. Confirm them in the run's travel review.
- Unmapped export category — a pay item your payroll software won't recognise. Fix it in payroll settings before exporting.
Most blockers can be acknowledged at finalise, but not all. Unresolved nights away cannot — each one means somebody would be paid the wrong amount. Anything you do acknowledge is recorded on the run.
Flagged is not blocked. A flag means worth a look — a Sunday, a day over twelve hours, or a work entry with no project against it. Review it and carry on.
"Not collected" should be zero. Approved work normally reaches its run within the hour. If a timesheet stays under Not collected, check it isn't held or waiting on an amendment, then contact support.
Connected pages
- Payroll Hub — the full reference for the page, its permissions and every action
- Team Approvals — where supervisors sign timesheets off
- Subcontractors — subbie work logs and RCTIs, which are paid separately