As Australia and New Zealand's HR tech market keeps consolidating into all-in-one suites, the organisations getting compliance and adoption right are increasingly doing the opposite.
In July 2026, Payday Super came into force. Employers now have to calculate and remit superannuation guarantee contributions on the same day as ordinary wages — not quarterly, not "close enough," but same-day, every pay run. It is the kind of change that only a properly engineered payroll platform absorbs without drama. It is also a reminder of something organisations running dedicated payroll systems already know instinctively: payroll is not a feature. It is an engineering discipline, and getting it wrong now carries criminal consequences, not just civil ones.If you're running your payroll on a specialist platform — MYOB Acumatica, MYOB AccountRight/Live, ichris, NetSuite, ZonePayroll, Aussiepay - ePayroll (Now ReadyTech), Microsoft Dialog PayFocus, Tanda, Payroll Metrics, Datacom Datapay, 2Cloud9, Xero, CloudPayroll, iPayroll, Access Group Payroll or similar — you already made that call. You picked a system built to interpret awards correctly, calculate entitlements correctly, and stand up to scrutiny from the Fair Work Ombudsman. That was the right instinct. The Fair Work Ombudsman recovered well over $350 million for underpaid workers in a single recent financial year, and since January 2025, intentional underpayment is a criminal offence carrying penalties that can run into the millions and, for individuals, years in prison. Payroll accuracy stopped being a nice-to-have a long time ago.
But here is the uncomfortable question few vendors ask you: if your payroll engine is that good, why does everything feeding into it still run on spreadsheets, email chains, institutional memory — or a bundled HR module that was never built to carry the load?
The all-in-one trade nobody talks about
Australia and New Zealand's HR technology market has spent the last decade consolidating. The dominant sales pitch is simplicity: one login, one vendor, one throat to choke. For many organisations, particularly those whose HR needs are genuinely simple, that trade makes sense.
But for organisations that already invested in a specialist payroll platform, "simplicity" usually means something else: ripping out a payroll engine that works — one that correctly interprets your award, that your finance team trusts, that has already survived an audit — in order to get generic HR modules bundled in alongside a payroll module that has to relearn everything your current system already knows.
Many organisations have already been down a smaller version of this road. Most specialist payroll platforms ship with a native HR module of their own — basic employee records, a simple leave request, maybe an onboarding checklist. It's usually the first thing tried, because it's already there and it's already paid for. And it's usually where the gap becomes obvious: no real governance over who can request or approve what, no structured way to manage change requests or crossboarding, nothing that scales past a handful of straightforward hires. That experience is often what sends organisations shopping for an all-in-one suite in the first place — not because the payroll was lacking, but because the HR module bolted onto it never was built to do the job properly either.
"I've spent twenty years watching organisations make this trade, and it's almost always framed as an HR decision when it's actually a payroll decision in disguise," says Mathew French, founder of Subscribe-HR, who has delivered hundreds of HR system implementations across Australian and New Zealand SMEs. "Nobody migrates payroll because the payroll was wrong. They migrate because the HR processes around it were never built properly, and someone decided the fastest fix was to replace everything at once. That's rarely the cheapest or safest path — and it's almost never the fastest one either."
There's a detail about the ANZ market that rarely makes it into the sales conversation: nearly all of today's all-in-one HR and payroll platforms didn't start out as a single, natively-built system at all. Almost every one of them began as two separate products — a standalone payroll engine and a standalone HR system, often built by entirely different companies on entirely different technology — that were later bolted together into one commercial suite, joined in exactly the same way two best-of-breed systems are joined today. The method isn't actually different. What's different is who gets to choose. When a vendor does the bolting, an organisation inherits whichever two products happened to be acquired or partnered together, integrated on the vendor's timeline and to the vendor's standard, with no visibility into how well the join actually holds up under load. When the organisation does it, it chooses the strongest payroll engine for its award complexity and the strongest HR layer for its process maturity — and it knows exactly who's accountable for making that join work, because it made that decision deliberately instead of inheriting it.
The alternative that gets far less airtime: keep the payroll engine that's already proven itself, and plug a genuinely best-of-breed HR layer in beside it.
Finance owns payroll. HR owns everything else. All-in-one blurs both
Part of why this trade keeps getting made badly comes down to something simpler than technology: who actually owns the decision. Payroll sits inside Finance's remit for good reason — general ledger reconciliation, statutory reporting, tax and superannuation remittance, and now, criminal liability if it's wrong. Finance needs certainty, an audit trail, and a platform proven at award interpretation. That's a different discipline from HR's job, which is process ownership across the employee lifecycle — who gets hired, how they're brought on, how their role and pay change over time, how they're developed and assessed, and how they leave. Those aren't the same kind of decision wearing different labels. They sit with different owners, carry different risk, and move at different speeds.
Many organisations get this wrong the moment they put both under one all-in-one platform, because a single system needs a single primary owner — and in practice, that's almost always Finance, since it's the department carrying the most acute compliance pressure and the one signing off the licence. The result is a platform selected, configured and governed against payroll-first criteria, with everything HR actually needs inheriting whatever priority is left over.
"One of the clearest signs an organisation has this backwards is who was in the room during the platform selection," French says. "If Finance chose the system HR has to run its entire people process through, HR was never really the customer for that decision — it was handed a seat at someone else's table. Keeping payroll and HR on separate, purpose-built platforms isn't just a technology choice. It mirrors the accountability that already exists on the org chart: Finance owns the numbers, HR owns the process that produces them."
The real problem was never the payroll engine
Payroll systems are extraordinarily good at one thing: processing the data they're given, exactly as instructed, every single pay run. What they were never built to do is govern where that data comes from — who requested a new role, who approved a pay change, who signed off on a promotion, whether an onboarding checklist was actually completed before day one, or who's accountable when a termination isn't processed until three pay cycles too late.
Those aren't payroll failures. They're upstream data-governance failures, and they land on payroll because payroll is where the consequences become visible — as an incorrect payslip, a super contribution that's late under the new Payday Super rules, or a Fair Work complaint that starts with "I was never told my pay had changed."
"In hundreds of implementations, the pattern repeats itself almost exactly the same way," French says. "The payroll numbers are usually fine. What's broken is everything before the numbers — who can request what, who's allowed to approve it, and whether onboarding actually finished before someone showed up for their first shift. Fix that layer properly and the payroll system you already trust just keeps doing what it's always done well."
This is the layer Subscribe-HR was built to own: Request to Hire, Talent Profiling, Authority to Hire, Onboarding, Change Requests, Crossboarding, and Performance Management — the data silos that sit upstream of every payroll run, handled as structured, auditable, best-practice workflows rather than ad hoc email threads.
The mechanism behind it is what Subscribe-HR calls HR Portfolio Management — the ability to assign specific data sets and processes to specific HR users, rather than routing every request through one overloaded central team. A regional manager can own onboarding and change requests for their patch. A talent lead can own profiling and performance data without touching payroll-adjacent authority settings. Responsibility devolves to the people closest to the data, while governance — who's allowed to touch what — stays centrally controlled and fully auditable. That combination is what most all-in-one suites struggle to offer: they either lock everything down centrally, or they open everything up and hope for the best.
The compliance conversation that isn't about payroll at all
There's a second audit trail hiding behind every onboarding, crossboarding and offboarding event, and it has nothing to do with Fair Work — it belongs to IT and security. Every new starter needs an identity provisioned correctly. Every internal move needs access rights updated to match the new role, not left over from the old one. And every departure needs that identity switched off completely, on the day it's supposed to happen, not whenever someone in IT gets around to a ticket.
That last part is where most organisations actually fail, and it's a security finding, not an HR one. Active accounts and lingering document access for people who no longer work there are a standard line item in IT security reviews — the same category of risk as an unpatched server, except the cause is almost always a process gap between HR and IT rather than a technical one. A payroll platform has no visibility into any of this. Neither does a native HR module bolted onto one.
Subscribe-HR treats identity and access as part of the same workflow as the HR event that triggers them, not a separate handoff to IT that happens if someone remembers. Every update to an employee's record — a new starter, a role change, a resignation — runs through Subscribe-HR's Change Request process: someone requests the change, it's authorised by whoever holds that authority, and only then does the employee record itself get updated. That authorised update is what's linked directly into Microsoft Entra ID for user provisioning, so an identity is created, modified or disabled as a direct consequence of an authorised HR change, not as a separate manual step someone in IT has to remember to action afterwards. The same connection extends to SharePoint, keeping document and folder access aligned with whatever the authorised record now says — including removing that access the moment an offboarding change request is approved, not weeks after.
"HR and IT have historically treated onboarding and offboarding as two separate processes running on two separate clocks, and that gap is exactly where security risk lives," French says. "Because a Change Request has to be authorised before the employee record updates, and that authorised update is what drives Entra ID provisioning, there's no gap left for an account to sit active after someone's gone, or for access to lag behind a role change. That's not an HR nicety — for most boards, it's now a cyber security control they're expected to be able to demonstrate."
It's worth noticing what this actually costs an all-in-one suite. These platforms are built, marketed and evaluated around payroll accuracy and core HR data — not around how cleanly they hand identity off to whatever IT environment a business actually runs. Entra ID and SharePoint integration typically isn't part of the core platform at all; it's a separate implementation project, quoted separately, built by a different team, months after the "simplicity" of a single-vendor go-live was the whole reason for choosing it. The identity and access gap the migration was supposed to close doesn't disappear. It just moves further down the project plan, and further away from the HR event that was supposed to trigger it.
Mandatory training is the silo most payroll-led suites forget entirely
Compliance training obligations don't stop at onboarding. WHS inductions, mandatory refreshers, and professional licensing requirements — CPD hours in aged care, allied health, financial services and a growing list of regulated roles — are another data silo an organisation has to track, evidence, and be able to produce on demand for an auditor or regulator. It's also one that most payroll-led all-in-one suites either don't touch at all, or treat as a premium add-on that still requires buying and implementing a separate, full enterprise LMS.
Subscribe-HR closes that gap without asking anyone to stand up a full LMS. Built-in SCORM package hosting and video file storage cover self-paced e-learning content directly inside the same system that holds the employee record, so mandatory modules and inductions don't need a separate learning platform to live in. Structured management of face-to-face training sessions and CPD hour tracking covers the training that can't be packaged as SCORM at all — the induction run in a room, the accreditation hours a professional has to log and prove every renewal cycle.
The same logic extends to certificates, licences and background checks — for applicants before they're hired, and for employees for as long as they hold the role. A working with children check, a police clearance, a professional registration or an industry licence isn't a one-time gate at the point of hire; it's an ongoing obligation with an expiry date attached, and it's the organisation's problem the day it lapses, not the employee's. Subscribe-HR automates that obligation end to end: tracking the certificate or licence against the employee or applicant record, notifying the relevant manager ahead of expiry, and triggering the re-check automatically rather than relying on someone noticing a date on a spreadsheet before it's too late.
"Training compliance keeps landing on someone's desk as a spreadsheet with expiry dates in red font, and it's a bigger risk than most boards realise," French says. "A mandatory certification you can't evidence on request is exposed in exactly the same way a payroll error is — it's just invisible until an auditor or regulator actually asks for it. Building this into the same platform that already owns onboarding and role changes means the training record, and the licence or background check sitting behind it, updates itself as part of the process, instead of being a separate thing someone has to remember to maintain."
For a payroll-led all-in-one, training compliance is rarely where product investment goes — the roadmap is set by tax and payroll deadlines, not learning and development. Organisations that migrated specifically to consolidate systems often end up running a genuine third-party LMS alongside their "all-in-one" anyway, for exactly the same reason the identity gap above never actually closes: it was never core to what the platform was built to sell.
Integration is the part vendors underestimate — and the part that determines whether any of this works
None of this matters if plugging a new HR layer into an existing payroll system is a six-month integration project that nobody in the business signed up for. This is where the "best-of-breed" argument either holds up or falls apart.
Subscribe-HR's role in a bolt-on deployment is deliberately narrow and deliberately thorough: integrating the platforms, importing and exporting the data that needs to move between systems, and getting both sides synced and genuinely live — not "live" in the sense that a project plan says so, but live in the sense that a pay run the following week processes correctly the first time. The same expertise extends to Time & Attendance and rostering, which sit in exactly the same upstream position as the HR data silos above: badly governed roster and attendance data is just as capable of producing a bad pay run as a badly governed change request is.
"The technology side of an integration is rarely where projects go wrong," French says. "What goes wrong is the same thing that goes wrong in every payroll go-live, regardless of the systems involved — readiness that was assumed instead of tested, training that happened too late to matter, and small changes that nobody flagged until they showed up as an error three pay runs later. We treat that as part of the integration job, not something to hand off once the technical connection is switched on."
That's a deliberate contrast with the all-in-one pitch, where "integration" isn't a project at all — it's marketed as something that doesn't need to happen because everything already lives in one system. In practice, that just moves the readiness and change-management risk from the integration layer into the migration itself, at a much larger scale and with far more at stake.
The question worth asking before any transformation decision
If you already run a payroll platform you trust, the decision in front of you was never really "replace it or keep it." It's narrower and more useful than that: does the HR process layer feeding your payroll system deserve the same standard of expertise you demanded from the payroll system itself?
For a growing number of Australian and New Zealand organisations, the answer is to keep two specialists working together — an expert payroll engine, and a purpose-built HR governance layer sitting beside it — rather than trade both down to get one generalist system that does neither particularly well.
