An employee changes their working hours. HR updates their record, the manager adjusts the roster, and payroll receives the information before the next pay run.
That sounds straightforward. In practice, those changes may happen on different dates, require separate approvals and pass through several systems. A successful data transfer does not necessarily mean every system now holds the information needed to pay the employee correctly.
As New Zealand employers prepare for the Employment Leave Act, these everyday handoffs deserve closer attention. They also raise a useful question for any organisation reviewing its HRIS or payroll technology: how well does employment information travel from an agreed change to the employee’s pay?
Employment New Zealand’s suggested preparation guide identifies November 2026 to January 2027 as a period for employers to identify agreements, policies and processes that may need updating. It is an indicative planning guide, rather than a deadline applying to every employer.
This gives organisations a practical starting point. Before deciding what to configure, they can establish how existing employment arrangements are recorded and maintained.
The current Holidays Act continues to apply until the new legislation takes effect. Preparation needs to support accurate payroll today while helping the business understand what its future systems and processes will require.
Consider a hypothetical employee who moves from five working days to four, with the change taking effect halfway through a pay period.
The employment variation records the agreed arrangement. The HRIS holds the employee’s hours and effective date. The rostering system reflects when they are expected to work. Payroll needs the appropriate information to process the change and assess any affected calculations.
Even when these systems are integrated, there are questions to resolve. Which record is authoritative? Who checks that the effective dates agree? What happens if the roster changes before the employment variation is approved? How does payroll identify information that arrives after processing has started?
An integration can move a field accurately while leaving these questions unanswered. The business needs an agreed process for creating, approving, transferring and checking the information.
A useful review does not have to begin with a full system replacement or an extensive technology exercise.
Choose a recent change to an employee’s hours, pay or role and follow it through the organisation. Compare the approved documentation with the HRIS record, roster, payroll setup and resulting payment.
The purpose is to understand whether the same decision appears consistently throughout the process. Where records differ, establish whether the cause is timing, interpretation, system design or an unclear responsibility.
For example, a manager may have correctly updated a roster without realising that a separate payroll notification was required. An interface may transfer weekly hours but omit the working-day pattern. A payroll team may be relying on a spreadsheet because the relevant information is unavailable in the main system.
Each finding points to a different solution. Buying more functionality will only help if the underlying requirement is understood.
For organisations selecting a new HRIS or payroll platform, these findings can improve the procurement process.
Ask providers to demonstrate representative employee changes using realistic effective dates and approval steps. Include situations that require information to move between HR, rostering, time and attendance, and payroll.
A demonstration of an employee changing hours during a pay period can reveal more than a general presentation about integration. It shows what the system receives, what a user must decide, how exceptions appear and what evidence remains available afterwards.
Employment New Zealand’s software-provider guidance also identifies the need to record agreed entitlements above statutory minimums and retain information supporting leave and pay calculations. These are useful areas to explore with providers alongside their plans for future legislative changes.
The employer’s task is to establish whether the proposed solution can support its actual workforce arrangements, including the information and decisions the business must supply.
A rejected interface file is visible. A plausible but incomplete employee record can be harder to spot.
Controls should therefore consider missing approvals, inconsistent effective dates and changes that have reached one system but not another. Exceptions need a named owner, a resolution process and a way to confirm that any correction has reached every affected record.
This also makes ongoing payroll less dependent on individual knowledge. When the process is documented and responsibilities are clear, another team member can investigate a discrepancy without reconstructing the employee’s history from emails.
Bring HR, payroll, operations and the relevant technology owners together around one question:
Can we trace an agreed employment change through every system and explain the resulting pay?
The answer can help identify where to improve data, processes, integrations and testing before committing to wider changes.
PPS supports employers with payroll advisory, data review and implementation assurance, working alongside existing payroll and HRIS providers. If you are reviewing your systems or preparing for employment leave reform, explore how PPS can support your readiness planning.
.png)
BACK TO BLOG