Integration Theatre tile

Your pay run finished on time. Nobody complained. So payroll must be under control, right?

Not necessarily. Payroll rarely fails loudly. It drifts: a spreadsheet here, a manual fix there, an integration someone double-checks every fortnight. Each looks minor. Together, they can lead to incorrect PAYG withholding, employee underpayments, unreliable reporting and too many people with access to sensitive data.

The eight warning signs of payroll software risk are routine manual workarounds, tax and pay rules that are hard to verify, recurring errors, too much comfort from successful STP reporting, loose user access, integrations that need constant intervention, difficult software and regulatory updates, and weak audit trails. Any one may have an innocent explanation. Several together suggest your payroll technology is getting harder to control, and with Payday Super now in effect, there is less room for drift.

Key takeaways

Payroll risk builds gradually. Workarounds become routine, settings get harder to verify and regulatory change gets harder to implement.

The combination matters most. One spreadsheet or one correction is not a reason to replace your system. A pattern of weaknesses is.

A successful STP submission is not proof of accuracy. It shows information was transmitted, not that the calculations behind it were right.

Payday Super leaves less room for error. Since 1 July 2026, super is calculated on qualifying earnings, paid each payday and generally must reach the fund within seven business days.

A review does not automatically mean replacement. It may point to better configuration, stronger governance, an upgrade or a platform better suited to your needs.

Manual workarounds have become routine

Spreadsheets and manual adjustments have a legitimate place in payroll. They become a warning sign when they are needed every pay cycle because the payroll application, or an integration feeding it, cannot handle a process cleanly.

Data is reformatted before import. A calculation happens outside payroll. Someone keeps a side spreadsheet to reconcile HR, time and attendance, and payroll. Every manual step is another chance for information to be entered incorrectly or changed without the validation and traceability built into the payroll application.

What to check: Start with manual processes that touch taxable payments, entitlements, hours, allowances or super. For every regular workaround, document why it exists, who performs and checks it, and whether the original limitation still applies.

Payroll rules and tax settings are hard to verify

Payroll settings have to keep pace with changes to tax requirements, employee circumstances and employment conditions. The Australian Taxation Office updated all 15 PAYG withholding schedules and 12 tax tables for application from 1 July 2026. The updates included changes arising from personal income tax cuts and indexation of study and training support loan repayment thresholds, although some schedules and tables had no material changes.

An old tax table, an incorrect employee setup or the wrong payment classification can quietly affect withholding and what is reported. Wages add their own complexity: awards or enterprise agreements, classifications, overtime, penalty rates, allowances and other entitlements. The Fair Work Ombudsman advises that employees must be paid in accordance with the Fair Work Act and any applicable award or enterprise agreement.

What to check: Can you show which schedules and rules are in use, and who last changed them? Where a calculation is heavily customised or understood by only one or two people, confirming it is still correct gets difficult. Payroll rules should be documented, maintainable and easy to check.

The same payroll errors keep coming back

An occasional correction is normal. A discrepancy that returns every pay cycle is not. It usually points to incorrect source information, an outdated rule, an interface failure or a process happening outside payroll. Fixing the result gets one employee's pay back on track but leaves the cause untouched.

Records matter here too. The Fair Work Ombudsman states that employers must keep time and wage records for seven years. Records cannot be changed unless the change corrects an error, and they must not be false or misleading. Legal responsibility stays with the employer, whatever technology holds the records.

What to check: Can your team trace a discrepancy to its source, make an authorised correction and keep a record of what happened? If fixing payroll has become easier than finding out why errors recur, the technology or process behind them needs a closer look.

A successful STP submission is giving you too much comfort

A successful Single Touch Payroll submission confirms that information passed through the reporting process. It does not prove that every payroll setting, source record or calculation behind it was correct.

Payday Super raises the stakes. From 1 July 2026, employers must pay super guarantee for each payday. The 12% rate has not changed, but it is now calculated on qualifying earnings rather than ordinary time earnings. Contributions generally need to reach the employee's super fund within seven business days after payday, although exceptions apply in some circumstances. Employers must also report year-to-date qualifying earnings and super liability through STP each payday.

What to check: Do payroll settings calculate qualifying earnings and super liability correctly? Are year-to-date amounts reported accurately? Do employee and super fund details support timely allocation of contributions? Treat successful transmission as one important control, backed by reconciliation and review of the information used to produce the submission.

User access is no longer tightly controlled

Payroll systems hold salary and wage details, bank accounts, tax information, super records and other employee data. Access should reflect what each person does today. In practice, permissions pile up as people change roles, administrators leave and temporary access is never removed.

Review periodically who can view payroll information, amend employee details, change payroll settings or hold privileged administrator access. There is no prescribed review frequency that we are aware of, so set a schedule that reflects your risk profile, workforce movement and security arrangements.

What to check: Many organisations use the Australian Signals Directorate's Essential Eight as a security baseline. It covers multi-factor authentication, restricting administrative privileges, patching, application control and backups. In October 2026, ASD also launched ASD Essentials, which builds on the Essential Eight, and existing Essential Eight investment remains valuable. These are cyber security frameworks, not payroll compliance standards for every employer.

Integrations need constant intervention

Payroll depends on information moving between HR, recruitment, rostering, time and attendance, finance and other business applications. Reliable integrations reduce re-entry and keep records consistent. Unreliable ones leave payroll staff checking files, fixing failed interfaces and reconciling competing versions of employee information.

Not every failure carries the same risk. A failed interface carrying an employee's address is an inconvenience. One carrying hours worked, leave, taxable payments or super information can change what people are paid and what you report.

What to check: Can you identify where critical payroll information originated, whether it transferred successfully and how failures are detected? Is there a defined process for resolving errors before the information is used to calculate or report pay? Constant intervention suggests critical information is moving through a process that is no longer dependable.

Software updates and regulatory changes are getting harder

Age alone does not make payroll software inadequate. A supported, maintained product that meets current requirements can perform well for many years. The real question is whether it can keep up with change.

Payday Super and the 2026 PAYG withholding updates were real-world tests. Both required payroll technology and related processes to change from 1 July 2026, and the ATO advised digital service providers that STP products needed to support qualifying earnings reporting. Unsupported software, delayed updates or heavy customisation make it harder to apply regulatory change accurately and on time.

What to check: Can you establish which software version you are running, and is it still supported by the vendor? Are security patches and regulatory updates available? Can changes be implemented and tested before their effective date? Have customisations made routine upgrades difficult or expensive? Patching matters for security too. Application and operating system patching is one of the Essential Eight strategies, and ASD recommends choosing a target maturity level suited to your circumstances.

Payroll reporting and audit trails fall short

When a payroll figure changes, you should be able to find out why without rebuilding the sequence from spreadsheets, emails and people's memories. Useful audit trails let payroll teams examine relevant transactions, understand changes and, where the software supports it, see who performed or authorised important actions. That is essential when investigating a suspected underpayment, checking a recurring adjustment or responding to an internal audit.

The Fair Work Ombudsman requires employers to maintain accurate and complete employee records containing prescribed information. Depending on the circumstances, this can include rates of pay, gross and net amounts, deductions, hours and separately identifiable entitlements. The legal responsibility sits with the employer, not the software. But the software should make that information accessible and help you show how figures were produced.

What to check: In any payroll software review, examine reporting and audit trails as closely as calculation capability.

When do warning signs justify a payroll technology review?

One manual spreadsheet does not prove a payroll application needs replacing. Nor does the age of a system, an occasional correction or one difficult update. The greater concern is the combination of weaknesses.

Rules that are hard to change lead to manual calculations. Unreliable integrations push those calculations into spreadsheets. Payroll staff then spend so much time reconciling and correcting that recurring problems get too little investigation. Confidence falls in how entitlements are calculated, how tax settings are applied, how payroll is reported and how sensitive data is protected.

Test your current set-up against these eight questions:

  • Can payroll run without routine manual workarounds?
  • Does it support current PAYG withholding schedules and payroll rules?
  • Can recurring errors be traced to their source?
  • Can we show that STP and Payday Super calculations are accurate, not just successfully lodged?
  • Is user access appropriately controlled?
  • Are critical integrations reliable?
  • Is the software supported, and can legislative changes be implemented and tested before they take effect?
  • Can payroll records, changes and approvals be readily examined?

The answers show whether you need better configuration and governance, an upgrade, or a payroll platform better suited to your organisation's current requirements.

Not sure where your payroll stands?

Frontier Software helps Australian organisations assess their payroll and workforce management requirements and identify the capabilities needed for accurate, controlled and sustainable payroll operations.

Talk to a Frontier payroll specialist about reviewing your payroll set-up.

Frequently Asked Questions

What are the warning signs that payroll software may be increasing compliance risk?

The eight signs are routine manual workarounds, tax or award settings that are hard to verify, recurring errors, too much reliance on successful STP reporting, loose user access, unreliable integrations, difficulty implementing software and regulatory updates, and weak audit trails.

Any one may have a reasonable explanation. Several together suggest payroll is becoming harder to control.

Can payroll software contribute to employee underpayments?

Yes, when its configuration, employee information or source data is incorrect. Common causes include outdated classifications, incorrect rates, inappropriate treatment of overtime or allowances, and inaccurate information transferred from another system.

The software applies the rules and data it is given, so employers still need processes to maintain those rules, check results and investigate recurring discrepancies.

Does successful STP reporting mean payroll is correct?

No. A successful Single Touch Payroll submission confirms that information has passed through the reporting process. It does not independently verify every payroll calculation, employee record or reporting classification behind it, so employers should support STP reporting with reconciliation and review.

How can payroll software weaknesses affect PAYG withholding?

Incorrect employee tax information, outdated withholding schedules or inappropriate payment classifications can change the amount withheld and reported. With all 15 PAYG withholding schedules and 12 tax tables updated for 1 July 2026, employers should confirm their software supports the applicable schedules and that employee settings are maintained correctly.

What does Payday Super require from payroll software?

From 1 July 2026, super guarantee is paid for each payday and calculated at 12% of qualifying earnings. Employers must report year-to-date qualifying earnings and super liability through STP each payday, and contributions generally need to reach the employee's super fund within seven business days after payday, subject to exceptions.

Payroll software needs to support these calculations and reporting, and employers should verify employee and fund information and resolve errors promptly.

How often should payroll system access be reviewed?

We are not aware of a prescribed review frequency for Australian employers. Reviews should reflect your risk profile, workforce movements, administrative changes and broader security arrangements, and should identify who can view payroll information, change employee details, alter payroll settings and use privileged administrator accounts.

What security controls should organisations consider for payroll software?

Relevant measures include multi-factor authentication, restricted administrative access, timely application and operating system patching, reliable backups and periodic access reviews. ASD's Essential Eight, which ASD Essentials now builds on, is a recognised cyber security framework, not a payroll-specific compliance standard.

Weak access controls are not automatically a notifiable data breach. Under the Notifiable Data Breaches scheme, organisations covered by the Privacy Act must notify affected individuals and the Office of the Australian Information Commissioner when a breach is likely to result in serious harm.

When should an organisation review or replace its payroll software?

A review may be warranted when manual workarounds have become routine, recurring errors are hard to trace, regulatory changes are difficult to implement, integrations need constant intervention or reporting cannot explain how payroll figures were produced.

A review does not automatically lead to replacement. It may identify the need for better configuration, stronger governance, an upgrade or a platform better suited to your current requirements.