Duplicated STP pay event file lodged with Govconnect. How to resolve?

  • 1
  • Question
  • Updated 4 weeks ago
  • Answered
When resolving early STP upload difficulties, one payroll file was submitted twice. The ATO suggested fix for this is to lodge an updated file for the duplicated pay event with zero values. Is it possible to create a zero value payroll file or is there another way to un-submit or reverse a submitted file. We use Reckon Desktop
Photo of richard

richard

  • 180 Points 100 badge 2x thumb

Posted 4 weeks ago

  • 1
Photo of Rav

Rav, Community Manager

  • 63,388 Points 50k badge 2x thumb
I would highly recommend not doing this. Remember STP is reported on a YTD basis.
If you were to submit a file with zero figures, it would update your YTD balances to zero for all employees.
Photo of richard

richard

  • 180 Points 100 badge 2x thumb
Hi Rav,
it's what the ATO recommend. Their advice " it appears that there are two lodgements of the same pay period as you noted. When you originally sent through the first message, there was only one lodgement appearing for 9 August. Lodgements can take up to 72 hours to appear in ATO systems. To correct this, you can submit either a Full File Replacement form or an Update Event form for the later submission lodged in September. You can changes the amounts to zero, however, they cannot be negative. If you require assistance with locating these forms within your software, please contact your Software Provider. "
Hope you can find a solution.
Cheers
Richard

Photo of Rav

Rav, Community Manager

  • 62,860 Points 50k badge 2x thumb
There's a couple of things here,

First up, Full File Replacement can only be performed to replace the most recent pay event submission. If you've submitted a pay event since the ones in question, you cannot use the Full File Replacement option. This is not a Reckon limitation. 

Secondly, for arguments sake, lets say that you do submit a Full File Replacement with zero values, you are in essence REPLACING the submission and since it contains only zero balances, YTD reporting will zero out values for all employees.
Photo of richard

richard

  • 180 Points 100 badge 2x thumb
Thanks Rav,
I can see that but there still needs to be a solution. The Govconnect system caused the problem by showing the lodgement as a fail - even though it hadn't failed. The second upload was only undertaken because the first had failed according to Govconnect. As you can see from the ATO response, their system doesn't help by not being up to date at any given time - weeks later in this case.
The ATO response suggests that an update event form for the specific duplicate upload is what is needed. That suggests duplicating the payrun with zero payments for the period but not changing any year to date figures should resolve. It will be cumbersome to do a payrun for 20+ employees amending every payment field for a payrun of the same date. I can use a test environment to produce a zero run process but will still have the problem of not being able to access a payrun that far back.
Any further thoughts before I go back to the ATO and say it can't be done and they'll have to delete the duplicate somehow?
Cheers
Richard
Photo of Rav

Rav, Community Manager

  • 62,860 Points 50k badge 2x thumb
The Govconnect system caused the problem by showing the lodgement as a fail - even though it hadn't failed. The second upload was only undertaken because the first had failed according to Govconnect.
Can you elaborate on this please, particularly on what you mean specifically where GovConnect showed the lodgement as a fail.
Photo of richard

richard

  • 180 Points 100 badge 2x thumb
During the submission process, we uploaded the file and tried to submit. This generated fail errors three times over. We left it and went back later and submitted. It worked without any error.
Much later, when checking ATO, I could see the duplication. I reported that to ATO immediately but they initially replied that there was no duplication. I reported it to them again with accompanying screenshot and they conceded it had duplicated.