1 April 2025 payrun not being included in superstream lodgement
Hi there,
I'm going to prepare employee super by SuperStream, however, the total amount is different with my payroll report. Don't know why…
I attached screenshot for this problem. Please help me with this issue. Many thanks.
Answers
-
Hi @Mavis Xu,
Did the employee change the Superfund that they are using within this period? That might affect the SuperStream for your employee, but I can't be absolutely sure.
Could you please check the pay run data for the employee and see if any of the Super items have changed?
Please let me know, if anything comes to mind or recent changes to your employee Super that might be causing the problem.
0 -
Hi @Mavis Xu,
Did you mark the unscheduled pay run and everything matched up correctly?
I believe some of our reports include draft pay runs as well, that might causing the figures to not be accurate.
That's all I can think of in this situation unfortunately. Do you think you could share the book with technical support if that's okay?
Thank you.
0 -
Hi @Mavis Xu,
Please take a look at this help guide on how to share your Reckon One book with our support team -
Could you also provide me with your email address and book name that you use for Reckon One in a private message so I know which account will have the book shared to support?
Thank you.
0 -
Hi @Mavis Xu,
Can I please just make a suggestion in relation to the pay run that was created on the 1st of April.
- Revert the pay run to draft
- Set the Pay date to the 2nd of April
- Mark the pay run as paid
- Create your SuperStream batch
It should now include the Pay run that was missing the amount.
I have noticed strange behavior when reviewing your book and I have tested this in mine as well. But I have raised this with our development team as it looks to be if a pay date is on the 1st of any quarter it's not being included in the SuperStream.
I will keep you posted with more information. In the meantime, let me know if this helps you.
Thank you.
0 -
Hi @Mavis Xu,
That's no problem! Sorry that you used to use a workaround in the meantime. But I really wanted to get this fixed for you now.
I will keep you updated once this issue has been identified properly and fixed by our amazing development team.
Thank you and speak to you soon.
0





