ERP Implementation Consultant, Australia

Where Australian ERP implementations usually stumble

Australian ERP projects run into the same broad risks as projects anywhere, but a handful of local patterns turn up repeatedly:

• GST codes that do not map to the BAS. Tax codes are configured early, but nobody tests whether they feed the right BAS labels until the first BAS period in the new system, when the accountant finds differences.
• Payroll boundaries left vague. The ERP and a separate STP-enabled payroll product are both in scope, but who owns employee records, leave liabilities and the wage journal is never written down.
• Bank files assumed to work. The ABA export is not tested with each bank until the first live payment run.
• MYOB or Xero structures copied as they are. Jobs, categories and tracking codes built up over years are migrated unchanged, so reporting problems move to the new system.
• Distance underestimated. Stocktakes, training and go-live support are planned as though every site were in one city, then struggle across states and time zones.
• Variations approved casually. Small requests agreed on calls add up to a blown budget.

None of these needs a dramatic fix. Each needs an owner on the client side, a plan and a weekly check. If several of these are already happening on your project, fixing a failed ERP implementation sets out the warning signs and the reset steps, and ERP recovery describes the service.

Keeping the partner accountable without slowing the build

Australian partners are often based in a different city or state from the business they serve, and their consultants move between several clients at once. That is normal, but it means the client needs its own rhythm for decisions, or the project waits on questions nobody has been asked to answer.

I set up that rhythm early. Each week there is a short session with the partner's lead where I bring the decisions your process owners have made and collect the questions they need answered next. Every agreed point goes into a log with the reason and the approver, so nobody has to rely on memory when the same topic resurfaces months later. When the partner raises a variation, I compare it with the signed requirements and the design documents. If it fills a gap the partner should have covered, I say so. If it is genuinely new, your sponsor sees the estimate, the effect on the schedule and the business case before deciding.

Design reviews happen before anything is configured. For Australian finance teams, that means walking through GST codes and the BAS labels they feed, tracking dimensions, and how the wage journal from payroll will be mapped. Operations leads review replenishment between warehouses, trade job costing and approval limits.

I also watch partner resourcing. If a named consultant is replaced mid-project, I check that the handover is documented and that the new person has read the decision log. Configuration stays with the partner throughout; acceptance stays with you. The general model is described under ERP implementation.

Data migration from MYOB, Xero and other Australian systems

Australian migrations often start from MYOB AccountRight or MYOB Business, Xero, QuickBooks or Reckon, often with separate inventory, job or CRM apps alongside. The partner's import tools help, but only after someone who understands the data has cleaned and mapped it.

Finance first decides how much history to bring. A common pattern is balances plus open transactions, with the old MYOB or Xero file kept read-only for lookups; some businesses also want prior-year detail for trend reports. Agree the choice with your accountant, who will also know how long the old records must stay accessible.

A trial import counts as passed only after it agrees with the source, not merely because it ran:

• Ledger balances per company on the cutover date.
• Open debtors and creditors by document, with GST on each invoice preserved.
• Stock quantities and values by site, reconciled to the balance sheet.
• Supplier records with ABN, bank details for ABA payments and payment terms.
• Customer records with credit limits, terms and any Peppol identifiers.
• Fixed assets, if depreciation moves into the ERP.

Where MYOB jobs or categories, or Xero tracking categories, carried meaning that the new system handles differently, I map old values to new dimensions with finance so comparisons still work. More detail sits on ERP data migration and the migration checklist.

Testing and timing an Australian go-live

UAT must prove the transactions that would hurt most if they failed. Business users run scripts built from your real data: sales and purchases with different GST treatments, a test BAS reconciled to the ledger, an ABA payment file accepted by each bank, the wage journal posted by job or department, a Peppol invoice where customers use it, an interstate stock transfer and a complete month-end close.

The cutover date then needs to fit the Australian reporting calendar:

• BAS periods. Switching at the start of a BAS period avoids preparing one statement from two systems. Where the timing cannot line up, your accountant or BAS agent should sign off the method for combining figures.
• End of financial year. Starting the new year in the new system keeps comparatives simple, but the end of the financial year is also when finance staff are busiest with year-end work and payroll finalization.
• Payroll. If payroll stays in its own product, only the journal and mappings change. If payroll moves mid-year, year-to-date figures and STP continuity come into scope, so involve your payroll provider and advisor early.
• Stocktakes across sites. Opening stock should come from counts taken as close to cutover as possible at every location, which needs planning across states and time zones.

The final yes or no depends on process owners signing UAT, balances agreeing, staff being ready and a fallback being available. See UAT and go-live support for the detail.

Hypercare and remote support across Australian states

The first weeks after go-live are when users decide whether to trust the system or return to their spreadsheets. In hypercare I hold a daily issue review with partner consultants and key users from each site. Each item is labeled as a defect, a training need or a later-phase request, given an owner and a target, and summarized for the sponsor at the end of the day.

A pair of checkpoints tells you whether the system has settled. The first month-end close shows whether bank, stock, debtors and creditors reconcile across all sites. The first BAS prepared from the new ledger shows whether GST design holds up with real volumes once your accountant or BAS agent reviews it. Problems from either go into a stabilization backlog that is estimated and scheduled, not patched in a hurry.

Everything is delivered remotely. Daily calls fall inside your business hours, which overlap more easily with Perth and need some planning for the eastern states, particularly while daylight saving changes the gap. Recorded walkthroughs help staff in regional sites, and a visit around launch week can be booked by arrangement.

If the platform or partner is not yet chosen, the Australian ERP selection page covers that stage. For more context, see ERP consulting in Australia, the freelance options and the Australia hub.