cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Intuit

End of Financial Year Processing using STP - Frequently Asked Questions

Section 1: Configurations

If your business consists of all closely held employees, you are able to delay STP reporting until the 20/21 Financial Year. Until then, you are not required to enable STP and report STP events. However, once you employ a new employee who is not closely held, you MUST start reporting STP for that one employee. 

 

To learn more about closely held employees, refer to this article.

Employers that are exempt from fringe benefits tax under section 57A of the Fringe Benefits Tax Assessment Act and have enabled it in the ATO Settings under Payroll Settings will now be provided with an additional setting. This setting deals with separating entertainment-related fringe benefits from other fringe benefit amounts.

As part of STP reporting, the data transmitted to the ATO separates reportable fringe benefits amounts into exempt and non-exempt amounts. 

Specifically, a separate single grossed up cap of $5,000 applies to fringe benefits that are salary packaged meal entertainment and entertainment facility leasing expenses. 

If employees are eligible, you must configure the business settings to allow separate reporting of RFB amounts.

To enable separate reporting:

  1. Navigate to Employees in the left hand menu.
  2. Select Payroll Settings, then ATO Settings.
  3. In the ATO Settings, select Yes under Are employees entitled to a separate cap for salary packaged entertainment benefits as per section 6.5 of the Fringe Benefits Tax legislation?
  4. Select Save.

Employees completing a Tax File Declaration Form have to specify what loans (if any) that they have:

  • Higher Education Loan Program (HELP)
  • Student Start-up Loan (SSL)
  • Trade Support Loan (TSL)
  • Student Financial Supplement Scheme (SFSS)

From 1 July 2019, HELP, SSL, TSL, SFSS will be consolidated under one name - Study and Training Support Loan (STSL) and one tax table. This change applies to all new and existing employees.

On pay runs with a date paid before 1 July 2019, the Withheld Amounts column is broken down into PAYG, SFSS and Help. However, after 1 July 2019, the Withheld Amounts column is broken down into PAYG and STSL. This change is also reflected when generating payroll reports and pay slips.

Section 2: Checklist before creating a Finalisation Event

Ensure Allowances are set up correctly (if you have allowances)

  1. Select Employees on the left menu.
  2. Select Payroll Settings, then select Pay Categories.
  3. Select the pay category name of your allowance.
  4. Select the Payment Summary Classification drop-down menu.
  5. Ensure that the allowance is allocated to the correct Payment Summary Classification.
  6. Select Save.

Ensure Salary Sacrifice Super Deductions (RESC) are reported correctly

It is essential to ensure that the Reportable Employer Super Contributions (RESC), otherwise known as Salary Sacrifice Super, is set up correctly, otherwise the employee YTD amounts will be incorrect when reporting to the ATO and the employee may be requested to owe money to the ATO.

To conduct an audit of RESC payments recorded for the financial year, run a Deductions Report and a Super Contributions Report, then compare the two for discrepancies.

  1. Select Employees from the left menu.
  2. Select Reports, then select Deductions Report.
  3. Enter the date range of the financial year, then select the Deduction Category.
  4. Select Run Report.
  1. Select Employees from the left menu.
  2. Select Reports, then select Super Contributions.
  3. Enter the date range of the financial year, then select Contribution Type to Salary Sacrifice.
  4. Select Run Report.

Compare the total amounts between both reports. If they don’t match, identify where the differences lie. The way to fix the differences depends on whether the amount comes from Opening Balances or from within a pay run.

  1. Select Employees on the left menu.
  2. Select the employee’s name, then select Opening Balances.
  3. Select Deductions, and ensure the Include on payment summary as RESC option is ticked.
  4. Select Save.
  1. Select Employees on the left menu.
  2. Select New Pay Run.
  3. Select Create.
  4. Select the name of the employee affected, then select Actions.
  5. Select Make Deduction, then enter the correct adjusting amount.
  6. Select Save.
  7. Select Finalise Pay Run.
  1. Select Employees on the left menu.
  2. Select Reports, then select Pay Run Inclusions Report.
  3. Check if the Salary Sacrifice Super (Pre-tax) amount is paid to the Super Fund. If not, follow the steps here to change the Pay Run Inclusion settings.

Ensure you have finalised all pay runs for the Financial Year

If a pay run is not finalised, it will not be reported to the ATO. If you lodge your finalisation event before finalising all pay runs for the financial year, you will then need to lodge an amended finalisation event so that the correct YTD figures are reported to the ATO.

If the pay run (normal or ad-hoc) relates to paying an employee or adjusting their pay, it must be finalised in order to be reported via STP.

What to do with failed STP events before commencing the Finalisation Event

Best practice is to ensure all pay events are successfully lodged before lodging subsequent events. However, for the purpose of lodging the finalisation event, it does not matter if all prior pay or update events have not been successfully lodged, as earnings shown in the Finalisation event are calculated from finalised pay runs, not just successfully lodged STP events.

Section 3: Should I lodge a Payment Summary or a Finalisation Event?

If you have lodged STP events during the financial year, you MUST lodge a finalisation event. DO NOT lodge payment summaries.

Doing both will duplicate the data to be reported to the ATO. However, here are some exceptions to this rule.

We only started reporting STP mid year. Do we still need to process a finalisation event?

Once you start reporting successfully through STP, you must also complete a finalisation event and NOT generate payment summaries/payment summary annual report (PSAR) as payroll data sent to the ATO will be duplicated. 

Also, STP events report YTD data to the ATO. For example, if you have only started reporting through STP from February 2019, but processing pays since the start of the Financial Year, that first STP event includes the payroll data of each employee since 1 July 2018. However you need to be aware that pay events only include employees who were paid in that particular pay run you are lodging.

If you have employees paid at the start of the Financial Year but have not been paid since lodging events through STP, create and lodge an Update Event prior to completing the Finalisation Event. The Update Event captures data of all employees paid in the Financial Year (who have not been marked as Is Final in an STP event).

We have not been reporting through STP during the financial year but want to process a finalisation event (ie STP end of year process). Is this possible or do we need to lodge an STP event first before lodging a finalisation event?

You can lodge a Finalisation Event if you have not been lodging STP events throughout the year. As long as you have registered for STP and have finalised pay runs for the Financial Year, you can lodge a Finalisation Event.

Note: If you do this, do not also issue payment summaries and lodge a PSAR with the ATO, as this will double up your data.

We only started reporting STP mid-year and had previously processed termination pays. Will the terminated employees appear in the finalisation event?

Your terminated employees will show up in the Finalisation Event if you have not lodged an Update Event prior to the Finalisation Event. 

However, if you have lodged an Update Event, the terminated employees will not show up in the Finalisation Event, given that they were marked Is Final in that Update Event. The Is Final signifies to the ATO that the Update Event is treated as a Finalisation Event for that particular employee.

As the employees have been included in either an Update Event or Finalisation Event, you must not generate payment summaries or PSAR for them.

We changed payroll software during the financial year and have not added previously terminated employees (from prior payroll software) in this payroll system. How do we deal with the terminated employees not entered into QuickBooks Payroll?

If you have been reporting STP events in the previous payroll software, ensure that the terminated employee is marked Is Final in their final STP event. If this is the case, then nothing further is required. If the employee is not marked as Is Final, then lodge an Update Event in the previous payroll software and mark the employee as Is Final.

Note: Do not add the terminated employees into QuickBooks Payroll after doing the above steps.

If you have NOT been reporting STP events in the previous payroll software, there are two options you can take to account for this:

  • Keep the terminated employee’s data in the previous payroll software and generate payment summaries for that employee
  • Add terminated employee’s data into QuickBooks Payroll and enter their YTD data using Opening Balances, so that they are included in the Finalisation Event. If you choose this option, you are not required to generate payment summaries for the terminated employee.

Refer to this article for more scenarios and how to account for them.

I have employees who still want a printed payment summary. Is it as simple as just printing it out?

With STP, payment summaries will not be generated. However, employees will now be provided with Income Statements that are available via their myGov account. 

Section 4:  Lodging a Finalisation Event

What if an update event has been successfully lodged and all employees marked as 'is final'? Do I still need to lodge a Finalisation Event?

Lodging an update event with all employees marked as Is Final is sufficient enough to close off the Financial Year’s data with the ATO. You do not have to lodge a Finalisation event if you have done this.

My employees are normally paid on a regular pay schedule (e.g. weekly) but sometimes I pay them using an ad-hoc pay schedule. Do I need to process a finalisation event for both the regular pay schedule and the ad-hoc schedule?

You do not need to process a finalisation event for the regular pay schedule and the ad-hoc pay schedule. Just by creating the finalisation event for the regular schedule, the YTD amounts are captured for all active employees in both schedules (who are not marked as Is Final in previous events). The YTD amounts will also include earnings paid using a different pay schedule during the financial year.

Can I still create an urgent ad-hoc pay run after lodging a finalisation event?

Yes, you can create an ad-hoc pay run, then create an amended Finalisation Event. However, ensure you notify your employees that an adjusted pay is required and to get them to hold off on lodging their tax return, as the successfully lodged original Finalisation Event would have marked the employee’s Income Statement as Tax Ready. 

Once you have finalised the ad-hoc pay run, create the amended Finalisation Event:

  1. Select Employees on the left menu.
  2. Select Reports, then select Single Touch Payroll.
  3. Select the drop-down next to Start Finalisation Process, then select Create an amended Finalisation Event.
    • This option only appears once a successful finalisation event has been lodged.
  4. Select the Pay Schedule and add the affected employees.
  5. The process will now be the same as a Finalisation Event.

Was this helpful?

You must sign in to vote, reply, or post