NetSuite implementation cost in Australia for a multi-entity group is driven less by the number of users than by how differently the entities operate. Each subsidiary adds setup, tax, currency, data and testing work, and every flow between entities adds intercompany and elimination work on top. Price those group lines separately and you can compare quotes on the same footing.
The trap is asking for a quote on the parent company and assuming the other entities are a copy. They rarely are. A New Zealand subsidiary has its own GST return, a US sales arm may bill in USD and the group close needs eliminations that no single-entity project ever tests. A quote that treats them as cloned setups will grow later, usually through change requests.
Start with a one-page group map before any partner estimates a day. List each legal entity, its country, functional currency, tax registrations, who owns its books and whether it trades with the others. Mark the entities that are dormant or holding companies, because they need far less work than an operating subsidiary with stock and staff.
Then sort the entities by how they actually run. Two Australian companies on the same chart of accounts with the same approval rules are close to one design. A New Zealand distributor with its own warehouse and pricing is a second design, even if it reports in the same group. That sorting tells a partner far more than "four subsidiaries" ever will. Our guide to NetSuite OneWorld design for subsidiaries, currencies and reporting covers the structural decisions in detail.
Intercompany work is where group quotes most often go thin. List every recurring flow between entities: management fees, shared service recharges, intercompany stock sales, loan interest and costs one entity pays on behalf of another. Each flow needs a decision on how it is raised, how the other side records it and how the pair is matched at month end.
Ask each partner to price these flows by name. A line called "intercompany setup" with no list behind it is a placeholder, not an estimate. Intercompany stock sales cost the most, because they touch pricing, transfer orders, landed cost and the elimination of unrealized profit. A monthly management fee between two AUD entities costs very little. Our post on NetSuite intercompany reconciliation from transaction pair to elimination shows what has to be tested before you can trust the numbers.
Consolidation sounds like a report. In practice it is a design, a set of tests and a sign-off. Someone has to agree the elimination rules, the translation method for each currency, how minority interests are handled if there are any and which reports the board sees. Then the finance team has to prove that a full month consolidates and ties back to each entity's trial balance.
Budget for at least two full close rehearsals with real data before go-live. The first rehearsal finds the mismatched intercompany pairs and the missing mappings. The second shows whether the fixes held. A single-entity project usually needs one rehearsal, which is why group projects that copy a single-entity plan run late at exactly this point.
Every additional currency brings bank accounts, exchange rate sources, revaluation runs and translation tests. An AUD parent with NZD and USD subsidiaries needs all three tested through a full cycle, including the realized and unrealized gains that land in the group accounts. Ask how exchange rates will be loaded and who checks them each month.
Tax is the same story. Australian entities need GST codes and BAS reporting that reconcile to the ledger. A New Zealand subsidiary needs its own GST setup and return, at a different rate. A US subsidiary may need sales tax review in each state where it has nexus. Confirm with each entity's tax adviser what has to be reported, and make each return a line in the quote with its own acceptance test.
A hypothetical Australian wholesale group runs four entities: an AUD parent that owns the stock, a second AUD services company, a New Zealand distributor in NZD and a small US sales company in USD. The group already has a quote for a core single-entity rollout of the parent at A$120,000 in services. The figures below are invented for this example, exclude GST and exclude NetSuite subscription and license fees.
| Group cost driver | What it covers | Hypothetical services cost |
|---|---|---|
| OneWorld design and subsidiary setup | Three extra subsidiaries, shared chart of accounts, roles by entity | A$18,000 |
| Intercompany flows | Stock sales to NZ, management fees, shared service recharges | A$22,000 |
| Consolidation and eliminations | Elimination rules, translation, two close rehearsals | A$16,000 |
| Currency setup | NZD and USD banks, rate loads, revaluation tests | A$9,000 |
| Tax per entity | AU GST and BAS, NZ GST return, US sales tax review | A$12,000 |
| Data migration per entity | Three more opening balance sets, open AR, AP and stock | A$15,000 |
| Extra testing and training | Entity-level test scripts, NZ and US users | A$14,000 |
| Group total | A$106,000 |
The group lines add A$106,000, taking services to A$226,000, or about 88% more than the single-entity figure the board first saw. When the group agrees to run the services company on the parent's processes with no local variations, the setup, testing and training lines for that entity shrink by roughly A$10,000. The structure stays the same. The work per entity falls. Your numbers will differ, but the pattern of pricing each driver by name is the part to keep.
Every local variation multiplies design, testing and training. A group that lets each entity keep its own approval chain, item naming and customer terms pays for that choice several times over. Decide early which processes are group standard and which stay local because the law or the market requires it.
A short rule helps here. Keep a process local only if a statute, a customer contract or a real operating difference demands it, and write down the reason. Everything else follows the group template. That rule usually removes a meaningful share of the testing effort and makes the system easier to support after go-live.
Data migration is counted per entity, not once for the group. Each subsidiary needs its own opening balances, open receivables and payables, stock on hand and fixed asset register, plus a reconciliation that the entity's accountant signs. If the entities sit on different legacy systems, each source needs its own extraction and mapping.
Agree how much history moves. Open items and balances are the usual minimum. Moving several years of transactions per entity can cost more than the rest of the migration combined, and the old reports often answer the same questions for far less. Put the history decision in writing before the estimate is finalized.
Once the group map, intercompany list, tax list and migration plan exist, send the same pack to every partner and ask for a price per driver. Proposals that bundle the group work into one line can then be split and compared. Our AUD total cost model for your NetSuite decision covers the subscription, internal effort and multi-year side of the budget, so this exercise can stay focused on services.
Check who carries the risk if the group work runs over. Under day rates that risk stays with you. CuriousRubik prices a defined outcome instead, and our NetSuite implementation services can help you turn a group map like this into a fixed scope with acceptance tests for each entity. You can also see the kind of work we deliver for NetSuite projects in Australia.
Related reading: NetSuite Implementation Timeline in Australia
No. A dormant holding company adds very little, while an operating subsidiary with its own stock, currency and tax return can add as much as a small implementation. Price each entity by how it operates.
Usually, if the entities need separate legal ledgers in one account with consolidation. Confirm the edition and licensing with NetSuite or your partner, because packaging changes and these costs sit outside the services quote.
Yes, but design the subsidiary structure, chart of accounts and intercompany rules for the whole group first. Adding entities to a design that never planned for them tends to cost more than doing it once.
It depends on the number of currencies, the intercompany volume and the reporting the board needs. Budget for at least two full close rehearsals and ask partners to price consolidation as a separate line.
Yes, if the New Zealand entity will run in the same account. List the NZ GST return as a deliverable with its own acceptance test, and confirm the requirements with the entity's tax adviser.