You need to sign in as an administrator.
Loading…
- 1 · Period
- 2 · Resources
- 3 · Entries
- 4 · Drafts
- 5 · Finalize
Finalize the pay run for …. Two buttons — ABN finalizes the RCTI bills + locks entries with paidPayrollRunId; PAYG does the same for pay runs + payslips. Each side runs independently so a failure on one doesn't roll back the other.
ABN — RCTI bills
PAYG — Xero pay run
Drafts for …. ABN section composes RCTI bills (pay rate per PO segment); PAYG section composes pay runs (ordinary hours × rate).
Composing…
ABN — RCTI bills
No ABN drafts.
PAYG — Xero pay run + payslips
No PAYG drafts.
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 J48 RCTI draft.
Eligible resources for …. ABN engagements bill via RCTI; PAYG engagements via Xero pay run. 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 in this period.
ABN (RCTI)
PAYG (Xero pay run)
Pay periods are per-engagement: ABN engagements follow the engagement's pay cycle + cycle-start; PAYG engagements use the Xero pay calendar period. To keep things simple, the admin picks a single date range and the wizard groups eligible resources by their respective period mapping in step 2.