PayGlobal The Loop - Winter 2019

Photograph of a hand writing a report

Payment Summaries and other end of year reports

We’ve been asked on many occasions – “Can MYOB PayGlobal still produce a Payment Summary?” The answer is yes, for now. Payment Summaries will no longer be available though, after the next release.

The question you should ask is, “do you need to produce one?” It’s our recommendation that they are no longer produced.

Whilst the details provided in the Payment Summary are very similar to details produced via STP reporting, they are in fact different reporting methods governed by different requirements. Simply meaning, they are close, but not 100%. During the year end process our consultants have found the majority are 100% the same however have also come across several examples where the Payment Summary and the details reported via STP have not matched. On investigation details reported to the ATO via each method are correct, just presented differently.

Once on STP, the Payment Summary is no longer an official reporting document. As an organisation the problem will come when the Payment Summary differs from what is provided online. How will you explain that to an accountant or employee?

It’s not too late to communicate to employees that they should go through myGov to get their new Online Statement. You can also download and send an employee information fact sheet from the ATO Website.

Other end of year reports

The following PayGlobal reports are no longer required due to STP and are in the process of being removed. It is quite likely that these reports will not be available from version 4.43.

·       PGPRTAXA041- Workplace Giving Statement

·       PGPRTAXA090 - INB Payment Summary v5.3

·       PGPRTAXA092A – ETP Payment Summary v5.3

·       PGPRTAXA093A – PAYGW PSAR v12.0.1

·       PGPRTAXA099A – YTD Balancing Report v11.  It is not a requirement to run this report. However, you may still find running it useful for reconciling with non-Payment Summary payroll reports.

Changes to Tax File Declaration report.

PGPRTAXA026A - TFN Dec v3.0 

-        This will get rejected after 1 July if you attempt to upload to ATO website.

This report is replaced by PGPRTAXA026B TFN Dec v4.0 and must be used after July 1st, 2019 and must stop being used after upgrading to version 4.42. In PayGlobal 4.42 STP has been improved and will report Tax declaration details. On-premise clients will have the chance to upgrade to PayGlobal 4.42 from Thursday 25th July and online clients will be upgraded on Friday 9th August (with the test database upgrade happening on Friday 2nd August). 

Hints & Tips

photograph of fingers on a keyboard

How to handle a rollback scenario in STP tool

The following pay event 5884 was closed and is successful in STP tool.

screenshot of pay event 5884

Pay sequence 5884 was rolled back, this will create an roll back event in STP tool, Important: This pay event should only be sent if we are planning to RESET pay 7323 completely from the system, otherwise should be left as it is in the STP tool

screenshot of pay event 5884

Please note: The “ROLLBACK PAY” Submission Type Pay Event can ONLY ever be sent manually, even if the submissions are set to automatic.

Re-closing the #5884 pay creates a NEW “PAY” Submission Type Pay Event…...this will be automatically sent if STP submissions are set to AUTO, and the submission will be unsuccessful with the below error

screenshot of pay event 5884

Conclusion: So, if a rolled-back pay is definitely going to be edited/processed and reclosed then in the interim we need to educate system users into not submitting the Rollback Pay (which can only be manually submitted anyway!)

When the pay is reclosed if the RollbackPay has a Status of ‘Unsubmitted’ it will automatically be deleted anyway.

Please ONLY submit the RollbackPay submission if you plan on running Reset Pay and fully clearing it from the DB.    

Photograph of man and woman looking at a computer

How to rebuild accumulators

1. Overview

You may need to rebuild the accumulators any time during the year if you have opened and processed a manual pay for a previous financial year or other reasons.

The rebuild accumulators’ function will clear all the YTD fields and rebuild them based on pays that have been processed with the same YTD Code as entered in the settings below.

The Rebuild Accumulators command rebuilds accumulators from the History Transactions file for the current YTD period.

Important: Rebuild Accumulators overwrites any manual changes, such as synchronization into accumulators (including UDF accumulators). This command updates accumulators using only data that was entered through a pay sequence.

2. When to use

Use this command when:

  • You suspect your accumulators are incorrect
  • An application or user error occurs during pay processing and the Accumulators are not updated correctly on close.

3. Get Accum Codes

One way to get the current accumulator codes to use for the Rebuild Accumulators is to look at the Pay Status details.

See example below:

screenshot of computer screen with arrow pointing to calculator icon

The highlighted section above displays the codes to use.

Please make sure the codes and dates displayed are from the last pay closed in the current financial year in your database.

4. Run Rebuild Accumlators


We highly recommend you take a backup of your database before running this process.

Go to Payroll and double click on Rebuild Accumulators.  The Filter screen will appear.

screenshot of folder traversal to rebuild accumulators

If you want to run this for one employee, make the Query Default and enter the employee code in the field.

screenshot of employee code

If you want to run this for a group of employees, select a query from the list:

screenshot of query selection dropdown

If you want to run it for ALL employees, select DEFAULT in the query field and clear any employee codes in the Employee field.

screenshot of query selection default dropdown

Press OK to continue.

Enter the Accumulator codes as per Pay Status (Last pay closed)

screenshot of accumlator codes per pay status

Press OK to continue.

The log file will be displayed when completed.

screenshot of log file

Close the log file and check your employees.

Meet the team - Giovanni Sutjiutama

Giovanni was born in Jakarta and is Indonesian-Chinese (with a quarter of Japanese blood) and an Italian name.  Although raised in Singapore, Giovanni hopes to be spending the rest of his life in Melbourne.  

Why did you decide to take up a position at MYOB?

The company’s culture. I believe that your working environment will motivate and energize yourself at work especially in the worst situation.

What do you love most about living in Melbourne?

Having access to the best coffee in the world.

Question: What gives you the greatest joy?

I am currently on a journey of becoming the best Uncle for my little nieces and nephew.

What is your biggest guilty pleasure?

A nice and warm Indian Curry + Roti Prata

Photograph of Giovanni Sutjiutama