Cant submit STP report to ATO nor connect to Payroll Reporting Centre

[L-Mac]

yes my client is also, this is the 1st chance i have had to try to troubleshoot what is wrong, interetsing that there are soooo many with this issue, appears that the Myob UPGRADE may have assumed all clients data files were online!

[L-Mac]

no it isnt ONLY a server based issue - my client has been a MYOB user for YONKS, appears that she is also running on Windows 8.1, just determined that - we are going to have to utilise the work a round discussed in order to get the STP data sent to ATO whilst they decide whether to upgrade their desktop to later one with a leter version of Windows and if so when ...... pity MYOB werent aware that some clients couldve still been utilising older Windows versions..

[PRF]

@L-Mac,

Also, Windows 8.1 is still on the MYOB list of AccountRight supported Windows versions, at least up to v2021.  MYOB hadn't updated the list to include AccountRight 2022 the last time I looked.

Regards

Paul

[PenJ]

Hi All, my understanding of all of this is that if you have to go to STP Phase 2 then the file must go online by end of year.

The Microsoft 8.1 will reach end of life in Jan (so will need to be upgraded anyway)

and Server 2012 will reach end of life in Jun (so again will need to be upgraded anyway).

regards

[John21]

I decided to log a call today (had some time to kill) and after waiting for 3 hours I spoke to a "payroll specialist" He confirmed the following:

- STP2 will only work on the cloud version of the software for those using payroll only. So if you have payroll there is no point updating your windows servers for MYOB accountright as you will be forced to go cloud.

- The Minimum specs they are quoting for 2022 version are the same as those listed for 2019-2021 (attached but I think others have linked these also). Yes we meet the requirements but still the problem exists.

- Sending reports to the ATO is also a problem in the cloud version of the software and the only way you can lodge them currently is using the browser to access your data file that is sitting on the cloud. This is a known problem but there is NO eta and when it will be fixed.

Their solution - upload the server data file to the cloud after you do payroll and access it via the browser to lodge ATO reports and then continue to use the server version as per normal. Then each week (or whenever you do payroll) you need to update the cloud version you previously installed so you can resubmit the reports. 

I will stick to my solution (refer earlier posts) for now and prepare to go cloud next month and prepare the staff as well.

PS why are we paying a monthly subscription? When I asked this they hung up on me. 

[Julie-G]

Holy Moly!    Our STP report just processed through to the ATO right after the payrun was processed.

So something has changed on the MYOB end (We are on Windows 10, Server 2012 R2).

I hope everyone else sees the same improvement.

Big shout out to John21 who  has been amazing with guidance throughout this saga, and came up with a solution to get prior week's reports lodged.

Julie

[PRF]

@Julie-G

What MYOB have done is add 2 additional ciphers to the list of TLSv1.2 ciphers accepted by the stp.payroll.prod.myob.com and pay-event-publisher.payroll.prod.myob.com web sites.  These are key web sites for STP reporting to MYOB and thus the ATO.

No changes have been made to these web site security certificates as far as I can tell.

I'm not sure why it has taken them so long to do this.  Not to "blow my own trumpet" but this was something I had discovered and suggested weeks ago.

There could be other things they've done which I am unaware of.

Regards

Paul

[John21]

Yippy, did a test this morning also and all up and running (for now)

Now to prepare to move to the cloud and STP2

[The_Doc]

Hi @PRF 

Yes agreed this is all working now on my Win 2012 R2 - what is disappointing is that MYOB have taken so long to sort this with no release - "oops we messed up - thanks for your help team!!!"

i.e. as a developer and MYOB forum surfer and helper ( when I can) - and there is no doubt in my mind after over 25 years plus of using and providing feed back and help to MYOB and forum users - that MYOB cannot be more open with problems like this.

There seems no doubt, with the volume of emails from disenchanted users - and the behind the scenes problem solving by such people as yourself, myself and a huge number of dedicated experienced IT MYOB users - that MYOB cannot be more open and admit "a bit of a stuff up in this case and thanks for the help to our dedicated team of users" or similar.

In this case Paul - you suggested the problem & solution  - but the silence from MYOB was so resoundingly loud as to be deafening.

I have had numerous cases like this in the past but MYOB mute acceptance of our help ( the users and the dedicated IT problem solvers) is just not a feel good thing.

The Doc having his say MYOB 

[IhateMYOBupgrad]

Hey Paul @PRF 

Thanks for all your time & help with this issue.  We were able to do the payrun & report from the server today

Cheers

Beth