STP App Pay Run Error

  • 3
  • Question
  • Updated 4 weeks ago
Hello!

One of my clients is having an issue with the STP App where the Pay Runs are coming back with an Error and saying they have been declined by the ATO. I have spoken to the ATO & they have said the Pay Runs have been received and there doesn't seem to be an issue from their end.

 The error message says "The value specified for an item does not match the item type (value = "5913.50000000001", item type = Decimal, uniqueID = http://www.sbr.gov.au/ato/payevntemp:EmployerContributionsSuperannuationGuaranteeA) Hint: The TotalDigits constraint failed..

Can someone please explain that to me & advise how to fix?

Thank you :)
Photo of Olivia Matthews

Olivia Matthews

  • 110 Points 100 badge 2x thumb

Posted 1 month ago

  • 3
Photo of Leanne Chudleigh

Leanne Chudleigh

  • 232 Points 100 badge 2x thumb
That happened to me yesterday too Olivia.
The pay run is showing on the ato business portal but an error shows on the app for that pay run.
Rav is looking in to it.
Photo of Olivia Matthews

Olivia Matthews

  • 110 Points 100 badge 2x thumb
Thanks Leanne.
This has happened to the last 3 pay runs so hoping to get it fixed up asap.
Photo of Nadia

Nadia

  • 852 Points 500 badge 2x thumb
This worked for me...
You need to decrease your year-to-date superannuation figure by 0.00000000001 to get back to TWO decimal places.
If you only have one employee...
Create a pay run, choose your employee and enter the pay run as:
Gross pay $0, PAYG Tax $0 Superannuation $-0.00000000001
When you hit save the large decimal will show up with only 2 decimal places.
This should lodge correctly.   Hope this helps.

If you have more than one employee in the payrun...
I'm not sure whether it matters which employee you allocate the $-0.00000000001 to.
I only had one employee in the payrun.  My employee's superannuation was 86.64.
Before I figured out how to fix it, I kept trying to lodge the payrun details & the error message decimal number kept increasing by $86.64 but still with the 11 decimal places ending in number 1.
If you have more than 1 employee and get a second error message you should be able to work out whether the "error decimal number" is increasing by the amount of "one particular employee's super'n", or if its changing by the amount of "several employee's superannuation added together".
This should help you work out which employee to allocate the $-0.00000000001

Good Luck!
(Edited)
Photo of Vu Nguyen

Vu Nguyen

  • 100 Points 100 badge 2x thumb
I got same problem as from July 19. Still don’t know why and how to fix it.
Photo of Leanne Chudleigh

Leanne Chudleigh

  • 232 Points 100 badge 2x thumb
Oh no! Hope so too.
Photo of Nadia

Nadia

  • 852 Points 500 badge 2x thumb
This worked for me...
You need to decrease your year-to-date superannuation figure by 0.00000000001 to get back to TWO decimal places.
If you only have one employee...
Create a pay run, choose your employee and enter the pay run as:
Gross pay $0, PAYG Tax $0 Superannuation $-0.00000000001
When you hit save the large decimal will show up with only 2 decimal places.
This should lodge correctly.   Hope this helps.

If you have more than one employee in the payrun...
I'm not sure whether it matters which employee you allocate the $0.00000000001 to.
I only had one employee in the payrun.  My employee's superannuation was 86.64.
Before I figured out how to fix it, I kept trying to lodge the payrun details & the error message decimal number kept increasing by $86.64 but still with the 11 decimal places ending in number 1.
If you have more than 1 employee and get a second error message you should be able to work out whether the "error decimal number" is increasing by the amount of "one particular employee's super'n", or if its changing by the amount of "several employee's superannuation added together".
This should help you work out which employee to allocate the $-0.00000000001


Good Luck!
(Edited)
Photo of Olivia Matthews

Olivia Matthews

  • 110 Points 100 badge 2x thumb
Thanks so much Nadia, I have just tried this & it has lodged with no errors. So should I be able to just lodge my next pay run now without any issues?  And am I able to go back & correct the previous pay runs that had errors (3 pay runs)?

No idea how you worked this out......very clever!!

Thanks again.

Olivia
Photo of Nadia

Nadia

  • 852 Points 500 badge 2x thumb
Hi Olivia,
I'm glad that worked for you too.
After I got it working correctly...I checked the ATO business portal & phoned the ATO to confirm that none of my "Error" message payruns had gone through. None of them had. Then I created new payruns and entered them all again.  So the ATO has the correct amounts for my employee Gross Pay & Tax.   
However, In the Reckon STP if I click Employee, then Pay Summary the Year-to-date figures are all overstated. I think they include the amounts that were entered in the "Error Payruns".  
The ATO said the ATO has the correct amounts, and I got the impression the Reckon year-to-date figures being wrong isn't a problem for the ATO.  I am still hoping Reckon will fix this though. It would be nice if everything reconciled before 30th June.
Nadia
Photo of Rav

Rav, Community Manager

  • 104,618 Points 100k badge 2x thumb
Hi Olivia,
If you can let me know the following details, I can pass this to our app devs to investigate further and hopefully fix up.

- The ABN you have registered into your app account
- The exact YTD totals for gross pay, super & tax for the employees you have reported in this erroneous submission

Cheers