Most New Zealand finance teams are not looking for financial planning software. They are looking for a way to get through the next planning cycle without spending three days reconciling versions of the same spreadsheet. The two things turn out to be the same problem.
This is not a technology failure. It is a design mismatch. Spreadsheets are genuinely excellent tools: for individual analysis, for contained problems, for one person working through a defined question. What they were never designed to do is carry the weight of a collaborative, multi-entity planning process for a finance team that is already stretched thin.
In New Zealand, that stretch is real. Most mid-market finance functions run lean. One or two people are often responsible for the entire budgeting and forecasting cycle: consolidating inputs from across the business, maintaining the model, producing the board pack, and then doing it all again when assumptions change. The manual overhead that a larger team might absorb becomes unsustainable at that scale. Financial planning software built for this kind of work changes that equation significantly.
What the spreadsheet is actually costing you
The costs of spreadsheet-based planning are easy to underestimate because they are hard to see. Nobody puts “three hours reconciling conflicting headcount figures” on a timesheet. But add it up across a planning cycle and the picture changes.
Version sprawl kills analysis time. Every contributor works in their own copy of the model. Consolidation is a manual exercise: chasing files, resolving conflicts between versions that diverged two weeks ago, rebuilding a picture that should already exist. Finance teams routinely spend more time assembling the plan than interrogating it. The question that should be getting answered, “what does this tell us about the business?”, gets deferred because the question actually being answered is “whose numbers are these?”
Reforecasting becomes a project in itself. A budget built on March headcount assumptions does not update when April’s numbers come in. It has to be rebuilt. For organisations on a June or March year-end, which covers most of the New Zealand market, this compression of the planning cycle around a fixed close date makes the problem worse. When reforecasting takes two weeks, it happens less often than it should.
Scenario modelling gets quietly abandoned. Running a base case, an upside, and a downside in parallel is theoretically possible in spreadsheets. Most teams do not do it. Not because they do not see the value, but because the effort is disproportionate to the time available. So decisions that should be informed by a range of futures get made on a single set of numbers, usually the one most recently updated.
The numbers in your plan are never quite current. Actuals live in the ERP. Headcount lives in the HR system. The spreadsheet knows neither until someone exports a file, pastes it in, and checks the formulas held together. Every manual step is a place where the plan and reality quietly drift apart.
What Workday Adaptive Planning does differently
The case for Workday Adaptive Planning is not that it does the same things as a spreadsheet, only faster. It is built for a different kind of work entirely.
The most immediate difference is structural. Contributors work in a shared environment rather than separate files. There is no consolidation step because consolidation is continuous. When a regional manager updates their cost assumptions, the model reflects it. No email, no file collection, no version conflict to untangle on a Friday afternoon.
The modelling approach is different too. Instead of hard-coding numbers, you build around the drivers that determine outcomes: headcount, revenue per unit, contract terms, occupancy rates. When a driver changes, every downstream number updates automatically. Reforecasting means adjusting assumptions, not rebuilding the model. Which means it actually happens when it should.
Scenario planning stops being a special project and becomes a normal part of the process. Multiple futures can be modelled simultaneously and compared directly. The board pack can show the base case and the downside side by side, rather than presenting a single number with a footnote that quietly hopes nobody asks too many questions.
Live connections to your ERP, HR system, and CRM mean actuals flow in automatically, without anyone exporting a file. The gap between what your systems know and what your plan reflects narrows considerably.
Configurable Workflows give finance teams direct control over how plans are routed, reviewed, and approved. Combined with updated access rules, the right people see the right data and act on it, without the finance team manually herding the process. Every change, input, and approval is logged, so when a number needs to be traced, the platform can do it.
What are you not doing because the tool makes it too hard?
Most finance leaders evaluating a move like this ask whether it is worth it. For most mid-market New Zealand organisations running material planning processes, it is, and the time savings in the first planning cycle tend to confirm that quickly.
The better question is what you are currently not doing because your tools make it too difficult. The scenario analysis that keeps getting pushed to next quarter. The reforecast you are delaying because starting it feels like a three-week commitment. The board conversation you cannot have because the numbers are two weeks stale. Those are not gaps in your team’s capability. They are gaps created by the tool.
Mero’s implementation approach is designed to close those gaps and leave your team genuinely self-sufficient on the platform, not reliant on ongoing consultancy to keep it running. If you would like to understand what that would look like for your organisation, get in touch.
Frequently asked questions
No, and this comes up a lot. The platform is used by organisations from mid-market through to large enterprise, and it scales in both directions. It handles the complexity of a multi-entity, multi-currency environment, and it works equally well for a small New Zealand finance team that simply wants to move from spreadsheets to something connected and auditable. The right question is not size. It is whether your current planning process is creating enough friction that a purpose-built tool would meaningfully change the way your team works.
A focused implementation covering budgeting, forecasting, and reporting for a defined business unit typically takes eight to twelve weeks. Broader deployments across multiple entities or with more complex modelling take longer. The most important factor is scope clarity before the build begins: organisations that are specific about what they need in the first twelve months move faster and get to value sooner. Mero’s approach is built to deliver a working environment your team can actually use, rather than a technically complete system handed over on go-live day with a wave and a user guide.
Yes. Workday Adaptive Planning has native connectors for a wide range of ERP, HR, and CRM systems, including SAP, Oracle, Workday HCM, Salesforce, and others. Where a native connector does not exist, data can be loaded via flat file or API. Getting the integration design right early matters: it is the difference between actuals flowing in automatically and someone spending Tuesday mornings doing exports. It is worth spending time on it at the start of an implementation rather than retrofitting it later.