You ran payroll. The super went out with it. Nine days later a chunk of it landed back in your account with a code you have never seen, attached to an employee who has worked for you for four years.
Meanwhile the seven business day clock expired sometime around day six.
This is the part of Payday Super that nobody spent much time on before 1 July. There was plenty written about the new deadline. There was almost nothing written about what happens when the money comes back, which is where a lot of Australian employers are now spending their Thursday afternoons.
Here is the thing worth understanding before anything else. The seven day deadline is not really a payments deadline. Read the wording on the ATO's page and the contribution is only on time if it reaches the fund with all the information needed to allocate it to the employee's member account. Money arriving without a match is money that has not arrived. Which means most Payday Super failures are not payment failures at all. They are identity failures, and the reform cut the time you have to fix them.
The clock runs on receipt, not on sending
The most expensive misreading we have seen so far. Contributions must be received by the fund within seven business days after you pay your employee.
If your money leaves on day six and the clearing house takes two days to pass it on, you have missed the deadline. The ATO says this directly: if you use a commercial clearing house, including one bundled into your payroll software, you need to leave enough time for them to process it. Their recommendation is to pay on payday itself and stop treating the seven days as a buffer you can spend.
The New Payments Platform changes the maths here. Contributions routed through the NPP can reach the fund the same day you send them. Some service providers are still slower than that, and it is worth knowing which category yours falls into before you find out the hard way.
A business day is stranger than you'd guess
This one catches people, and it caught us.
A business day excludes weekends and any day that is a public holiday for the whole of any Australian state or territory. Not your state. Any state.
So if you run payroll in Adelaide, Picnic Day in the Northern Territory is not a business day for you. Neither is Labour Day in Queensland. Your deadline quietly shifts by a day and nothing in your calendar tells you.
The reverse also holds. A holiday covering only part of a state, like Royal Hobart Show Day, still counts as a business day. If you are calculating deadlines by hand in a spreadsheet, this is the rule that will eventually bite you, because it requires you to track the public holiday calendar of seven other jurisdictions.
What happens to your money after you hit send
Worth walking through, because the failure points only make sense once you can see the sequence.
- Payroll produces the contribution data and the payment instruction
- Your clearing house or gateway forms a SuperStream message
- Message and money arrive at the fund
- The fund tries to match the payment to a member account
- It either allocates the contribution or returns it
Step four is where everything falls over, and step five is where the timing changed. Funds used to have twenty business days to allocate or return a contribution. Since 1 July they have three, not counting the day it arrived.
That is a genuine improvement. You now find out about a problem in days instead of a month. But look at where three business days lands relative to seven. A rejection can arrive on day four, leaving you three days to work out what went wrong, correct it somewhere upstream, and get a resubmission all the way back to the fund. That is not much room, and it is why the fix has to happen before the money moves rather than after.
Two errors cause almost all of it
According to HESTA, roughly 90% of SuperStream errors come down to two things: the fund cannot find the member from the details you supplied, or the employee is no longer with that fund at all.
Neither is a payments problem. Both are a stale record sitting in a system somebody forgot to update.
The fields that break matching are boring and predictable:
- Legal name against preferred name. Your payroll says Katie, the fund has Katherine.
- Missing or wrong TFN, which removes the strongest matching key available.
- Date of birth typo, usually from onboarding.
- Member account number that was transcribed once, years ago.
- A retired or changed USI, often after a fund merger.
- The employee rolled over to a different fund in March and never mentioned it.
That last one is the quiet killer. Under the old quarterly regime a stale fund record cost you a phone call and some rework. Now it costs you the deadline, every single pay run, until somebody notices.
What to do in the first 24 hours after a rejection
- Read the error class. Under the updated SuperStream messaging, fund responses now come back standardised. An error means the contribution failed and was returned, and you need to act. A warning means it went through but something will break later. A positive confirmation means it landed.
- Classify the failure. Identity, fund status, or message format. The fix is different for each and guessing wastes a day you don't have.
- Fix it at the source. Correct the record in your HR or payroll system, not just in the clearing house portal. If you only patch the portal, the same bad value flows through again next fortnight and you will be back here.
- Send a Member Verification Request before you resubmit. More on this below. Resubmitting a payment against details you have not verified is how one rejection becomes three.
- Resubmit and confirm receipt. Do not assume. Sent is not received, and received is not allocated.
- If you can't land it in time, know what you're facing. Covered in the SGC section further down. The short version: it is not the end of the world, but ignoring it makes it considerably worse.
Member Verification Requests, which most employers aren't using
The MVR is a new SuperStream message type and it is the most useful thing to come out of this reform. It lets your payroll software or clearing house ask a fund, before any money moves, whether it can match this employee and whether it will accept a contribution for them.
The rules:
- You must use one before contributing to a fund for the first time for an employee.
- Use one whenever employee details change, a name change being the obvious case, and after any rejection.
- Do not fire one before every routine contribution where nothing has changed. That is noise, and the ATO says so explicitly.
- Funds respond within 24 hours.
If you write software for a living, you already know what this is. It is moving validation left. You are shifting the check from post-payment reconciliation, where failure costs you money and a deadline, to pre-payment verification, where failure costs you an email to an employee. Same check, wildly different blast radius.
Alongside it, the Fund Validation Service now gives earlier warning of changes at the large funds, including mergers, which is where a lot of the dead USI problems come from.
Two rules that are catching people out
Out-of-cycle payments. If you pay someone outside their normal schedule, a bonus, a commission, a back payment after a wage review, an allowance, then the super on that payment is not due seven days after you paid it. It is due seven business days after the employee's next regular payday.
Read that twice, because the instinct is to treat every payment as starting its own clock, and doing so means you are paying earlier than required and probably generating extra contribution messages for no reason. Payments to people who are simply on irregular schedules, like a contractor who invoices you, are not out-of-cycle. The detail sits in Legislative Instrument LI 2026/20.
The bunching rule. When you have an extended due date on one payday and the next payday's ordinary due date falls before it, the second one gets pulled out to match the first. In practice this shows up with new starters. Their first contribution has a 20 business day window, their second would normally be due sooner, and the rule aligns them.
Neither of these is intuitive. Both are the sort of thing a payroll system either handles correctly or handles wrongly and silently.
If you miss the deadline
The super guarantee charge works differently now, and some of the changes are in your favour.
You no longer self-assess it. The ATO assesses it and you do not lodge a super guarantee statement, which removes a step but also removes your ability to quietly sort it out on your own timeline. It is calculated on qualifying earnings rather than salary and wages. Interest compounds daily at the general interest charge rate rather than sitting at a flat 10% per annum. There is an administrative uplift amount covering enforcement cost, and it can be reduced if the ATO has not previously taken action against you and you make a voluntary disclosure.
The genuinely good news: the SGC is now tax deductible, which it never was before. Penalties on top are 25% or 50% of the unpaid charge depending on your history, down from a theoretical maximum of 200%.
Paying late, before the ATO assesses you, reduces the charge. It does not erase it. You can still be liable for the interest and administrative components and any choice loading even after you have paid every dollar of the underlying super.
There is also a carve-out most employers will never need but should know exists. The ATO can issue an exceptional circumstances determination covering a class of employers hit by a natural disaster or a widespread IT and communications outage, extending the deadline to 20 business days. You do not apply for it. The ATO issues it and you self-assess whether you are covered, keeping records that show you were.
What the ATO is actually doing this year
PCG 2026/1 was finalised on 28 January 2026 and sets a risk-rated approach for the first year, running to 30 June 2027. Employers get sorted into low, medium and high risk zones. The ATO has said it will be facilitative about minor errors during the transition and considerably less so about serious or deliberate non-compliance, which includes employers who simply are not attempting to pay on each payday.
The reading we would push back on: this is not a grace period. The concession is aimed at employers who are trying and fixing their mistakes quickly. If your process has not changed since June, you are not in the low risk zone, you are just undetected so far.
If you want the interpretive detail, the ATO published four draft Law Companion Rulings on 18 March 2026.
Fixing it upstream instead
Here is the pattern we keep running into when we look at this properly.
An employee's super details usually live in three or four places that do not talk to each other. There is the HR system where onboarding captured them. There is the payroll system where they were re-keyed. There is the clearing house portal where somebody once patched a rejection without going back to the source. And there is a spreadsheet, because there is always a spreadsheet.
Under quarterly super, that fragmentation produced a cleanup exercise four times a year and everyone lived with it. Payday Super turned the same fragmentation into a recurring penalty risk that fires every pay cycle. Nothing about the data got worse on 1 July. The cost of it being wrong went up by about twelve times.
What actually addresses it:
- One authoritative record for employee super details, with everything else reading from it rather than holding its own copy
- Validation at onboarding, when you have the employee's attention, instead of at payment when you have their money
- Automated MVR on new starters and on any change to name, TFN or fund, rather than relying on someone remembering
- Error responses routed to a named person with a response time, not into a shared inbox nobody owns
- Alerting on contributions that have not been confirmed as allocated, so you find out on day three rather than when a refund appears
None of this is exotic. Most of it is integration work and a bit of discipline about where the truth lives. It is also the sort of thing that gets deferred indefinitely until a deadline attaches a dollar figure to it, which is roughly what just happened.
We build the integration and data plumbing behind systems like this. If super contributions have been bouncing since July and you would rather fix the cause than keep triaging the symptom, get in touch and we will take a look at where your employee data actually lives.
This is general information about systems and process, not tax or legal advice. For advice on your own super guarantee obligations, talk to your accountant or registered tax agent.
Sources
- About Payday Super, ATO, last updated 10 August 2026
- Payment deadlines for Payday Super, ATO, last updated 10 August 2026
- SuperStream changes, ATO
- Payday Super FAQs, HESTA
- Clean data now, fewer Payday Super errors later, AustralianSuper
- Payday Super frequently asked questions, Clayton Utz
- Payday Super: new rules starting 1 July 2026, Fair Work Ombudsman
