Our developers are investigating this error. In the meantime, reversing the salary sacrifice payrun and reprocessing in the AccountRight browser is resolving this error.
Please let me know if you need further help.
If my response has answered your enquiry please click "Accept as Solution" to assist other users find this information.
I do not like using the browser version and pay $160 per month to use the desktoop version, i would appreciate MYOB solving the problem ASAP
I do not like how MYOB are surreptitiously forcing us to go to the Web Browser. They have just started doing this with the Payroll Reporting Centre. So are you saying that the pay run on the desktop should be deleted and then started again on the Browser version? I thought everything was in both.
Where is the Electronic Payments Register report in the MYOB browser version? After STP Phase 2 lodgement to ATO rejected in the desktop, I had to delete the pay run and re-create in the browser version. Lots of features in the pays seem to be missing such as putting in dates of leave. However this time it lodged although I wasn't confident of the totals until I had checked against what I had originally printed off from the desktop pay run.
But then I wasn't able to locate the electronic payments registerr report to show what had actually been paid in the browser version. Please can you advise where this is.
Many thanks
Polly
Hi everyone
This post on the Community Forum homepage, ATO error code: CMN.ATO.PAYEVNTEMP.000389 , has information regarding this error. For updates please subscribe to that post.
Hi,
this is nightmare for us and hopefully that MYOB fix a.s.a.p as it is very hard to fix for payroll officers.
same issue - on the phone to MYOB - they are useless!
Agree
Agree. I dont like the browser version. MYOB you charge us $160 a month, please resolve URGENTLY or discount our fee!
Hi
CAN MYOB PLEASE CONFIRM:
If a report is rejected there is no action necessary, as if the same payees are paid in the next pay run, the report to the ATO will then be corrected in the next pay run (assuming MYOB has fixed the problem by then)?
Thanks!
