You need to sign in as an administrator.
Loading…
- 1 · Type
- 2 · Calendar
- 3 · Period
- 4 · Resources
- 5 · Entries
- 6 · Drafts
- 7 · Finalise
Finalise the … pay run for ….
ABN — RCTI bills
Finalising creates the RCTI bills and locks every contributing entry with paidPayrollRunId. No undo.
PAYG — Xero pay run
💸 Reimbursement-only pay run (Route A). Confirming creates a new draft pay run in Xero for this person's calendar — even if a draft already exists there (you reconcile the two in Xero) — and puts only the reimbursement on the payslip. The claim flips to reimbursed once the run is posted in Xero.
🧪 Pre-flight rehearsal. The run's checks are made for real and the result is shown here. Nothing is posted — no payslip line is written whether the checks pass or fail.
Drafts for ….
💸 Reimbursement-only run (Route A): only the chosen expense claim is on this payslip — no hours, allowances or public-holiday top-ups. Those stay for the next scheduled run.
Composing…
No drafts.
ℹ️ These are a preview — the RCTI bills are created in Xero when you finalise (step 7). Nothing exists in Xero yet, so there are no links to open here.
Review entries for …. Resource-submitted entries are read-only here (lock state already enforced via G29). RCTI engagements get an "Add entry" form below the table — those are the hours the client sent via PDF/email; admin enters them now so they roll into the RCTI draft.
Eligible … resources for …, on the chosen pay calendar. Engagements with the client_supplied_rcti flag are always eligible (admin enters hours in the next step) — others need at least one entry in the period.
No candidates on this calendar in this period.
Pick the pay period to process for the chosen calendar. The default is the period with the next upcoming pay date; adjust as needed.
Which payroll are you running? ABN and PAYG are processed as separate runs — pick one, then its calendar.