Unearth the future of payroll solutions with ZonePayroll. Revolutionise your business management today, and experience the benefits yourself.
Infinet Cloud, the payroll application that many Australian NetSuite customers have run for years, is now ZonePayroll. It sits within the Zone family alongside the other Zone applications, and the change reflects that ownership rather than a change of direction for the product.
For customers already running it, the practical impact is small. The application is the same, your configuration is intact, and your pay runs continue. What changes is the name, the branding and, over time, how the product sits within a wider suite.
This article covers what the change means in practice, what has not changed, and what it is worth understanding if you are evaluating on platform payroll for the first time.
This is a rebrand following acquisition rather than a replatform. The application your payroll runs on is the same application, built as a SuiteApp inside NetSuite, and your existing configuration carries across.
That matters because ERP customers are conditioned to treat product name changes as a warning that a migration is coming. In this case it is not, and there is no version to move to and no data to shift.
The naming aligns the product with the rest of the Zone portfolio, which includes applications across billing, reconciliation, approvals and reporting. The common thread is that they are all built natively for NetSuite rather than integrated to it.
Practically, you will see the name change in the interface, in documentation and in your commercial paperwork over time, and the mechanics of running payroll are unaffected.
Worth stating plainly because this is the question customers actually have.
Your payroll configuration remains as it was. Pay codes, award rules, leave accruals, superannuation setup, entity structure, all of it persists.
Your historical data remains, so year to date figures, prior period runs and reporting history are intact.
Your reporting obligations continue to be met the same way, including Single Touch Payroll submissions and superannuation processing.
And the fundamental architecture is unchanged, which is the most important part. The payroll runs inside NetSuite, posts directly to your general ledger, and reads from the same employee and department records the rest of your system uses.
This is the reason the product exists and it is worth restating, particularly for anyone comparing options.
Most payroll applications sit outside the ERP and connect through an integration. Data moves on a schedule, in one direction or both, and somebody owns reconciling the two sides when they disagree. That reconciliation is ongoing work that nobody budgets for and everybody does.
An on platform payroll has no integration because there are no two systems. The pay run creates the journal directly. Employee records are NetSuite records. Departments, classes and locations are the same dimensions your financial reporting uses.
The consequences are practical rather than theoretical. Labour cost by department or project is available in standard NetSuite reporting without an export. There is no payroll clearing account requiring investigation each month. There is no synchronisation failure to notice, diagnose and correct. And there is a single security model rather than two sets of permissions to keep consistent.
The reporting consequence deserves more than a passing mention, because for many finance teams it is the whole argument.
Labour is usually the largest cost in a service business and among the largest in most others, and yet it is frequently the cost least visible in management reporting, because it arrives as a single journal line.
When payroll posts natively, every pay component carries the same dimensional coding as the rest of your ledger. Labour cost by department, by project, by location or by class is available in a standard saved search, at transaction level, without an export.
That changes what you can ask. Project profitability including real labour rather than an allocation. Departmental cost trends month on month. Overtime concentration by location. None of these require a special exercise, which means they get looked at regularly rather than annually.
A smaller benefit that removes a persistent irritation.
Where payroll is separate, every employee exists twice. A change of department, manager, cost centre or address has to happen in both places, and the two drift apart quietly because nobody notices when they do.
That drift causes real problems downstream. Reporting attributes cost to the wrong department. Approval routing sends requests to a former manager. Onboarding and offboarding checklists have to cover both systems and frequently miss one.
On platform, the employee is one record. The department field that drives your financial reporting is the same field the payroll uses. Change it once and everything follows.
Modest in isolation, and across a few hundred employees and a normal rate of internal movement it removes a steady source of small errors.
Any payroll operating in Australia has a specific set of obligations, and this is where generic international products consistently struggle.
Single Touch Payroll Phase 2 requires disaggregated reporting of gross pay, separating out overtime, allowances, bonuses, paid leave and salary sacrifice, along with employment and cessation details. This is considerably more granular than Phase 1 and it constrains how pay codes must be configured.
Superannuation guarantee obligations require correct identification of ordinary time earnings, which is a legal definition rather than an obvious one, calculation at the current rate, and payment by the quarterly deadlines with the fund's receipt date being what counts rather than the payment date.
Modern award coverage brings minimum rates by classification, allowances, overtime, penalty rates and span of hours provisions, updated annually following the wage review.
Leave entitlements accrue under the National Employment Standards with long service leave varying by state, and record keeping obligations extend to seven years under the Fair Work Act.
A payroll application designed for Australian conditions handles these as core functionality. One designed elsewhere and localised handles them through configuration, which usually works and requires more of you.
Even for a rebrand, a short verification pass is sensible practice.
Confirm your support arrangements, specifically who to contact and through what channel, since these frequently change even when the product does not.
Review your commercial terms at renewal, since ownership changes sometimes bring pricing or packaging adjustments over time.
Check that your internal documentation reflects the new name, because a procedure referring to a product nobody recognises causes confusion for new starters.
And run your normal post change verification on the next pay run. Not because anything is expected to differ, but because verification after any change is good discipline and the cost of doing it is an hour.
The longer term significance is that payroll now sits alongside other applications built on the same principle.
Zone's portfolio covers advanced billing, bank reconciliation, approvals and reporting, all built as SuiteApps rather than integrations. For an organisation already committed to NetSuite as its system of record, that consistency has value.
The benefit is architectural rather than about any individual feature. Applications built natively share the security model, the customisation framework, the reporting engine and the release cycle. They do not each bring their own user administration, their own data model and their own failure modes.
Whether that matters to you depends on how many gaps you have around NetSuite and how you are currently filling them. For businesses running four or five bolt on systems with integrations between them, consolidating onto natively built applications removes a genuine maintenance burden.
If you are running NetSuite and payroll elsewhere, the case for bringing it onto the platform rests on a few concrete things.
The reconciliation work disappears, which for most finance teams is several hours per pay cycle plus the month end investigation when the clearing account does not clear.
Labour cost reporting becomes available at the same dimensional granularity as everything else, which for project based or multi entity businesses is frequently the deciding argument.
The employee record stops being duplicated, so a change of department, cost centre or manager happens once.
And the failure surface shrinks, because integrations fail, they fail quietly, and somebody has to notice.
Against that, migration has a cost. Year to date figures must move, configuration must be rebuilt and verified, and parallel runs are necessary before cutover. It is a project, not a switch.
Where you decide to move, the timing materially affects the difficulty.
The start of a financial year is the cleanest option, because year to date figures start from zero and the reconciliation burden largely disappears.
Mid year is possible and requires migrating year to date balances accurately, verifying them against your existing system, and running parallel for at least two cycles before relying on the new one.
Avoid periods of peak activity, award rate changes, or anything else that adds variables to the verification.
Allow more time than the software vendor suggests. The application configuration is rarely the long pole. Establishing exactly how your current payroll interprets your awards, which is often undocumented and lives in one person's head, usually is.
Parallel running is the standard control and it is frequently done in a way that proves less than people assume.
Comparing net pay totals is not sufficient. Two systems can arrive at the same net through different combinations of gross, tax and deduction, and the difference matters for reporting even when the payment is identical.
A proper parallel compares at component level for every employee. Gross by pay code, tax, superannuation, each deduction, and leave movement. Differences are then explained individually rather than netted off.
It also needs to cover the awkward cases deliberately rather than by chance. A termination, a back pay, a leave payment, a salary sacrifice arrangement, someone who crossed a threshold. A clean cycle with no exceptions proves the easy path works.
Two cycles is a reasonable minimum, and where the payroll is complex three is better. The cost of an extra cycle is small against the cost of discovering a systematic error after cutover.
Whether you are migrating or reviewing an existing setup, a few areas account for most payroll errors.
Pay code configuration determines Single Touch Payroll Phase 2 reporting, so a code categorised incorrectly produces a submission that is wrong in a way nobody notices until the ATO does.
Ordinary time earnings determination drives superannuation, and the treatment of allowances, overtime and bonuses is not uniform. Getting this wrong understates or overstates super across every employee simultaneously.
Award interpretation covers classification mapping, allowance eligibility and penalty rate application, and is where most underpayment remediation originates.
Leave accrual rules, particularly for part time and casual staff and for long service leave across states, produce errors that compound silently over years before surfacing at termination.
Each of these is worth an explicit review rather than an assumption that it was set up correctly at some point.
On platform payroll is a strong fit for NetSuite customers with Australian employees who value dimensional labour reporting and want to remove reconciliation work. The more entities, departments or projects you report across, the stronger the case.
It suits organisations with award covered staff, since the Australian specific handling is where the product is differentiated.
It is a weaker fit where payroll is genuinely trivial, a handful of salaried people on identical arrangements, because the integration burden you would be removing is small.
And it is a poor fit where you have a substantial international payroll footprint that a single Australian product would not cover, in which case a global provider with local capability may be the better structure even at the cost of integration.
Being honest about which situation you are in saves an evaluation that was never going to land.
If you are moving, the partner matters at least as much as the product.
The award interpretation question is the one that separates capable partners from ones who will configure what you tell them and leave the correctness with you.
Payroll is not a system you configure and leave, because the rules underneath it change every year.
The annual wage review flows into modern award rates from the first full pay period after the operative date, which means somebody has to know which of your classifications are affected and apply the change on time.
Superannuation guarantee rate changes take effect on a fixed date and apply based on when the payment is made rather than when the work was performed, which catches out payrolls that span the change.
Tax scales and thresholds change, reporting requirements are extended, and the treatment of particular payment types occasionally shifts.
A good arrangement makes this somebody's explicit responsibility, whether that is your provider or a named person internally. Where it is nobody's job, changes get applied late, and late is the same as wrong for the pay periods in between.
If you are an existing customer, the answer is largely nothing. Note the name change, update your internal references, confirm your support contact, and verify the next pay run as you would after any change.
If you are evaluating, the rebrand does not change the underlying question, which is whether payroll running inside your ERP is worth more to you than the migration costs.
For businesses with dimensional reporting requirements, multiple entities or a finance team currently spending real time on payroll reconciliation, it usually is.
Our payroll and bookkeeping service covers both implementation and ongoing processing, and our guide to Australian payroll compliance sets out the obligations any arrangement has to meet.
If you would like to talk through what a move would involve for your business, get in touch.
