Team + AU Payroll (Region Example)
This page shows how region-specific docs look when the core Team module intersects with AU payroll compliance.
Applies to
- Region:
AU - Audience: Payroll admins, finance operations, support agents
- Related core page: Team
What is different in AU
Compared to a generic Team setup, AU payroll requires role and process controls for:
- STP-related payroll actions (STP is lodged automatically when wages are marked paid via Mark as Paid & Lodge STP on each pay run; retry from the ATO Reporting card if lodgement fails)
- distinction between pay-event STP lodgement (automatic with wage payment) and EOFY wrap-up — EOFY tells the ATO a year’s figures are complete; it’s done from Team → STP as a one-click action after the last pay for the year is processed (no pay run required), and re-finalisation is available via a hover affordance on already-finalised rows
- superannuation-related workflows
- AU-specific employee/payroll field handling
- employment types Full-time / Part-time / Casual only — contractor / labour-hire / voluntary-agreement payroll and STP (VOL/LAB) are not supported
- in-service leave cash-out handling from Team → Leave → Cashouts, imported into draft pay runs and reported as STP Paid Leave Type C
- manual Leave & Cash-Out pay-run rows for payroll-only leave adjustments; these use the same payroll/STP/balance pipeline but do not create leave requests or calendar entries
- salary leave taken as a salary carve-out with the rate locked to the salary-derived hourly rate, while salary cash-out remains extra gross pay
- assistant-assisted pay item editing on draft pay runs: the in-product assistant resolves the correct STP code and super treatment and opens the pay item editor pre-filled, but the admin confirms with Save (see modules/team/payroll → Payroll assistant)
- final-pay termination handling through a draft pay run, including cessation details, unused leave payout, lump sums, ETP rows, and separate Remove from Business access removal
- mid-year payroll migration: the previous payroll provider must finalise STP before the first Rebased pay run; Rebased starts from zero and reports only Rebased-paid wages, so employees may see separate Income Statements for the transition year. Employee start date remains the actual employment start date, not the Rebased migration date
- opening leave balances: these are for payroll leave tracking only and do not update ATO/STP YTD or Income Statements
- duplicate employee record zero-out: restricted to accidental Rebased-reported duplicate records only; do not use zero out STP record for migration, normal corrections, or changing Payroll IDs
See Australia → Team → Payroll for the end-user flow.
V1 STP scope: The product registers four income types (SAW, CHP, WHM, SWP with full descriptions in-app) and the reporting components described on that page (including RESC, child support, and RFBA). Rebased does not migrate previous-provider Payroll IDs or BMS IDs. STP is lodged automatically with each wage payment — no separate lodge step.
Suggested support flow
- Confirm the customer business region is AU.
- Confirm the user has payroll-relevant access.
- Validate whether the issue is Team permissions vs payroll data/compliance.
- Route to payroll technical review if compliance behavior appears incorrect.
Common issues
Issue: User can access Team but not payroll actions
- Symptom: User appears active in Team settings but payroll tasks are unavailable.
- Likely cause: Role/access scope does not include payroll-sensitive actions.
- Resolution: Review Team access settings and payroll-specific permissions for AU context.
Issue: Payroll setup fields do not match expectation
- Symptom: Customer expects fields/process from another region.
- Likely cause: Region-specific AU payroll requirements differ.
- Resolution: Confirm AU workflow and follow AU-specific payroll guidance.
Escalate when
Escalate if:
- AU payroll compliance behavior differs from expected production behavior,
- STP/super-related actions fail consistently,
- role permissions and payroll outcomes conflict across screens.
Last updated on