This guide is for Australian employers with 20 or more employees who must report to the ATO via STP starting 1st July 2018. The ATO has provided extensive documentation on Single Touch Payroll for businesses/employers. At a minimum, we recommend you've read the Single Touch Payroll employer reporting guidelines available from the Report through Single Touch Payroll section of the ATO's site. As an employer, it is your responsibility to ensure that you're familiar with and full-fill your STP reporting obligations.
How to get started with STP
The quickest and easiest way of getting started with STP is to do the following BEFORE your first 2018/2019 Pay Run:
Continue to process Payroll as you normally would. Reporting via STP will be initiated automatically.
Accessing STP functionality
You should use the Jcurve Payroll Admin role when using STP functionality. If you have a NetSuite One World account, then Subsidiary permissions and restrictions are respected throughout the solution. All functionality can easily be accessed from the JCurve Payroll > Single Touch Payroll menu.
Note: The JCurve Payroll module is developed by Infinet Cloud Solutions. In order to meet your STP reporting obligations starting 1st July 2018 - it is necessary to notify the ATO that you are using JCurve Payroll. You will need to do this for each business entity (I.e ABN or Branch) that you run JCurve Payroll for. The process should take less than 5 minutes to complete online.
Before you get started, you will need the following:
Note: As per point 2 below, the JCurve Payroll solution is developed by Infinet Cloud Solutions. This is why you need to reference ICS in the ATO portal, not JCurve.
A login to the ATO's Access Manager - this includes an Administrator AUSkey or an ABN connected to your myGov account. For more information see ATO Online Services > Access Manager
Infinet Cloud's details - our payroll developers full business name is Infinet Cloud Solutions Pty Ltd and ABN is 27 146 064 762
Your Software ID - this is a unique number that you'll find on your Licence record.
The Software ID is a 10-digit number unique to your NetSuite account and JCurve Cloud installation. The ATO requires knowledge of your Software ID to authorise STP transmissions sent to them. Your Software ID is not public knowledge and therefore, if recorded, should be kept in a safe place. However, there is no reason to record your Software ID as it will not change and will always be available in your NetSuite account when JCurve Payroll is installed. Note: If you have Multiple Subsidiaries setup in NetSuite, the Software ID will be the same across all subsidiaries.
How To locate your Software ID:
Note: Your role should be Administrator or JCurve Payroll Admin Navigate to JCurve Payroll > Payroll Setup > View License. Your License details, including the Software ID will be displayed. Notify the ATO of JCurve Payroll and your Software ID as per the linked instructions below.
How to notify the ATO of JCurve Payroll
Note: The JCurve Payroll solution is developed by Infinet Cloud Solutions. This is why you need to reference ICS in the ATO portal, not JCurve. Provided you have the details listed above then please follow the ATO's instructions on the below link: Click the following link for instructions Notify ATO of a hosted SBR software service You should find Infinet Cloud Solutions Pty Ltd on the first page of Service Providers to select from.
3. Important Employee Details (STP)
Standard Fields
The following employee fields will be included with each STP Pay Event and therefore sent with each submission. Thus, you must ensure that these fields are complete and up-to-date.
Field
Where
Comments
First Name
Employee
Can be overridden in config, see below.
Last Name
Employee
TFN
Employee > Tax Info tab
Birth Date
Employee > HR tab
Email for Payslips
Employee
Optional. Can be overridden in config, see below.
Mobile Phone
Employee
Optional. Can be overridden in config, see below.
Address line 1
Employee > Home Address
Address line 2
Employee > Home Address
Optional
City
Employee > Home Address
State
Employee > Home Address
Not sent for non-Australian addresses.
Postcode (Zip)
Employee > Home Address
Not sent for non-Australian addresses.
Country
Employee > Home Address
Overriding Fields
The following fields can be overridden through configuration, meaning the system will source values from the fields you configure instead of the defaults listed above. For most customers, we do NOT recommend that you override any fields. You should only do this if you know what you're doing and/or have been told to do so.
To report via STP, you will need to run through the STP Setup Assistant. If you need to report via STP starting July 1 2018, then it is important that you run through the assistant prior to the first pay run for the financial year. To access the STP Setup Assistant:
Login as JCurve Payroll Admin.
Navigate to JCurve Payroll > Single Touch Payroll > Branch Setup Assistant.
The setup assistant will walk you through all the configuration necessary. If possible, it's a good idea to have a previous BAS statement on-hand to ensure you enter the correct details. If you have multiple subsidiaries, companies or branches then you will need to run-through the assistant for each entity. If you log out, switch roles or leave the assistant inactive for a prolonged period of time it may result in an error being thrown or not completing successfully. If this happens then go through the assistant again from step 1.
Step 1: Select Branch
As per the on-screen instructions, select a branch that you would like to configure. You should find a branch for each Australian entity you've previously run Payroll for. If you have multiple PAYG Branches registered with the ATO, then you will need to create the other (non 1/001) branches. To do so, just click the + icon, or select - New - from the the Branch dropdown.
Step 2: Verify Branch Details
Enter the details exactly as they appears on your BAS. The form will validate any inputs you enter. Note that all designated mandatory fields are required, plus State, Postcode and Country Code for Australian addresses. The phone number you enter in the Contact Phone field should include the relevant area code and can only include digits and spaces. For example, an acceptable format is: 02 9888 8736 If you need to enter a foreign (non-Australian) address, then you must leave the State and Postcode fields blank. The Country Code should be set to the country's code (e.g. NZ for New Zealand).
Step 3: Load AUSkey Credentials
If you've previously run the STP Setup Assistant then you may get the following message: Valid credentials exist and no action is required. Click 'Next > ' to continue. In this case, as per the instructions, just click the Next > button. As per the on-screen instructions, you will be using Infinet Cloud's AUSkey to report via STP. To load these credentials, do the following:
When you visit this step for the first time, you should be instructed to CLICK HERE to load signing credentials link. As per the instructions, click the link.
A window will pop-up that looks like the below.
3. Click the blue Save AUSkey Credentials button 4. The window should now close and you should be back in the Assistant and presented with a green message as per the below 5. As per the instructions, click the Next > button to continue.
Step 4: Configure STP Options
Complete the fields on this step as per the descriptions below.
BMS ID - This is your unique Business Management Software ID that will be sent with each submission to the ATO. It cannot be changed and you do not need to do anything with it.
Initiate STP at Pay Run Step - Identifies the Pay Run step after which the Report STP submit action will automatically be triggered. We recommend that you set this to Pay to ensure the Pay Run has truly been finalised prior reporting via STP. If you are using the One Step feature then set this to Approve.
STP Submission Time - The time STP Pay Events will get scheduled to be submitted to the ATO. Each submission must happen on or before the Pay Date of a Pay run. We recommend setting this to as early as possible (i.e. morning of the Pay Date).
Use Production Servers - This checkbox should be marked. Only unmark it if you know what you are doing, or are running on a Sandbox/Test environment.
Override default values
These fields should be left blank unless you know what you're doing or have been instructed to complete them.
Payee First Name Field - Enter a field ID to override which field Employee first names are sourced from.
Payee Email Field - Enter a field ID to override which field Employee email addresses are sourced from.
Payee Phone Field - Enter a field ID to override which field Employee phone numbers are sourced from.
Payroll ID Field - Enter a field ID to override which field Employee Payroll IDs are sourced from.
Step 5: Review Allowance Types
As per the on-screen instructions, review the Allowance Types and ensure that each line has an STP Allowance Type set. Do not attempt to create any additional Allowance Types on this screen. Also, you cannot delete any Allowance Types here. Note: Not all Allowance Types available in your account will be displayed. Only those that have been designated to appear in the Allowance Box on a Payment Summary will be displayed.
Step 6: Confirm & Save
There is nothing to complete on this step. It provides a summary of what you have entered/configured. If the information displayed is correct then click the Finish button. If you note something that requires a change, then click < Back until you return to the step where you can make the change required.
There are a number of scenarios when you may need to send an Update Pay Event. An Update Pay Event includes YTD totals for the employees you send it for. Since it is not linked to a Pay Run, no specific Pay Run information is included. Some of the scenarios when you may need to Send an Update Pay Event include:
To fix previously reported data for an Employee (or Employees)
If you are transitioning to STP mid-year
When finalising a Financial Year or a specific employee
For detailed information on when you should send an Update Pay Event, you should refer to the Single Touch Payroll employer reporting guidelines available from the ATO's Reporting through Single Touch Payroll section of their website.
How to Initiate and Send
To send an Update Pay Event:
From the menu, select Payroll Administration > Single Touch Payroll (AU) > Send Update Pay Event
If you have multiple Branches setup, select a Branch
The page will refresh with Employees and their YTD data
Select the Employees you would like to send an Update Pay Event for
You will not be able to select any employees that are identified as having invalid data. By hovering your mouse over the symbol, a message with what's been identified as invalid will show. You should fix all invalid data identified and then refresh the page.
If this is the final Pay Event for any Employee, then mark the relevant checkbox in the Final?column
Once you have reviewed the data presented, read and accept the declaration by marking the Acceptance Checkbox
Click the Submit Now button to send the Update Pay Event to the ATO.
NOTE: Clicking the Submit Nowbutton will not actually result in the Update Pay Event being sent to the ATO immediately. The system first needs to calculate the data and create the appropriate records, and then it will schedule its submission. All this will run in the background, allowing you to continue on with other work. You will receive email alerts as this process progresses.
Finalising STP Payroll data
If the Pay Event you are creating and submitting is final (last one) for a specific Employee, you should mark the associated checkbox in the Final? column. Typical scenarios when you will need to do this are:
When an employee has been terminated and they will not receive any additional pay;
At the end of a financial year.
Once sent, the ATO will flag the employee as being finalised and will make pay details (e.g. Payment Summary) available to the employee. For more info, see the ATO's article on Finalising your Single Touch Payroll data.
As long as you've run the Branch Setup Assistant, you will automatically be prompted to create a STP Pay Event towards the end of every Pay Run you process in Infinet Cloud Payroll. Exactly when you are prompted, depends upon the stage of the Pay Run. When prompted, you will be presented with a screen similar to the one above. You should:
Review the information presented, including:
The employees to be reported (these will match to those included on the Pay Run)
The amounts to be reported including summary types
Any new on-boardings that will be included
Total PAYGW and Gross amounts
Read the Declaration and if you agree, mark the Acceptance Checkbox
Click the Schedule Submission button. Clicking this button will result in the following:
Data will be calculated and the relevant Pay Event and Pay Event Employees records will be created
Submission of the created Pay Event will be scheduled for the Pay Date on the Pay Run
You will be returned to the Pay Run
You are now done
If you identify any issues in the data whilst you are reviewing, do NOT click the Schedule Submission button. Instead use your Browser's back button to go to the Pay Run and make adjustments to the Pay Run as required.
Manually Initiate Report STP
If you need to manually initiate the STP process as detailed above:
Open the relevant Pay Run record
From there, click the Report STP button
You will now be taken to the STP Pay Event for Pay Run screen as above
The Report STP button will only be available if the Pay Run has reached the relevant stage
When to Report via STP
As per the ATO's guidelines, you must report payroll information on or before a Pay Date. Thus you should report via STP when you have finalised a Pay Run. You should be automatically prompted to report via STP during the Pay Run process. Alternatively, you may manually initiate the process using the Report STP button. The availability of the button, and when you will be automatically prompted, depends upon the stage of the Pay Run and the STP Configuration Options set on the associated Branchrecord. The Branch setting that drives this is named Initiate STP on Pay Run Step and provides two options: Pay and Approve. For information on changing this option, see Branch Setup Assistant (Configure STP). We highly recommend you have this option set to Pay to ensure that you report via STP only when you are confident a Pay Run is correct and complete. This setting should only be set to Approve if you're using the One Step feature with Payroll. The table below lists the Configuration Options and Pay Run Stages that will result in the Pay Run directing you to Submit a STP Pay Event for the Pay Run. Any one of the Pay Run stages needs to be reached for STP to be triggered.
Configuration Options
Pay Run Stages
Pay
Pay Run Paid (Including Partially) Emailed Payslips
Approve
Payslips Approved Pay Run Posted (including Partially) Pay Run Paid (including Partially) Emailed Payslips Payment Scheduled
Please refer to the list of frequently asked questions below, if you cannot find your question or an appropriate answer then please contact support@jcurve.com.au. Note: The JCurve Payroll module is developed by Infinet Cloud Solutions.
When does STP come into effect?
Single Touch Payroll is being rolled out with the 2018/2019 financial year. Therefore the start date is 1 July 2018. From this date, you will need to report all pay data (e.g. from pay runs) through STP.
As an employer, what are our obligations under STP?
The ATO has an in-depth article detailing employer obligations. Our software solution will assist you with all your mandatory reporting requirements. And because of the built-in nature of our solution, when processing a pay run, doing an STP submission will mean just a few additional clicks.
What Employee details need to be updated? Your employee data will be sent to the ATO with each STP submission, and the ATO will use the information you send to match up employees on their end. To ensure a smooth transition to STP, it is critical that the info on your employee records in NetSuite is correct. Please check all the fields below for all your employees:
Name (first and last name fields)
Tax Info > Tax File Number
HR Tab > Birth Date
Address
Each employee must have a Home address defined.
For Australian based employees and addresses, the following fields must be correct: Country, Address line 1, City (Suburb), State and Postcode
For non-Australia addresses, ensure the following fields are correct: Country, Address line 1, and City
Are we a 'substantial employer'?
In short, you will need to count the number of employees on your payroll on 1 April 2018 to find out if you are a 'substantial employer'. You need to do a headcount, not a count of your full time equivalent (FTE). If you have 20 or more employees on 1 April, you will be a 'substantial employer' and will need to report through Single Touch Payroll from 1 July 2018. Once you are a substantial employer you will be required to continue reporting through Single Touch Payroll even if your employee numbers drop below 20. For more detailed information please refer to the ATO's How to count your employees article.
What happens if we're not a 'substantial employer'?
If you're not classified as a 'substantial employer' then there is no requirement to report via STP starting 1 July 2018. However, since the STP solution will be available in your account, you may choose to report via STP anyway - the choice is yours. Using STP has many benefits including the ability to electronically lodge TFN Declarations for new employees and a possible reduction in end-of-year Payroll processes (e.g. distributing payment summaries). It is expected that all employers (including non-substantial) will be required to report via STP starting the 2019/2020 financial year.
Should we be worried about complying with the new regulations and incurring a penalty?
No, the STP solution will be in your account and available prior to 1 July 2018. When you start reporting through STP, the first 12 months will be a transition period. The ATO will be working closely with employers (and if required their Digital Service Provider) to help ensure submitted information is correct. Employers will also likely be exempt from administrative penalties for failures to report on time. For further information see: Penalties, exemptions and deferrals
Will we need to issue Payment Summaries for the 2017/2018 FY?
Yes, employers’ obligations for the 2017/2018 financial year are un-changed. Therefore, your end-of-year process should be the same as last - you will need to distribute Payment Summaries to employees and submit the relevant Payment Summary Annual Report (PSAR file) to the ATO.
Once using STP, will we need to issue Payment Summaries?
For detailed information on this topic see Finalising your Single Touch Payroll Reporting. You will not have to provide payment summaries for the following payments if you reported them voluntarily through Single Touch Payroll:
payments under voluntary agreement
payments under a labour hire arrangement
death benefit employment termination payment.
You will need to provide a payment summary for any payments not reported through STP.
Will our pay run process need to change?
Since you will need to submit pay event information to the ATO on or before each pay date - there will be an additional step to the pay run process. We are striving to keep this as simple and intuitive as possible for you with a minimal learning curve. This means, that meeting your obligation to report through STP will be down to just a few more clicks.
Is the STP solution an integration?
No, the STP solution - much like our JCurve Payroll solution - is built-in within NetSuite. No external integration(s) are necessary and your NetSuite account will connect directly to the ATO's servers to submit STP information.
Are there any additional security concerns with STP?
No, at JCurve we take security very seriously. All your payroll data will continue to reside within your NetSuite account. When submitting pay data via STP, your NetSuite account will connect securely directly to the ATO's servers and communicate directly - your data will not be transported through any other 3rd party. Further, prior to any STP submission, you will have an opportunity to review the data being submitted.
What is Infinet Cloud's relationship with the ATO?
Infinet Cloud have a long-standing relationship with the ATO and ABSIA. Under the their definitions, they are a Software Provider and Digital Service Provider (DSP) of STP-enabled payroll software.
Once using STP, how will employees view their Payment Summary information?
Pay information submitted through STP will be visible to individual employees through the ATO's online services (accessible through MyGov). Obviously employees will need to register for MyGov access and link their ATO Online Services if they haven't done so already.
Can we report data for employees via STP even if they haven't signed up to MyGov?
Yes, you must report pay data for all employees as required, regardless of their MyGov access. MyGov and ATO Online Services access is each employee's individual responsibility.
Follow the step by step procedure below.
1. Single Touch Payroll (STP) Guide
https://jcurvesolutions1.zendesk.com/hc/en-us/articles/360001102006-Single-Touch-Payroll-STP-GuideThis guide is for Australian employers with 20 or more employees who must report to the ATO via STP starting 1st July 2018.
The ATO has provided extensive documentation on Single Touch Payroll for businesses/employers. At a minimum, we recommend you've read the Single Touch Payroll employer reporting guidelines available from the Report through Single Touch Payroll section of the ATO's site. As an employer, it is your responsibility to ensure that you're familiar with and full-fill your STP reporting obligations.
How to get started with STP
The quickest and easiest way of getting started with STP is to do the following BEFORE your first 2018/2019 Pay Run:Accessing STP functionality
You should use the Jcurve Payroll Admin role when using STP functionality. If you have a NetSuite One World account, then Subsidiary permissions and restrictions are respected throughout the solution. All functionality can easily be accessed from the JCurve Payroll > Single Touch Payroll menu.2. Notify ATO of JCurve Payroll (STP)
https://jcurvesolutions1.zendesk.com/hc/en-us/articles/360000933406-Notify-ATO-of-JCurve-Payroll-STP-Note: The JCurve Payroll module is developed by Infinet Cloud Solutions.
In order to meet your STP reporting obligations starting 1st July 2018 - it is necessary to notify the ATO that you are using JCurve Payroll. You will need to do this for each business entity (I.e ABN or Branch) that you run JCurve Payroll for. The process should take less than 5 minutes to complete online.
Before you get started, you will need the following:
Note: As per point 2 below, the JCurve Payroll solution is developed by Infinet Cloud Solutions. This is why you need to reference ICS in the ATO portal, not JCurve.- A login to the ATO's Access Manager - this includes an Administrator AUSkey or an ABN connected to your myGov account. For more information see ATO Online Services > Access Manager
- Infinet Cloud's details - our payroll developers full business name is Infinet Cloud Solutions Pty Ltd and ABN is 27 146 064 762
- Your Software ID - this is a unique number that you'll find on your Licence record.
Note: See Finding your Software ID belowOnce you have the above ready then continue onto the ATO's instructions on how to notify them of a hosted SBR software server.
Finding your Software ID
The Software ID is a 10-digit number unique to your NetSuite account and JCurve Cloud installation. The ATO requires knowledge of your Software ID to authorise STP transmissions sent to them. Your Software ID is not public knowledge and therefore, if recorded, should be kept in a safe place. However, there is no reason to record your Software ID as it will not change and will always be available in your NetSuite account when JCurve Payroll is installed.Note: If you have Multiple Subsidiaries setup in NetSuite, the Software ID will be the same across all subsidiaries.
How To locate your Software ID:
Note: Your role should be Administrator or JCurve Payroll AdminNavigate to JCurve Payroll > Payroll Setup > View License.
Your License details, including the Software ID will be displayed.
Notify the ATO of JCurve Payroll and your Software ID as per the linked instructions below.
How to notify the ATO of JCurve Payroll
Note: The JCurve Payroll solution is developed by Infinet Cloud Solutions. This is why you need to reference ICS in the ATO portal, not JCurve.Provided you have the details listed above then please follow the ATO's instructions on the below link:
Click the following link for instructions Notify ATO of a hosted SBR software service
You should find Infinet Cloud Solutions Pty Ltd on the first page of Service Providers to select from.
3. Important Employee Details (STP)
Standard Fields
The following employee fields will be included with each STP Pay Event and therefore sent with each submission. Thus, you must ensure that these fields are complete and up-to-date.Field
Where
Comments
First Name
Employee
Can be overridden in config, see below.
Last Name
Employee
TFN
Employee > Tax Info tab
Birth Date
Employee > HR tab
Email for Payslips
Employee
Optional. Can be overridden in config, see below.
Mobile Phone
Employee
Optional. Can be overridden in config, see below.
Address line 1
Employee > Home Address
Address line 2
Employee > Home Address
Optional
City
Employee > Home Address
State
Employee > Home Address
Not sent for non-Australian addresses.
Postcode (Zip)
Employee > Home Address
Not sent for non-Australian addresses.
Country
Employee > Home Address
Overriding Fields
The following fields can be overridden through configuration, meaning the system will source values from the fields you configure instead of the defaults listed above. For most customers, we do NOT recommend that you override any fields. You should only do this if you know what you're doing and/or have been told to do so.4. Branch Setup Assistant (Configure STP)
https://jcurvesolutions1.zendesk.com/hc/en-us/articles/360001084623-Branch-Setup-Assistant-Configure-STP-Introduction
To report via STP, you will need to run through the STP Setup Assistant. If you need to report via STP starting July 1 2018, then it is important that you run through the assistant prior to the first pay run for the financial year.To access the STP Setup Assistant:
- Login as JCurve Payroll Admin.
- Navigate to JCurve Payroll > Single Touch Payroll > Branch Setup Assistant.
The setup assistant will walk you through all the configuration necessary. If possible, it's a good idea to have a previous BAS statement on-hand to ensure you enter the correct details. If you have multiple subsidiaries, companies or branches then you will need to run-through the assistant for each entity.If you log out, switch roles or leave the assistant inactive for a prolonged period of time it may result in an error being thrown or not completing successfully. If this happens then go through the assistant again from step 1.
Step 1: Select Branch
As per the on-screen instructions, select a branch that you would like to configure. You should find a branch for each Australian entity you've previously run Payroll for.If you have multiple PAYG Branches registered with the ATO, then you will need to create the other (non 1/001) branches. To do so, just click the + icon, or select - New - from the the Branch dropdown.
Step 2: Verify Branch Details
Enter the details exactly as they appears on your BAS. The form will validate any inputs you enter. Note that all designated mandatory fields are required, plus State, Postcode and Country Code for Australian addresses.The phone number you enter in the Contact Phone field should include the relevant area code and can only include digits and spaces. For example, an acceptable format is: 02 9888 8736
If you need to enter a foreign (non-Australian) address, then you must leave the State and Postcode fields blank. The Country Code should be set to the country's code (e.g. NZ for New Zealand).
Step 3: Load AUSkey Credentials
If you've previously run the STP Setup Assistant then you may get the following message: Valid credentials exist and no action is required. Click 'Next > ' to continue. In this case, as per the instructions, just click the Next > button.As per the on-screen instructions, you will be using Infinet Cloud's AUSkey to report via STP. To load these credentials, do the following:
3. Click the blue Save AUSkey Credentials button
4. The window should now close and you should be back in the Assistant and presented with a green message as per the below
5. As per the instructions, click the Next > button to continue.
Step 4: Configure STP Options
Complete the fields on this step as per the descriptions below.STP Options
Override default values
These fields should be left blank unless you know what you're doing or have been instructed to complete them.Step 5: Review Allowance Types
As per the on-screen instructions, review the Allowance Types and ensure that each line has an STP Allowance Type set. Do not attempt to create any additional Allowance Types on this screen. Also, you cannot delete any Allowance Types here.
Note: Not all Allowance Types available in your account will be displayed. Only those that have been designated to appear in the Allowance Box on a Payment Summary will be displayed.
Step 6: Confirm & Save
There is nothing to complete on this step. It provides a summary of what you have entered/configured. If the information displayed is correct then click the Finish button. If you note something that requires a change, then click < Back until you return to the step where you can make the change required.5. Sending an Update Pay Event (STP)
https://jcurvesolutions1.zendesk.com/hc/en-us/articles/360015753032-Sending-an-Update-Pay-Event-STP-Overview
There are a number of scenarios when you may need to send an Update Pay Event. An Update Pay Event includes YTD totals for the employees you send it for. Since it is not linked to a Pay Run, no specific Pay Run information is included. Some of the scenarios when you may need to Send an Update Pay Event include:- To fix previously reported data for an Employee (or Employees)
- If you are transitioning to STP mid-year
- When finalising a Financial Year or a specific employee
For detailed information on when you should send an Update Pay Event, you should refer to the Single Touch Payroll employer reporting guidelines available from the ATO's Reporting through Single Touch Payroll section of their website.How to Initiate and Send
To send an Update Pay Event:- From the menu, select Payroll Administration > Single Touch Payroll (AU) > Send Update Pay Event
- If you have multiple Branches setup, select a Branch
- The page will refresh with Employees and their YTD data
- Select the Employees you would like to send an Update Pay Event for
- You will not be able to select any employees that are identified as having invalid data. By hovering your mouse over the
symbol, a message with what's been identified as invalid will show. You should fix all invalid data identified and then refresh the page.
- If this is the final Pay Event for any Employee, then mark the relevant checkbox in the Final? column
- Once you have reviewed the data presented, read and accept the declaration by marking the Acceptance Checkbox
- Click the Submit Now button to send the Update Pay Event to the ATO.
NOTE: Clicking the Submit Now button will not actually result in the Update Pay Event being sent to the ATO immediately. The system first needs to calculate the data and create the appropriate records, and then it will schedule its submission. All this will run in the background, allowing you to continue on with other work. You will receive email alerts as this process progresses.Finalising STP Payroll data
If the Pay Event you are creating and submitting is final (last one) for a specific Employee, you should mark the associated checkbox in the Final? column. Typical scenarios when you will need to do this are:- When an employee has been terminated and they will not receive any additional pay;
- At the end of a financial year.
Once sent, the ATO will flag the employee as being finalised and will make pay details (e.g. Payment Summary) available to the employee. For more info, see the ATO's article on Finalising your Single Touch Payroll data.6. Reporting a Pay Run (STP)
https://jcurvesolutions1.zendesk.com/hc/en-us/articles/360001084943-Reporting-a-Pay-Run-STP-Schedule Submission of a Pay Event
As long as you've run the Branch Setup Assistant, you will automatically be prompted to create a STP Pay Event towards the end of every Pay Run you process in Infinet Cloud Payroll. Exactly when you are prompted, depends upon the stage of the Pay Run.When prompted, you will be presented with a screen similar to the one above. You should:
- Review the information presented, including:
- The employees to be reported (these will match to those included on the Pay Run)
- The amounts to be reported including summary types
- Any new on-boardings that will be included
- Total PAYGW and Gross amounts
- Read the Declaration and if you agree, mark the Acceptance Checkbox
- Click the Schedule Submission button. Clicking this button will result in the following:
- Data will be calculated and the relevant Pay Event and Pay Event Employees records will be created
- Submission of the created Pay Event will be scheduled for the Pay Date on the Pay Run
- You will be returned to the Pay Run
- You are now done
If you identify any issues in the data whilst you are reviewing, do NOT click the Schedule Submission button. Instead use your Browser's back button to go to the Pay Run and make adjustments to the Pay Run as required.Manually Initiate Report STP
If you need to manually initiate the STP process as detailed above:The Report STP button will only be available if the Pay Run has reached the relevant stage
When to Report via STP
As per the ATO's guidelines, you must report payroll information on or before a Pay Date. Thus you should report via STP when you have finalised a Pay Run.You should be automatically prompted to report via STP during the Pay Run process. Alternatively, you may manually initiate the process using the Report STP button. The availability of the button, and when you will be automatically prompted, depends upon the stage of the Pay Run and the STP Configuration Options set on the associated Branchrecord. The Branch setting that drives this is named Initiate STP on Pay Run Step and provides two options: Pay and Approve. For information on changing this option, see Branch Setup Assistant (Configure STP).
We highly recommend you have this option set to Pay to ensure that you report via STP only when you are confident a Pay Run is correct and complete. This setting should only be set to Approve if you're using the One Step feature with Payroll.
The table below lists the Configuration Options and Pay Run Stages that will result in the Pay Run directing you to Submit a STP Pay Event for the Pay Run. Any one of the Pay Run stages needs to be reached for STP to be triggered.
Pay Run Paid (Including Partially)
Emailed Payslips
Pay Run Posted (including Partially)
Pay Run Paid (including Partially)
Emailed Payslips
Payment Scheduled
--------------------------
Single Touch Payroll - FAQ
https://jcurvesolutions1.zendesk.com/hc/en-us/articles/360000339366-Single-Touch-Payroll-FAQPlease refer to the list of frequently asked questions below, if you cannot find your question or an appropriate answer then please contact support@jcurve.com.au.
Note: The JCurve Payroll module is developed by Infinet Cloud Solutions.
When does STP come into effect?
Single Touch Payroll is being rolled out with the 2018/2019 financial year. Therefore the start date is 1 July 2018. From this date, you will need to report all pay data (e.g. from pay runs) through STP.How do we register for STP?
There is no need to explicitly register for STP, substantial employers will automatically be required to report via using STP starting 1 July 2018. If you aren’t already though, then you must register for PAYG withholding.You also need to notify the ATO that you are using Infinet Cloud Payroll.
As an employer, what are our obligations under STP?
The ATO has an in-depth article detailing employer obligations. Our software solution will assist you with all your mandatory reporting requirements. And because of the built-in nature of our solution, when processing a pay run, doing an STP submission will mean just a few additional clicks.How do we get ready for STP?
- If you haven't done so yet, then register with the ATO for PAYG withholding.
- Make sure all your employee data is up-to-date (see below)
- Notify the ATO that you are using a hosted SBR software Service (Infinet Cloud Payroll).
What Employee details need to be updated?Your employee data will be sent to the ATO with each STP submission, and the ATO will use the information you send to match up employees on their end. To ensure a smooth transition to STP, it is critical that the info on your employee records in NetSuite is correct. Please check all the fields below for all your employees:
Are we a 'substantial employer'?
In short, you will need to count the number of employees on your payroll on 1 April 2018 to find out if you are a 'substantial employer'. You need to do a headcount, not a count of your full time equivalent (FTE). If you have 20 or more employees on 1 April, you will be a 'substantial employer' and will need to report through Single Touch Payroll from 1 July 2018. Once you are a substantial employer you will be required to continue reporting through Single Touch Payroll even if your employee numbers drop below 20.For more detailed information please refer to the ATO's How to count your employees article.
What happens if we're not a 'substantial employer'?
If you're not classified as a 'substantial employer' then there is no requirement to report via STP starting 1 July 2018. However, since the STP solution will be available in your account, you may choose to report via STP anyway - the choice is yours. Using STP has many benefits including the ability to electronically lodge TFN Declarations for new employees and a possible reduction in end-of-year Payroll processes (e.g. distributing payment summaries).It is expected that all employers (including non-substantial) will be required to report via STP starting the 2019/2020 financial year.
Should we be worried about complying with the new regulations and incurring a penalty?
No, the STP solution will be in your account and available prior to 1 July 2018. When you start reporting through STP, the first 12 months will be a transition period. The ATO will be working closely with employers (and if required their Digital Service Provider) to help ensure submitted information is correct. Employers will also likely be exempt from administrative penalties for failures to report on time. For further information see: Penalties, exemptions and deferralsWill we need to issue Payment Summaries for the 2017/2018 FY?
Yes, employers’ obligations for the 2017/2018 financial year are un-changed. Therefore, your end-of-year process should be the same as last - you will need to distribute Payment Summaries to employees and submit the relevant Payment Summary Annual Report (PSAR file) to the ATO.Once using STP, will we need to issue Payment Summaries?
For detailed information on this topic see Finalising your Single Touch Payroll Reporting. You will not have to provide payment summaries for the following payments if you reported them voluntarily through Single Touch Payroll:- payments under voluntary agreement
- payments under a labour hire arrangement
- death benefit employment termination payment.
You will need to provide a payment summary for any payments not reported through STP.Will our pay run process need to change?
Since you will need to submit pay event information to the ATO on or before each pay date - there will be an additional step to the pay run process. We are striving to keep this as simple and intuitive as possible for you with a minimal learning curve. This means, that meeting your obligation to report through STP will be down to just a few more clicks.Is the STP solution an integration?
No, the STP solution - much like our JCurve Payroll solution - is built-in within NetSuite. No external integration(s) are necessary and your NetSuite account will connect directly to the ATO's servers to submit STP information.Are there any additional security concerns with STP?
No, at JCurve we take security very seriously. All your payroll data will continue to reside within your NetSuite account. When submitting pay data via STP, your NetSuite account will connect securely directly to the ATO's servers and communicate directly - your data will not be transported through any other 3rd party. Further, prior to any STP submission, you will have an opportunity to review the data being submitted.What is Infinet Cloud's relationship with the ATO?
Infinet Cloud have a long-standing relationship with the ATO and ABSIA. Under the their definitions, they are a Software Provider and Digital Service Provider (DSP) of STP-enabled payroll software.Once using STP, how will employees view their Payment Summary information?
Pay information submitted through STP will be visible to individual employees through the ATO's online services (accessible through MyGov). Obviously employees will need to register for MyGov access and link their ATO Online Services if they haven't done so already.Can we report data for employees via STP even if they haven't signed up to MyGov?
Yes, you must report pay data for all employees as required, regardless of their MyGov access. MyGov and ATO Online Services access is each employee's individual responsibility.