What payroll looks like here.
Every calculation has documented logic behind it. Not a habit someone learned from the previous processor. Not a formula in a spreadsheet no one can explain. A recorded rule, reviewed by someone who did not write it, maintained so the reasoning survives regardless of who is doing the work.
Runs follow a defined cadence with built-in checkpoints. Data is validated before processing. Where inputs are unclear or incomplete, the process pauses until they are resolved. It does not proceed on assumption.
Peer review is standard. No payroll run is released by the person who prepared it. This catches the errors that are invisible to the person closest to the work — the transposition, the missed update, the entitlement that changed three months ago and was never applied.
Oversight sits with experienced leadership who carry the compliance judgement layer. Legislation changes. Edge cases arrive. Employment agreements contain clauses that interact with leave rules in ways the platform does not automate. That judgement is available when it matters, not retrofitted after a mistake.
What sits on your balance sheet.
Payroll liability does not announce itself.
A leave balance miscalculated by three days per year across forty employees is invisible until someone leaves and the payout is wrong. An incorrect KiwiSaver rate applied for two quarters sits quietly until an IRD review finds it. A casual employee classified incorrectly accrues entitlements no one budgeted for.
These are not dramatic events. They are the ordinary consequence of payroll run without documented controls, without review, without anyone checking whether the logic from two years ago still applies to the organisation that exists today.
The cost is not just correction. It is the gap between what you reported and what was true. That gap sits on your balance sheet whether you look at it or not. And when it is found — by an auditor, by an employee, by a regulator — the correction happens on their timeline, not yours.
What this applies to.
Admin Army runs payroll across a range of complexity. Single-entity businesses with straightforward cycles. Multi-entity structures with different employment agreements, different leave configurations, and different reporting obligations across each entity. Environments inherited from previous providers where the calculation logic was never recorded and the assumptions were never tested.
Where this work shows up.
Admin Army operates inside payroll platforms including Employment Hero, PayHero, and Xero.
We are payroll-agnostic. A platform is a tool, not a philosophy. The right environment depends on entity structure, workforce profile, reporting requirements, and internal capability. What works for a ten-person consultancy is not automatically fit for a multi-entity group with layered employment agreements.
The platform matters. But configuration, calculation logic that has been recorded and reviewed, and controlled change management matter more. Two organisations can run the same software. One will carry hidden liability. The other will not. The difference is not the logo. It is whether the environment has been designed and governed properly.
Admin Army ensures the logic is sound and that the platform reflects it accurately. The tool executes the run. The operating model protects the outcome.
If the current platform cannot support governed payroll, that becomes a stabilisation conversation before ongoing delivery begins.
What makes this work.
Payroll works when both sides treat it as a compliance function.
- You provide the inputs payroll depends on — timesheets, leave approvals, new starter details, termination instructions — on time and with the information required. Not after the run has started. Not in fragments over three emails. Complete and prompt.
- You treat payroll as governance, not administration. If the instinct is to find the lowest-cost option and minimise interaction, this is a different kind of engagement than you are looking for.
- You are willing to formalise what currently exists only as institutional knowledge. If payroll logic has never been written down, if leave rules have never been checked against employment agreements, that work happens during onboarding. It requires your participation.
- You can name someone internally who will own the relationship and make decisions without delay. Payroll cannot wait because no one is authorised to approve a change.
- You accept that compliance interpretation may override convenience. If a calculation is technically incorrect but has been done that way for years, it gets corrected. That is not negotiable.
What does not work.
Payroll treated as processing — interchangeable, lowest-cost, with no expectation of controls or governance. If the requirement is “just run what we send” without reviewing whether what you send is correct, this engagement will not produce the outcome you expect.
Environments where known errors are left unresolved because correction is inconvenient. Admin Army will not carry ongoing compliance responsibility for a payroll system built on uncorrected foundations. If the environment needs stabilisation, that work comes first. Admin Army does that work with you. But it is not skipped.
Organisations that expect payroll to continue when required inputs are missing or late. Where information is incomplete, processing pauses. That is not punitive. It is how compliance is protected.
We do not provide task-only services. If someone wants output without change, they are not a fit.
Where to go from here.
If your payroll environment is sound — documented logic, confirmed configurations, no known unresolved issues — and you are ready to proceed, the next step is Before You Contact Us.
If your payroll environment carries inherited errors, unverified configurations, or undocumented calculation logic, start with If Things Are Broken. That is how ongoing payroll becomes safe to deliver.