Can Payroll Software Guarantee Compliance in New Zealand?

Payroll software is often sold on the promise of accuracy, automation and compliance.

Modern systems can certainly make payroll faster, more consistent and easier to manage. They can automate calculations, connect time and attendance data, produce reports and reduce some forms of manual error.

But can payroll software guarantee that employees are being paid correctly under New Zealand employment law?

Not on its own.

A payroll system will calculate what it has been configured to calculate. If the legislation has been interpreted incorrectly, the source data is incomplete, or the employment agreement does not reflect how the employee actually works, the system may produce the wrong result perfectly.

That is why payroll compliance cannot be treated as a software feature. It is an outcome created by the interaction between legislation, employment arrangements, data, configuration, processes and people.

‍

A successful pay run does not prove compliance

When a payroll system completes a pay run without producing an error message, it confirms that the system was able to process the information it received.

It does not necessarily confirm that:

the correct legislative rule was applied
the employee was classified correctly
all relevant payments were included
contracted and actual working hours were accurately recorded
leave was calculated using the correct method
the payroll configuration matches the employment agreement
the result reflects what happens in the workplace

Consider an employee whose agreement states fixed hours but who regularly works a different pattern. The payroll system may contain the contracted hours, the roster may contain another pattern, and managers may approve additional hours through a separate process.

Each system can appear to be working. The compliance problem sits in the gaps between them.

‍

Software executes rules. It does not decide whether the rules are right

Payroll systems need rules. Someone must decide how an allowance is treated, which earnings are included in a calculation, how an employee's work pattern is represented and what should happen when employment circumstances change.

Those decisions require more than technical system knowledge.

They may require an understanding of:

the Holidays Act and other minimum employment standards
individual and collective employment agreements
payroll policies and historical business decisions
the employee's actual working arrangements
relevant payroll data and system limitations
how different systems exchange information

A technically correct configuration based on an incorrect interpretation will still produce incorrect pay.

Likewise, a compliant rule cannot produce a reliable result if the source data feeding it is incomplete or inaccurate.

‍

Employment agreements, payroll data and workplace reality must align

Many payroll risks begin before information reaches the payroll system.

HR may create an employment agreement. A manager may establish the employee's actual roster. Time and attendance may capture hours worked. Payroll then applies configured rules to the information it receives.

If these parts do not agree, payroll is often left to resolve the difference at the end of the process.

Common examples include:

an employment agreement that no longer reflects the employee's hours
allowances or bonuses treated differently from their contractual wording
employees working multiple positions under one payroll record
manual changes that are not consistently documented
time data arriving after payroll cut off
changes in work patterns that are not passed to payroll
policies that promise more than the system has been configured to provide

These are not simply software problems. They are payroll governance and operating model problems.

‍

Why configuration must be tested against real employee scenarios

System implementation projects often include configuration testing. This is necessary, but it should not be limited to confirming that an individual rule performs as designed.

Payroll assurance should also test whether the system produces the correct outcome when real workforce conditions interact.

That may include employees who:

have variable hours or changing work patterns
receive allowances, bonuses or commissions
hold multiple roles
work on public holidays
move between full time, part time or casual arrangements
take different forms of leave within the same pay period
transfer between entities or payroll groups
return from parental leave
terminate employment with outstanding entitlements

These scenarios help identify problems that may not be visible when configuration items are tested separately.

The objective is not only to confirm that the system follows its design. It is to confirm that the design, configuration and calculated outcome are correct.

‍

Data migration can carry old problems into a new system

Moving to a new payroll system does not automatically create clean payroll data.

Historical employee records, leave balances, pay components and configuration decisions may all be transferred from the existing environment. If those records contain errors, the new system can inherit them.

This is particularly important as employers prepare for the Employment Leave Act 2026.

The new Act is due to replace the Holidays Act on 6 August 2028. Employment New Zealand has told employers to continue complying with the current Holidays Act and to make sure existing payroll data is accurate before the transition. Its guidance specifically identifies leave balances, leave pay calculations, employment agreements, payroll related systems, rostering, time and attendance, multiple roles and employee transfer processes as areas employers may need to review.

The message is clear: implementation should not begin with an assumption that the current state is correct.

It should begin with evidence.

What should independent payroll assurance cover?

Independent assurance is not a second implementation team and it should not duplicate the work of the software vendor.

Its role is to provide an objective view of whether the payroll outcome is accurate, compliant and supported by appropriate controls.

A well designed assurance programme may include:

1. Legislative and agreement interpretation

Confirm that payroll requirements have been correctly identified from legislation, employment agreements and policies before they are translated into system rules.

2. Source data validation

Review whether employee records, hours, earnings, leave information and historical balances are complete, accurate and suitable for migration or calculation.

3. Configuration assurance

Check that the approved requirements have been correctly configured and that related rules work together as intended.

4. Scenario and calculation testing

Test real employee scenarios and independently validate the resulting calculations, rather than relying only on expected system behaviour.

5. Integration and process review

Examine how information moves between HR, rostering, time and attendance, payroll and finance, including manual workarounds and exception handling.

6. Parallel payroll and go live assurance

Compare results between environments, investigate differences and confirm that material issues have been resolved before the system becomes the source of employee pay.

7. Post implementation review

Check whether the system continues to operate as intended once it is processing live data and real operational changes.

‍

Who is accountable when software produces the wrong result?

Using a recognised payroll platform does not transfer the employer's legal obligations to the software.

Employers remain responsible for maintaining wage, time, holiday and leave records and for paying employees their minimum entitlements. Where arrears arise, the cost may extend beyond correcting the original underpayment. Employers may also face investigation, penalties, remediation costs, employee complaints and loss of trust.

This does not mean payroll technology should be avoided. It means technology needs the right governance around it.

The strongest payroll environments combine: Sound legal interpretation + accurate data + appropriate configuration + disciplined processes + independent testing

Remove any one of those elements and the risk increases.

‍

What should employers ask during a payroll implementation?

Whether an organisation is replacing its entire payroll platform or making a smaller configuration change, it should ask:

Who has confirmed the legislative interpretation behind each requirement?
Do the employment agreements match how employees actually work?
Has the source data been independently validated?
Have complex and unusual employee scenarios been tested?
Have calculations been independently reproduced or checked?
Are integrations and manual processes included in the test scope?
Is there a clear record of decisions, exceptions and approvals?
Who provides assurance that the final payroll outcome is correct?

If the answers rely entirely on the system accepting the configuration without an error, the implementation may have tested functionality without fully testing compliance.

‍

A payroll system should not simply go live. It should go live correctly

Payroll software is an essential part of modern payroll delivery, but it is not a substitute for payroll expertise.

The system can automate a rule. It cannot independently determine whether the rule reflects the legislation, the employment agreement and the employee's real working arrangement.

PPS works alongside employers, payroll providers and implementation partners to connect these parts of the payroll environment. Drawing on more than 11 years of New Zealand payroll experience and work across 100 plus remediation projects, our team provides payroll audits, configuration assurance, calculation testing, remediation support and independent assurance throughout transformation.

Whether you are implementing a new system, reviewing an existing configuration or preparing for the Employment Leave Act, the objective should be the same:

Do not just confirm that the system works. Confirm that it pays people correctly.

[Talk to PPS about payroll audit and independent assurance.]

‍

Frequently Asked Questions

Does payroll software automatically comply with New Zealand employment law?

Payroll software can support compliance, but it depends on correct interpretation, accurate data, appropriate configuration and effective processes. Employers should not assume that using a recognised system guarantees every calculation is compliant.

What is a payroll system audit?

A payroll system audit examines how legislation, employment agreements, employee data, payroll configuration, calculations and operational processes work together. Its purpose is to identify gaps that may create incorrect payments or compliance risk.

Why is independent payroll testing important?

Independent testing provides a separate assessment of whether configured rules and calculated outcomes are correct. It can identify issues that may be missed when the same team designs, configures and approves the solution.

Should payroll be audited before changing systems?

Yes. Reviewing the current environment before migration can identify unreliable data, incorrect balances, unresolved compliance issues and configuration decisions that should not be carried into the new system.

How does the Employment Leave Act affect payroll systems?

The Employment Leave Act will change how leave is earned, taken, paid and recorded from 6 August 2028. Employers may need to update payroll and related systems, employment agreements, workplace policies, pay statements and record keeping processes. Detailed implementation guidance is still being developed.

‍

Sources

‍