Correcting super payments¶
Sometimes a super payment does not go through the way you meant it to. The amount might be wrong, it might go to the wrong fund, or it might be recorded against the wrong employee. When that happens, the goal is simple — make sure the correct amount of super reaches the correct fund, and keep a record of how you fixed it.
In one line
If a super payment was wrong, fix the details, pay any shortfall to the correct fund as soon as you notice, and keep a record — because late super triggers the Super Guarantee Charge.
Why this matters¶
Super is your employees' money, and the Australian Taxation Office (ATO) treats super as "paid" only when the fund actually receives the correct amount. A payment that was wrong may not count as paid on time. Fixing it quickly keeps your employees' super on track and helps you avoid the extra cost that late super brings.
What you will learn¶
- The common ways a super payment can be wrong
- The general steps to correct a wrong super payment
- Why timing matters when you are fixing super
Understanding the concept¶
Super payments can go wrong in a few common ways:
- Wrong amount — you paid too little (a shortfall) or too much.
- Wrong fund — the money went to a fund that is not the employee's chosen fund.
- Wrong employee — the contribution was recorded against the wrong person.
The ATO's general advice is the same whichever way it went wrong. First, identify the error — work out exactly what happened and how much is involved. Next, fix the details so the right employee, fund and amount are used. Then make up any shortfall by paying the correct amount to the correct fund as soon as you realise the mistake. Finally, keep a record of what happened and how you corrected it.
Timing is the part people miss. Super only counts as paid when the fund receives it. If the correction means the right amount reaches the fund late, the ATO can work out a Super Guarantee Charge — an extra amount that applies when super is not received in full and on time. That is why the safest move is always to act as soon as you spot the error.
For accountants & bookkeepers
The ATO says the most important thing when you spot a super mistake is to pay the correct amount to the fund as soon as you can. If super ends up late, making a voluntary disclosure to the ATO before an assessment is made can reduce the final charge — the earlier the better. Keep records of the original payment, the error, and the correction, including any adjustment carried to a later payday.
Example¶
Nina runs a small cafe and pays super for her three staff each payday. One payday she notices she paid one employee's super into an old fund the employee had already left. Nina identifies the error, confirms the employee's current fund, and pays the correct amount to that fund straight away. She saves a note of what went wrong, the date she fixed it, and the amount — so if the ATO ever asks, she can show exactly how she put it right.
Common mistakes¶
- Waiting to "sort it out later" — super is only paid when the fund receives it, so delay can make it late.
- Fixing the record in your software but not actually moving the money to the correct fund.
- Not keeping a record of the error and the correction.
- Assuming an overpayment can simply be clawed back without checking with the fund.
How this works in myaccountant¶
In the app — myaccountant tracks each super payment so you can see where it went and how much. If a contribution is returned or looks at risk, myaccountant flags it, and helps you re-send to the correct fund. Your record of the original payment and the correction stays with the contribution.
Key points¶
- Super counts as paid only when the fund receives the correct amount.
- Identify the error, fix the details, pay any shortfall, and keep a record.
- A wrong payment can be wrong amount, wrong fund, or wrong employee.
- Act as soon as you notice — late super triggers the Super Guarantee Charge.
- Keep a record of what happened and how you fixed it.
Learn next¶
General information only — not tax, super or financial advice.
Did this answer your question?
Thanks for your feedback.