A payroll provider is not obliged to tell you whose software it runs. Many don't. Buyers often find out partway through implementation, or during a security review when the certifications are in a different company's name from the one on the contract.
That arrangement is white label payroll. It is common across Australia and New Zealand, it is rarely advertised, and it is neither good nor bad in itself. What matters is whether it fits the payroll you actually run. This guide explains how the model works, where it holds up, where it breaks, and what to ask.
What is white label payroll?
White label payroll is an arrangement where one company builds and maintains the payroll engine, and a second company sells it to you under its own brand. You sign with the reseller. You see the reseller's logo, portal and support desk. The software underneath is somebody else's.
What you see – the reseller, on your contract
What you run – the platform vendor, not on your contract
That opacity is the defining feature of the model, and it is what makes the trade-offs worth understanding before you sign.
Two routes to a white labelled product
Not all white label arrangements are the same. Two very different types of company arrive at the model for different reasons, and the risk they carry for you is different in each case.
| HR vendor adding payroll | Bureau or outsourcer licensing a platform | |
|---|---|---|
| Why they do it | To become a one-stop shop: own the whole employee record and lift account value | To deliver a payroll service without building and maintaining software |
| Core competence | HR software: onboarding, performance, engagement, records | Payroll operations: processing, checking, compliance, employee queries |
| What payroll is to them | A module that closes a gap in the suite | The product itself, but the technology is not theirs |
| Where payroll sits on the roadmap | Behind the HR features that win their deals | Nowhere they control. They queue with every other licensee |
| How it's sold to you | Led by the HR buyer, with payroll demonstrated briefly | Led by service and relationship, with technology barely discussed |
| Typical failure mode | Compliance depth: the engine can't handle your awards or leave rules | Product change: the service is strong until you need the software to do something new |
| Probe hardest on | Award and Holidays Act handling, with your real scenarios | Escalation path to a code fix, and who owns your configuration |
The distinction tells you where to spend your evaluation effort. A bureau's payroll people will usually know payroll better than an HR vendor's. That expertise is real and worth paying for. What they can't do is change the product. An HR vendor may have better software engineering and a cleaner integration story, but payroll is not where their attention goes, and AU/NZ compliance is unforgiving of divided attention.
Does bundling everything with one provider actually help?
The one-stop-shop pitch is the HR vendor's whole proposition, so it's worth testing. Consolidation is a genuine benefit: one contract, one invoice, fewer vendors. But an all-in-one bundle is generally assembled from whatever the vendor could licence or acquire, not from the strongest product in each category. Payroll is often the weakest component, because it's the hardest to get right under AU/NZ conditions and the least visible during a sales process.
The alternative is best-of-breed: choose the strongest system for each function and connect them. That was once a real trade-off, when integration meant custom development and brittle file transfers. With mature two-way APIs it is far less of one.
The question to put to a bundled offer is not “does it do everything?” but “is each part of it good enough to have won on its own?”
Where white label payroll works well
For smaller and mid-sized organisations with a reasonably standard payroll, the model has real advantages.
One relationship. A single contract and invoice covering payroll, HR advisory and often bookkeeping.
Lower entry cost. The reseller has already absorbed the configuration and licensing work across a book of clients, and prices accordingly.
No internal payroll expertise required. Their team runs the process, so you don't need to recruit and retain payroll specialists, which is genuinely difficult.
Deep tool familiarity. A bureau running the same platform across dozens of clients knows its quirks well.
If your payroll is salaried, single-jurisdiction and stable, these benefits are substantial and the drawbacks below may never surface.
Where it starts to break
The problems are structural rather than a matter of provider quality. They appear as the payroll gets harder.
Support becomes indirect
When something goes wrong in the engine, your provider cannot fix it. They log a ticket with the vendor and wait, as one client among many. You are now two SLAs from a resolution, with no visibility into the second one. Under a payrun deadline, that gap is where the damage happens.
Configuration becomes homogenised
A reseller's margin depends on running one template across its client base. Your genuine exceptions – an enterprise agreement with unusual overtime, allowances that flow differently by site, a leave policy that predates the award – get answered with "the system doesn't do that". Often the system does. The reseller's standard build doesn't.
Product influence disappears
You have no route to the roadmap. Enhancement requests pass into an intermediary with no commercial reason to advocate for one client's edge case.
Accountability blurs
When a calculation is wrong, is it a configuration error, a product defect, or a misread of the award? Two organisations own the answer between them, and neither owns it alone. Establishing that in an underpayment remediation is slow and expensive.
Due diligence gets harder
Certifications, data residency and sub-processor lists belong to whichever entity actually holds them. Your procurement and IT teams need to assess a company that isn't on your contract, and may not be named in the documentation.
If you're reviewing payroll systems in Australia or New Zealand, our free evaluation guide and selection toolkit help you define requirements before you talk to vendors.
Why your shortlist may be smaller than it looks
Run a selection process in Australia or New Zealand and you can end up with three vendors on the shortlist, three sets of branded collateral, three demos, and two of them running the same underlying payroll engine.
The demos will look different, because each reseller has built its own portal skin and configured its own template. The engine, the calculation logic, the release cycle and the compliance roadmap are identical. If that engine handles your leave accruals badly, it handles them badly in both proposals.
Try it
A three-vendor shortlist
Three brands, three proposals, three demos booked. Ask each one who builds the software.
HR suite with payroll module. One login, one employee record.
Underlying engine
Not disclosed
Payroll and workforce management. Builds, implements and supports its own platform.
Underlying engine
Not disclosed
Outsourced payroll bureau. Experienced team, strong references.
Underlying engine
Not disclosed
The damage is to your evaluation. A weighted scoring matrix assumes the options are independent. If two entries share a platform, your scoring is measuring sales presentation rather than product capability. A reference check gives you a view of the reseller's service, not the software. And the diversity of your shortlist, the thing that gives a board confidence the market was tested, is partly an illusion.
The fix takes one question
Ask every shortlisted vendor, in writing, to name the platform they run and who builds it, at RFI stage, before you invest in demos.
The line is complexity, not headcount
It's tempting to frame this as small versus enterprise. That's the wrong axis. Plenty of 2,000-employee salaried payrolls run comfortably on a white labelled service. Plenty of 300-employee organisations in aged care, retail or construction have award interpretation requirements that will break a templated build.
The honest test is how much of your payroll sits outside the standard configuration. Multiple awards or enterprise agreements, rostering and time-and-attendance integration, trans-Tasman operations, high casual turnover, complicated leave entitlements: each one increases the value of speaking directly to the people who own the code.
Self-check
How much of your payroll sits outside the template?
Tick everything that applies to your organisation.
0 of 6 selected
A white labelled service will probably serve you well
Your payroll sits close to the standard configuration. One relationship, lower entry cost and someone else running the process are real advantages here. Still ask the five questions, and put the answers in writing.
Five questions worth asking
Ask these before you sign, and put the answers in writing.
- 1
Who builds the software?
Name the entity. If the answer is evasive, that is your answer.
A good answer: A named company and a named product, offered without hesitation.
- 2
Where does an escalation land?
Trace the path from your first call to a code change, and ask who holds the SLA at each step.
A good answer: A written path with an owner and a response time at every hop, including the one you cannot see today.
- 3
Is my configuration mine?
Can you see it, document it and change it, or are you on a shared template?
A good answer: Yes, it is documented, you can review it, and you can take a copy on exit.
- 4
Who holds the certifications, and where does my data sit?
Confirm which entity is certified and which one processes your data.
A good answer: Certificates in the name of the entity that processes your data, plus a current sub-processor list.
- 5
What does exit look like?
What data do you get back, in what format, and how long does it take?
A good answer: A defined format, a defined timeframe, and a stated price if there is one.
None of these are hostile questions. A confident provider answers them quickly.
How Affinity approaches this
We build our own payroll platform, implement it, and support it. There are no white labels, no middlemen and no offshoring in the delivery chain. That means one accountable partner from contract through to compliance, and a direct line between a payroll issue and the people who can resolve it in the product.
On bundling, our position is best-of-breed rather than all-in-one. We build payroll and workforce management deeply, and integrate with your chosen HRIS, time-and-attendance and finance systems through two-way APIs and file-based interfaces. We have partnerships and ready-built interfaces with many providers. We have worked with Australian and New Zealand organisations for over 40 years, hold ISO 27001 certification, and offer three delivery models – SaaS, Supported and Fully Managed – so the level of service can change without changing platform.
Compare the three delivery models
SaaS, Supported and Fully Managed, side by side: what you run, what we run, and how to move between them.
Compare delivery modelsSee how award interpretation works
Rule-based pay calculation for awards, enterprise agreements and the Holidays Act, configured and tested with you.
Award interpretationWant a direct view of who builds, implements and supports your payroll?
If you're evaluating providers, we're happy to walk through how the platform handles your awards, agreements and leave rules, and who you would be dealing with at each step.