For Australian finance and operations leads with a stalled NetSuite project, one hypothetical rescue followed from diagnosis to go live.
Last reviewed: 6 November 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
A NetSuite implementation rescue in Australia resets a stalled project without starting again. You freeze new scope, test real Australian transactions for two weeks and rank what is broken by business impact. Then you set a new go live date at the start of a BAS quarter. Usually, much of the build you already paid for can be kept.
Key takeaways
A NetSuite implementation rescue is a short, structured reset of a project that has stalled before go live, or gone live without working as planned. It is not a new implementation. It keeps the account, the configuration and the data that are sound, and fixes or removes the rest.
The platform is rarely the problem. NetSuite already handles Australian GST, BAS reporting, ABA payment files and multi entity accounting. Projects stall when decisions wait for weeks, data is loaded before it is clean, or nobody owns testing.
That is good news for the business. The fixes are mostly about scope, data and ownership, and they can be planned.
A few signs usually show that a project needs a rescue rather than more effort. Go live dates move more than once. Testing never finishes a round. Finance staff stop trusting the numbers they see in the sandbox account.
Here is one hypothetical case, followed from start to finish. All figures are in AUD and exclude GST unless shown.
A Brisbane wholesale distributor with 45 staff signed for NetSuite in February 2026. It was moving off entry level accounting software and a set of spreadsheets. The plan was to go live on 1 July 2026, the start of the new financial year.
That date slipped to 1 October, and then the project stopped moving. It is now early November 2026, and the company has spent AUD 150,000 of an AUD 180,000 budget.
User acceptance testing, the stage where staff try real work in the new system, is stuck in its first round. The finance manager no longer trusts the opening balances. Nobody has tested the BAS report or the payroll journal.
The managing director asks a simple question. Do we fix this, or do we start again? The answer comes from a two week diagnosis.
The diagnosis runs from Monday 9 November to Friday 20 November 2026. The team first secures Administrator access, the sandbox account, the statement of work and the issue log. Then they run five Australian transactions from start to finish in the sandbox:
Each transaction either works or shows exactly where it breaks. In this hypothetical case, the findings go into one table, ranked by what they would cost the business:
| Finding | Business consequence | Fix |
|---|---|---|
| Customer records loaded twice in testing, about 600 duplicates | Wrong AR aging and statements | Clean the source file, use one import template, reconcile record counts |
| Some GST free purchase items mapped to a taxable code | BAS would overstate GST credits | Correct the tax codes on items and vendors, rerun the BAS test |
| ABA file never tested with the bank | Supplier payments at risk on day one | Finish the bank setup and send a test file to the bank |
| Payroll journal not mapped to departments | Wage costs in one account, no margin by team | Map payroll items to accounts and departments, test the import |
| 14 custom scripts, 5 with no clear purpose | Slower testing and future upgrades | Retire the 5 unused scripts after sign off |
| No single owner for open decisions | Sign offs waiting three weeks or more | Name one steering owner and hold a weekly 30 minute decision meeting |
The opening balance worry traces back to the duplicate customers. Once the customer file is clean, the receivables total matches the closing trial balance from the old system.
Notice what is not on the list. The order to cash flow works, inventory by location works and the chart of accounts is sound.
Most of the AUD 150,000 has built something useful, so starting again would throw good work away.
The reset plan starts from one date. The company lodges BAS quarterly, so the cleanest go live is the first day of a quarter. That way each BAS comes from one system only.
1 January 2027 is too close, with the Christmas shutdown in the middle. The team chooses Thursday 1 April 2027, the start of the April to June quarter. The old system will still produce the January to March BAS, due 28 April 2027. NetSuite will produce the April to June BAS, due 28 July 2027.
Working back from that date gives the plan below.
Payroll needs its own check. Since 1 July 2026, Payday Super means super must reach the fund within 7 business days after payday. The payroll provider still runs pay and super, but the first NetSuite payroll journal and the super liability have to reconcile in week one. Our guide to NetSuite payroll integration in Australia covers that journal design.
The first weeks after go live follow the plan in our NetSuite hypercare guide for Australia, which ends hypercare on the first clean BAS.
The rescue is budgeted in three parts: a fixed fee diagnosis, fix work in hours and a contingency. The hourly rate here is a round hypothetical figure.
| Item | Working | AUD |
|---|---|---|
| Diagnosis | Fixed fee, two weeks | 12,000 |
| Data cleanup and reload | 60 hours | |
| Tax codes and BAS testing | 24 hours | |
| Payroll journal mapping | 40 hours | |
| ABA file and bank testing | 16 hours | |
| Testing support and two mock cutovers | 40 hours | |
| Training | 20 hours | |
| Fix work total | 200 hours at AUD 200 | 40,000 |
| Contingency | 15% of fix work | 6,000 |
| Rescue total before GST | 12,000 + 40,000 + 6,000 | 58,000 |
| GST | 10% | 5,800 |
| Rescue total including GST | 63,800 |
The project has AUD 30,000 left in its original budget. The rescue needs AUD 58,000 before GST, so the board is asked to approve an extra AUD 28,000. The whole project would then cost AUD 208,000 against the first budget of AUD 180,000.
That is a real overrun, and the team presents it honestly. The alternative is a fresh start, which would repeat most of the AUD 150,000 already spent. In this case, the board approves the rescue in one meeting.
If your own NetSuite project feels stuck, these five checks take a few days and cost nothing:
In my experience, these five answers tell you more than another status report. Our NetSuite implementation rescue checklist for Singapore adds more diagnosis questions, and our NetSuite health check in Australia suits accounts that are already live.
At CuriousRubik, we start a rescue with one bounded problem and agree the evidence before anyone commits to a full plan. Our NetSuite implementation team can run the diagnosis, rank the fixes and set a go live date that suits your BAS calendar. See how we work with NetSuite customers in Australia.
A diagnosis checklist for a NetSuite project that has gone off track.
What a review of a live Australian account looks at and what you get.
How to run the weeks after go live, through the first pay run and BAS.