Frequently asked questions about enterprise payroll software and services in Australia and New Zealand
Enterprise payroll in Australia and New Zealand involves complex decisions around compliance, technology, and operational ownership. This FAQ helps Payroll Managers, HR Directors, and Finance leaders at organisations with 100–5,000+ employees cut through that complexity – covering delivery models, compliance obligations, data security, and switching providers. If your question isn't here, schedule a call.
Understanding payroll delivery models
What is the difference between SaaS payroll and fully managed payroll?
SaaS payroll provides cloud-based software that an organisation operates itself, with vendor support available on request. Fully managed payroll transfers day-to-day processing responsibilities to the vendor, including pay runs, third-party payments, and employee queries. The key distinction is operational ownership: SaaS keeps it in-house, while fully managed outsources it entirely.
What does supported payroll mean?
Supported payroll sits between SaaS and fully managed. The organisation retains control of its payroll system but gains an allocated support person, configuration validation, and ad-hoc reporting assistance from the vendor. It suits teams that want to manage payroll independently but benefit from expert backup without committing to full outsourcing.
Which payroll delivery model suits an organisation with a dedicated payroll team?
SaaS payroll is typically the best fit for organisations with an established in-house payroll team. It gives the team direct control over the system, full access to configuration and reporting, and access to vendor expertise as needed. Supported payroll is an alternative if the team wants a named expert available for escalations and periodic validation.
Can an organisation switch delivery models without replacing the payroll software?
Yes. When the underlying payroll platform is the same across models, organisations can move between SaaS, supported, and fully managed arrangements without a system migration. This allows payroll operations to scale up or down as business needs change – for example, moving to fully managed during a restructure or transition period – without disrupting data or configuration.
What size organisation is each delivery model designed for?
All three delivery models – SaaS, supported, and fully managed – are designed for enterprise and mid-market organisations, typically with 100 or more employees. The right model depends on team capability and appetite for ownership rather than headcount alone. Organisations with complex multi-entity structures, Modern Award obligations, or cross-border AU/NZ operations are well suited to all three.
Does Affinity offer payroll services in both Australia and New Zealand?
Yes. Affinity operates a single payroll platform that handles both Australian and New Zealand payroll within the same database. This avoids the complexity of maintaining separate systems for each jurisdiction and simplifies reporting for organisations that employ people across both countries.
What is a hybrid payroll model?
A hybrid payroll model combines elements of in-house and outsourced delivery within the same organisation. For example, a group may self-manage payroll for its main entity while engaging a fully managed service for a subsidiary with more complex requirements. The arrangement is defined by contract and supported by a shared platform, so reporting remains consolidated.
How do I know which delivery model is right for my organisation?
The right model comes down to team capacity and payroll complexity. If you have experienced in-house payroll staff who want direct control of the system, SaaS payroll is typically the fit. If your team manages payroll independently but needs expert backup for configuration validation, complex reporting and training, Supported payroll provides that without full outsourcing. If you want to remove operational payroll responsibility from your organisation entirely, Fully Managed transfers that burden to the vendor.
Payroll intelligence and accuracy
What is Payroll IQ?
Payroll IQ is Affinity's payroll intelligence dashboard – a single view that consolidates everything payroll teams currently track across multiple reports and screens. On top of that unified view, it applies automated rules to flag anomalies, variances, and potential errors before the pay run is finalised, so teams can investigate and resolve issues ahead of payment rather than after.
How does payroll intelligence help reduce errors?
Payroll intelligence compares each employee's current pay result against prior periods and expected values, identifying deviations that fall outside normal ranges. This shifts error detection from post-payment auditing to pre-payment review. Teams receive a structured list of exceptions to investigate rather than reviewing every pay line manually, reducing both the time spent on quality assurance and the risk of errors reaching employees.
What types of anomalies can an intelligent payroll system identify?
An intelligent payroll system can identify a wide range of anomalies: pay movements above or below defined thresholds, missing or duplicate payments, variances at a pay element level, and missing information. The specific rules depend on how the system is configured for each organisation.
How does automated variance checking work in payroll?
Automated variance checking compares each employee's gross pay in the current period against a baseline – either the prior period or an expected value derived from contracted hours and rates. Where the variance exceeds a defined tolerance, the system raises an exception for review. Teams can configure sensitivity thresholds and exclude known one-time payments such as bonuses or back-pay from the comparison.
Does payroll intelligence replace the need for a payroll team?
No. Payroll intelligence is a decision-support tool, not a replacement for human judgment. It surfaces exceptions and reduces the volume of manual checking required, but the payroll team retains responsibility for reviewing flagged items, understanding context – such as a recent pay increase or a leave cashout – and approving each pay run. It makes the team more efficient, not redundant.
How does Payroll IQ integrate with the core payroll system?
Payroll IQ is embedded within the Affinity payroll platform rather than operating as a separate tool. It draws on live payroll data at each stage of the pay run cycle, so anomaly detection reflects actual calculated values rather than imported snapshots. This tight integration means exceptions are visible to payroll teams within their normal workflow rather than in a separate application.
Australian and New Zealand compliance
How does enterprise payroll software handle Modern Award compliance in Australia?
Enterprise payroll software handles Modern Award compliance through built-in award interpretation rules that calculate pay rates, penalty rates, overtime, and allowances based on each employee's classification and hours worked. These rules are configured to reflect the specific awards an organisation is covered by and are updated as awards change. Automated interpretation reduces the risk of underpayment arising from manual rate application.
What is Single Touch Payroll (STP) and is it required in Australia?
Single Touch Payroll (STP) is an Australian Tax Office reporting standard that requires employers to report payroll information – including salaries, wages, PAYG withholding, and superannuation – to the ATO each time they run payroll. STP Phase 2, which introduced more granular income type reporting, has been mandatory for most employers from 2022, with a staged rollout across employer groups. Enterprise payroll systems generate and submit STP reports automatically as part of the pay run process.
How does payroll software manage Holidays Act compliance in New Zealand?
New Zealand's Holidays Act 2003 is widely regarded as one of the most complex holiday pay frameworks. Compliant payroll systems must calculate annual leave using the higher of ordinary weekly pay or average weekly earnings, and calculate other leave using relevant daily pay or average daily pay. Correct handling of variable hours is a common source of payroll errors in New Zealand.
What is KiwiSaver and how is it administered through payroll?
KiwiSaver is New Zealand's voluntary, work-based savings scheme. Employees contribute a percentage of their gross earnings, and employers are required to contribute a minimum percentage. Payroll software administers KiwiSaver by calculating deductions at the correct rate for each employee, including opt-out and contribution holiday status, and by generating the required Employer Monthly Schedule (EMS) for Inland Revenue.
What is Pay Day Super and when does it take effect?
Pay Day Super is an Australian government reform requiring employers to pay superannuation contributions at the same time as wages, rather than quarterly. The measure is scheduled to take effect from 1 July 2026. It will significantly change payroll processing workflows for Australian employers, particularly around cash flow planning and reconciliation. Enterprise payroll systems will need to support per-pay-period super calculations and payment instructions.
How often are payroll compliance rules updated?
Payroll compliance rules in Australia and New Zealand are updated regularly. STP, superannuation, and tax settings change with each federal budget. In New Zealand, tax thresholds and KiwiSaver contribution rates change periodically. Enterprise payroll vendors release compliance updates in advance of each effective date to allow organisations to test before go-live.
How does enterprise payroll handle annualised salary arrangements?
Annualised salary arrangements pay a flat annual amount in lieu of award rates, provided the salary covers all entitlements owed. Payroll software tracks hours and overtime against the relevant award and calculates any shortfall at each reconciliation point. Underpayment exposure arises where the award entitlement exceeds the salary in a given period.
What is the difference between award interpretation and payroll processing?
Award interpretation is the process of determining what an employee is entitled to be paid based on their award, classification, and rostered hours – including base rates, penalties, allowances, and overtime. Payroll processing is the broader function of calculating gross and net pay, applying tax and deductions, and producing payslips and payment files. Award interpretation feeds into payroll processing; without accurate interpretation, the downstream payroll calculation will be incorrect.
Data security and integrations
Where is payroll data stored for Australian and New Zealand organisations?
Affinity stores payroll data in Australian data centres to meet data sovereignty requirements for organisations in both Australia and New Zealand. This means sensitive employee and payroll data is not replicated to offshore infrastructure. Organisations with specific data residency obligations – such as those in government, healthcare, or critical infrastructure – should confirm storage arrangements in writing during vendor evaluation.
What security certifications should an enterprise payroll system hold?
Enterprise payroll systems should be ISO 27001 compliant, which covers information security management, and comply with the Australian Privacy Act 1988 and New Zealand Privacy Act 2020. Systems that process payment data should also comply with relevant financial data handling standards. Organisations in regulated industries may require additional attestations such as SOC 2 Type II reports or IRAP assessments for Australian government work.
How does payroll software integrate with HR systems?
Payroll software integrates with HR systems through either native connectors or API-based data exchange. Typical integration points include employee master data (new starters, terminations, role changes), leave balances, and organisational structure. The integration eliminates duplicate data entry and ensures that changes made in the HR system – such as a pay rate update – flow automatically to payroll without manual re-keying.
What is a general ledger (GL) export and how does it work?
A general ledger export maps payroll costs to the chart of accounts in a finance system such as SAP, Oracle, or Microsoft Dynamics. After each pay run, the payroll system generates a structured file or API payload that allocates wages, superannuation, taxes, and deductions to the correct cost centres and GL codes. This eliminates manual journal entry and ensures finance teams have accurate payroll costs reflected in their general ledger in a timely manner.
How does workforce management integration work with payroll?
Workforce management integration connects rostering and time and attendance data to the payroll system. Approved timesheets and shift records flow into payroll automatically, where award interpretation rules are applied to calculate correct pay. This replaces manual timesheet keying, reduces processing time, and ensures that hours worked – including penalty rates and overtime – are captured accurately rather than relying on approximations or default values.
Can payroll data be integrated with ERP systems?
Yes. Enterprise payroll systems typically support integration with major ERP platforms including SAP, Oracle, and Microsoft Dynamics through both native connectors and standard API frameworks. Integration covers GL posting, cost centre allocation, employee master data synchronisation, and headcount reporting. The level of pre-built integration varies by vendor; organisations should confirm which ERP versions are supported and whether custom mapping is required.
What is single sign-on (SSO) and do enterprise payroll systems support it?
Single sign-on (SSO) allows employees and administrators to access the payroll system using their existing corporate identity provider – such as Microsoft Entra ID or Okta – without maintaining a separate password. Enterprise payroll systems should support SSO via SAML 2.0 or OpenID Connect. SSO reduces the risk of weak or reused credentials and simplifies offboarding, as revoking access in the identity provider immediately removes access to payroll.
How is sensitive payroll data protected from unauthorised access?
Sensitive payroll data is protected through a combination of role-based access controls, data encryption at rest and in transit, audit logging of all data access and changes, and multi-factor authentication. Enterprise payroll systems apply field-level permissions so that employees can view their own payslips without accessing the pay details of colleagues, and so that payroll administrators can process pay without accessing data outside their assigned entities.
Switching payroll providers
How long does it take to implement a new payroll system?
Enterprise payroll implementations typically take 6 weeks to twelve months. Single-entity projects with straightforward pay rules can be completed in two to three months; multi-entity, multi-jurisdiction implementations with complex award and EBA obligations generally require six to twelve months. Scope, data quality, and team availability are the primary drivers.
What data needs to be migrated when switching payroll providers?
A payroll migration covers employee master data – name, TFN or IRD number, bank details, super fund details – current year-to-date earnings and tax figures, leave balances, and payroll configuration including pay rules and GL mappings. Data completeness and accuracy is the single biggest driver of migration risk.
What happens to historical payroll data during a system migration?
Historical payroll data is either migrated to the new system or retained in the legacy system under a read-only access arrangement. Most organisations migrate current financial year data to support STP reporting and leave balance continuity, while retaining prior years in the legacy system or as data extracts. In New Zealand, at least 21 months of detailed payment data is needed to support accurate leave calculations. The approach depends on audit, legal, and compliance retention requirements in each jurisdiction – typically seven years in AU and NZ.
How do organisations manage payroll during the transition period?
During a transition period, most organisations run parallel payrolls – processing the same pay run in both the legacy and new system and reconciling outputs before decommissioning the old system. This approach confirms the new system produces correct results before it is used for live payments. Parallel running typically covers one to three pay cycles and is resource-intensive, so organisations should plan team capacity accordingly.
What are the most common risks when switching payroll providers?
The most common risks are data quality issues causing incorrect opening balances, underestimated timelines that compress testing, insufficient parallel running, and inadequate staff training. Compliance exposure peaks during transition when teams are unfamiliar with new pay rule configurations. A structured implementation methodology with defined milestones and sign-off points reduces exposure.
What is the role of parallel running in a payroll migration?
Parallel running is the process of processing the same pay period in both the old and new payroll systems and comparing the output. Differences are investigated and traced to configuration or data discrepancies in the new system. Once the new system consistently produces results that match or exceed the accuracy of the legacy system, the organisation can decommission the old system with confidence. Most enterprise payroll projects include at least two parallel pay runs.
What should an organisation ask a payroll vendor before switching?
Key questions include: how does the vendor handle data migration and what format is required; what does the implementation methodology look like and who leads each phase; how are compliance updates delivered and tested; what support arrangements are available post go-live; and how are defects managed if errors arise in the first live pay runs. Asking for references from organisations of similar size and complexity in the same industry provides additional validation.
Is it possible to migrate from a legacy payroll system like Preceda?
Yes. Affinity has experience migrating organisations from Preceda and other legacy payroll platforms. Migration from a legacy system involves extracting employee master data, YTD figures, and leave balances in a structured format and mapping them to the target system's data model. Configuration – including pay rules, GL mappings, and integrations – is rebuilt in the new environment and tested against historical pay outputs.
About Affinity
What industries does Affinity Payroll specialise in?
Affinity Payroll supports organisations across all industries, from straightforward payroll environments to highly complex operations. The platform handles standard payroll requirements with ease and is designed to manage demanding scenarios such as Modern Awards, EBAs, shift penalties, and variable-hours workforces. It is commonly used by organisations with multi-site operations and high compliance exposure.
How long has Affinity been providing payroll services?
Affinity has been providing payroll software and services since 1984. With over 40 years of experience in Australian and New Zealand payroll, the business has supported organisations through multiple generations of compliance reform, including the introduction of STP, Pay Day Super legislation, and successive changes to Modern Award structures and NZ Holidays Act interpretation requirements.
Does Affinity provide payroll for both Australia and New Zealand in a single system?
Yes. Affinity operates a single cross-country database that processes Australian and New Zealand payroll within the same platform. This means organisations operating across both countries maintain a single source of truth for employee data, payroll configuration, and reporting. It also simplifies GL integration and reduces the administrative overhead of maintaining separate system logins, support relationships, and compliance update schedules.
What support options are available to Affinity customers?
Affinity customers have access to a helpdesk for system support queries, compliance guidance as legislative changes occur, and dedicated support arrangements under supported and fully managed delivery models. All customers receive access to compliance updates delivered ahead of effective dates. Supported and fully managed customers also have an allocated support person who provides configuration validation, ad-hoc reporting, and escalation management.
Is Affinity payroll software hosted in Australia?
Yes. Affinity hosts payroll data in Australian data centres, providing local data sovereignty for both Australian and New Zealand customers. This is relevant for organisations with data residency requirements set by their board, IT security policy, or regulatory obligations. Organisations in highly regulated sectors – such as government, healthcare, and critical infrastructure – should confirm hosting arrangements and any subprocessor relationships as part of vendor due diligence.
What is the onboarding process for new Affinity customers?
Onboarding follows four phases: solution design and scoping, build (configuration, migration, integration setup), testing (user acceptance testing, parallel running), and deployment (go-live support, post-launch stabilisation). Timeline and resource requirements depend on the delivery model, number of entities, and pay rule complexity. Affinity provides project management support throughout.
Does Affinity offer payroll consulting or transformation services?
Yes. Affinity offers transformation consulting as an optional service alongside system implementation. This covers process mapping and redesign, risk identification, control framework development, and change management support. It is particularly relevant for organisations transitioning from a legacy platform or a managed service where internal processes have not been documented, or where compliance exposure from prior underpayment needs to be quantified and remediated.
What is Pay on Demand and does Affinity support it?
Pay on Demand – also known as earned wage access – allows employees to access a portion of their earned wages before the scheduled pay date. It improves employee financial wellbeing by reducing reliance on short-term credit. Affinity supports Pay on Demand through its platform, enabling organisations to offer this benefit without disrupting normal payroll processing cycles or requiring separate integrations with third-party earned wage access providers.
How does Affinity help organisations prepare for compliance changes?
Affinity monitors legislative and regulatory changes across Australia and New Zealand and delivers system updates ahead of each effective date. Customers receive advance notice of upcoming changes, guidance on any configuration action required, and updated compliance rules applied to their environment before go-live. For significant reforms – such as Pay Day Super – Affinity provides detailed readiness resources and proactive support to help organisations prepare operationally, not just technically.
What makes Affinity different
Why does it matter whether payroll software is built for Australia and New Zealand rather than adapted from a global platform?
Global payroll platforms treat AU/NZ compliance as a configuration layer added on top of a system built for another market. That means workarounds for configuration, manual processes to account for gaps, and slower responses when legislation changes. Affinity is built here from the ground up, so compliance is native – not bolted on after the fact.
What is the risk of using an offshore payroll platform for organisations with complex payment obligations?
Offshore architectures are designed for broad applicability, not AU/NZ depth. Award interpretation, complex rule sets, and accurate leave reconciliations require configurability that global platforms often can't support natively. The result is manual workarounds, increased checking, and underpayment exposure – risks that a locally built platform eliminates by design.
What does it mean that Affinity builds its own platform and also delivers the service?
Most payroll providers either sell software or provide outsourced services – rarely both from the same team. With Affinity, the people who built the platform are the same people who support and deliver the service. One accountable partner, no handoffs between vendor and service provider, and no ambiguity when something needs to be fixed.
How is Affinity's support model different from raising a ticket with a helpdesk?
If you've spent time re-explaining your configurations to a support agent who didn't know your setup, you'll understand why this matters. Under Affinity's Supported and Fully Managed models, you have a dedicated local expert who knows your business, your configuration, and your obligations – available when you need them, not when a queue clears.
How does Affinity's approach to HR system integration work?
Affinity is built on a best-of-breed model – with certified integrations to leading HR platforms including ELMO, Cornerstone, and HiBob. You don't need to compromise your HR system choice to get payroll right. Data flows cleanly between platforms, so changes made in your HR system flow through to payroll without manual re-keying or reconciliation.
What does Affinity's intelligence layer actually change about how a payroll team spends its time?
Most payroll teams carry a significant checking burden – reviewing pay lines to catch issues before they reach employees. Affinity's intelligence layer shifts that upstream: anomalies are flagged automatically before approval, variances are explained, and exceptions surface for review. The result is around 50% less checking effort and more time for work that requires human judgment.
What is myPA and what does it do?
myPA is Affinity's configurable payroll assistant – a rules engine that monitors data and triggers automated actions based on defined conditions. It can send alerts when employee data changes, generate scheduled reports, flag compliance risks, or send files to an SFTP location without manual intervention. It's designed to reduce the administrative load on payroll teams by automating routine monitoring tasks.
What is Costing IQ and who is it for?
Costing IQ is Affinity's labour cost intelligence module, designed for managers and finance leaders who need visibility over scheduled and actual payroll costs before and after they occur. It supports comparison by timesheet, pay period, employee, or pay element, and enables variance analysis against budget or revenue actuals – particularly useful where cost predictability is critical.
Still have questions?
If your question isn't answered here, our team is available to talk through your specific situation – whether you're evaluating delivery models, planning a migration, or trying to understand your compliance obligations.