Forum Discussion

KayVeron's avatar
KayVeron
Experienced Cover User
3 years ago

ATO error code: CMN.ATO.PAYEVNT.000199

Hello

 

The Payrun information error was for the following using STP1:

The date entered for Pay/Update Date must not be later than today’s date (ATO error code: CMN.ATO.PAYEVNT.000199).

Until this current year I have not had any error reports.

 

The pay period was 01/08/2022 – 31/08/2022  paid on 31/08/2022. Payment date is Wednesday 31 August 2022.

This report was submitted on the 23rd August 2022 as I would not be in the office again until 6 September 2022.

The Payrun information errors states the date entered for Pay Date must not be later than today’s date … this is not possible as all the pay runs are entered fortnightly on a Tuesday and get paid on the Wednesday, which continue to be accepted with no problems.

I contacted the ATO Community regarding the above error message and received this reply.

 

ATO Community response

That is the validation message you receive for an UPDATE rather than a SUBMIT action.

Of course, for a submit, you can use a future date, but an update can only use a current or historic date, NEVER a future date.

Are you able to check to confirm that you sent an update instead of a submit? If so, you can just do a SUBMIT that you originally intended and won't get that error message.

Can you also check with your DSP, as I would have thought the product wouldn't allow you to create an update with a future Pay/Update Date?

This is an issue with your payroll product specifically. How your DSP has designed their solution and the process they require you to follow is at issue here.

Sorry I can't help you with how to do this in your solution! There should be no impediment to report 100% salary sacrifice.

 

I have checked the entry and I did lodge it as a SUBMIT but it looks like MYOB AccountRight has changed it to an UPDATE as there is a zero amount for Net Pay as this is all paid to superannuation salary sacrifice. 

I can't see how to change this from an UPDATE to SUBMIT either to resubmit this report.

 

How do I correct this and stop this from happening again going forward please.

 

Regards
Kay

9 Replies

Replies have been turned off for this discussion
  • SamaraM's avatar
    SamaraM
    Former Staff
    3 years ago

    Hi Kay (KayVeron)

     

    Where the error message says; "The date entered for Pay/Update Date must not be later than today’s date" - that is not looking at what you entered for the Payment Date, but physically the date in time when you submit the pay run.

     

    If you were to put the payment date as 31 August 2022 and sent it on 23rd August 2022, then the software is behaving correctly. You won't be able to prevent this from happening, but don't worry, you can just submit the next pay run as normal.


    If my response has answered your enquiry please click "Accept as Solution" to assist other users find this information.

  • KellieL's avatar
    KellieL
    Contributing Cover User
    3 years ago

    I'm getting this message each pay run and now the last 3 pays I have scheduled for the holiday period are now rejected.  How do I fix this.  Also, I am reporting Nil pays (as the Director is not taking payment at the moment)

  • SamaraM's avatar
    SamaraM
    Former Staff
    3 years ago

    Hi KellieL 

     

    As I mentioned, the ATO will not accept pay runs with a date in the future. If you have scheduled the pay runs by entering it now with a future date, that will be the cause of the error.

     

    There is no fix, as this is intended behaviour. A workaround would be to either do an update event after the date has passed to send it through again, or send the information through with the following pay run. 

     

    Hope that helps.


    If my response has answered your enquiry please click "Accept as Solution" to assist other users find this information.

  • KellieL's avatar
    KellieL
    Contributing Cover User
    3 years ago

    Hi SamaraM 

     

    Sorry, I have schedule pays for several clients and this is the only one it has rejected - so not sure how to fix it.  Nothing has changed, I haven't updated anything - it's just a standard pay that I have been putting through - so unfortunately, my query hasn't been answered

  • gavin12345's avatar
    gavin12345
    Ultimate User
    3 years ago

    Hi SamaraM 

     

    Perhaps check this with the ATO. A Pay Event 'must be reported on or before the Payment Date' according to the ATO. It therefore makes no sense to say you cannot report a future dated Pay Event - you can - and all other STP Reporting software allows this.

     

    An Update Event however cannot be future date, and an Update event is a correction to a previous Pay Event. If lodging an Update event the Date must be today's date.

     

    Regards

    Gavin

  • SamaraM's avatar
    SamaraM
    Former Staff
    3 years ago

    Hi KellieL and gavin12345 

     

    Sorry if I was not clear in my explanation. Yes, this is true for an update event - not a pay event.

     

    The reason you are receiving it on this one specific pay is because you have entered no values in the pay run. If a pay run is submitted with no amounts entered, the software treats it as an update event instead of a pay event.

     

    The other pay runs would be submitted successfully if they have amounts entered. For the one with no payments, the only workaround is to wait until the date passes and then do the update event / $0.00 pay run. 

     

    Hope that is more clear on the specific cause of this error.


    If my response has answered your enquiry please click "Accept as Solution" to assist other users find this information.

  • KellieL's avatar
    KellieL
    Contributing Cover User
    3 years ago

    Hi SamaraM 

     

    All the pay runs for this financial year have been nil.  So there seems to only be a problem with the last 3 pays I processed through STP2 in AccountRight - which I processed/scheduled pays this week.  Could it be an internal MYOB error with the latest upgrade?   

  • SamaraM's avatar
    SamaraM
    Former Staff
    3 years ago

    Hi KellieL 

     

    There are 2 factors in this error:

    1. Sending a pay run for $0 which is an event type called update event

    2. Sending a pay run with a future date

     

    If you were to send either a $0 pay run for the current date, (what we call an update event)

    or

    a pay run with a value entered with a future date (what we call a pay event)

     

    Then it would be accepted, like it has with your previously recorded transactions.

     

    As the payment date is in the future and it is an update event, that is the reason you are getting the error.

     

    If you are unsure if the rejected report is indeed recorded as an update event, you can go to payroll reporting > open the report and under the Declaration information, it will state if it was a pay event or update event. 

     

    Hope that makes sense.


    If my response has answered your enquiry please click "Accept as Solution" to assist other users find this information.

     

  • KayVeron's avatar
    KayVeron
    Experienced Cover User
    3 years ago

    Hi KellieL 

     

    I had the same issue with entering payroll for one employee only with Net Pay $0.00 all others were accepted.
    For some reason somewhere there is an issue with process pays with Net $0.00 and I found it only occured after August this year.

    When processing a nil pay there should be a question asking is this for a new payrun or an update. You have to choose new payrun otherwise it is processed as an update. This has to be done for each payrun for the employee with nil pay.

    The next payrun if you select "new payrun" or similar this should fix your problem.

    I hope this has helped.

    Regards