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; } } }

How do I re-submit a Beam super payment that has been partially re-funded?

Kaye

We have 2 batches where one employees super contribution has been returned. Subsequent batches went through ok with no changes made to the employees record - bizarre!

So how do I re-submit a part batch with just one employee on it? Without creating a new pay run……….

Accepted answers

All comments

Rav

Hi @Kaye

What was the reason for the refund on those particular lodgements?

If you go into the specific lodgements and click on View History, are there messages that have been returned from Beam? Example below.

Kaye

The batch submission was Succesfull - the individual payment is marked Refunded. We lodged 7 batched on the same day. This employees super from Batch2 and Batch 3 was refunded - the rest were sucessfull………….

Kaye

Hi Rav

Any updates on how to re-submit one super payment that was returned. It was part of a batch with a total of eight employees - seven super contributions went through, but one didn't. The superfund details are correct - subsequent batches went through ok.

Some assistance would be apreciated.

redman

I would like to know this also. I also had an issue today with one employee who was not being “captured “ in my batch with the rest of my employees. Is there a way to submit a single employee so as not to hold up the rest (who don’t have any issues)??

Rav

Hi @Kaye

I'd like to get more of an understanding on why those contributions were refunded. You've mentioned the superfund details are correct and their subsequent batches were successful, do you have any info on the reason those particular contributions were refunded?

Did the subsequent successful batches include those employees who were refunded and if so, were any changes made to the pay run and/or their super details etc?

@redman I'm not sure what you mean when you say the employee is not being 'captured'. Can I get you to elaborate on that so I can get a better understanding?

redman

@Rav by “captured “ I mean 👉🏻 I have 3 employees, 2 were showing in my batch, one was left out.

Rav

@redman Does the employee that is not being included in the batch have valid superfund details in their profile along with a super contribution included in their pay run(s)?

Do you still have that batch in your book at the moment so I can take a look?

Kaye

Hi Rav

There was no explanation in the History as to why this one employee's contribution was returned - this was the batch…..

And if you can make sense of the batch history………

As I said before, subsequent payments have gone through ok.

JEN

I found some information doing a Google search on how to resubmit a partial rejected superannuation submission via Beam but I want this verified here by the Dev Team.

I want to be prepared for this scenario in the event it should come up in the future.

Thank you.

Regards,

Jen

Rav

Thanks for that additional detail @Kaye

If the contribution has been refunded, then the next batch creation from the same pay run, or from the SuperStream page using the correct start and end dates, will pick that refunded contribution and add it to the new batch to send through Beam.

@redman were you able to check the details from my previous reply to your case specifically?

Kaye

Excellent - that worked :):)

We also have an issue now with the payment that we processed last week - the monies have left our bank account, but the batch is still showing as Awaiting Payment. Payment was made 09/07/2026.

Why is the processing taking so long when it needs to be processed in 7 days?????

redman

@Rav we managed to sort it out this week. I was able to batch and send in the end. I will give it another day then check to see it has gone through correctly.

I had the same issue last week. I called last week also and was given assistance by support . That tech didn’t explain what the issue was but did put through the missed employee separately. I suspect this weeks issue was as a result of the dates entered at the point of last week’s fix being incorrect, so my understanding is that this week’s batch dates overlapped for the one employee who needed to be entered separately last week and as a result the system “dropped them” out of the batch I attempted to run this week. I’m hoping I won’t have the same problem again.

redman

@Rav I have a query regarding my Pay Day Super batch I just lodged. (I'm hoping to mitigate what might be a potential problem for next week's lodgement)

My pay cycle runs weekly from a Wednesday to a Tuesday, with pay day being the Wednesday (the following day after the completed pay cycle).

When I put through my batch today(payday) the description, (chosen by the platform), on the "from" and "to" dates for the batch, is todays date 22 July for both 'from' and 'to', rather than reflecting the pay cycle 15 July-21 July.

My question is, when I run my NEXT super batch and want to use the 'from' and 'to' dates 22 July-28 July(reflecting the next pay cycle) will the platform give me an error message because TODAY's batch is labelled as 22 July??

I'm not sure why the platform chose to use today's date for both 'from' and 'to' rather than the dates of the paycycle….

Can you forsee if this is going to cause a headache for next week's batch run due to the 'overlap' of date??

redman

@Rav I have a query regarding my Pay Day Super batch I just lodged. (I'm hoping to mitigate what might be a potential problem for next week's lodgement)

My pay cycle runs weekly from a Wednesday to a Tuesday, with pay day being the Wednesday (the following day after the completed pay cycle).

I'm not sure why the platform chose to use today's date for both 'from' and 'to' rather than the dates of the paycycle….

Can you forsee if this is going to cause a headache for next week's batch run due to the 'overlap' of date??

Rav

Hi @redman

When creating a SuperStream batch, the From and To dates do not refer to the pay period of pay run, it refers to the pay date as that is the determining factor.

Before Payday Super took effect, you could pay super quarterly rather than every pay as you're now required to. So when creating a SuperStream batch you'd enter in a time period in the From and To date selection which would then capture all of the pay runs that fall within that chosen time period using the pay date.

Now that Payday Super has taken effect, you're required to lodge your super contributions every pay so the From and To dates will display the pay date of that specific pay run only.

This isn't an issue, its working as designed so it won't cause you any problems.

Reckon One Announcements & Important Info

Don't miss announcements and important info for Reckon One.

Button

Reckon One Help Videos 🎥

Check out our Reckon One how-to videos for tips & tricks, and help with common tasks!

Button

Reckon One Ideas & Feature Requests 💡

Got a cool idea or want a new feature in Reckon One? Click here to let us know!

Button

Find more posts tagged with

Beam