PayDay Super was introduced to improve superannuation compliance by requiring super contributions to be paid on or before payday. The policy intent is straightforward. Super payments should move in step with wages, reducing late payments, underpayments and end-of-quarter reconciliation work.
What is becoming increasingly clear in practice is that PayDay Super has exposed a structural weakness in many payroll workflows. A significant number of systems and firms rely on a single authorised approver to release super payments.
Recent discussions in online payroll and accounting forums have highlighted how easily this reliance turns into an operational and compliance risk when real-world conditions are introduced.
How PayDay Super is meant to work
Under PayDay Super, employers are expected to calculate, authorise and pay super contributions as part of each pay cycle. Super is no longer something that can be queued, reviewed later, or handled in bulk at the end of a quarter.
If super is not paid on time, penalties and interest can apply, and any compliance failure sits with the employer rather than the adviser or software provider.
In an ideal workflow, payroll is finalised, payments are authorised, and super is remitted without delay or additional manual intervention.
In practice, the authorisation step is where many processes slow down or stop entirely.
Where the process breaks in real life
One firm shared a scenario that reflects how fragile this setup can be.
A payroll deadline was approaching, and one client required a one-week super payment to be processed in Xero before the 28 January due date. Payroll calculations were complete, reviewed and ready to go.
Payroll calculations had been completed correctly and on time, but the super payment could not proceed because no authorised approver was available in the system.
The only person authorised to approve the super payment was a staff member who was on approved leave dealing with a personal emergency. No secondary approver had been set up, there was no mechanism for temporary delegation, and the system did not allow the payment to be pre-authorised safely.
As a result, the only viable option was to contact the staff member during their leave and ask them to log in and approve the payment.
This situation was not the result of poor planning or unusual circumstances. It was a foreseeable interruption that payroll systems currently struggle to accommodate.
Similar failures reported by payroll teams
Other payroll professionals described near-identical experiences.
One reported having an employee overseas for several weeks. Although they had access to the work phone and could receive SMS messages, they were unable to authorise the super payment because they were not configured as the authorised approver in the payroll platform.
Another explained that a client travelling overseas had to temporarily change the authorised user on their file purely to receive SMS verification codes. Once the client returned home, the authorisation settings had to be reversed.
These workarounds resolved the immediate issue, but they introduced additional steps, increased the risk of error, and relied heavily on things going right at exactly the right time.
As one participant observed, the process functions in controlled conditions but breaks down when even minor changes occur late in the pay cycle.
The single point of failure problem
This creates direct exposure to compliance risk, rather than being a matter of minor inconvenience.
Many payroll systems continue to rely on a single authorised approver for super payments. If that individual is unavailable due to leave, illness, travel or technical issues such as failed SMS delivery, the payment cannot proceed.
This creates a single point of failure where:
• Super payments can be delayed even when payroll has been completed correctly and on time
• Staff are pressured to interrupt leave or personal emergencies to meet compliance deadlines
• Employers carry the risk of penalties despite having limited control over approver availability
Several contributors made the same observation. Staff, business owners and advisers should be able to take leave without being required to monitor payroll approvals or carry devices for authorisation purposes.
Why adding another approver is not a simple fix
Some responses suggested that the solution is to add an additional authorised approver.
In practice, this assumes a set of conditions that often do not apply in small businesses:
• The subscriber and the approver are separate individuals
• There is more than one suitable bank signatory available
• Authorisation changes can be planned well in advance
• No unexpected events occur during the pay cycle
In many small and micro businesses, the business owner is the subscriber, the bank signatory and the payroll approver. Adding additional approvers can also raise governance, bank authority and professional indemnity considerations that need careful management.
Even where dual authorisation is technically possible, it increases administrative overhead. Roles must be configured, monitored and updated whenever someone takes leave. That is ongoing process management rather than built-in resilience.
Where payroll software has not caught up
A consistent theme in the discussion was that the legislation has moved faster than payroll software design.
PayDay Super was finalised relatively late, leaving software providers to retrofit compliance requirements into existing workflows. In many platforms, super remains a separate manual approval step that occurs after the pay run has already been processed.
This separation has frustrated payroll teams. A common question raised was why super cannot be authorised as part of the same approval action used to finalise payroll.
By keeping super as a distinct approval step, timing risk is shifted back onto employers, even though employers may not control who is available to authorise payments at the required moment.
The hidden admin firms are absorbing
Until systems evolve, firms are compensating through additional process.
Common approaches include:
• Creating and maintaining documented internal backup procedures
• Manually switching authorised users when staff are unavailable
• Chasing approvals earlier than operationally necessary to create buffer time
• Running payroll earlier than ideal to reduce the risk of missed deadlines
These measures increase workload and complexity without materially reducing compliance risk.
What firms should raise with clients before 1 July
Given the current state of payroll tooling, firms should be having clear and direct conversations with clients about PayDay Super readiness, including:
• Who is authorised to approve super payments
• What process applies if that person is unavailable
• Whether bank signatories and payroll approvers are aligned
• How leave, illness and travel will be managed around pay cycles
These scenarios occur regularly in payroll environments and should be assumed as part of normal operations rather than treated as rare exceptions.
What accountants reasonably expect next
PayDay Super is not optional, and compliance will occur.
What payroll professionals reasonably expect is system support that reflects how payroll operates in practice, including:
• More than one authorised approver by default
• Temporary or time-bound delegation options
• Safer pre-authorisation or scheduled approval models
• Closer alignment between pay run approval and super authorisation
Until those changes are delivered, firms will continue to manage PayDay Super through contingency planning rather than system design. That approach works, but it introduces cost, friction and risk that were never part of the original compliance promise.
