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

Enabling BEAM

Kali

Hi Rav,

Could you please confirm whether, once we enable BEAM within our Reckon One books, we are required to start submitting superannuation via BEAM immediately?

My understanding is that we may no longer be able to continue using our current clearing house for monthly super payments once BEAM is activated, even though the Payday Super changes don’t commence until 1 July 2026.

Ideally, we would like to continue using our existing process for April–June contributions, but register for BEAM now so we are set up and ready to transition to weekly/payday super from 1 July 2026.

Can you please confirm if this approach is possible, or whether enabling BEAM requires an immediate switch?

Thanks,

Kali

Comments

Rav

Hi @Kali

You don't necessarily need to start using it right away but is there any particular reason you don't want to? Is it just to start the new financial year on Beam and close out the current year on your existing clearing house?

You could potentially use that last quarter's lodgement to give Beam a test run to ensure your employee and super fund info is all accurate and valid. But as I said, you don't need to so whatever works best for you.

Something to bear in mind is, if you don't start using Beam straight away then you'll need to ensure that you don't include any prior pay runs in any batches that you've already taken care of using your other clearing house. Once Payday Super kicks in that won't really be an issue since you'll be required to send the batch off upon completion of each pay run but I'll just add it so you're aware.

Kali

Ok - good to know, thanks. I thought I read somewhere once you enable, it turns off your current clearing house. Good to know that's not the case.

Yes, mainly just for a clean start at the new financial year.

I'll move some over earlier, but others not until 1 July 2026.

Kali

Also, will we need to do anything different with our STP lodgements to include QE or will this happen automatically?

Kali

Sorry - and referring back to your original comment about coming over earlier to BEAM. I guess you could still use BEAM monthly in the interim if clients were happy to come across but didn't want to pay weekly as yet?

Rav

The STP process itself won't change, you'll still do that the same way you are now, we do however have something coming within a couple of weeks to designate which pay items are QE. I've seen preview of it and its super super easy, and yes, it'll include an automatic option as well. There's more info on that come so stay tuned for that.

I guess you could still use BEAM monthly in the interim if clients were happy to come across but didn't want to pay weekly as yet?

Sorry can you clarify this for me a bit more? Do you mean sending a lodgement but not making payment for it until later? If so, just bear in mind Beam have timeframes on payments depending on which payment method you choose. There's some info on this on Beam's website here which might be worth a look.

Kali

We currently process superannuation contributions on a monthly basis (rather than quarterly) via our existing clearing house.

Would it be possible to transition to BEAM for the May and June submissions on the same monthly basis, lodging contributions at the end of each month to test out BEAM.

Obviously then switch to pay day super 1 July 2026.

Rav

Oh yes absolutely you can do that

Reckon One Announcements & Important Info

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

Click Here

Reckon One Help Videos 📽️

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

Button

Reckon Payroll Ideas & Feature Requests 💡

Got a cool idea or want a new payroll feature in Reckon One? Let us know here!

Button

Find more posts tagged with

Component react.online had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.