SAP Single Touch Payroll Implementation Guide V1.1

Single Touch Payroll – Pay Event
Implementation Guide
Non-Concurrent Employment Solution (Non-CE)

Concurrent Employment Solution (CE)
EXTERNAL
Version: 1.1
Status: Final
TABLE OF CONTENTS
1 PURPOSE ......................................................................................................................................... 5
2 INTRODUCTION ............................................................................................................................... 5
2.1 Law Reference and Guidelines ...................................................................................................... 5
2.2 Single Touch Payroll Deferrals ...................................................................................................... 6
2.3 Scope of Solution ............................................................................................................................ 7
2.4 Software Requirements................................................................................................................... 7
2.4.1 Support pack Requirements ........................................................................................................... 7
2.4.2 SAP Cloud Platform Integration Requirements (SCPI) ................................................................ 8
3 DESIGN ............................................................................................................................................. 9
3.1 Standard Business Reporting (SBR) ............................................................................................. 9
3.1.1 What is ebMS3/AS4? ..................................................................................................................... 10
3.1.2 Pay Event Services ........................................................................................................................ 11
3.2 High Level Design .......................................................................................................................... 13
3.2.1 Overview of SAP Single Touch Payroll End to End Solution .................................................... 13
3.2.2 STP Business Process Overview ................................................................................................. 13
3.2.3 Getting Device AUSKey ................................................................................................................ 14
3.2.4 The Role of AUSkey in Standard Business Reporting Services............................................... 14
3.2.5 Overview of Business to Authorities(B2A) ................................................................................. 15
3.2.6 Overview of SAP Cloud Platform Integration (SCPI) ................................................................. 16
3.3 Detailed Design .............................................................................................................................. 18
3.3.1 Payroll Changes ............................................................................................................................. 18
3.3.2 Schema Changes ........................................................................................................................... 24
3.3.3 Tables.............................................................................................................................................. 24
3.3.4 Wage Types .................................................................................................................................... 27
3.3.5 Constants (T50BK) ........................................................................................................................ 31
3.3.6 Features .......................................................................................................................................... 31
3.3.7 Mid-year Go Live Utility (Transaction: PC00_M13_CLST_MYGL)............................................. 32
3.3.8 STP Report Programs ................................................................................................................... 33
3.3.9 Communication with Authorities (B2A) – Transaction PC00_M13_STP_SEND ...................... 44
3.3.10 SAP Cloud Platform Integration(SCPI) ........................................................................................ 49
3.3.11 Customer-Specific BADI’s ............................................................................................................ 49
3.3.12 Authorizations ................................................................................................................................ 49
4 IMPACT ASSESSMENT ................................................................................................................. 50
4.1 Impact on Pay Calculation ............................................................................................................ 50
4.2 Impact on Business Process ........................................................................................................ 50
4.3 Unsupported Functionality ........................................................................................................... 50
4.4 Security Authorisations ................................................................................................................ 50
PY-AU Single Touch Payroll (Australia)

Implementation Guide Version: 1.1 Page 2 | 67
4.5 Out of Scope Impact ...................................................................................................................... 51
4.6 System and Configuration Impact ............................................................................................... 51
4.7 Custom Developments .................................................................................................................. 51
4.8 Data Impact..................................................................................................................................... 51
4.9 Process Impact .............................................................................................................................. 52
5 IMPLEMENTATION APPROACH ................................................................................................... 53
5.1 Recommended Approach ............................................................................................................. 53
5.2 Sample Implementation Approaches .......................................................................................... 53
5.2.1 Combined with Support pack ....................................................................................................... 53
5.2.2 Standalone Project ........................................................................................................................ 54
5.2.3 Initial Migration to STP .................................................................................................................. 54
6 GETTING STARTED ....................................................................................................................... 55
7 CONFIGURATION INSTRUCTIONS .............................................................................................. 55
7.1 High Level Overview ...................................................................................................................... 55
7.1.1 Schema Changes ........................................................................................................................... 55
7.1.2 SAP Cloud Platform Integration (CPI) ......................................................................................... 56
7.1.3 T50BK – Integration with CPI........................................................................................................ 56
7.1.4 Table T5QGP .................................................................................................................................. 57
7.1.5 Table T512W – Evaluation Class 13 ............................................................................................. 57
7.1.6 Table T5QSO (STP Override Table) ............................................................................................. 58
7.1.7 Table T5QPC .................................................................................................................................. 58
7.1.8 New Feature – 13STP .................................................................................................................... 59
7.1.9 Pay Event – STP Report Generation ............................................................................................ 59
7.1.10 Communication with Authorities (B2A) – Transaction PC00_M13_STP_SEND ...................... 60
8 TESTING APPROACH .................................................................................................................... 60
8.1 ATO External Vendor Testing Environment (EVTE) Requirements ......................................... 61
8.1.1 Usage of ATO EVTE ABN .............................................................................................................. 61
8.2 Scenario Testing ............................................................................................................................ 62
9 ISSUE REPORTING ........................................................................................................................ 63
9.1 Logging Issues .............................................................................................................................. 63
10 APPENDIX....................................................................................................................................... 64
10.1 STP Pay Event Field to SAP Table Mapping ............................................................................... 64
10.2 SAP Cloud Platform Integration (SCPI) Guide & FAQ ............................................................... 64
10.3 Payroll Calculation log examples ................................................................................................ 64
10.3.1 QSABN ............................................................................................................................................ 64
10.3.2 QACRT ............................................................................................................................................ 65
10.3.3 QSETP ............................................................................................................................................. 65
10.4 Glossary.......................................................................................................................................... 65

Document Change Control
Version Description Date
Draft 0.1 Initial Draft 22.08.2018
Draft 0.2 Incorporate the Internal 20.09.2018

feedback
1.0 GA Release 11.10.2018
1.1 Updated customer 28.02.2019

feedback

1 PURPOSE
The purpose of this document is to

• Provide information on the design of the Single Touch Payroll Australian solution. This
will be at a reasonably high level.
• Provide information on the impact of the solution to existing SAP customers
• Provide a recommended implementation approach including required configuration
tasks and recommended testing.
2 INTRODUCTION
Single Touch Payroll (STP) is the next step in streamlining your payroll reporting. It will change the
way you report your employees’ payroll information to the ATO. It starts from 1 July 2018 for
employers with 20 or more employees.
You will report payments such as salaries and wages, pay as you go (PAYG) withholding and
super information to the ATO when you pay your employees.
What does STP mean?
• When you start reporting through Single Touch Payroll you will send your employees’
payroll and super information to the ATO from your payroll solution each payday.
• Your payroll cycle will not change. You can still pay your employees weekly, fortnightly or
monthly.
• Your payment due date for PAYG withholding and super contributions will not change.
However, you can choose to pay earlier.
• You may not need to provide your employees with a payment summary at the end of
financial year for certain payments you report through Single Touch Payroll. The ATO will
make that information available to employees through myGov.
• You will have the option to invite your employees to complete Tax file number declaration,
Superannuation standard choice form and Withholding declaration online. This feature will
not be available immediately.
• When you report to the ATO through Single Touch Payroll, your employees will be able to
view their year-to-date tax and super information through myGov.
For more information, please refer to the following hyperlink.

https://www.ato.gov.au/Business/Bus/Single-Touch-Payroll---for-employers/
2.1 Law Reference and Guidelines

In December 2014, the Australian Government announced it would cut red tape for employers and
come out with initiative known as Single Touch Payroll reporting. It was introduced to streamline
tax and superannuation reporting.
Single Touch Payroll legislation was included in the Budget Savings (Omnibus) Act 2016. It
became law on 16 September 2016. Please refer to the legislation link and then Schedule 23 –
Single Touch Payroll Reporting
Budget Savings (Omnibus) Act 2016 & Bill
• https://www.legislation.gov.au/Details/C2016A00055
• https://www.aph.gov.au/Parliamentary_Business/Bills_Legislation/Bills_Search_
Results/Result?bId=r5707

The ATO has provided all STP project guidelines and documentation via the Software developers
page. Please refer to the following website
Australian Taxation Office website
• ATO Website for Single Touch Payroll
• ATO STP Employer Reporting Guidelines
• ATO Software Developers Website for Single Touch Payroll
Standard Business Reporting
Please see below the Payroll Event MST Structures link
• http://www.sbr.gov.au/software-developers/developer-tools/ato/employer-
obligations-eo2#PayrollEvent
Other Sources
▪ Do not rely on other general information you source through search engines
▪ Consult with your tax agent for specific advice for your business
2.2 Single Touch Payroll Deferrals

Some employers may not be ready to start STP reporting from 1 July 2018 and will need a later
start date. ATO calls this process as a deferral. Employers, software providers, tax professionals
and payroll service providers can apply for a deferral.
The ATO has provided SAP with the Deferral Reference Number (DRN) and Deferral Date. Only
ECC6.0, ECC6.04 and ECC6.08 versions of SAP Payroll (including all EhPs) for AU and those
who are receiving support from SAP on those versions will be covered by the DRN.
Additional information
Below the ATO have listed the product version, deferral date and Deferral Reference Number.
Customers with 20 or more employees that use any of these product versions will have until the
first pay event falling on or immediately after the deferral date to submit their first Single Touch
Payroll report.
Employers that are unable to start their Single Touch Payroll reporting by the deferral date will
need to apply to the ATO for a separate further deferral. Similarly, if the ATO has not already
granted a deferral for the product version they are using, and they will not be ready to start Single
Touch Payroll reporting from 1 July 2018, they will need to apply directly to the ATO for a deferral.
Failure to lodge on time penalties will not be applied if Single Touch Payroll reporting obligations
are met in accordance with the approved deferral date. Where an employer has been granted a
deferral, they must continue to meet their existing lodgement and payment obligations (issuing
payment summaries and submitting PAYG withholding Payment Summary Annual Reports, BAS
for small and medium with holders, electronic payment for large withholders), unless they have
been granted separate relief from these obligations.
Product Versions Deferral Date Deferral Reference Number

ECC 6.0 On-premise 31/05/2019 66 361 489
ECC 6.04 On-premise 31/05/2019 66 361 489
ECC 6.08 On-premise 31/05/2019 66 361 489
ECC 6.08 Cloud 31/05/2019 66 361 489

SAP Customers who are unable to start their Single Touch Payroll reporting by the deferral date
(31/05/2019) will need to apply to the ATO for a separate further deferral. For further information,
please refer to the ATO website.
https://www.ato.gov.au/Business/Single-Touch-Payroll/Get-ready-for-Single-Touch-Payroll/Single-
Touch-Payroll-deferrals/
2.3 Scope of Solution
The scope of this solution is confined to the following

• Australian Private & Public-sector Solution
• Non-CE & CE
Functionality NOT supported:

SAP Design does not include these OPTIONAL features:
• Full File Replacement
• Alternatives are to use the update service, or next submit service
• Deferral of Off-Cycle Payments
• Must report on or before payment date for each off-cycle
• Onboarding in Pay Event
• Continue to report TFN Declaration details using the current method
• Generation of GUID (BMS ID)
2.4 Software Requirements
2.4.1 Support pack Requirements
The new solution will be delivered via OCT CLC/HRSP Support packages.
OCTOBER 2018 CLC/HRSP (PLANNED):

Product Release HRSP Level RTC (Release to Customer)
SAP_HR 600 G5 11.10.2018
SAP_HR 604 D1 11.10.2018
SAP_HR 608 59 11.10.2018
EA-HR 606 93 11.10.2018
EA-HR 607 82 11.10.2018
EA-HR 608 59 11.10.2018
PRE-REQUISITES HRSP (SAP_HR AND EA-HR RELEASES) FOR THE OCTOBER 2018
CLC/HRSP: MAY 2018 SYNC-POINT
Please see below the minimum HRSP level.

2.4.2 SAP Cloud Platform Integration Requirements (SCPI)
• Customer need to get the SCPI Licence.

• Integration Services Process Integration (PI) is the product required to support STP
Compliance
• STP specific pricing model has been developed for market readiness (standard
discount included)
• Multiple instances (Production/Dev/Test) have been catered for
• For more information, please contact your Account Executive (AE)

3 DESIGN
Single Touch Payroll is a government initiative to streamline business reporting obligations. When
an employer pays their employees, the payroll information will be sent to the ATO from their payroll
solution. Employers will be able to report salary or wages, pay as you go (PAYG) withholding and
super guarantee information directly to the ATO from their payroll solution, at the same time they
pay their employees.
The data need to be extracted from SAP Payroll system and send to ATO through Standard
Business Reporting (SBR) software using the SBR2 channel in a prescribed XML format. The
documentation of the format and data items has been released and published in the ATO website.
It can be found at the following ATO website.
http://www.sbr.gov.au/software-developers/developer-tools/ato/employer-obligations-
eo2#PayrollEvent.
3.1 Standard Business Reporting (SBR)
What is SBR?
Standard Business Reporting or SBR is a standard approach to online or digital record-keeping

that was introduced by government in 2010 to simplify business reporting obligations.
Software Developers (SWDs) build SBR rules into their business/accounting software to make it
‘SBR-enabled’. Businesses that use SBR-enabled software can then report using information
already recorded as part of running their business.
When a report is required, SBR-enabled software knows what information is needed for that report
and fills it out. The result for businesses is less time spent collating information, filling in forms and
submitting reports to participating government agencies. The only cost is the investment in SBR-
enabled software.
SBR is the primary channel for ATO and SuperStream superannuation industry transactions. It
works by using a dictionary of standard terms (Taxonomy) needed for each report. These terms
are used by government agencies for reporting, and by SWDs for software development.
The Australian Business Register (ABR) program is responsible for SBR.
What is the Message?

Using SBR-enabled software, businesses will be able to realise the benefits of reporting to
government directly from their financial, accounting or payroll system via messages.
A message through the system is made up of two parts
Envelope (ebMS)
• A set of layered extensions to the SOAP protocol, providing security and reliability features
enabling e-Commerce transactions.
• ATO is using the ebMS 3 standard with the addition of the AS4 profile
Payload (XBRL, XML, JSON)
• Allows for a standard base to communicate and exchange business information between
parties

• This is the chosen format for SBR and provides consistent reporting for agencies using the
associated AU taxonomy.
For further information on SBR as well as ebms3, please see below Important links
Software Developer detail on SBR.GOV.AU
http://www.sbr.gov.au/software-developers
SBR taxonomy architecture

http://www.sbr.gov.au/software-developers/enabling-sbr-in-my-application/sbr-taxonomy/taxonomy-
architecture
SBR eBMS web service artefacts (WIG, SDK)
http://www.sbr.gov.au/software-developers/developer-tools/new-form-pages/ebms-webservice
SBR forms / services for the ATO
http://www.sbr.gov.au/software-developers/developer-tools/ato
ATO common artefacts and reference documents

http://www.sbr.gov.au/software-developers/developer-tools/ato/ato-common-information-
documents#ATOplatformspecific
3.1.1 What is ebMS3/AS4?

The whole of government approach to provide a platform supporting obligations reporting and
business event transactions from business management systems (BMS) was jointly assessed by
ATO, SBR and Industry. For Single Touch Payroll, the digital message exchange capability
required a common authentication, message taxonomy and message transport standard. The
ebMS3/AS4 profile was selected.
OASIS open standard ebMS3/AS4 profile refers to electronic business using XML (extensible
markup language) Messaging Service version 3.0 with the AS4 (Applicability Statement 4)
conformance profile, to constrain and pare down options to the “just enough” design principles.
This official OASIS standard provides for secure payload-agnostic exchange of business
documents using web services that signifies the highest level of ratification.
The SBR profile draws on features from the ebMS3 core, ebMS3 advanced and AS4
specifications. The ebMS3 standard uses SOAP (Simple Object Access Protocol) messages to
exchange business documents. ebMS3 defines 6 message exchange patterns (MEP) that support
synchronous and asynchronous modes of operation.
The SAP ebMS3/AS4 solution is the Universal Client MEP:

Message Model/MEPs: Universal Client
• One-way push • Y
• One way pull • Y
• Two-way sync • Y Y – required to be implemented
• Two-way push pull • Y C – required for compliance
• Two-way push push • X X – optional
• Two way pull push • X
Msg Pulling & Partitioning:
ebMS3 • Authenticated pull • Y Normal text – Full implementation
Core Features • Msg partition channel • X Bold text – Partial implementation
Processing Modes • C Grey text – Optional
Message Packaging • Y
Error Handling • Y
Security Module:
• User/password • Y
• XML encryption • X
• XML signature • Y
Reliable Messaging Module • X
SAML Token • Y
SBR Security Signing of Message • Y
Split/Join • X
ebMS3 Multi-Hop Intermediate Point • X
Advanced Selective Pull • Y
Features
Bundling • X
MPC Sub Channels • X
Multi-Hop End Point • X

Reception Awareness • Y
AS4 Profiles Compression Body • Y
and Features Duplicate Detection • Y
MPC Sub Channels • X
Alt Authentication of Pull • X
3.1.2 Pay Event Services

The SAP Single Touch Payroll Pay Event services are sent using ebMS3/AS4 Bulk Message Types:
What is ebms user Message?

Structure of ebms response message.
For further information regarding the ebms3, please refer to the following website (
SBR ebMS3 webservices artefacts)
http://www.sbr.gov.au/software-developers/developer-tools/ato/employer-obligations-eo2#PayrollEvent

3.2 High Level Design
3.2.1 Overview of SAP Single Touch Payroll End to End Solution
3.2.2 STP Business Process Overview

3.2.3 Getting Device AUSKey
Points to Note:
• Please note that SAP provided consulting note (2705107) on how to create a App.
• Use the code in the consulting note to create an App
3.2.4 The Role of AUSkey in Standard Business Reporting Services

For further information on AUSKey, please see below Important links
• Australian Business Register AUSkey
• ATO AUSkey Access Manager Responsibilities
• Device AUSkey Custodian Responsibilities
• AUSkey Password Security
• VANguard Secure Token Services
• Digital Transformation Agency Identity Management
• DTA myGovID Trial
• ATO Operational Framework
• Tax Practitioners Board Tax Agent Services Regulation
• TPB Payroll Service Providers
3.2.5 Overview of Business to Authorities(B2A)
The Business to Authorities (B2A) Manager is a commonly used transaction by multiple countries
for managing files that need to be submitted to authorities (B2A is short form for Business to
Authorities). The B2A Manager is used for data exchange between SAP & ATO. It can send XML
files wrapped in the Electronic Business XML Messaging Service 3.0 (EbMS3) communication
protocol to the Australian Taxation Office (ATO) using the SAP Cloud Platform Integration (SCPI)
server.
For more information, please refer to the following link.
https://help.sap.com/viewer/ee28331957584b94a2239163f1cbbef5/603_HRSP_C1/en-
US/d258dd538636424de10000000a174cb4.html

3.2.6 Overview of SAP Cloud Platform Integration (SCPI)
What is SCPI?
SAP Cloud Platform Integration is a cloud-based platform, supported by SAP, that allows you to
orchestrate business processes and integrate data between on-premise system and cloud
solutions. It runs as a core service on SAP Cloud Platform and has the following key capabilities:
• Pre-packaged integration content – to integrate SAP and non-SAP applications

• Web-based tool – to discover, model and monitor integration content easily
• Support of process, data, mobile, and IoT integration use cases
• Strong focus on security – such as data isolation, multitenancy and message payload-level
encryption
• Rich set of connectivity options and standard adapters – for A2A and B2B integration
provided by SAP as well as by partners
• High performance messaging queueing – provided by the SAP Enterprise Messaging
Service.
• Adapter SDK – to build own custom adapters for additional connectivity needs
• Asset Interoperability – Integration mappings from SAP Process Orchestration can be
reused in SAP Cloud Platform Integration
Further information about SAP Cloud Platform Integration can be found in the following links:
SAP Help Portal - SAP Cloud Platform Integration

SAP Cloud Platform Integration Onboarding Guide
SAP Cloud Platform Integration Operations Guide

SAP Help Portal - SAP Cloud Platform Capabilities
SAP Cloud Platform - Integrate the Intelligent Enterprise
SAP Cloud Platform Integration Training Course
SAP Cloud Platform Integration YouTube Video
For more information about STP related configuration, please refer to the document “Cloud
Platform Interface for STP.pdf” in the SAP Note “2570793 - Single Touch Payroll (STP) Reporting
for Australia”

3.3 Detailed Design
3.3.1 Payroll Changes
New Cluster tables has been introduced to cater for the Single Touch Payroll. These clusters will
be created when you run the payroll. Customers can see these cluster tables in the transaction
PC_PAYRESULT. Please see below for the better understanding.
3.3.1.1.1 New Cluster Tables: SABN
• This is a standard SAP payroll cluster table used to store ABN and Branch Number
associated with the employees during payroll execution. It stores the Personnel
Area, Personnel Subarea, Start Date, End Date, Australian Business Number,
Branch Number. It also stores an indicator, if the table creation is done via Mid-Year
Go-Live Upload utility (details below) or payroll execution.
• Start Date and End date is based on the Payment date
a) If the Payment date is greater than pay period end date, then SABN End
date will be payment date
b) If the payment date is less than pay period start date, then SABN start date
will be payment date
c) If the payment date is between pay period start and end date, then there is
no change
d) ABN Split, WPBP Split – you will find the split in the table. For example, an
employee moves from ABN 99000000000 to ABN 88000014675. Please see
below the ABN Split in SABN table
• Payroll Splits (V_T530_all) – If you have configured your system to generate payroll
splits, you will be able to see multiple payroll results for the same period with
specific dates.
3.3.1.1.2 New Cluster Tables: ACRT
• This is a standard SAP payroll cluster table used to store cumulated year-to-date
results for an ABN and Branch Number combination for an employee during a pay
period. It stores the Australian Business Number, ABN Branch Number, Wage types,
Cumulation type, number, amount, currency, cumulation year, cumulation number,
begin date and end date. It also stores an indicator, to indicate whether an employee is
a Working Holiday Maker (WHM) during a pay period.
• ACRT will reflect each ABN/Branch/WHM flag split for the employee
• One of the key aspects SAP discussed in the co-design process with the ATO was the
impact of changing the reporting timeframe from EOFY to every pay. Right now, the
SAP payment summary allows for retrospective reassignment of ABN/Branch – who
SHOULD HAVE paid. However, moving to reporting each pay, ATO has clarified the
requirements for ABN changes. We must report the ABN/Branch that actually paid the

employee on payday – even if that is retrospectively changed, creating accounting
corrections and cash exchange/invoices between those ABNs. This means that for
STP, you will report the ABN on payday of the IN PERIOD and no corrections or
overrides will be required to reflect who SHOULD have paid – ATO want to know who
DID pay.
• Assigns all wage types to the ABN/Branch/WHM flag the employee had on payment
date, including retrospective payments
• When an ABN split occurs in a single period, then the ABN reported in ACRT will be
based on the payment date. For example, if an employee in ABN1 in given period
(01/07/xx – 15/07/xx) and he moved to ABN2 in same period (16/07/XX – 31/07/xx). In
this case ACRT will be formed based ABN relevant on the payment date.
• When there is an ABN change, the ACRT will show all the wage types for all ABNs,
current and from previous periods in the current financial year.
• For example, if employee changes from ABN1 to ABN2 then both the ABN will be
shown in the ACRT table with all the wage types and amount.
• Similarly, when an employee moves from WHM to Non-WHM, then a split will be
created for the ABN.
• Employee changed from ABN1 to ABN2. He is currently in ABN2. When there are any
retro changes back to ABN1 then it will be reported in ABN2 only. For example, MA01
(Meal Allowance). When he was in ABN1, he didn’t get Meal allowance. When you retro
back the Meal allowance. It is paid in the “IN Period”. It will get reflected in the ABN2
and it will not get reflected in ABN1. As per the ATO requirements, it should be
accounted for the current paying ABN.
• Payroll Splits (V_T530_all) – If you have configured your system to generate payroll
splits, you will be able to see multiple payroll results for the same period with specific
dates.
• When the employee changes ABN, SAP reports both ABNs till end of the financial year.
3.3.1.1.3 New Cluster Tables: AETP
• This is a standard SAP payroll cluster table used to store cumulated year-to-date
ETP payments for an ABN and Branch Number combination and payment date for
an employee during a pay period. It stores the Australian Business Number, ABN
Branch Number, Pay date, ETP Payment Code, Wage types, number, amount,
cumulation year and currency. ETP Payment codes are from T5QPC, for more
information, please refer to the section “3.3.3.2 Changes to the existing tables -
T5QPC”.
• An entry will be created for each ABN/Branch/WHM flag, the ETP Code and
Payment Date for each ETP wage type amount

• ETP record formation is based on the Payment date
• Irrespective of whether the ETP amounts are positive or negative, a new AETP
record will be created for each for each ABN/Branch/WHM flag, ETP Code and
Payment Date combination. Negative entries will be rejected by Pay Event report
and will require override to clear negative back to original result.
Positive Additional ETP Payments:
As ETPs must be reported by Payment Date (of In-Period) and ETP Code, any subsequent ETP
payments that are positive amounts will result in additional “YTD amounts” reported in the AETP
table and the Pay Event ETP View. In this example, the employee was originally paid ETP codes R
and O on 15.08.2018. The next pay, additional amounts of $30,000 and $5,000 were paid, creating
new entries:
This created an error-free Pay Event: See below

This is in accordance with the ATO requirements defined in the BIG S3.1.7:
OUTCOME: NO MANUAL INTERVENTION REQUIRED: OUTPUT AS PER ATO

REQUIREMENTS
OVERPAID ETP AMOUNTS – Corrections creating negative “YTD Amounts” in error
If you discover you have overpaid an ETP and correct the data, the amount will be recovered,
creating a claim, to be offset by a loan payment. The In-Period where the correction was entered
will generate a new entry in the AETP table to reflect the overpayment as at the Payment Date of
the In-Period:
In this example, it is discovered that the ETP R Payment was overpaid by $5,000, creating a
negative for the In-Period Payment Date:

When the Pay Event is generated for this pay period, the employee is rejected from the file, as you
cannot report negative YTD amounts:
OUTCOME: MANUAL INTERVENTION IS REQUIRED: EMPLOYEE NOT INCLUDED IN PAY

EVENT, LEGAL OBLIGATION NOT MET. (Please see below how to fix this)
STP Override Required to Move Overpayment to Original Period
Download the log report with the error details that contains the fields required for the override
(except for the wage types). Refer to the AETP table for that employee for that period to determine
which wage types are to be used in the overrides. Create an upload file to clear the negative at
15.04.2019 and reduce the original payment at 15.08.2018:

This now clears the error from the Pay Event report and shows the cleared error as at 15.04.2019
(does not remove it) and the reduced original payment of 15.08.2018:
This shows the manual effort required of any user to clear an ETP overpayment.
3.3.1.1.4 New De-Clustered Tables
Please see below the list of corresponding de-clustered tables for the above cluster tables:
1. P2RQ_SABN
2. P2RQ_ACRT
3. P2RQ_AETP
3.3.1.1.5 New Payroll Functions
1. QSABN: This Payroll function creates the Australian Business Number Details (SABN)
table with the ABN and Branch Number for each pay period. ABN details from
Configuration table (T5QGP) are associated with the corresponding Personnel Area,
Personnel Subarea applicable for the employee during a particular pay period. These ABN
details are subsequently used to create the ABN-specific CRT Details (ACRT) and ABN-
specific ETP Details (AETP).
2. QACRT: This function, creates the ABN-specific CRT Details (ACRT) table with the year-
to-date results cumulated ABN-wise. Subsequently, values can be fetched from this table
for reporting data based on ABN and Branch Number.

3. QSETP: This function, creates the ABN-specific ETP Details (AETP) table with the ABN-
wise employment termination payment (ETP) details.
4. Please see Payroll calculation log examples in the Appendix 10.2
3.3.2 Schema Changes

Please note that above new payroll functions need to be incorporated in the Non-CE (Private &
Public sector) and CE (Private and Public Sector) payroll schemas. For further information, please
refer to the “Schema changes.pdf” document in the SAP Note “2669232 - Payroll Australia:
Introduction of New Payroll Cluster Tables”.
3.3.3 Tables
3.3.3.1 New Tables

Table Name Description
T5Q_STP_ER This is a standard SAP table that stores employer relevant transaction
details used for STP reporting. Entries in this table are stored based on
Submission ID's (unique ID generated per ABN).
T5Q_STP_EE This is a standard SAP table that stores employee relevant transaction
details used for STP reporting. Entries in this table are stored based on a
combination of Submission ID's (unique ID generated per ABN) and
Employee numbers.
T5Q_STP_PAY This is a standard SAP table that store employee's payment relevant
details used for STP reporting. Allowances, Deductions, Employee
Termination Payments (ETP) information is stored in this table. Entries in
this table are stored based on a combination of Submission ID's (unique
ID generated per ABN) and Employee numbers.
T5QSO This is a customer specific override table used to override Year-to-Date
Payroll data for STP reporting.
3.3.3.2 Changes to Existing Tables
3.3.3.2.1 T5QGP
New fields have been added to the table to support STP reporting.

Intermediary Section
ABN/Branch (or WPN) will now be critical for payroll, as Single Touch Payroll requires it to be
specifically setup:
1. New group of fields added for Intermediary (Please see above)
2. Intermediary is used either for:
a. ‘Related parties’, where ABN of owner/device AUSkey owner is required for one of
these related parties
b. ABN and Registered Agent Number (RAN) for outsourced provider
3. Branch number validation:
a. cannot be <null> or zero
b. use 001 if no branch number
4. Employer (Single ABN only)
a. It is not required to define any new Intermediary fields
b. Employer should be the device AUSKey owner
5. Employers (Multiple ABNs) –
a. There must exist a legal relationship between the ABNs, as defined in AUSkey
Access Manager, using Cross Entity Authorisations and Roles
b. Define Intermediary ABN as device AUSkey owner/owner of wholly owned group
6. Registered Agent (RAN) -
a. Payroll services performed by agent registered with Tax Practitioners Board
b. ABN of agent and RAN
7. Review all existing entries to ensure consistency in fields used in pay event report

3.3.4 Wage Types
3.3.4.1 Evaluation Class 13 and Processing classes

There are some aspects of configuration that must be correct at pay calculation to generate the correct data
in the correct place for accurate STP Pay Event reporting. New Evaluation class 13 has been introduced.

• New Evaluation class 13 is used for the STP Reporting. It is like the existing Payment
summary evaluation class 11
• Wage types that need to appear on the STP report need to be configured in Evaluation
class 13
• Evaluation class 13 is better aligned with Pay event fields
• Allowance types aligned to tables on ATO website: https://www.ato.gov.au/business/payg-
withholding/payments-you-need-to-withhold-from/payments-to-employees/allowances-and-
reimbursements/withholding-for-allowances/
• Processing classes determine cumulations of wage types as well as appearance in CRT
and ACRT. ACRT follows the same cumulation rules as CRT but has all data at the ABN
/Branch/WHM level.
• Report reads the T5QGP to find the ABN/Branch based on the payment date
• For WHM employees, report reads the master data 188 (Tax Scale W or WU).
• For the better understanding of EC11->EC13->Pay Event field mapping, please refer to the
Excel sheet (SAP STP Pay Event Field Overview V0.3) in Appendix 10.2
• It is recommended that to compare the table T512W from client 000 to current QA/Dev
clients. This will help to identify the missing of evaluation classes
3.3.4.2 T5QPC – Employment Termination Payment (ETP) Codes
• No new fields have been added to this table.

• V_T5QPC assigns the various ETP evaluation classes to ETP codes. Currently, it stores all
ETP Payment codes corresponding to Evaluation class 11 settings.
• It is required to maintain corresponding entries for EC 13 in this view, for all entries which
currently exist in customer landscape with EC 11.

• This step is required for payroll to identify ETP codes and populate cluster table AETP
correctly. STP reporting also refers to this table to generate ETP data.
• This table defines which wage types assigned to the specific evaluation class 13 values for
ETP payments will appear as:
▪ ETP Codes:
– B Death Beneficiary – Non-Dependant – Split
– D Death Beneficiary – Dependant
– N Death Beneficiary – Non-Dependant
– O Life Benefit – Other
– P Life Benefit – Other – Split
– R Life Benefit – Redundancy
– S Life Benefit – Redundancy – Split
– T Death Beneficiary – Trustee
• Lump Sum A wage types are generated based on the setting in the table T5Q30 (Reasons
for Termination actions)
• As per the Pay event MST structures, pay event fields such as ETP code, Tax Fee
component, Taxable component and PAYGW Amount need to be reported.
ETP
Code Payment Type Reason Type Split Tax Free Taxable Tax
B Death Benefit Non-dependant Yes S3 ETP - Death Benefit - Taxable Component - S6 Tax - ETP - Death Benefit - Non-
N/A
Non-Dependant - Split Dependant - Split
D Death Benefit Dependant No DE ETP - Death Benefit - Taxable Component - T1 Tax - ETP - Death Benefit - Dependant
N/A
Dependant
N Death Benefit Non-dependant No ED ETP - Death Benefit - Taxable Component - TD Tax - ETP - Death Benefit - Non-
N/A
Non-Dependant Dependant
O Life Benefit Other No C2 ETP - Life Benefit - Tax Free EL ETP - Life Benefit - Taxable Component - TL Tax - ETP - Life Benefit - Other
Component - Other Other
P Life Benefit Other Yes C5 ETP - Life Benefit - Tax Free S1 ETP - Life Benefit - Taxable Component - S4 Tax - ETP - Life Benefit - Other - Split
Component - Other - Split Other - Split
R Life Benefit Redundancy No C4 ETP - Life Benefit - Tax Free LE ETP - Life Benefit - Taxable Component - TE Tax - ETP - Life Benefit - Redundancy
Component - Redundancy Redundancy
S Life Benefit Redundancy Yes C6 ETP - Life Benefit - Tax Free SE ETP - Life Benefit - Taxable Component - TS Tax - ETP - Life Benefit - Redundancy -
Component - Redundancy - Split Redundancy - Split Split
T Death Benefit Trustee No DT ETP - Death Benefit - Taxable Component -
N/A N/A
Trustee
Please see below the table T5QPC with entries

3.3.4.3 New Wage Types
New wage types have been created for the following reasons:
• To report Joint Petroleum Development Area (JPDA) and Foreign Employment Income
(FEI) related pay components
• To cater to new Allowances reporting
• New Wage types: FEGA, FEGW, FETX, JFGA, JFGW, JFTX, ACAR, ALAU, AMEA,
AOTH, ATRA, ATVL
• Evaluation class 13 needs to be configured for the new model wage types
• Evaluation Class settings have been updated for number of Wage types. These have been
detailed in the workbook (EVCL_specifications_&_wagetypes.xlsx) attached with SAP Note
2570793.
3.3.4.4 Changes to Existing Wage Types
• Changes have been made to existing wage types for the following reason:
New Evaluation Class 13 has been introduced with corresponding specifications to cater to
STP reporting requirements
• Refer to "EVCL13_Specifications_&_Wagetypes.xlsx" in the SAP Note “2570793 - Single

Touch Payroll (STP) Reporting for Australia” to get details of changes made to the existing
wage types. Please compare and adjust the changes from client '000' to all relevant clients
and systems.

3.3.5 Constants (T50BK)
Following constants has been delivered as standard table entries in 'T50BK'.

SERVC, ACTSB, ACTUD, BMSID, PATBN, PTRAN, RLEMP, RLINT, RLRAN, AUSKY, LPPUL, LPSUB,
PROA1, PROA2, PROA3.
These constants are used in B2A and some of the constants like Party type, employer role and Intermediary
role are passed to B2A and then to SCPI Iflows.
3.3.6 Features
This feature 13STP determines whether to check if the payroll control record for a period has been
exited for generating a live submission of the Single Touch Payroll (STP) report.
This feature is essentially used to allow customers to test the STP Report in a Dev/QA (non-Prod)
environment and not have the restriction of the payroll area period in an exit status. In a productive
client this needs to set to ‘Y’.
• If it is set to 'Y', then the user will be able to run the STP report in LIVE mode only if the
payroll control record for that period has exited.
• If it is set to 'N', then a LIVE run of the STP report can be performed without exiting the
payroll control record for the period.
Note: To ensure that correct STP data is generated, it is recommended that you set the value of
this feature to 'Y' in your productive client.

3.3.7 Mid-year Go Live Utility (Transaction: PC00_M13_CLST_MYGL)
This report is used to create the ABN-specific tables (ACRT, AETP and SABN) used in Single
Touch Payroll, for each payroll period from the beginning of the specified financial year. This report
will execute only if the tables (ACRT, AETP & SABN) do not exist from the very first payroll period
of the year. The tables will be created only for those payroll periods for which a payroll result
exists. The report fetches the existing payroll results, relevant master data and configuration data
to create these cluster tables.
PP1 PP2 PP3 PP4 PP5 PP6 PP7
PP8 PP9 PP10
• In the above scenario, PP1 is Pay period 1 (01/2018), PP2(02/2018) and so on

• Go live happens in the pay period 05 (Red)
• Since STP reporting is year to date, customer need to create ACRT, AETP, SABN table for the
period between PP1 – PP4
• Mid-year go live report will create those cluster tables in the payroll cluster for the period starting
from PP1-PP4

The report output comprises three sections as follows:
• Input – Displays names of the tables (Results Table, Cumulative Results Table and
T5QGP) and the infotype (IT0001) based on which the new cluster tables are created.
• Output – Displays names of the new cluster tables (SABN, ACRT and AETP) created.
• Error Messages – Displays errors that occurred while executing the report, if any.
• You can view the contents of any of the above tables by clicking on it.
Points to Note:
• This report should be used only once per employee for creation of new cluster tables in
mid-year go-live scenarios. It should not be used if Single Touch Payroll go-live is planned
from the beginning of a particular financial year.
• In the selection screen financial year should be 2019 or later because Single Touch payroll
is effective only from 01/07/2018.
• Report can run the Test Mode as well as Update mode
• It does not pick up the information from STP Override tables
• It can be run only once when you go live
• This report will mark the utility field in SABN table with “Y”
3.3.8 STP Report Programs

The data need to be extracted from SAP Payroll system and send to ATO through Standard
Business Reporting (SBR) software using the SBR2 channel in a prescribed XML format. The
documentation of the format and data items has been released and published in the ATO website.
It can be found at the following ATO website.

http://www.sbr.gov.au/software-developers/developer-tools/ato/employer-obligations-
eo2#PayrollEvent.
STP Pay Event file is generated in a prescribed format and send to ATO in following steps
1. Run the Payroll Driver
2. Run the STP Report (RPCSTPQ0)
3. Run the Display, finalise and Declare Report (HAU_DISPLAY_STP)
4. Run the B2A
5. SCPI will send XML files wrapped in the (EbMS3) format to the ATO
For the better understanding, please see details of above steps below.
3.3.8.1 RPCSTPQ0 (Transaction - PC00_M13_STP_GEN)
STP Generation Report is used for generation of STP data. It 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.
• Submit Event – When you select this option then program will create the submission id and
submit the data

• Update Event – Select to report changes to previously submitted year-to-date amounts via
an Update event. With update event, you do not report the employer/payer total. You can
only update and report the child/employee YTD totals.
• Test Run – Able to run in the Test mode (Simulation)
• Live Mode/Update Mode – Uncheck the Test Run check box
• Every off-cycle run need to be reported.
• STP report will generate unique submission id per ABN
Report Output – Payer Data
• Able to lists multiple ABN’s

• To view the list of employees under the ABN, please select the ABN and choose the Payee
Data
• Payer data is related to Employer information
• Unique submission ID's will be generated per ABN and Branch Number combination for
STP reporting.
• Payer data contains period totals from RT table. It may contain retro deltas flowing in from
the previous periods. It does not contain Year to date (YTD) values.
• In ATO Terminology, it is called Parent Total or Period total
• Period total will not include override amounts from T5QSO table
Report Output – Payee Data
• List all the employees based on the selection criteria

• Payee data contains Year to date totals from ACRT
• Wage types are retrieved based on the Evaluation class 13

• Super liability amount or OTE amount need to be reported to STP. SAP uses Super Liability
only.
• Employee/Child total will be ACRT + Override amount (T5QSO). If you didn’t maintain the
amount in T5QSO then it will be only ACRT amount.
• Payee commencement date is from the ENTRY feature.
• For all other fields in the Payee data, please refer to the mapping document in the Appendix
10.1 that may assist you to understand from where the data for the Pay Event report is
sourced.
Report Output – Allowance Summary
• List all the allowances types specified by ATO

• Allowance data contains Year to date totals from ACRT
• Allowance are shown in 2 decimal places as per the ATO Requirement
• ATO classify the allowance into six categories as below
Allowance Type Evaluation Class 13 Value

Car Expense Allowance CA
Laundry Allowance LA
Meal Allowance MA
Transport Allowance TR
Travel Allowance TA
Other Allowance OT

Report Output – Deductions Summary
• List all the deductions types specified by ATO

• Evaluation class 13 need to set up
• Deductions are shown in 2 decimal places as per the ATO Requirement
• Need to report two type deductions as below
Deduction Type Evaluation Class 13 Value

Union Fees UD
Workplace Giving WG
Report Output – ETP Summary
• List all the ETP Codes specified by ATO

• ETP Payment Codes are specified in the T5QPC.
• ETP record formation is based on the Payment date
• Irrespective of whether the ETP amounts are positive or negative, a new AETP record will be
created for each for each ABN/Branch/WHM flag, ETP Code and Payment Date combination.
Negative entries will be rejected by Pay Event report and will require override to clear negative
back to original result.
• Please refer to the section “3.3.1.1.3 New Cluster Tables: AETP” for negative and positive
payments

Report Output – Log
• List all the field Error/Warning/Successful messages in the Log

• It is report specific. For example, if you are in the payer screen then it displays payer error
details
• Users can download the errors via printing it to the spool
• Important Note:
✓ Business Management System (BMS) ID - STP users need to generate BMS ID at their
end. SAP STP solution facilitates users to store the generated BMS ID into
configuration provided in the SAP system. BMS Id acts like a “serial number” for the
payroll client/instance and should be the same in all technical environments.
✓ ABN Device AUSKey - Specific checks have been configured in the SAP system to
ensure that authorized ABN associated to the Device AUSKey matches either of the
two: Payer ABN or Intermediary ABN (T50BK)
✓ It is strongly recommended that you validate/reconcile the data generated via report
program (RPCSTPQ0) before executing this report in 'LIVE MODE'. Ignoring this step
might result in incorrect STP results for the employee/s in STP transaction tables
(T5Q_STP_ER, T5Q_STP_EE, T5Q_STP_PAY)
3.3.8.2 RPCSTOQ0 (Transaction – PC00_M13_STP_OVR)
• This transaction is used to override STP related Year-to-Date data for a group of
employees.
• STP generation report will pick up the wage types from the table.
• STP Generation Report = ACRT + Override
• Period totals/Payer totals will not contain the override
• Due to Audit Trail considerations, users can only create new entries, cannot modify or
delete entries.
• Mid-year go live utility does not read this table.
• Payroll functions (QSABN, QACRT, QSETP) will not read this table. This will not be part of
the payroll clusters
• Exclude wage type will exclude the wage type in Single Touch Payroll report.

• Incorrect entry of ABN/Branch may result in Pay Event errors in finding a matching ABN/Branch in
T5QGP, as Pay Event will read ACRT + T5QSO.
• Override table (T5QSO) has following fields

▪ Financial Year e.g.: 2019
▪ PERNR
▪ ABN
▪ Branch
▪ WHM flag
▪ Wage Type
▪ Amount
▪ ETP payment date
▪ Override Description
▪ Changed By
▪ Changed Time
▪ Exclude Wage type
▪ Exclusion Timestamp

3.3.8.3 RPUSTOQ0 (Transaction – PC00_M13_STP_OVR_UPL)
• The main objective of this report to help the users to maintain STP Override Entries through
File
• This 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:
o Personnel Number
o Australian Business Number (ABN)
o ABN Branch Number
o Working Holiday Maker status
o Wage type that holds the override value to be adjusted
o Amount to be added to original value
o ETP Payment Date (optional; needed only if you are adjusting ETP payments in
AETP cluster table)
o Description of override (optional)
• Users can run this report by specifying 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 updating the database. Specify the name of the text file that contains the
tab-separated override data.

3.3.8.4 Display, Finalise and Declare
What is Finalisation?
An employer is required to make a declaration to the ATO that they have provided all the
information for each employee for a financial year. This is done by providing the finalisation
indicator as a part of an employee’s STP report. This declaration allows the ATO to make the
employee information available for income tax return prefill for employees. It will also update the
employee’s MyGov payroll page, to show the employee income statement for STP reported
information is final for the financial year. This is similar to sending the Payment Summary Annual
Report (PSAR) to the ATO. Providing the declaration for STP reported information removes the
employer obligation to provide their employees with payment summaries in relation to the STP
reported information.
For further information, please refer to the Finalisation section of STP BIG Version 3 document in
ATO website.
Report HAU_DISPLAY_STP (PC00_M13_STP_VIEW) – Display, Finalise and Declare
• The main objective of this report to Display, Finalise and Declare Data for STP Submission
• This 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 criteria:
o Australian Business Number (ABN) and branch based on which you want to select
STP submissions (every STP file uniquely identified by a submission ID) for viewing
and reconciliation
o The date on which the records were updated whose corresponding STP submission
data is to be viewed
o Whether you want to view all records or only those that are already declared or still
undeclared
o Whether you want to view all records or only those that are already finalised or still
unfinalized
o Specific submission IDs whose STP submission data you want to view
o Specific personnel numbers whose submission data are you want to view
• 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.

Finalisation in SAP
• On the Payee Details screen, you can mark a record as final by clicking Finalise. System
controls the finalisation status is at employee level
• Auto Finalise/Finalise/Un-finalise button won’t be appearing in the Payer details screen,
only in the Payee screen.
• Auto-finalise copies the finalisation status from the last employee pay event (submit or
update). By default, the STP payee finalisation flag to set to False on each occurrence of
data. To reset back to its original setting if previously it was True, then use of the Auto
Finalise should be used. 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 also reset at the start of a new financial year.

• Upon finalising a record, its Final Indicator field in the STP file gets updated.
• Allows the user to finalise or unfinalized individual records
• Upon un-finalising a record by clicking Un-finalise, its Final Indicator field in the STP file is
set to blank.
• Finalisation is the formal communication from the employer to ATO to alert them that all
data for the employee is correct and complete and the data can be published, pre-filled into
their tax return, and ATO can act on that data with confidence. Getting this flag incorrect
may adversely impact the personal tax matters of the employee.
• At this stage, Final reconciliation on parent and child data and amounts is recommended
• 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. ATO expecting to receive parent amount of PAYGW
What is Declaration?
As per the ATO requirement, every customer need to declare the information they are sending to
ATO is “True and Correct”. It means that, there is a conscious decision by the user to choose to
submit the final form of the data. For more information, please refer to the ATO website
https://softwaredevelopers.ato.gov.au/STPdocumentlibrary (Authorization and Declaration)
Declaration in SAP:
Declaration report reads the information from the table T5QGP and produce the declaration
statements. SAP utilises the Employer Direct model as per the BIG V3.0 (section 5.3). For better
understanding, please see below
STP functionality has four types of declaration

1. Employer Single ABN Submission
2. Employer Multiple ABN Submission
3. Registered Agent (RAN) Single Submission
4. Registered Agent(RAN) Multiple submission

Customer need to declare for each Submission Id (parent) for each payroll area, pay period,
ABN/Branch
• Legal declaration statement required for SBR services
• User may select one submission at a time or all at once
• Different declaration statements for one ABN vs many
• Acceptance of legal liability that the data sent is true and correct.
• Making the declaration transforms the data into XML format
• Queues the XML STP Pay Event submission id in B2A Business to Authorities, ready to be
sent to the ATO
3.3.9 Communication with Authorities (B2A) – Transaction PC00_M13_STP_SEND
The Business to Authorities (B2A) Manager is used for data exchange between SAP Payroll
system and ATO. It can send XML files wrapped in the Electronic Business XML Messaging
Service 3.0 (EbMS3) communication protocol to the Australian Taxation Office (ATO) using the
SAP Cloud Platform Integration (SCPI) server.
The B2A Manager is a commonly used transaction by multiple countries for managing files that
need to be submitted to authorities (B2A is short for Business to Authorities). Each country has
slightly different display layouts. To change the country to Australia, go to the top menu and select
Go to – Change Country Group and select Australia (13).
3.3.9.1 Execution Process in B2A
1. Upon declaration of the data using the Display, Declare and Finalise Data for STP
Submission (HAU_DISPLAY_STP) report for a specific submission ID, document will be
created in the B2A Manager.
2. To display the documents, use the transaction PB2A.
3. Using the Document Area and the Document Class, you can filter the documents that you
want to process in the B2A Manager. For Australia, the following standard entries are
delivered:
• Document Area: QATO
• Document Class: STP

Field Name Description/Meaning
Area QATO - Pre-delivered by SAP
Document Class STP
Only Display open When you check this then it will only show the open process. If you
process uncheck this then it will show all the processes
History Which allows you to display list of activities
Log Log will give the user about the errors or successful information
B2A Identifier Submission id
Status & Sub status Status
Note Allows you to add some note/text to the submission id
Display Display the XML file
Simulation The ‘simulation’ tick box has no purpose in the Australia context.
4. To send the file to ATO (PUSH), you need to push the file to ATO by pressing
button
5. To pull the response from ATO, you need to press button again. Execute button
is used for Push and Pull
6. Successful Log will be displayed as follows

7. Each data file sent to the ATO can have one of the following different statuses:
Status Text Sub-status Text Description

New New Ready to be sent to ATO
In Process Sent to ATO Sent to ATO; technical receipt received
In Process No response; Retry No business response available for polling
Error Process Again Comm. error; Send again Data transmission issues – file not
submitted to ATO
Error Process Again Comm. error; Request again Business response polling request not
received by ATO
Ok Accepted Successful submission to ATO
Ok Partially rejected At least one successful submission
Ok Corrected Manually Rejected by ATO; error handling done
manually
Incorrect Rejected Rejected by ATO
Incorrect Fatal Error Product error
8. File will be verified for authorisations such as AUSkey, Access Manager, Cross Entity
Authorisations. If failed, no further processing: transmission rejected. Cannot resend.
9. ATO will check the Parent record and validates fields. It sends to ATO back end systems to
confirm integrity of reporting party. If not, reject whole message. If OK, ATO will start
processing child records.
10. ATO will check Child records and validates fields. Sends back message if all records okay,
may send error messages per child if data rejected by ATO back end systems.
11. File will be accepted if at least one child successful (status: Partial Rejection), but entire file
rejected if parent fails
12. All responses will be displayed in the log

13. Please refer to the document “B2A Manager – Procedure for Australia” document attached
to the SAP Note 2570793 for further details.
Additional Information:
1. Deletion of B2A File
If you accidently created the B2A file through STP reports or any error occurs or for any reason file
need to be deleted, then payroll users can delete the file.
• In B2A Manager select ‘Go To –> Further Administration’ from the top menu to take you to
the ‘HR-B2A: Reorganization B2A-Manager’ program (H99_B2AREORG).
• In the selection screen for the Functional area choose QATO and document class as “STP”
• Test a deletion by selecting the B2A identifier file(s) and select the ‘Delete’ button.
• To delete the files permanently (Update Mode), remove the ‘simulation’ flag and then
reselect the Delete button.
2. How to view or download the XML File in B2A
View/Display the XML:
An XML view of the data that is going to be sent or the response that was received from ATO can
be viewed in the B2A Manager. This can be useful when troubleshooting.
To view the file that is being (or was sent) to ATO:

• Highlight the required line (Submission id) that has the status ‘New’ (you may have to
expand the history to get to the original ‘new’ file line).
• Click the Display button.

Download the XML:
For the error handling or better search for a specific content, downloading the file will be very useful.
To download select the required line in B2A and select the display button to view the XML on screen. Then
go to the top menu and select “XML” and then “Download”.
3.3.9.2 Troubleshooting or Error Handling
1. Please refer to the B2A log for error handling. All the B2A errors or ERP errors will
be displayed in the B2A log
2. If you receive the Authentication error from ATO, please see meaning of the ATO
errors. Authentication Error Messages
3. If you receive the ebms3 errors from ATO, please see meaning of the ATO Errors in
the following link.
http://www.sbr.gov.au/software-developers/developer-tools/ato/employer-
obligations-eo2#PayrollEvent (Click the link -> Go to Appendix A of SBR ebMS3
Web Services Implementation Guide.docx)
4. Please note that some time ATO systems are down due to scheduled maintenance
or upgrades. During that time, you may not get the response from ATO and you may
be getting the error in pull request. For more information about SBR2 services
outages, please refer to the following link
https://softwaredevelopers.ato.gov.au/Known_outages
5. ATO Message Repository.zip file contains all ATO generated messages at the
validation platform boundary layer and backend error responses.
http://www.sbr.gov.au/software-developers/developer-tools/ato/ato-common-
information-documents#SS
6. Status of ATO SBR2 Environments

3.3.10 SAP Cloud Platform Integration(SCPI)
SAP delivered the package and iflows in the SCPI Environment.
Packages & Iflows

Package Name Single Touch payroll (STP) Reporting – Australia
Iflows Name • Data submission for STP reporting
• Receiving response for STP submission
ebMS3 AS4 • ebms3 AS4 Adaptor is built only in SCPI.

Adaptor
For more information regarding, how to implement the package and iflows, please refer to the
SCPI document. “Cloud Platform Interface for STP.pdf”
3.3.11 Customer-Specific BADI’s
To facilitate users to overwrite the data generated via the STP report, customer specific BADI's are
provided as part of STP report:
• Record level BADI (HR_AU_CUST_REC_STP) - This BADI can be used by users to

overwrite specific records in the STP report. Methods:
OVERRIDE_EE_DATA_PREPROCESS and OVERRIDE_EE_DATA_POSTPROCESS
• Report level BADI (HR_AU_CUST_REP_STP) - This BADI can be used to overwrite the
entire data set generated by STP report. Method: OVERRIDE_REPORT_DATA
3.3.12 Authorizations
• To run the STP reports (RPCSTPQ0), authorization objects P_KW_REPT need to be
assign to the Roles. SAP did not provide any standard profile. Customer need to create the
profiles
• Transaction code “PFCG” can be used to create and assign authorization profile to users.
• Create Authorization profile “ZPAXX” using authorization object “P_KW_REPT” with access
to reports “RPCSTPQ0_**” and assign it to authorized users.
• Ensure that authorized users with profile “ZPAXX” can access the 5 inbuilt report outputs -
RPCSTPQ0_ER, RPCSTPQ0_EE, RPCSTPQ0_ETP, RPCSTPQ0_DED,
RPCSTPQ0_ALL.
• Authority Object related to B2A Manager is 'P_B2A'.

4 IMPACT ASSESSMENT
4.1 Impact on Pay Calculation

Upon implementation of SAP Note 2669232, new payroll functions ensure cumulations at
Australian Business Number (ABN) and Branch ID's for each of the corresponding WT's present in
RT and CRT.
SABN, ACRT and AETP needs to be created from the beginning of the financial year. Once you
implement this SAP Note into your system, SABN, ACRT and AETP needs to be created from the
first pay period of the financial year.
4.2 Impact on Business Process

ATO strongly recommend the employers to review their business process. There are a few things
employers should check before Single Touch Payroll starts.
• Make sure the right people in your business know about Single Touch Payroll
– especially your payroll staff.
• Check if you are paying your employees correctly.
• Check if you are calculating your employees’ super entitlements correctly.
• Check if you are addressing overpayments correctly.
• Is your employee information accurate, including names, addresses, date‑of‑birth records?
• Meeting the legal obligations
– Check who will perform these STP Reporting tasks in your organization?
– Check who will accept the liability for one/all ABN’s / Branch
4.3 Unsupported Functionality
SAP Design does not include these OPTIONAL features:

• Full File Replacement
• Alternatives are to use the update service, or next submit service
• Deferral of Off-Cycle Payments
• Must report on or before payment date for each off-cycle
• Onboarding in Pay Event
• Continue to report TFN Declaration details using the current method
• Generation of GUID (BMS ID)
4.4 Security Authorisations

• As mentioned in the section “3.3.12 Authorizations”, new authorization objects were
introduced for the STP as well as B2A.
• Customer need to re-evaluate their authorization matrix, roles and profiles

4.5 Out of Scope Impact
Changes to the Employee Master Data screens are outside the scope of these changes.
4.6 System and Configuration Impact
The changes to the system can be summarized by the following

• Introduction of 3 new payroll functions and 3 new de-clustering tables.
• The solution is simply a change to ensure cumulations at Australian Business Number
(ABN) and Branch ID's for each of the corresponding WT's present in RT and CRT. The
inputs and outputs are the same, with only difference being creation of 3 new cluster tables
in pay results for an employee. After implementing the solution, this change shall largely be
transparent to the user as far as cumulations are concerned at ABN and Branch Number
level.
• Importantly, any retrospective calculation over old results will generate the same results, as
previously.
• There are additional details in the payroll log related to the ABN and Branch level
calculations. This allows end users to view key values and results related to the
cumulations at ABN level.
4.7 Custom Developments
1. New Evaluation class 13 has been introduced for the STP Reporting. Any custom
development reports/functions using this evaluation class need to be changed
2. New cluster tables like ACRT, SABN, AETP has been introduced. Any payroll reports
reading cluster tables need to be analysed and confirm whether any changes are required
3. Any custom developments / custom payroll rules or schemas affecting payroll calculations
will require separate customer analysis to confirm whether any additional changes are
required.
4. Any third-party reconciliation or reporting tools need to be re-evaluated
4.8 Data Impact
• There are no additional or new data requirements for the Single Touch Payroll solution in
respect to master data or payroll results.
• From a technical perspective, the existing Technical wage types will remain, and many new
model wage types are delivered. These are used as a part of STP calculations and should
not impact any other standard reporting.
• Customers who go live in the middle of financial year need to run the Mid-year go live utility
for the continuity of STP Reporting. For more information about Mid-year go live report,
please refer to mid-year go live utility section.
• STP streamlined reporting requires data to be accurate in real time and therefore
customers should review any data that will impact STP to ensure that it will be correct as
generated in payroll. Any manual workarounds or interventions should be reviewed for
automation.
• As part of transition, that any 2017/2018 PS overrides that are set to reverse AND any
existing PS override entries for 2018/2019 must be created in SAP STP override table.

4.9 Process Impact
Impacts to customer payroll procedures and processes will include
• Review Pay Calculation variants to be updated to reflect new schema
• Review batch Pay Calculation jobs to use new schema / variants
• Process documentation to be reviewed and checked for references to old schema and
change to new schema as appropriate
• Since all other objects delivered for STP are new, customers will not be seeing an
impact on their already existing processes.
• New STP Processes and working instructions need to be built
• As per the ATO guidelines, adhoc advance payments don’t have to be reported
because it will pick up in the next payroll.

5 IMPLEMENTATION APPROACH
5.1 Recommended Approach
Timelines for implementation will vary for each customer and will be dependent on number of
employees, number of custom developments, project resources etc.
5.2 Sample Implementation Approaches
There are two approaches for applying the new Single Touch Payroll solution.
1. Apply the changes as part of a normal support pack application

2. Apply the changes as a standalone project.
Both approaches follow the same steps; however, the standalone project could potentially be
done quicker as it allows for testing focussed directly on the STP.
5.2.1 Combined with Support pack
This approach is to apply these changes as part of the extended Support Pack application
process. It is recommended that the process be completed using the following steps:
1. Apply Support Packs and identify any payroll variations.

2. Apply STP Changes and identify any payroll variations
3. Perform targeted scenario Testing
This approach will allow you to clearly identify, if there are differences, what the source of the
difference is.
Most customers have well defined approaches when it comes to applying Support Packs. The
list below is simply a recommended approach to follow:
1. Perform a copy of Production data to Test environment.

2. Run Baseline Payroll run
3. Extract Payroll results for later comparison
4. Apply Support Packs
5. Re-run Payroll and compare the results to Step 3
7. Apply STP Changes
8. Re-run Payroll and compare the results to Step 6
9. Perform UAT / Scenario testing
10. Sign off Test Results
11. Migrate to Production

5.2.2 Standalone Project
This approach is to implement the new solution as a separate project and to apply the changes
and perform targeted testing of the new solution. This would include the following steps:
1. Perform a copy of Production data to Test environment.

2. Run Baseline Payroll run
4. Apply STP Changes
5. Run Payroll and compare the results to Step 3
6. Perform Targeted Scenario testing
7. Sign off Test Results
8. Migrate to Production
5.2.3 Initial Migration to STP
SAP recommends following approach to the customers who go live with STP solution in the middle
of the financial year.
Initial migration to STP solution
1) Execute Mid-Year Go Live Report to update clusters for all Employees (terminated and
active) after STP solution migrated into each environment and before executing next payroll
of any frequency
2) Perform an Update submission (for all employees in the current financial year – both
terminated and active) via STP report
3) Declare and send to ATO this Submission
4) Submit current payroll results via STP report/declare/send to ATO - BAU
SAP recommends following approach to all customers at the end of the financial year.
At year end:
1) Perform an Update submission for all employees via STP Report
2) Finalise all the employees (both Terminated and Active) in the Submission
3) Declare and send to ATO

6 GETTING STARTED
To be able to use the Single Touch payroll solution requires following steps:
• Implementing prerequisite/minimum HRSP/SAP Notes
• Apply the OCT 2018 CLC/HRSP Support packs
• Applying the configuration changes in ERP
• Subscription to SAP Cloud Platform Integration (SCPI)
• Applying configuration changes in SCPI
7 CONFIGURATION INSTRUCTIONS
7.1 High Level Overview
The required configuration tasks are detailed below. The full details of the changes will be
maintained in the SAP Note. We’ve attempted to consolidate the details in this document.
7.1.1 Schema Changes
Schemas need to be changed for the Non-CE (Private & Public sector) and CE (Private and Public
Sector) payroll schemas. For further information, please refer to the “Schema changes.pdf”
document in the SAP Note “2669232 - Payroll Australia: Introduction of New Payroll Cluster
Tables”.

7.1.2 SAP Cloud Platform Integration (CPI)
For more information regarding, how to configure the CPI, please refer to the SCPI document.
“Cloud Platform Interface for STP.pdf”
7.1.3 T50BK – Integration with CPI

This table is client specific table. Most of the entries are pre-configured except AUSKY & BMSID
T50BK defines the device AUSkey owner
▪ Pay Event generation checks authorization relationships between T5QGP and T50BK
▪ Mandatory validations cannot create file if in error, else file will be rejected by ATO
Field Name Configuration Instruction

AUSKY Need to configure the Customer ABN
BMSID Obtain each GUID by accessing URL:
https://www.uuidgenerator.net/guid
Additional Information – BMS ID

• BMS Identifier is used by ATO to create a virtual 3rd dimension to the ABN/Branch, to be
able to distinguish from which payroll your pay event is sent:
• It is client-specific
• Must be a GUID Version 4
• Obtain each GUID by accessing the GUID Generator Website

• It is unique to your system/client
• BMS Id is used by ATO to further categorise YTD employee data. If changed, YTD
amounts must be managed according to BMS Id balances
• Employees will see this reference in myGov ATO Online
7.1.4 Table T5QGP

1. Intermediary section needs to be configured
2. ABN Branch number should not be 0. Need to configure either 1 or greater than 1
Please refer to the above section “Changes to existing tables T5QGP” for more details.
7.1.5 Table T512W – Evaluation Class 13

• New Evaluation class 13 has been introduced for STP Report
• Configuration of customer wage types included in STP Pay Event report is required
• Please refer to the above section “Wage types” for more details.
• For the better understanding of EC11->EC13->Pay Event field mapping, please refer to the
Excel sheet (SAP STP Pay Event Field Overview V0.3) in Appendix 10.2

7.1.6 Table T5QSO (STP Override Table)
To execute STP ‘Overrides’ functionality, it is required to maintain an interval for auto generating
sequence numbers for override entries. This can be done using the following steps:
1. Execute ‘Transaction Code’ SNRO
2. Enter Object name –> HR_AU_OVID
3. Select ‘Change’ mode and select ‘Interval Editing’ as shown in the below screenshots:
4. Select ‘Change Intervals’ and enter a suitable range as shown
The ‘Year’ must be current year/ other years when the override functionality will be used.
7.1.7 Table T5QPC
• V_T5QPC assigns the various ETP evaluation classes to ETP codes. Currently, it stores all
ETP Payment codes corresponding to Evaluation class 11 settings.
• It is required to maintain corresponding entries for EC 13 in this view, for all entries which
currently exist in customer landscape with EC 11. Sample entries are depicted below:
• This step is required for payroll to identify ETP codes and populate cluster table AETP
correctly. STP reporting also refers to this table/view to generate ETP data.

7.1.8 New Feature – 13STP
Feature Description Details

This feature determines
13STP Determine whether to check
whether to check if the payroll
payroll control record exit for
control record for a period has
STP
been exited or not for
generating a live submission of
Single Touch Payroll (STP)
report.
Refer feature documentation
for further details.
7.1.9 Pay Event – STP Report Generation
• STP Report is generated based on the payroll clusters, master data and configuration
tables. For more information, please refer to the above sections “STP Report Programs”.
• Please find a mapping document in the Appendix 10.1 that may assist you to understand
from where the data for the Pay Event report is sourced. It also includes a mapping of the
EC11 to EC13 to Pay Event fields, which is a simple overview to assist you with
configuration.

7.1.10 Communication with Authorities (B2A) – Transaction PC00_M13_STP_SEND
To execute B2A functionality, it is required to maintain an interval for auto generating

sequence numbers. This can be done using the following steps:
Create Number Range with name 'HRB2A' for interval '01'.

a) Execute transaction code 'SNRO'.
b) Enter Object Name as 'HRB2A' and select 'Display'.
c) Select 'Interval Editing' tab.
d) Select 'Change Intervals' tab
e) Create an entry as follows:
i. No -> 01
ii. From No. ->0000000000000000001
iii. To Number -> 99999999999999999999
iv. NR status -> 10
f) Save your entries.
8 TESTING APPROACH

8.1 ATO External Vendor Testing Environment (EVTE) Requirements
For the testing purposes, customers can submit their STP file to ATO EVTE Environment.
customers cannot use their production ABN for testing in the EVTE environment. Please see below
the list of requirements from ATO.
Requirement for ATO EVTE
• Must scramble the names of employees to de-identify them

✓ TFNs may only be used as follows:
✓ ATO EVTE TFN: 485215078 and/or
✓ ATO special codes: all 0s, 1s, 3s, 4s and/or
✓ Production TFNs that are re-assigned to other identities (cannot be their own TFN)
• Cannot use full payload if >100 child records per ABN
• EVTE has no integrated systems connectivity:
✓ TFN database
✓ AUSkey and Access Manager
✓ myGov or ATO Online or Business Portal
• Cannot use production ABN/Branch or WPNs:
✓ Employer (Single ABN) – use ABN/Branch of 14088411787/001
✓ Employers (Multi ABNs) – Please see below
✓ T50BK device AUSkey owner ABN to be set to 14088411787 for the authorisations
to be valid to send STP Pay Event files in EVTE.
8.1.1 Usage of ATO EVTE ABN
Customer ABN’s cannot be used in the EVTE environment. ATO will only accept a few ABN’s in
EVTE. Therefore, customers should configure dummy personal area and sub area for testing STP
connectivity to EVTE in development and Quality environment (Non-Production Environment).
Please see below the configuration for ABN and intermediary ABN field in T5QGP table and for
other fields you can use the existing configuration in your system
Employers (Single ABN) - T5QGP Configuration for EVTE
INTERMEDIARY
ABN/BRANCH TYPE/ROLE ABN
Device AUSkey owner and
14088411787/001 “corporate head office”
Employers (Multiple ABN) - T5QGP Configuration for EVTE
INTERMEDIARY
Device AUSkey owner and “corporate head
14088411787/001 office”
16000023656/001 Related Parties 14088411787
19087046080/001 Related Parties 14088411787
17088268884/001 Related Parties 14088411787
62483468038/001 Related Parties 14088411787

INTERMEDIARY
11000002568/001 Related Parties 14088411787
11000703613/001 Related Parties 14088411787
32087112105/001 Related Parties 14088411787
49425379391/001 Related Parties 14088411787
Employers with Registered Agent - T5QGP Configuration for EVTE
INTERMEDIARY REGISTERED
ABN/BRANCH TYPE/ROLE ABN AGENT NUMBER
DEVICE AUSKEY OWNER 17801003
AND “CORPORATE HEAD
17088268884/001 OFFICE” 14088411787
Note:
Please note that ANY branch codes can be used for the test ABNs in EVTE environment. You can
use “001” or any other code. You can use the Registered Agent Number (RAN) with any of the
ABN or Branch as well
8.2 Scenario Testing
The scenarios selected for testing should be run for each of the payroll cycles and/or payroll
areas used in the organisation.
Sample list of scenarios / conditions to be tested include:
Pay Calculations
• Standard & Complex pays for different tax scales

• Bonus Processing
• Off-cycles
• Termination Processing including
o Termination Organiser
o Various Lump Sum payments
• Payroll Area Changes
• Super calculations
• ABN Changes
• Retro processing within financial year and across financial year
• Transition to STP New solution
o Retro calculations over pay periods originally calculated before STP go live
period
o Retro calculations over pay periods originally calculated after the STP go live
period
o Ensure that ACRT, SABN, AETP tables are created by mid-year go live utility
o Reconciliation of ACRT Vs CRT Vs RT. Customers can use either third party
tool or international report Payroll results Dashboard. Program name is
RPUCVRX and Transaction code - HR99S00_PY_DASHBOARD

Reporting
• Payslip
• Pay Details Report
• Pay Summary Report
• Run to Run Report
• Reconciliation reports
• Reconcile ACRT Vs CRT Vs RT
• Test third party tools reports if relevant
Post to Finance (FICO Posting)
• Confirm balanced pays

• Confirm error free posting document creation
• Confirm successful post to finance
9 ISSUE REPORTING
9.1 Logging Issues
In the event any issues are encountered which require SAP support, please log via SAP
Marketplace and raise the customer incident using the Application Area of PY-AU for Non-CE
customers and for PY-AU-CE for Concurrent Employment (CE) customers with OSS prefix as
“STP:xxxxxx”.

10 APPENDIX
10.1 STP Pay Event Field to SAP Table Mapping
Excel Sheet SAP STP Pay Event Field Overview V0.5 under “Attachments” section of this Note
contains following items
• Data Mapping between Pay event fields and SAP Tables

• Mapping between Evaluation class 11 -> Evaluation Class 13 -> Pay event fields
• Newly created wage types
10.2 SAP Cloud Platform Integration (SCPI) Guide & FAQ
Please refer to OSS Note 2705107 for the CPI guide and FAQ document
10.3 Payroll Calculation log examples
10.3.1 QSABN
Payroll AS-PARM1 AS-PARM1 AS-PARM1 AS-PARM1

function
QSABN

10.3.2 QACRT

function
QACRT
10.3.3 QSETP

function
QSETP
10.4 Glossary
Term Definition
A digital service provider (DSP) is anyone who develops or delivers digital

Digital service
services that assist the Australian community (and business) to meet their tax

provider and super obligations
BMS ID Business management software identifier.
This is the ATO equivalent of an employer-issued payment summary containing

Employment the annual STP data reported by employers. It is published by the ATO on
income statement myGov. If an employee does not have a myGov account or access to the
published data, they can contact ATO.
The generic term used to describe finalisation. This is where an employer is

required to make a declaration to the ATO that they have provided all the
Finalise
information for each employee for a financial year. This is done by providing the
finalisation indicator as a part of an employee’s STP report.
This is the file generated by STP-enabled software which includes payments

Pay event
subject to withholding.
Payee payroll ID A unique number that identifies an employee.
Sending Service Providers (SSPs) enable digital service providers to transmit

data to the ATO via a standard platform (known as SBR ebMS3 messaging
standard). They carry out the following actions on behalf of a DSP:
Sending service
provider 1. Facilitate the transformation of Single Touch Payroll (STP) compliant data
received from an STP compliant solution.
2. Transmit STP conforming data to the ATO.
STP report or
The generic name for reporting either a pay event or an update event.
reporting
This is the term used refer to the mechanism which allows an employer to
Update event
report changes to an employee’s YTD amounts via STP.

www.sap.com/contactsap
© 2018 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.


SAP Single Touch Payroll Implementation Guide V1.1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Single Touch Payroll Implementation Guide V1.1

Uploaded by

Copyright:

Available Formats

Single Touch Payroll – Pay Event

Non-Concurrent Employment Solution (Non-CE)

PY-AU Single Touch Payroll (Australia)

PY-AU Single Touch Payroll (Australia)

Version Description Date

Draft 0.1 Initial Draft 22.08.2018

Draft 0.2 Incorporate the Internal 20.09.2018

1.0 GA Release 11.10.2018

1.1 Updated customer 28.02.2019

PY-AU Single Touch Payroll (Australia)

The purpose of this document is to

For more information, please refer to the following hyperlink.

2.1 Law Reference and Guidelines

PY-AU Single Touch Payroll (Australia)

2.2 Single Touch Payroll Deferrals

Product Versions Deferral Date Deferral Reference Number

PY-AU Single Touch Payroll (Australia)

2.3 Scope of Solution

The scope of this solution is confined to the following

Functionality NOT supported:

2.4 Software Requirements

2.4.1 Support pack Requirements

OCTOBER 2018 CLC/HRSP (PLANNED):

Please see below the minimum HRSP level.

PY-AU Single Touch Payroll (Australia)

• Customer need to get the SCPI Licence.

PY-AU Single Touch Payroll (Australia)

3.1 Standard Business Reporting (SBR)

Standard Business Reporting or SBR is a standard approach to online or digital record-keeping

The Australian Business Register (ABR) program is responsible for SBR.

What is the Message?

PY-AU Single Touch Payroll (Australia)

SBR taxonomy architecture

ATO common artefacts and reference documents

3.1.1 What is ebMS3/AS4?

PY-AU Single Touch Payroll (Australia)

Multi-Hop End Point • X

3.1.2 Pay Event Services

What is ebms user Message?

PY-AU Single Touch Payroll (Australia)

PY-AU Single Touch Payroll (Australia)

3.2.1 Overview of SAP Single Touch Payroll End to End Solution

3.2.2 STP Business Process Overview

PY-AU Single Touch Payroll (Australia)

3.2.4 The Role of AUSkey in Standard Business Reporting Services

PY-AU Single Touch Payroll (Australia)

3.2.5 Overview of Business to Authorities(B2A)

For more information, please refer to the following link.

PY-AU Single Touch Payroll (Australia)

• Pre-packaged integration content – to integrate SAP and non-SAP applications

SAP Help Portal - SAP Cloud Platform Integration

PY-AU Single Touch Payroll (Australia)

PY-AU Single Touch Payroll (Australia)

3.3.1 Payroll Changes

3.3.1.1.1 New Cluster Tables: SABN

3.3.1.1.2 New Cluster Tables: ACRT

PY-AU Single Touch Payroll (Australia)

3.3.1.1.3 New Cluster Tables: AETP

PY-AU Single Touch Payroll (Australia)

Positive Additional ETP Payments:

This created an error-free Pay Event: See below

PY-AU Single Touch Payroll (Australia)

OUTCOME: NO MANUAL INTERVENTION REQUIRED: OUTPUT AS PER ATO

OVERPAID ETP AMOUNTS – Corrections creating negative “YTD Amounts” in error