ERP — Enterprise Resource Planning — is a category of software that integrates core business functions into a single system. For growing businesses, the right ERP implementation can be transformational: eliminating manual processes, improving data quality, and giving management a real-time view of the business. The wrong implementation, or the right system implemented badly, can cost hundreds of thousands of dollars and years of recovery time.
This guide is written for business leaders — not IT professionals — who are considering or approaching an ERP implementation for the first time.
When Does a Business Need an ERP?
Not every business needs a full ERP system. Many SMEs operate well on modular solutions — accounting software plus dedicated add-ons for specific functions. The question is when the complexity of the business justifies the investment in a more integrated platform.
Common triggers for an ERP consideration:
- Multiple disconnected systems that require manual data transfer or reconciliation (a sure sign of growing complexity outpacing the current tech stack)
- Inventory and manufacturing complexity that exceeds what accounting software can manage
- Multi-entity structures (multiple companies or warehouses) that create consolidation challenges
- Rapid growth that is exposing the fragility of existing systems
- Acquisition integration — bringing two businesses together often requires a common platform
- External reporting obligations (lenders, investors, or regulators) that require more rigorous and auditable financial data
For most Australian SMEs, the ERP conversation becomes relevant somewhere between $10M and $50M in revenue, though this varies considerably by industry. Manufacturing, wholesale distribution, and multi-site hospitality tend to hit ERP-relevant complexity earlier; professional services firms often operate on simpler systems for much longer.
The Australian ERP Market
For SMEs, the most commonly implemented ERP platforms in Australia include:
- MYOB Advanced (formerly Greentree) — well-suited to mid-market Australian businesses with strong local support
- NetSuite — cloud-native, strong for multi-entity and international businesses
- Microsoft Dynamics 365 Business Central — widely supported, strong integration with the Microsoft ecosystem
- SAP Business One — strong in manufacturing and distribution
- Pronto Xi — Australian-developed, widely used in retail, distribution, and manufacturing
The right platform depends on your industry, size, growth trajectory, and the specific functional areas where you need the most improvement.
The Three Biggest ERP Implementation Mistakes
1. Under-Investing in the Implementation
ERP implementations fail more often due to poor project management and inadequate change management than due to software quality. The licence fee is only part of the cost — a well-resourced implementation (including internal project management time, staff training, data migration, and change management) typically costs 1.5 to 3 times the annual licence cost.
Businesses that cut corners on implementation end up with a system that is technically installed but poorly configured, inadequately trained, and not fully adopted. The result is often worse than what was there before: staff working around the system, data quality problems, and management making decisions based on unreliable output.
2. Implementing Yesterday's Processes
An ERP implementation is an opportunity to redesign business processes, not just automate the existing ones. If you configure the system to replicate how things are done today — including all the workarounds and manual interventions — you miss much of the available benefit.
Before configuring the system, map your current processes and identify where they are inefficient, error-prone, or not fit for purpose. Design the future-state process first, then configure the system to support it.
3. Inadequate Data Migration
Data quality at go-live determines the usability of the system from day one. A new ERP loaded with incomplete, inconsistent, or inaccurate data creates immediate problems:
- Inventory records that do not match physical stock
- Customer and supplier records with missing or incorrect information
- Opening financial balances that do not reconcile
Data migration requires a structured programme: extract historical data, clean it, validate it against source systems, test it in a test environment, and validate again before go-live. This is typically more time-consuming than anyone expects.
A Framework for a Successful Implementation
Phase 1: Discovery and Vendor Selection (2–4 months)
Define your requirements clearly before approaching vendors. What processes are you trying to improve? What does "success" look like 12 months post go-live? What are your non-negotiables?
Run a structured vendor selection process: issue a requirements document, shortlist three or four vendors, conduct product demonstrations, check references from businesses similar to yours, and assess the quality of the implementation partner (not just the software).
The implementation partner selection is as important as the software selection. Look for:
- Experience with businesses similar to yours in size and industry
- Proven methodology and project management approach
- Strong local support capability
- References you can call
Phase 2: Project Planning and Design (1–3 months)
Establish the project team with clear ownership. At minimum, you need:
- An internal project sponsor (a senior leader with authority to make decisions and drive adoption)
- An internal project manager (the day-to-day owner of the implementation)
- Subject matter experts from each functional area affected
The design phase defines how the system will be configured for your specific business. This involves workshops with each functional area, process documentation, and sign-off on the design before build begins.
Phase 3: Build and Test (2–4 months)
The implementation partner configures the system to the agreed design. The business team tests it rigorously — not just that it works as designed, but that it works for real business scenarios. User acceptance testing should include your most complex and edge-case transactions, not just the happy path.
Phase 4: Training and Change Management (1–2 months)
Staff need to be trained on the new system before go-live, not during it. Training should be role-specific — a finance team member does not need to know how to process purchase orders; a warehouse team member does not need to understand month-end journals.
Change management is about more than training. It is about helping staff understand why the change is happening, what the benefit is to them and the business, and how to escalate issues during and after go-live.
Phase 5: Go-Live and Post-Implementation Support (Ongoing)
A hypercare period — typically 30 to 60 days immediately after go-live — provides intensive support while staff adapt to the new system and initial issues are resolved. This period should be resourced, not assumed to be self-managing.
Post go-live, establish a regular review cadence: are the business benefits being realised? What configuration adjustments are needed? What training gaps exist?
The CFO's Role in ERP Implementation
The CFO (or fractional CFO) should be deeply involved in an ERP implementation — not as a technical project manager, but as the custodian of the financial data integrity and reporting requirements of the system.
Specifically, the CFO should own:
- Chart of accounts design
- Financial reporting configuration
- Month-end close process design in the new system
- Financial control and audit requirements
- The integrity of the opening financial balances at go-live
An ERP implementation that delivers clean, timely financial data and integrates operations and finance is a significant competitive advantage. Approached with appropriate rigour and resources, it is one of the most valuable investments a growing business can make.
Tags