Single Touch Payroll

Application Help

CUSTOMER
CONTENTS

SINGLE TOUCH PAYROLL 3

GENERATE REPORTING DATA 4
PREREQUISITES 5
SINGLE TOUCH PAYROLL – GENERATE REPORTING DATA 6
OVERRIDE STP DATA MANUALLY 7
MAINTAIN STP OVERRIDE ENTRIES THROUGH FILE 9
RECONCILE, FINALISE AND DECLARE DATA 10
COMMUNICATE WITH ATO AND TRACK RESPONSES 12

2
SINGLE TOUCH PAYROLL

Single Touch Payroll (STP) is a government initiative to streamline business reporting obligations. STP
leverages an employer’s natural business processes around its payroll event. Employers will be able to
report salary or wages, pay as you go withholding (PAYGW) and superannuation information to the
Australian Taxation Office (ATO) from their payroll solution, at the same time or before they pay their
employees.

When their employer reports through STP, employees will be able to view their employment-related tax and
super information in one place via MyGov (a simple and secure way to access government online services).

Every employer (including Australian subsidiaries of overseas organizations) who uses their own payroll
software must electronically report employees’ payments and deductions to the ATO on or after each
payday, in real time, for each payroll run. STP also provides employers more options for completing tax and
super forms electronically.

3
GENERATE REPORTING DATA

The following programs can be used to generate and report Single Touch Payroll data:

• Single Touch Payroll – Generate Reporting Data (RPCST2Q0)

• Override STP Data (RPCSTOQ0) (manually)
• Maintain STP Override Entries through File (RPUSTOQ0) (through file)

4
PREREQUISITES

• Maintain the date on which Single Touch Payroll Phase 2 will go live.

You can do this in Customizing for Payroll Australia under Single Touch Payroll - Phase 2 ->
Maintain Constant for Go-live Date of STP Phase 2.

• For every employee, Income Type and/or Country/Region must be maintained in Australia Tax
(IT0188) infotype from the start of the financial year in which the STP Phase 2 solution goes live.

• Ensure you have run the Migration Utility for STP Australia (RPCMYGQ2) report for mid-year go-live of
Single Touch Payroll.

• Maintain details of the intermediary who submits STP information to the ATO on behalf of the
employer.

You can do this in Customizing for Payroll Australia under Single Touch Payroll - Phase 2 ->
Maintain Details of Intermediary.

• Maintain Wage Type Allocation for STP Phase2 Reporting (evaluation class 13) settings to configure
your wage types with payments, deductions, allowances and taxes for reporting on STP.

You can do this in Customizing for Payroll Australia under Single Touch Payroll - Phase 2 ->
Configure Wage Types for Reporting.

• Maintain the values of constants needed for STP reporting in Customizing for Payroll Australia under
Single Touch Payroll - Phase 2 -> Communication with Authorities (B2A) -> Maintain Constants.

• Maintain the Determine whether to check payroll control record exit for STP (13STP) feature to
determine whether the exit status of the payroll control record (PCR) should be checked before a live
submission of the STP report.

You can do this in Customizing for Payroll Australia under Payroll Australia under Single Touch Payroll -
Phase 2 -> Override Details -> Maintain Check for PCR Exit Status.

5
SINGLE TOUCH PAYROLL PHASE 2 – GENERATE REPORTING DATA

Purpose

The Single Touch Payroll Phase 2 – Generate Reporting Data (RPCST2Q0) program is used to report the
employee’s payments such as salaries and wages, pay-as-you-go (PAYG) withholding and super information directly
to the Australian Taxation Office (ATO) at the same time when these payments are made, that is, through Single
Touch Payroll (STP).

Selection

Payroll Period

In this section, select the payroll period for which the report should be executed.

• Period – Select Current Payroll Period or Other Payroll Period or Special Run (off-cycle run).

• Payroll Area – Select the payroll accounting area.

• Period – If Other Payroll Period is selected, specify the payroll period for which you want to run the report.

• Run - If Special Run is selected, specify the payroll type, payroll identifier and payroll payment date for which
you want to run the report.

Selection Criteria

In this section, specify criteria to select the employees for whom the report should be executed, such as Personnel
Number, Employment Status, Company Code, Personnel Area, Employee Group and Payroll Area.

Event Type

In this section, specify the type of event the report will trigger.

• Submit Event – Select to report payments for the chosen criteria via a Submit event.

• Update Event – Select to report changes to previously submitted year-to-date amounts via an Update event.

o Replace Key Identifiers – Select this if you would like to replace a BMS ID and specific Payroll ID(s).

- Previous BMS ID – Specify the previous BMS ID that you wish to replace.
- Previous Payroll IDs File – From your local PC select the excel file that contains the previous
Payroll IDs to be replaced as well as the corresponding current Payroll IDs.
Note: The excel file must contain the current and the previous Payroll IDs in its first and second
columns respectively.

Execution Mode

• Test Run – Select this if you want to execute a test run of the report instead of the default live run that
updates the database and allows submission of live data to ATO.

o Do not Update Database - Select this if you do not want the database to be updated in the test run.
The report output will only be displayed in ALV format.

o Update Database - Select this if you want the database to be updated with simulated data in the test
run.

6
 Note: This simulated data cannot be sent to ATO.

• Spool Generation in Background – Select if a spool should be created when the report is run in the
background.

• Download STP Data as Excel File – Select if you wish to download the output of the report as a Microsoft
Excel file.

o PC File Path – Select this if you would like the file to be downloaded to your computer, and provide
a path for the downloaded file.

o Application Server Path – Select this if you would like the file to be downloaded to the application
server, and provide a path for the downloaded file.

Output

For the selected criteria, the system displays the employee's payroll data and related organization data that will be
reported to the ATO.

Note: If the employee is deceased and is given any death benefits, such payments will be displayed with the
beneficiary's information instead.

If you do not select the Test Run check box, the system updates the report output in the STP-related database tables
(T5Q_STP2_ER, T5Q_STP2_EE and T5Q_STP2_PAY).

7
OVERRIDE STP DATA MANUALLY

Purpose

The Override STP Data (RPCSTOQ0) report is used to adjust the values of an employee’s year-to-date
(YTD) earnings, deductions and other payments used for Single Touch Payroll (STP) reporting. These
values are read from the ABN-wise cumulation result tables (ACRT and AETP) and reported to the
Australian Taxation Office (ATO). If override data corresponding to these pay components is created via this
report, the year-to-date amounts are adjusted in accordance for reporting purpose alone. The actual
amounts in the payroll cluster are not modified.

Note: In order to negate a particular override from STP reporting during the course of a financial year, a new
entry has to be created in this table (T5QSO) with reversed figures.

Prerequisites

Ensure that you maintain a number range for auto-generated sequence numbers assigned to override
entries.

This can be maintained in the STP Override Seq.No. (HR_AU_OVID) number range object in transaction
SNRO.

Note: No. should be maintained as '01' for STP overrides.

Activities

• To view existing override information for selected financial year(s) and personnel number(s), specify the
desired selection criteria and click Execute.

Note: Existing information can only be viewed and not be edited.

• To maintain new override information, click Execute without specifying any criteria, click New Entries and
provide the following details:

o STP Year – Financial year for which you want to adjust the amount.

For example, for payroll year July 2018 – June 2019, the financial year is 2019.

o Personnel No. – Personnel number of employee whose amount you want to adjust

o ABN – Australian Business Number (ABN) of the employer

o ABN branch number – Branch of the ABN

Note: '0' or 'NULL' value is not accepted for ABN branch by the ATO.

o WHM Flag – Whether or not the employee is a working holiday maker

o Income Type – Income type under which the payments will be grouped and reported (Maintain only
in STP phase 2)

o Country/Region Code – ISO code of the employee (Maintain only in STP phase 2 if Income Type is
IAA, WHM or FEI)

o Wage Type – Wage type that holds the amount value to be adjusted

8
 o Amount – Amount that should be added to the original value of the wage type

o ETP Payment date – Termination date if the employee is terminated.

Note: This date is needed only if you are adjusting ETP payments present in the AETP cluster table.

o LSE Financial Year – Financial year in which Lump Sum E payment was made (Maintain only in
STP phase 2)

o Override Description – Information about the amount adjustment such as its reason

o Exclude - Select this checkbox if the entry should not be considered for STP reporting.

The following information is maintained automatically and cannot be edited:

o Changed by – SAP name of the user who created the override entry

o Creation Date and Time – Date and time at which the override entry was created

o Exclusion Date and Time – Date and time at which the override entry was excluded from being
reporting in STP

9
 MAINTAIN STP OVERRIDE ENTRIES THROUGH FILE

Purpose

The Maintain STP Override Entries through File (RPUSTOQ0) report is used to upload a batch of multiple
entries in the override table through a text file that contains the tab-separated override data in the following
sequence:

• Personnel Number

• Australian Business Number (ABN)

• ABN Branch Number

• Working Holiday Maker status

• Wage type that holds the override value

• Amount to be added to original value

• ETP Payment Date (optional; needed only if you are adjusting ETP payments in AETP cluster table)

• Description of override (optional)

Additionally, in phase 2 of the Single Touch Payroll solution, the file contains the following data as well:

• Income Type

• Country/Region Code

• Lump Sum E financial year

Prerequisites

Ensure that you maintain a number range for auto-generated sequence numbers assigned to override
entries.

This can be maintained in the STP Override Seq.No. (HR_AU_OVID) number range object in transaction
SNRO.

Note: No. should be maintained as '01' for STP overrides.

Selection

• Specify the financial year for which the override entries need to be uploaded.

• Select Test run if you wish to view and validate the override data from the text file without actually
updating the database.

• Specify the name of the text file that contains the tab-separated override data.

10
Output

• An ALV list of the override data from the text file is displayed.

• On clicking Back, a list of errors that might have occurred during validation of the override data is
displayed.

• When a live update is successful, the “Update successful” message is displayed in the status bar.

11
RECONCILE, FINALISE AND DECLARE DATA

Purpose

The Display, Finalise and Declare Data for STP Submission (HAU_DISPLAY_STP) report is used to view
and reconcile Single Touch Payroll (STP) data before sending it to the Australian Taxation Office (ATO). It
can also be used to do the following:

• Finalise employees, a declaration that will update the employee’s myGov display to indicate that the
Single Touch Payroll information from the employer is final for the financial year.

• Declare and sign STP data contained in a file before sending to ATO

Selection

Specify the following selection criteria:

• Australian Business Number and branch based on which you want to select STP submissions (every
STP file uniquely identified by a submission ID) for viewing and reconciliation

• The date on which the records were updated whose corresponding STP submission data is to be
viewed

• Whether you want to view all records or only those that are already declared or still undeclared

• Whether you want to view all records or only those that are already finalised or still unfinalised

• Specific submission IDs whose STP submission data you want to view

• Specific personnel numbers whose submission data are you want to view

Output

For the selected criteria, the system displays the payroll data and related organization data that will be
reported to the ATO.

• You can view the Payer Details, Payee Details, Allowances Summary, Deductions Summary and
ETP Summary separately by clicking the button with these options on the toolbar.

• On the Payee Details screen, you can mark a record as final by clicking Finalise.

o Auto Finalise will set the finalisation status of the selected records to the same status that
was last sent for the employee to the ATO. Note that this is applicable only when the
employee’s record was last sent in the same financial year. This flag is reset at the start of a
new financial year.

o Upon finalising a record, its Final Indicator field in the STP file gets updated.

o Upon unfinalising a record by clicking Unfinalise, its Final Indicator field in the STP file is set
to blank.

12
• After having reconciled the data if you are sure you want to send it to ATO, you can click Declare on
the Payer Details screen.

o In the Declaration and Authorisation pop-up that appears, do the following:

- If the data is declared by a registered agent, in Employer Declaration Details provide the
name of the employer’s representative authorised to declare STP data, as well as the
declaration date.

- In Declarer Credentials, the SAP name of the user who is logged in as well as the current
date appear automatically and cannot be edited.

- Select ‘I declare the above statements and information to be true ......... ’

- Click Update.

Note: It is mandatory for all the fields to have information for successful submission of an
STP file.

o Note that only ‘Declared’ data can be sent to ATO.

Once STP submission data is reconciled and declared, it is ready to be sent to the ATO. This can be
done via the B2A Manager in transaction PB2A by selecting the declared records that you wish to
send.

13
COMMUNICATE WITH ATO AND TRACK RESPONSES

It is possible to exchange data electronically between the employers and the Australian Taxation Office
(ATO). You can use the Business to Administration Manager (B2A Manager) to send and receive data
quickly and simply over the Internet. For detailed information about the procedure, see the documentation for
the H99_B2A-Manager report.

Data is exchanged with the ATO for Single Touch Payroll reporting via HTTPS as follows:

1. The data to be reported is added to an XML file and transferred to the SAP Cloud Platform Integration
(SCPI) server. The XML file is transferred from SAP ERP in GZIP compressed format.
2. The data is then wrapped in the Electronic Business XML Messaging Service 3.0 (ebMS3) standard and
sent to ATO.

Note: The standard signature permitted for this is 'SHA256'.

Prerequisites

Maintain the necessary settings and constants for communication with the ATO using the B2A Manager in
Customizing for Payroll Australia under Single Touch Payroll - Phase 2 -> Communication with Authorities
(B2A).

14
www.sap.com/contactsap

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.