STP Overview

Team → STP is where you check each employee’s Single Touch Payroll (STP) finalisation status, run year-end finalisation, and review the full STP filing history for your business.

Pay-event STP submissions are lodged automatically when you click Mark as Paid & Lodge STP on each pay run. This page is for year-end finalisation, YTD corrections, and submission status review.

Before you lodge: SSID & Access Manager (one-time)

Before Rebased will accept production STP lodgement for your business, you must complete a one-time ATO authorisation. You don’t need an Ozedi account — Rebased registers your ABN with Ozedi via API on your behalf. The only step you have to do yourself is the ATO Access Manager nomination, because the ATO requires that to be done by you — specifically the business’s principal authority (typically a director or public officer) signing in with their own myGovID/myID, or a registered tax/BAS agent acting for the business.

1. Register with Ozedi in Team → Settings → STP SSID & ATO Access Manager — one click, Rebased calls Ozedi for you and retrieves the SSID for your ABN.
2. Notify the ATO yourself in Access Manager  that your ABN uses OZEDI as its Sending Service Provider, using the SSID Rebased shows you.
3. Confirm in Rebased by ticking the Access Manager checkbox on the same settings card.

If this is incomplete, this page shows a Needs Attention banner and pay-event lodgement is blocked. See Team → Settings → STP SSID & ATO Access Manager for the full walkthrough.

What you’ll see

Column headers

Two financial years are shown side-by-side. A small chip tells you where each year is in its lifecycle:

• closed DD Month YYYY (mint) — the year has ended and is ready for finalisation.
• current (lavender) — the year is still in progress. You can still finalise mid-year if required (e.g. all staff have left), but the usual pattern is to wait.

The columns automatically advance on 1 July each year — you don’t need to configure anything.

Status per employee

Each employee row shows one of the following states per FY:

Bulk actions

Bulk actions are selection-based. Tick the employees you want to act on, or use the header checkbox to select all visible/applicable rows, then open Selected actions:

• Adjust YTD + finalise selected for FY 20XX-XX for current- or prior-FY corrections that should be lodged in one STP Update Action.
• Finalise selected for FY 20XX-XX for a selected subset of pending employees.
• Un-finalise selected for FY 20XX-XX for selected prior-FY employees that need to be reopened in one Update Action.

How to finalise

1. Open Team → STP.
2. Wait for the current chip to switch to closed on 1 July. (You can finalise mid-year — see the warning in the confirmation modal — but most businesses wait for the year to end.)
3. Click Finalise on an individual row, or tick the employees you need and choose Finalise selected for FY 20XX-XX from Selected actions. To finalise everyone shown, use the header checkbox first.
4. Confirm in the modal. The copy adapts to whether the FY is closed (standard) or still current (cautionary).
5. The ATO receives each employee’s cumulative year-to-date totals with FinalI=true. No wages, tax, or super are paid — this is purely a finalisation event.
6. The row flips to Submitted, then to Finalised once the ATO acknowledges it (typically within a minute).

Adjusting YTD

Use Adjust YTD when the ATO needs corrected year-to-date figures and no wages or super are being paid.

For one employee:

1. Open Team → STP.
2. Find the employee and financial year.
3. Hover over the row and select Adjust YTD.
4. Enter the corrected YTD values. Rebased calculates the deltas to lodge.
5. Tick Mark this payee as finalised if the same Update should also mark the employee tax ready.
6. Enter a reason and lodge the Update.

For multiple employees in one Update:

1. Open Team → STP.
2. Tick the employees you want to include.
3. Open Selected actions and choose Adjust YTD + finalise selected for FY 20XX-XX for the financial year you are correcting.
4. Enter signed deltas for each selected employee:
   • Gross delta increases or decreases STP gross YTD.
   • PAYGW delta increases or decreases STP withholding YTD.
5. Keep Mark selected payees as finalised checked if they should become tax ready in the same Update.
6. Enter a reason and select Lodge one STP Update.

Use positive values for increases and negative values for reductions. For example, enter 100.00 to increase gross YTD by $100, or `-100.00` to reduce it by$100.

YTD Updates are no-payment events. They do not create a pay run, pay wages, create journals, or remit super.

Income Stream Changes

STP history is tied to the employee’s payroll identity and income stream. If a Working Holiday Maker (WHM) becomes a Salary and Wages (SAW) employee after payroll has already been lodged, use Team → Team Members → [member] → Pay & Tax → Transition to SAW before creating future pay runs.

Rebased preserves the historical WHM stream and uses a new STP payroll identity for future SAW pays, so the ATO receives the right year-to-date amounts for each stream.

Re-finalising

Sometimes you need to re-send a finalisation event. Common reasons:

• Year-to-date figures were corrected after the first finalisation.
• A late adjustment pay went out after you thought the year was closed.
• The ATO asked you to re-send.

How to re-finalise:

1. Hover over an employee’s row where the FY column shows Finalised.
2. A small ↻ Re-finalise link appears next to the Finalised pill.
3. Click it. A confirmation dialog opens asking for a reason — this is required (minimum 4 characters) and is saved in the audit trail.
4. Click Re-finalise anyway to lodge a fresh finalisation event.

The ATO treats the latest final event as authoritative (“last event wins”), so the new figures will replace the earlier ones. No special process is needed on your side — the employee simply sees the updated figures at tax time.

If none of the reasons above apply, you probably don’t need to re-finalise. The Re-finalise link is intentionally subtle so it doesn’t get clicked by accident.

Un-finalising

Use Un-finalise when a finalised prior-year Income Statement needs to be reopened before lodging a corrected finalisation. This flips the selected employee’s ATO status back to “not tax ready”; it does not pay wages, create journals, or remit super.

For one employee, hover over a Finalised prior-FY row and select Un-finalise. For several employees in the same prior FY, tick the rows and select Un-finalise selected for FY 20XX-XX so one STP Update carries all selected payees. You must enter a reason, which is saved in the audit trail.

Retrying a rejected finalisation

If the ATO rejects a finalisation, the cell shows a Retry button. Hover over it to see the ATO’s rejection reason. Fix whatever the ATO flagged (usually on the employee’s profile — e.g. missing address, wrong TFN), then click Retry. The system cleans up the rejected record and lodges a fresh event.

Filing history

Below the employee table, every STP submission your business has ever lodged is listed newest-first, with:

• The pay period covered.
• The number of employees in the event.
• Current status — Queued, Filed, or Error.
• The submission timestamp.

Click a row to open the associated pay run (for regular pay-event submissions).

Migrating from another payroll provider mid-year?

Have your previous provider finalise year-to-date payments in their system before your first Rebased pay run. Employees will then receive two Income Statements for the transition financial year — one from each provider — which they combine on their tax return. Rebased only finalises the YTD figures it has in its own records.

Related pages

• Payroll — pay run lifecycle, Pay & Lodge (where STP is lodged automatically with wages).
• Team Members — employee profiles (make sure addresses, TFNs, and employment dates are complete before finalising).
• Superannuation — super contributions and fund management.