Skip to Content
Technical Articles

How to set up Single Touch Payroll (Australia) Using SAP Cloud Platform Integration/Employee Central Payroll.

In this blog post I have mentions the steps in how to configure Single Touch Payroll Australia via SAP Cloud Platform Integration (SCPI). After making the necessary configuration in the payroll mentioned in the master note 2674330 &2570793.

How to set up single touch Payroll (Australia) Using SAP Cloud Platform Integration/Employee Central Payroll.

Single Touch Payroll (STP) aims to align the employer’s reporting of Pay As You Go (PAYG) withholding (PAYGW) and superannuation contributions with their payroll processes.

Every employer (including AU subsidiaries of overseas organizations) that uses its own payroll software must electronically report employees’ payments and deductions to the Australian Taxation Office (ATO) on or after each payday, in real time, for each payroll run. Electronic communication with the government gateway for customers in Australia is now enabled via SAP Cloud Platform Integration (SCPI).

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

Payroll Calculation log

QSABN

In the payroll log look for the ABN no

Prerequisites on the SCPI side

The user whom you will engage for the communication must be assigned the following permission: • ESBMessaging.send on the iflmap application This permission is needed so that the SAP ERP and the SCPI systems can communicate with each other.

The following roles are required for other administrative and operations tasks in SCPI:

  • AuthGroup.Administrator on the tenant application This permission is needed to add, replace or delete keystore entries in SCPI.
  • AuthGroup.IntegrationDeveloper on the tenant application This permission is needed so that the required integration flows (iFlows) can be deployed on the SCPI tenant.

Task which you need to do

  1. Deploy certificates and credentials to the SCPI tenants
  2. Copy iFlows to workspace
  3. Configure iFlows
  4. Deploy iFlows

Deploy certificates and credentials to SCPI tenants

  1. Register for a device AUSkey by logging in to your AUSkey Manager at https://abr.gov.au/. Follow the instructions from the Australian Business Register at https://www.technicalhelpdesk.com.au/s/article/Device-AUSkey-Guide.

 

  1. The downloaded device AUSkey file is in XML format.
  2. Login to SCPI and go to the Operations view. In the Manage Security section, select the KeyStore tile. Using the Add dropdown button, select ‘KeyStore’. Enter your device AUSkey KeyStore
  3. Deploy the KeyStore

Copy iFlows to workspace

  1. In your browser, go to the web UI of the tenant
  2. From the menu in the upper left corner, choose Discover
  3. Click the package name
  4. In the lower right corner, choose Copy to Workspace.

Configure iFlow – Data Submission for STP Reporting

  1. In your SCPI tenant, from the menu in the upper left corner, choose Design.
  2. Click the package Single Touch Payroll (STP) reporting – Australia.
  3. For the iFlow that you want to change, choose Actions -> Configure
  4. Must configure the sender tab, Receiver tab and More tab

Configure iFlow – Receiving response for STP submission

The way to configure is same.

Deploy iFlows on test and productive tenants

  1. In your SCPI tenant, from the menu in the upper left corner, choose Design.
  2. Click the package name.
  3. For the iFlow that you want to deploy, choose Actions -> Deploy

 

Setup of SAP ERP system

In the Employee Central payroll system, you need to configure the Web Services in the SOA Manager through which communication between the Employee Central payroll system and the government gateway via SCPI can be established. In the following steps, the Employer Alignment Submission (EAS) Report (RPCEASG0) is used as an example: Note: You must configure the proxy for each report. For some reports you need to configure the proxy only once, while for the other reports you must reconfigure the proxy once every year due to object names and port names changed as per government requirements. For more information, see the table of object names and port names at the end of this section. 1. Open the SOA Manager using transaction SOAMANAGER.

  1. Click Web service configuration.

Enter the object name CO_HRAU_ATO_STP_* and click Search.

For both objects found in the search, follow the steps below: a. Click the internal name link and then select Create > Manual Configuration.

Enter a logical port name (for example, HRAU_ATO_STP_PUSH), select Logical Port is Default, and then click Next.

a)In the Consumer Security tab, select User ID / Password, enter the username and password of the SCPI communications user, and then click Next.

In the Transport Settings tab, enter the relevant information as follows and then click Next.

In the Messaging tab, select ‘Suppress ID Transfer’ for Message ID Protocol and then click Next.

Proceed with the remaining default settings and click Finish.

On the Define Logical Ports page, select the entry and click Activate.

This are the steps to configure the STP web service. Please let me know if you need help to configure the sender tab, Receiver tab and More tab. I can help you with the format the SAML End Point gov urls. I can also help you to see the status of the deployment of the iflows please mention that in the comments.

Please let me know if you have any queries.

 

2 Comments
You must be Logged on to comment or reply to a post.