ERP will run your business. It won't manage your spend

There's a moment in the life of a growing business when the finance systems that got you here visibly stop coping. Entities multiply, transaction volumes climb, and the month-end close that was once a day's work stretches across a week. This is usually the point where a business decides to make the leap to an ERP, and in Australia and New Zealand the answer is increasingly a platform like MYOB Acumatica, the Acumatica-based system MYOB positions, with a localised look and feel, above its small-business products for exactly this stage of growth.

Moving to a full ERP is a significant step up, and for the right business it's the correct one. A platform of that class brings the general ledger, payables and receivables, multi-entity finance, distribution, inventory, manufacturing, projects and compliance into a single system built to handle a scale that accounting packages were never designed for. None of what follows is an argument against it.

There's a false assumption that the leap to ERP covers everything - that once the new platform is live, all spend is handled. It's an understandable belief, because the ERP is now the financial heart of the business. It's also wrong, in a specific and expensive way.

ERPs are systems of record. Spend management is something else entirely.

ERPs are, by design, systems of record. They're very good at holding the authoritative version of what has happened: the posted transaction, the reconciled account, the closed period. What they were never built to do well is manage the messy, human, front-end process that happens before a transaction is clean enough to post. That process is spend management, and it sits upstream of the ledger.

Consider where money actually starts:

• An employee needs to buy something.
• A manager approves it, or should.
• A supplier sends an invoice that has to be matched, coded and authorised.
• A team needs a card with the right limit.
• A purchase order should exist before the commitment, not be reconstructed after it.

All of this happens at the edges of the organisation, in the hands of people who aren't accountants and never will be. They need best-of-breed tools built for their process, so the data is clean before it ever reaches the ERP. This is precisely where ERPs are weakest. Not through any failing, but because capturing spend at the front line is a fundamentally different job from recording it in the ledger.

The gap most businesses only notice after go-live

The ERP is running and finance has its system of record, yet employees are still emailing approvals, invoices are still being keyed in by hand, expense claims are still arriving as photos of receipts, and card spend is still reconciled after the event. The business has modernised its back office while leaving its front-of-house spend as manual as ever, and it's now feeding that error-prone data into a powerful and expensive system that is only ever as good as what it receives.

The business has modernised its back office while leaving its front-of-house spend as manual as ever.

The answer is to treat spend management as its own layer, sitting outside the ERP but fully connected to it through tight integration. A dedicated spend layer captures each transaction where it starts, whether that's the request, the approval, the card, the invoice or the expense claim; applies policy and coding in that moment; and passes clean, approved, audit-ready data into the ERP to post.

What that looks like in practice

• Invoices matched to a purchase order and authorised before they hit payables
• Card and reimbursement claims arriving with receipts and coding already attached
• Every exported transaction carrying a link back to its source, so the supporting document and approval history are one click from the ledger entry

The controls that prevent loss live here too: approval limits and delegation of authority that decide who can commit spend, and duplicate-invoice and supplier bank-detail checks that catch error and fraud before payment, not at reconciliation.

ProSpend alongside MYOB Acumatica: a decade of integration

This is the role ProSpend plays alongside MYOB Acumatica, and it's one we've played for a long time. MYOB Acumatica, or MYOB Advanced as it was then, was ProSpend's first true API-driven ERP partnership, back in 2015, the year the platform launched in Australia and New Zealand. A decade on, that integration matters most for businesses running several branches or entities, where managing expenses, invoices, purchase orders and cards for every entity in one workflow is far cleaner than handling each separately and reconciling later.

The point sharpens as AI arrives in these platforms. MYOB and Acumatica, like their peers, are building AI into the ERP: contextual insights, natural-language queries, automated document handling. It's genuinely useful, and it raises the stakes on data quality, because AI applied to spend is only ever as reliable as the spend data it's given. If what reaches the ERP is inconsistent, miscoded or captured late, no amount of intelligence downstream will fix it.

The advice for any business planning an ERP move

Resist the assumption that the platform completes the picture. Map where spend actually begins, and be honest about how much of that process the ERP will really handle, and how much will quietly fall back to email, spreadsheets and manual keying. That gap is where the return on an expensive ERP investment leaks away.

An ERP will run a business, and handled well it will run it for years, but the spending that flows into it begins long before the ledger, in the hands of people who will never open the ERP. Manage that well, and the ERP finally gets the clean data it deserves.