nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Correcting Super Stream lodged

Ania

Hi Rav,

The questions are mounting, sorry :) I hope I can explain clearly. We pay fortnightly and had two pays this month: 8 and 22 Jul. In the pay on 8 Jul there are mistakes in calculating SG super, N.B. the gross salaries/tax are all correct, but SG was not calculated on annual leave loading for 4 employees. The second pay run 22 Jul was correct.

I can update pay run and upload to ATO again with the correct super figures. This is relatively easy (revert to draft/re-submit) so I'm OK here. Just wanted to confirm that I should resubmit the 8 Jul pay run for all the employees and not just the 4 with mistakes? Also, I'm not clear what happens to YTD totals once I re-submit 8 Jul, since we also had pay on 22 Jul. I assume I don't have to worry about it because the totals will show correctly once we process the next pay and upload another STP, is this right?

My bigger issue is how to update Super Stream file. If I create a new Super Stream file for 8 July it'll have a total super for that pay, but I only need to pay a little super top-up for 4 employees. How do I go about it please? I don't see any option to amend a Super Stream file already lodged. Btw, we use BEAM in the Reckon One Payroll from July, so we have lodged two Super Stream files so far and they have gone through OK.

Thanking you in advance,

Ania

Accepted answers

All comments

Rav

Hey Ania,

Ask away! That's what this Community is here for 🙂

Ok so in regard to the STP side of things, everything you've said is correct. You can revert the pay run to draft and make any corrections required then send through an update event to amend any employee balances. Since the employee end of STP is reported on a YTD basis only, it'll automatically update on your next successful submission.

Now when it comes to the SuperStream reporting, since you're using Reckon One with Beam we have some built-in functionality when it comes to making corrections/amendments and I'll try to explain below.

Following from the previous point above, when you do revert that 8 July pay run to draft to make the pay corrections, you'll see an alert popup that will look similar to the below.

Essentially, if the alterations you're making to the pay run result in the super contribution in the pay run INCREASING, then that difference will be included in the next lodgement you send, either from that same pay run or the next one you batch you create that includes the 8 July pay run in its date range.

To put simply, make the corrections you need to in the 8 July pay run, and if that results in the super contribution value increasing then you can click the Create & Lodge SuperStream button in that pay run and it will generate a new lodgement for just the difference.

Hopefully that explanation somewhat makes sense but let me know if you have any questions on it 🙂

Ania

OK, thank you Rav. So just to make sure I understand:

I will correct the pay run from 8 Jul (say, today) and send a new STP to ATO. This update will result in a higher super. I will then click Create & Lodge SuperStream and a new file will be lodged (today). This new SuperStream lodgment will ONLY include the employees with increased super values, and ONLY for the difference we need to pay to their superfunds. Is this right?? This sounds almost too easy to be true 😊

Then, in the next SuperStream lodgment (in the next week payroll), this difference will be added to the new super we pay.

Rav

I will correct the pay run from 8 Jul (say, today) and send a new STP to ATO. This update will result in a higher super. I will then click Create & Lodge SuperStream and a new file will be lodged (today). This new SuperStream lodgment will ONLY include the employees with increased super values, and ONLY for the difference we need to pay to their superfunds. Is this right?? This sounds almost too easy to be true 😊

All of the above is correct 🙂

Then, in the next SuperStream lodgment (in the next week payroll), this difference will be added to the new super we pay.

The above is correct too with an small exception/correction. The above only applies if you don't create a new lodgement from the pay run after making your corrections but instead create a BATCH lodgement from the next pay run from the SuperStream screen AND the batch date range covers both that previous and new pay run.

I know that second part sounds a bit confusing so let me let me work through an example with you on what I'd recommend as your workflow.

In the video example below you'll see I have a pay run with 2 employees that has previously been marked as paid and sent to Beam. But, I see the earnings for one of the employees is incorrect so I'll revert that pay run to draft, make my correction and then re-mark it as paid. Note: I've skipped the STP part for the sake of this example.

Because the change I made has resulted in the super for this employee INCREASING, I can then simply click the Create & Lodge SuperStream button to create and send a new lodgement for that difference ONLY.

Again, for the sake of this example rather than just sending it directly I've created a draft lodgement so that I can show you the new lodgement being sent to Beam only includes that one employee along with the difference in super.

https://reckon-1.wistia.com/medias/ccoikehyig

Hopefully that helps a little more but again let me know if you have any questions 🙂

Sloan

I'm not the OP but I just wanted to say this was a very helpful post as I have a similar situation and was wondering how to deal with it. Thank you

Ania

Hi Rav, I just noticed that my last comment from yesterday was not posted! ARRRGH!! It seems I didn't click the Post Comment… Anyway, I won't repeat it now, since I have done an update and YES, unfortunately ran into troubles again :(

Firstly, thank you for your clear video and help. I have corrected the payrun from 8 July and sent an update to ATO. All gross/net/tax figures are the same, the only difference is SG super for 4 employees being higher than before. I have checked and rechecked all the amounts. STP has been reported successfully.

All went well until I created a draft SuperStream batch. For some reason, the batch was created only for 1 employee not 4, and even for that one employee the super showing was incorrect - it was not the expected DIFFERENCE between what was paid on 8 July and what I have just reported as correct amount but, instead, it was the TOTAL amount of Super for this employee as per his corrected pay on 8 July.

I don't know what to do. Please let me know if you have any ideas and, if not, maybe you could look into our book?

Many thanks!

Rav

Sorry for the late reply @Ania, was out of the office yesterday.

Is this still happening for you at the moment? From what you've outlined, you've gone through the normal process. What aspect of the pay run did you change/edit which resulted in the SG increasing?

Ania

Hi Rav, yes, still the same problem. Please let me explain from the beginning:

In our fortnightly Pay on 8 July, the leave loading (LL) on AL was not ticked to be included in SG super calculation. This affected 4 employees who took annual leave in that fortnight.

For 3 employees super was simply a bit lower because of that. The 4th employee was different because he was set up with a flat SG super amount per fortnight of around $1,250 PF (his salary is above the max contr. rate and the coy is paying him only up to the max SG of $32,500). After learning that I should pay him 12% until he reaches the limit and not flat amount (even though the expectation is that he’ll reach max $32,500 before the end of fin. year), I corrected his rate to statutory 12%. So, in his case the super on 8 July was lower not just because LL was not included, but because his rate was a fixed, incorrect amount.

After 8 July pay, I have done two things: ticked LL to be included in SG super calculations, plus changed the 4th employee rate to statutory 12%, just as it is for all others. N.B., I have since done another pay on 22 July with the correct 12% for everyone and including super on LL - it was all calculated/paid correctly.

Yesterday, I reverted 8 July Pay run to Draft and within the draft I checked the pay info for the four affected employees. For 3 of them the super showing in the draft was now the correct higher amount (with super on LL), so I really didn’t have to do anything, just save it. For the 4th employee, the pay run draft was showing the fixed $1,250 super, so I deleted it and clicked 12% SG option, and the system calculated his super correctly at 12% including LL. I saved the draft, checked payslips and payroll reports, all showing the correct amounts i.e. NO changes to Gross/Tax/Net amounts, the only change was an increase in Super amount for the 4 employees. I re-submitted the pay run and STP was successful.

I then created a Draft SuperStream batch for 8 July pay however, the batch was only showing one employee, the 4th one. The 3 employees were not showing at all, and I could not add them manually - an option ‘Add Employee’ would not let me. Additionally, the super amount for the 4th employee was the total super as per his corrected 8 July payslip of $1,500 (the actual figure is different, just to simplify), instead of only showing the difference between $1,500 and $1,250 = $250.

I’m sorry I wrote so much but trying my best to explain. How can I create SuperStream batch for all 4 employees and showing just the super increase? I don’t see an option to do it manually. Btw, we use BEAM since July. I should pay the super difference asap so not to get into trouble :) I'd really appreciate your help if you can please! Many thanks ahead.

Rav

Thanks for that detail @Ania, it definitely helps.

Can I get you to send me a private message with the email address your Reckon One book is registered under so I can shoot through an access request. I'd like to take a little look from my end so will send that through ASAP.

Ania

Great! To send a private message, do I go to Inbox - New message and type Rav as a recipient (?) Sorry, I forget.

Rav

Yep you could do that or an easier way is just click my name then click the Message button on my profile card that pops up.

Rav

Hey @Ania

Quick update -

I asked very nicely for my devs to take a look at what may be happening here.

From what they can see, you did pretty much everything right for the most part but where things went a little bit sideways was the part highlighted in bold below 👇

Yesterday, I reverted 8 July Pay run to Draft and within the draft I checked the pay info for the four affected employees. For 3 of them the super showing in the draft was now the correct higher amount (with super on LL), so I really didn’t have to do anything, just save it. For the 4th employee, the pay run draft was showing the fixed $1,250 super, so I deleted it and clicked 12% SG option, and the system calculated his super correctly at 12% including LL.

To explain, when the original super item is deleted, there isn't any value to compare with which is why the new total value is being included in the next batch for that particular employee. Its also resulted in the other employees not appearing in the new lodgement.

Usually this wouldn't be problem as instead of deleting items, you'd generate a variance in the super balance for the employee(s) by either editing the existing super item or other items in the pay run eg. earnings. However in this case, because the super item was deleted then readded, it treats it like a whole other item resulting in the pay run losing its link with the previous lodgement. This is why its not 'seeing' the difference in super when creating that new lodgement.

I'm hoping that somewhat makes sense but if you have any questions let me know.

Now with all that said, looking forward from here..

What we're trying to do on our end is re-establish the link from the pay run to the previous lodgement so you can generate that new lodgement for just the differences in super. At this stage that needs a little bit of investigative work to see if its possible so that's happening at the moment.

Seeing as you've sent through your update event, the other alternative I'm going to raise, just as an option, would be to make payment directly to the employee's super funds just for this difference.

Either way, I'll keep you updated with more info as soon as I have it.

Ania

Thanks Rav. I hope I explained it correctly - when I deleted Jon's super item (fixed) it was within the pay run draft. The super re-entered as 12% was still the same super category for reporting purposes, so wouldn't the system just compare it to the super previously paid? Well, obviously not :) Maybe I should've kept Jon's super as fixed and just enter a different amount, but didn't know. Mystery of IT programming! Also, why would the other 3 employees be affected.. Anyway, I am grateful someone is looking into this, and hoping we can still solve it.

I'd prefer to lodge a SuperStream batch for the difference, but what happens if I don't? Will this somehow be picked up later and cause troubles? Are the SuperStream batches compared to e.g. ATO STP reporting etc? Or, we use them simply to PAY/DISTRIBUTE super? If that's the case then all I need to do is find a way to pay the difference - is this correct?

I think I can quite easily pay super to 2 out of 4 employees (including Jon), as they have SMSF, but the other 2 employees have commercial superfunds so it may be more complex. Or maybe the superfunds won't even allow me to do that since we are into the new super regime since July? Do you know anything about it?

Please let me know your thoughts. Thank you again,

Ania

Rav

I hope I explained it correctly - when I deleted Jon's super item (fixed) it was within the pay run draft. The super re-entered as 12% was still the same super category for reporting purposes, so wouldn't the system just compare it to the super previously paid? Well, obviously not :) Maybe I should've kept Jon's super as fixed and just enter a different amount, but didn't know. Mystery of IT programming! Also, why would the other 3 employees be affected.. Anyway, I am grateful someone is looking into this, and hoping we can still solve it.

Yep for sure you explained it really well and it actually helped me understand as well so thank you for that 🙂

I think rather than deleting the item to change it from fixed to 12%, there's an option in the draft pay run to change the rate type on the existing super item eg. from Fixed to Statutory Rate (example below). I tested that out myself in my own book and it worked successfully where it only generated the variance of the super.

I'd prefer to lodge a SuperStream batch for the difference, but what happens if I don't? Will this somehow be picked up later and cause troubles? Are the SuperStream batches compared to e.g. ATO STP reporting etc? Or, we use them simply to PAY/DISTRIBUTE super? If that's the case then all I need to do is find a way to pay the difference - is this correct?

Fair enough. I'll do my best to see if our team can get the link re-established and I'll keep you posted on that.

The ATO uses a few components when it comes data matching under Payday Super and there's a bit of info from them on that here.

I have heard some whispers that some super funds may be limiting direct payments but I can't really verify that unfortunately as I think its a case-by-case basis.

The other thing I'll add, and I'm not an authority by any means so take it with a grain of salt, but its worth keeping the ATO’s compliance approach in mind for this first year under Payday Super. The focus is on making a genuine effort and fixing any issues quickly, rather than getting everything perfect from day one. If you’re doing your best to get things right and taking action to resolve anything that comes up (which in my view you definitey are 🙂), you’re not the main focus of compliance action in this first year.

Will come back to you with more info as soon as I can.

Ania

Thanks. Hmm.. I didn't notice the rate type - seems easy :)

I will call our previous clearing house and check if I can still contribute. If I can, and I will simply pay the extra super, will it be all right NOT to worry about creating the SuperStream batch for the difference? Or will there be some unforeseen consequences just because the SuperStream batches don't match what was reported via STP, even though what was actually paid does match it??

Ania

Hi Rav,

I have taken your suggestion and have just paid the super difference for the 4 employees directly to superfunds. I was still able to do that, and it seemed the easiest option.

So, I understand I don't really need another SuperStream batch, and we don't need to re-establish any links as you described above, is this correct?

Thank you for all your help :)

Rav

Hey @Ania

That's great! Glad you were able to get that done.

Yes, in this case you won't need to do any further batches and we won't have to try to re-establish the link to the batch either 🙂

Just a question, do you usually create lodgements directly from within the pay run using the Create and Lodge SuperStream button OR do you manually create batches in the SuperStream screen?

Ania

Good morning, Rav!

Thank you for confirming. Initially I thought the SuperStream batches must match STP reporting so that's why I was so concern about creating the correct batch for the super difference payment. I understand now that the SuperStream batches and Beam are basically for lodgment and payment, and that the matching is between the STP lodged and what the superfunds receive.

If I make any more mistakes in the future, I will not delete any items and will probably check with you before I do any corrections :) The super clearing house we used to use will close its door at the end of October.

As to your question - I have only created the batches twice in July when we started using Beam. We used super clearing housed before July, so not via payroll. Both times I went to Payroll/ Pay runs, then next to the appropriate pay run I clicked the three dots on the right-hand side and clicked an option 'Create draft SuperStream'. This is the way it was suggested in one of the videos and it's the only way I know so far. I hope that's all good.

Rav

Yep that's totally all good 🙂

The only reason I asked, and its a bit of a long shot as it is, if you ever find yourself creating a batch lodgement in the future that INCLUDES 8 July 2026 in its date range then you might see the full balance of Jon's super from this edited pay run reappear in that new lodgement.

There is something we can do about that which involves creating a dummy lodgement and manually marking it as lodged (but not actualy sending it to Beam). But with that said, its a super far-fetched scenario and provided that you're creating and sending lodgements from the pay run (which you are), you won't ever find yourself with this.

Just wanted to flag it in case it ever came up and you wondered why, but again, super rare situation you'd have to find yourself in to ever see it.

Ania

I'd better make sure 8 July is never included then! 😉 Thank you Rav for pointing it out anyway, I'll try not to make too many mistakes. Thank you again for all your help, I appreciate it.

I will probably run for your help some time in the future but will try to leave you alone for a while 😀 There is one other general thing I'd like to just make you aware of, but that's more of a comment and I will write about it another time.

Ania