United States United Kingdom Australia Canada (English) Canada (French) France Singapore South Africa Global Ireland
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
keeperdavid
Level 3
posted
‎June 12, 2019 04:32 AM
last updated ‎June 11, 2019 11:32 AM

STP error relating to "Payer Declaration Date"

I am attempting a pay run with STP for the first time.

The pay run has failed at the step for "Lodge Pay Run with ATO."

 

When attempting to "Lodge with ATO," a popup appears:
   "Please correct all validation warnings before lodging with the ATO."

 

Next to the Lodgement Details tab, there is a Warning tab with an active warning:

    "There are validation issues with the Business Settings:

  • Reason: The date entered for Payer Declaration Date must not be later than today's date" 

I have reviewed the Business Settings menu, but I cannot find the field for Payer Declaration Date. (Maybe it's staring me in the face, but I'm just missing it.)

 

Can anyone assist with resolving this error and lodging the pay run with the ATO?

Solved
Reply
Best answer June 12, 2019
Solved

Best Answers
keeperdavid
Level 3
‎June 12, 2019 08:53 PM

STP error relating to "Payer Declaration Date"

I received a response from support.

 

This appears to have been a system-wide problem with the Keypay system that is being fixed now. Specifically, the Keypay system was doing validity checks against UTC time instead of AEST.

 

For part of each day, UTC and AEST time zones are on different dates, which was causing the system to produce this error message when doing validity checks. During a normal Australian workday at this time of year, this error would only be appearing for users who attempt to lodge with the ATO prior to 10:00am AEST. This could be why nobody has reported it before now.

 

I successfully lodged it with the ATO a few minutes ago.

Both UTC and AEST are on the same date right now, but Support indicated that the problem would be fixed before it can happen again at midnight AEST tonight.

View solution in original post

Reply
2 Comments 2
MirriamM
Moderator
Moderator
‎June 12, 2019 07:10 AM

STP error relating to "Payer Declaration Date"

Thanks for visiting the Community, keeperdavid,

 

I'm here to help share information to ensure you'd able to pay run with STP.

 

To further isolate the issue, kindly make sure that the data set up into your QuickBooks Online account matches your ATO information. Once verified, I invite you to contact ATO for them to validate if your eligible to file online.

 

Once done, I'd also recommend you contacting our Customer Care support. They have the necessary tools to pull up your account in a secure environment and determined what cause the issue.

 

To reach them, here’s how:

  1. Click this link https://help.quickbooks.intuit.com/en_AU/contact.
  2. Choose the QuickBooks Product.
  3. On the Contact Us page, select a topic.
  4. Click on Get Phone Number button to see the support number.

I've attached some articles for additional reference:

That will guide you on the right track, keeperdavid. If there's anything else you need help with concerning your QuickBooks Online account, feel free to leave a comment below. Have a great day!

Reply
keeperdavid
Level 3
‎June 12, 2019 08:53 PM

STP error relating to "Payer Declaration Date"

I received a response from support.

 

This appears to have been a system-wide problem with the Keypay system that is being fixed now. Specifically, the Keypay system was doing validity checks against UTC time instead of AEST.

 

For part of each day, UTC and AEST time zones are on different dates, which was causing the system to produce this error message when doing validity checks. During a normal Australian workday at this time of year, this error would only be appearing for users who attempt to lodge with the ATO prior to 10:00am AEST. This could be why nobody has reported it before now.

 

I successfully lodged it with the ATO a few minutes ago.

Both UTC and AEST are on the same date right now, but Support indicated that the problem would be fixed before it can happen again at midnight AEST tonight.

Reply