The Complete Guide to ERP Readiness for Australian Businesses

​Why ERP Readiness Is the Most Overlooked Step in Any ERP Project

Most businesses approach an ERP purchase the same way they approach buying a car — they go to the showroom, test a few models, and pick the one they can afford. What they don't do is check whether they know how to drive. 

This is the fundamental problem with the way ERP selection is typically conducted. Businesses invest months evaluating vendors, comparing feature lists, and negotiating licence deals. They sign the contract, kick off the project, and then discover — usually about three months in — that their data is a mess, their processes aren't documented, their chart of accounts doesn't make sense, and their team isn't sure who owns what.

The result is cost overruns, delayed go-lives, and in the worst cases, complete project failures. Research consistently shows that between 50 and 75 percent of ERP implementations are considered unsuccessful by the organisations that commissioned them. The root cause, almost without exception, is inadequate preparation.

ERP readiness is the discipline of preparing an organisation before implementation begins. It is not a quick checklist exercise. It is a structured assessment across five distinct dimensions — process, data, people, technology, and compliance — that gives you an honest view of what needs to happen before your ERP project can succeed.

This guide covers everything Australian businesses need to know about ERP readiness and the ERP selection process that follows. It is written from the perspective of chartered accountants who have delivered over a decade of ERP implementations across Australia and New Zealand — which means it gives particular attention to the financial, accounting, and compliance factors that IT-focused guides routinely ignore.

Section 1: What Does 'ERP Ready' Actually Mean? 

Enterprise resource planning (ERP) software integrates the core functions of a business — accounting, inventory, purchasing, sales, manufacturing, HR, and payroll — into a single connected system. When it works, it eliminates data silos, automates repetitive tasks, and gives leadership a real-time view of the business.

Being 'ERP ready' does not mean your business is perfect. It means your business has reached a sufficient level of maturity across five dimensions that an ERP implementation can proceed without the foundational issues that cause most projects to fail.

The five dimensions of ERP readiness are:

Most ERP readiness guides focus on process and technology. What makes the Australian context unique — and what most technology-led implementations miss — is the compliance dimension. Australian businesses operate under a compliance framework that is specific, detailed, and unforgiving. A business that goes live on an ERP without having validated its GST configuration, BAS lodgement workflow, and STP Phase 2 setup is not ready. The cost of getting this wrong is not just inconvenience — it is ATO penalties, incorrect reporting, and significant rework.

We will cover the compliance dimension in detail in Section 6 of this guide.

​Section 2: The Warning Signs Your Business Needs an ERP

Before assessing readiness, you need to determine whether an ERP is the right solution at all. The investment is significant — in money, time, and organisational energy — and it is not appropriate for every business at every stage.

The following are the most reliable indicators that a business has outgrown its current systems and is a genuine ERP candidate.

1. Month-end close takes longer than five business days

If your finance team spends the first week of every month reconciling accounts, chasing information from other departments, and manually consolidating reports, this is a process and data integration problem. ERP systems automate the reconciliation of inventory, accounts receivable, accounts payable, and payroll in real time, which compresses month-end close to hours rather than days.

2. Your team re-enters data across multiple systems

A customer order entered in your CRM should not need to be re-entered in your invoicing software and again in your inventory system. Every re-entry point is a source of error and delay. ERP systems eliminate this by creating a single source of truth — data entered once flows automatically to every part of the system that needs it.

3. You cannot get a real-time view of your financial position

If answering 'what is our cash position right now?' requires you to pull three spreadsheets and make a phone call to your bookkeeper, your systems are holding you back. ERP platforms provide live dashboards showing cash, debtors, creditors, inventory value, and payroll liabilities — updated continuously as transactions occur.

4. You are preparing for growth, a capital raise, or a compliance audit

Investors, acquirers, and auditors all want clean, auditable financial data. If your records are fragmented across multiple systems and partially maintained in spreadsheets, you are exposed. ERP implementations are often triggered by an upcoming due diligence process or the realisation that the current systems cannot support the growth trajectory the business is targeting.

5. Your accountant or CFO keeps asking for reports you cannot produce

Investors, acquirers, and auditors all want clean, auditable financial data. If your records are fragmented across multiple systems and partially maintained in spreadsheets, you are exposed. ERP implementations are often triggered by an upcoming due diligence process or the realisation that the current systems cannot support the growth trajectory the business is targeting.

6. You have hit $5M in revenue or 20+ staff

These are rough thresholds, not rules, but they reflect a common inflection point. Below these numbers, a well-configured accounting platform combined with a CRM is often sufficient. Above them, the coordination costs of disconnected systems start to compound — and the risk of an error in stock, payroll, or reporting starts to become consequential.

​Section 3: How to Conduct an ERP Readiness Assessment

An ERP readiness assessment is a structured review of your organisation across the five dimensions described in Section 1. The output is a readiness score, a gap analysis, and a prioritised list of actions to take before implementation can begin.

The assessment typically takes between two and six weeks, depending on business size and complexity. It should involve your finance manager, operations manager, IT contact, and at least one senior leader who has authority to make decisions about process change.

Step 1: Process mapping

Document your current state processes across the functions the ERP will cover. This does not need to be a formal BPMN exercise — a clear written description of how work flows through each function is sufficient. The goal is to identify which processes are standardised and which are ad hoc, and which processes will need to change to fit the new system.

Pay particular attention to financial processes: how invoices are raised, how purchases are approved, how payroll is calculated, how the BAS is prepared, and how month-end close works. These are the processes an ERP will change most significantly.

Step 2: Data audit

Pull a sample of your key data sets: your customer list, supplier list, product/SKU master, chart of accounts, and opening trial balance. Assess each for completeness, accuracy, and deduplication. 

Ask:

• How many duplicate records exist in your customer and supplier lists?
• Are all products in your inventory system accurately valued and coded?
• Does your chart of accounts reflect how your business actually needs to report
• Do your opening balances agree with your most recent signed financial statements?

Data migration is the part of ERP implementation that is most commonly underestimated. A data audit at the readiness stage surfaces problems early — when they can be fixed before the project clock starts.

Step 3: People and change readiness

ERP implementations fail for technical reasons less often than they fail for human reasons. Assess your team's readiness honestly:

• Does your leadership team have genuine sponsorship of this project, or is it being driven by one enthusiastic champion?
• Are the people who will use the system daily involved in the scoping process?
• Is there documented awareness of what will change and why?
• Is there budget and time allocated for training, not just go-live support?

Step 4: Technology environment review

Understand what you currently run, what integrates with what, and what will need to connect to the new ERP. Document your current software stack, note which systems are contractually committed, and identify any legacy data formats or API limitations that could affect migration.

Step 5: ANZ compliance requirements check

This step is specific to Australian and New Zealand businesses and is often omitted entirely from international ERP readiness frameworks. Before any ERP can be considered, you must confirm it can handle:

• GST: correct tax coding, BAS worksheet generation, and ATO-lodgeable outpu.
• BAS: automated preparation of all sections including PAYG withholding, FBT, and fuel tax credits where applicable.
• Single Touch Payroll Phase 2: disaggregated income type reporting, salary sacrifice treatment, and STP-enabled payroll.
• TPAR: automated tracking of reportable contractor payments for businesses in TPAR-applicable industries.
• Payroll compliance: Award interpretation, superannuation guarantee calculations, and leave accrual under the National Employment Standards.
  

6. You have hit $5M in revenue or 20+ staff

These are rough thresholds, not rules, but they reflect a common inflection point. Below these numbers, a well-configured accounting platform combined with a CRM is often sufficient. Above them, the coordination costs of disconnected systems start to compound — and the risk of an error in stock, payroll, or reporting starts to become consequential.

​​

​Section 4: The Most Common ERP Readiness Gaps (And How to Close Them) 

After conducting readiness assessments for businesses across Australia and New Zealand over more than a decade, we see the same gaps appear repeatedly. Here are the five most common, and how to address each one.

Gap 1: A chart of accounts that doesn't reflect how the business reports

The chart of accounts is the backbone of your financial reporting. If it was set up when the business was founded and has never been restructured, it is almost certainly not fit for purpose. ERP implementation is the right time to redesign it — but this must happen before migration, not during.

Work with your accountant or CFO to design a chart of accounts that reflects your current business structure: profit centres, cost centres, product lines, or geographic segments. This investment pays back every month in cleaner, faster management reporting.

Gap 2: Dirty or duplicated data

Almost every business that has never run an ERP has data quality issues. The most common are: duplicate customer and supplier records, products with inconsistent coding or missing cost data, and receivables or payables ledgers that don't agree with statements.

The only solution is manual remediation. Assign data owners for each data set, set a cleanup deadline that sits at least four weeks before your planned migration date, and build data validation into your migration testing process.

Gap 3: Undocumented processes

This does not require a formal process management programme. A clear one-page description of each core business process, agreed by the people who perform it, is sufficient to begin system design.

Gap 4: No executive sponsor

If your project does not have an identified executive sponsor with clear accountability, appoint one before proceeding. The project's success will depend on it.

Gap 5: Compliance requirements not mapped

Map your compliance requirements explicitly and include them in your system design and testing plan. Do not assume compliance capability — validate it.

Section 5: The ERP Selection Process — A Step-by-Step Framework

Once your readiness assessment is complete and the identified gaps have been addressed or scheduled for remediation, you are ready to begin the ERP selection process. This is the process of identifying, evaluating, and selecting the right ERP system and implementation partner for your business.

Evaluating ANZ compliance capability during selection

If a vendor cannot demonstrate these workflows in a live system, the compliance claim is marketing language, not a validated capability.

​Section 6: ERP and Australian Compliance — What Your System Must Handle 

This section covers the ANZ compliance requirements that every ERP must meet before an Australian business can safely go live. It is the section most commonly missing from ERP readiness guides written for a global audience.

Goods and Services Tax (GST)

Australia operates a 10 percent GST with a complex set of supply types: taxable, GST-free, input-taxed, and out-of-scope. Your ERP must support:

• Correct tax code mapping for all supply types.
• Automatic calculation of GST collected and GST credits on each transaction.
• Generation of the BAS worksheet with accurate figures for G1 through G20.
• Handling of mixed supplies, adjustments, and GST on imported services

Business Activity Statement (BAS)

The BAS brings together GST, PAYG withholding, PAYG instalments, FBT instalments, and fuel tax credits into a single quarterly or monthly lodgement. Your ERP must:

• Automatically populate BAS worksheet fields from transaction data.
• Handle PAYG withholding calculations for employees and contractors.
  
• Support both cash and accruals accounting methods for GST reporting.
  
• Produce an ATO-ready output that can be lodged through the business portal or via your tax agent.

Single Touch Payroll Phase 2

STP Phase 2 expanded the information reported to the ATO each pay run. Your payroll module must support:

• Disaggregated income type reporting (salary and wages, closely held, working holiday makers, etc.).
  
• Salary sacrifice reporting for superannuation and non-super salary sacrifice.
  
• Lump sum reporting with the correct payment type codes.
  
• Child support deductions reporting where applicable.
• The correct treatment of allowances, overtime, and leave payments.
  

Taxable Payments Annual Report (TPAR)

Businesses in the building and construction, cleaning, courier, information technology, and security industries must report contractor payments to the ATO annually via TPAR. Your ERP must:

• Identify which suppliers are subject to TPAR reporting.
  
• Capture ABN, name, address, and total gross payment for each reportable contractor.
  
• Generate the TPAR in ATO-accepted format for lodgement.
  
  

​Section 7: Accounting Process Maturity and Why It Matters for ERP Readiness 

The concept of accounting process maturity is rarely discussed in ERP readiness literature — but it is, in our experience, the most reliable predictor of implementation success.

Accounting process maturity describes how systematically and consistently a business manages its financial processes. A business at a low maturity level has informal, inconsistent, and largely undocumented financial processes. A business at a high maturity level has defined, consistent, and continuously improved processes that produce reliable financial information with minimal manual effort.

The four maturity levels

• Level 1 — Ad hoc: Financial processes are performed differently each period. Reconciliations are irregular. Reporting is reactive. Month-end close is a crisis.
  
  
• Level 2 — Defined: Core processes are documented and followed consistently. Reconciliations happen on schedule. Reports are produced reliably, though largely manually.
  
  
• Level 3 — Managed: Processes are measured and controlled. Variances are investigated. Reporting is timely and used for decision-making. The finance function is a business partner.
  
  
• Level 4 — Optimised: Processes are continuously improved. Automation is maximised. The finance team spends its time on analysis, not data entry.

An ERP is the primary tool for moving from Level 2 to Levels 3 and 4. But attempting an ERP implementation at Level 1 — without first establishing basic process discipline — is a common and expensive mistake. The ERP amplifies what is already there. If what is already there is chaos, the ERP makes it faster chaos.

Before beginning your ERP project, conduct an honest assessment of your accounting maturity. If you are operating at Level 1, a period of process discipline and documentation — typically 8 to 12 weeks — is a prerequisite for a successful implementation.

​​

​Section 8: How to Choose an ERP Implementation Partner in Australia 

Your choice of implementation partner will have more impact on the outcome of your ERP project than your choice of ERP software. A well-supported implementation of a simpler system will outperform a poorly executed implementation of the most sophisticated platform every time.

What to look for

• ANZ-specific experience: Your partner must understand Australian payroll, tax, and compliance requirements. This is non-negotiable. An implementation partner who has never configured STP Phase 2 or built a BAS lodgement workflow should not be working on your project.
  
  
• Accounting-led approach: The best ERP implementations are led by people who understand financial processes, not just software configuration. Chartered accountants who also understand ERP systems are rare — and significantly more valuable in an implementation context than pure technologists.
  
  
• Demonstrated industry experience: Ask for case studies from businesses of similar size, industry, and complexity. Generic references are of limited value.
  
  
• A structured implementation methodology: Your partner should have a documented implementation methodology that covers discovery, design, configuration, testing, training, and hypercare. If they cannot describe their methodology clearly, it probably does not exist.
  
  
• Post go-live support model: The go-live is not the end of the project. Understand what support is available in the weeks following go-live, and what the ongoing support model looks like.
  

Questions to ask before signing

1. Who will be my day-to-day project contact, and what is their relevant experience?
   
   
2. Can you show me a BAS preparation workflow and STP Phase 2 payroll run in a live demo environment?
   
   
3. What does your data migration process look like, and how do you validate data integrity before go-live?
   
   
4. How do you handle scope changes, and what does your change request process look like?
   
   
5. Who are your three most comparable Australian client references, and may I speak to them directly?
   
   
6. What does your go-live support and hypercare period look like?
   
   
7. What happens if something goes wrong after go-live?

​Section 9: The Cost of Getting ERP Readiness Wrong 

The cost of a failed or struggling ERP implementation is substantial. Research from organisations including Gartner and Panorama Consulting consistently estimates that between 50 and 75 percent of ERP projects fail to meet their original objectives — either by exceeding budget, running over time, delivering reduced scope, or being abandoned entirely.

The direct costs of a failed implementation include:

• Licence fees paid to a vendor whose system is not used.
• Implementation fees for work that must be redone.
• Internal staff time diverted from the business for months.
• Data migration costs incurred twice.
• System downtime and the operational disruption it causes.

The indirect costs are often larger:

• Staff turnover caused by implementation frustration.
  
• Customer service failures during system transition.
  
• Compliance errors and ATO penalties from misconfigured GST or payroll.
  
• Management reporting failures at critical decision points.
  
• Erosion of confidence in the finance function.
  

In our experience, the single most effective risk mitigation for an ERP project is a thorough readiness assessment before the implementation contract is signed. Identifying and addressing gaps before the clock starts is always cheaper than discovering them during a live implementation.

​Section 10: From Readiness to Selection — Your Next Steps 

If you have read this far, you are taking ERP readiness seriously. Here is a practical path forward.

1. Complete the WAO Group ERP Readiness Scorecard. Our 50-point assessment covers all five readiness dimensions with specific criteria for Australian businesses. Download it at waogroup.com.au/erp-readiness-scorecard.
   
   
2. Address your critical gaps. If your scorecard identifies process, data, or compliance gaps, schedule a remediation sprint before moving to vendor selection. Typically four to eight weeks for a focused effort.
   
   
3. Build your selection criteria. Define what matters most for your business — functional fit, ANZ compliance capability, total cost, implementation approach, or partner experience.
   
   
4. Download our ERP Selection Criteria Framework and Scoring Matrix. Available at waogroup.com.au — it includes pre-weighted criteria for common Australian SMB scenarios and ANZ-specific compliance requirements.
   
   
5. Shortlist three to five vendors and issue a structured RFP. Use our ANZ ERP RFP Template to ensure every vendor answers the same questions, including the compliance questions that matter most.
   
   
6. Evaluate implementation partners as rigorously as the software. The implementation partner is the most important variable in your project's outcome.
   
   
7. Book a complimentary readiness consultation with WAO Group. As Australia's only accounting-led Odoo implementation partner, we offer a no-obligation readiness consultation to help you understand where you sit and what it will take to get to a successful go-live.
   

​Related Articles in This Series

This pillar guide is supported by a series of focused articles covering each stage of the ERP readiness and selection journey:

• Is Your Business Ready for an ERP? 7 Signs It's Time.
  
  
• What Is an ERP Readiness Assessment? (And Why You Need One Before Buying).
  
  
• The Real Cost of a Failed ERP Implementation in Australia.
  
  
• How to Build an ERP Selection Criteria Framework.
  
  
• ERP Implementation Phases Explained: What to Expect from Day 1 to Go-Live.
  
  
• ERP RFP Template for Australian Businesses: What to Include.
  
  
• How to Calculate the Total Cost of ERP Ownership in Australia.
  
  
• ERP and Australian Compliance: GST, BAS, STP, and TPAR.
  
  
• Accounting Process Maturity: The Hidden ERP Readiness Factor.
  
  
• How to Choose an ERP Implementation Partner in Australia.
  

​