Spend management is not a volume problem

Here's how the conversation usually starts. A finance leader tells me they process thousands of invoices a month, or they've got hundreds of expense claims coming in, or the card program has sprawled across every department. Then comes the line: "So we probably need a system."

And the line isn't wrong. But it's asking the wrong question.

You're not overwhelmed by invoices. You're missing control.

Volume is measurable, and that makes it feel like the real problem. You can count invoices. You can pull a report on expense claims. You can see how many card transactions landed last month without a receipt. These numbers feel like ROI math, and they make a compelling slide in a business case.

But volume rarely explains why the work is painful. Two finance teams can both process thousands of invoices a month. One of them has clean data hitting the ERP on time, approvals happening before payment, and a clear audit trail for every GST claim. The other is stuck in rework loops, chasing approvers who bypassed policy, and reconciling exceptions at month-end. Same volume. Completely different outcome.

Spend management is not a volume problem. The problem is what the volume hides: late visibility, weak controls, duplicate invoice risk, missing tax evidence, and approval workflows that exist on paper but not in practice.

Name the catalyst, and everything else follows

If there's one thing worth taking from this, it's the idea of naming your catalyst before you evaluate any software.

A catalyst is the specific outcome gap your workflow is failing to close. It's not a document count. It's something like: "We have no enforceable delegated authority framework, so approvals are inconsistent and untraceable." Or: "We're capturing GST/FBT evidence after the fact, which means our audit trail is always incomplete." Or: "Supplier invoices are being paid before anyone confirms a PO was raised."

When you can name it that specifically, everything downstream gets easier. Your routing rules, approval tiers, matching controls, export logic, and reporting all get designed around a real outcome rather than a vague efficiency target. More practically, that specificity is what gives you change management momentum. People don't change workflows because software is available. They change because there's a named problem with a named owner and a named consequence if it doesn't get fixed.

Why volume feels like the reason

Volume is an easy proxy because it looks like ROI. If each invoice takes 30+ minutes to receive, key, code, approve, and reconcile manually (ProSpend's own Xero integration page documents this), then processing 500 invoices a month looks like 250 hours of recoverable time. That's a compelling number.

The problem is that it treats all 500 invoices as equal, assumes the current process is the right one to accelerate, and ignores the failure modes embedded in that process. If your approval workflow has gaps, automating it faster means your control failures happen faster too. Volume doesn't give you a north star. It gives you more of whatever you already have, including the problems.

What projects that actually go the distance look like

The spend management projects that stick share a pattern. Stakeholders align on a specific outcome before selecting tools. Policies and approval tiers get redesigned, not just digitized. Data quality is addressed before spend reaches the ERP, not patched afterward. And someone owns the adoption problem explicitly, separate from the technology rollout.

The tech is genuinely the easy part. Connecting expenses, cards, and supplier invoices to Xero or MYOB Acumatica takes weeks, not months. What takes time is getting a team of 40 managers to submit expense claims within 48 hours, or getting procurement to raise purchase orders before committing spend, or getting accounts payable to reject invoices that don't match a PO. Those are behaviour changes, and behaviour changes need a reason to exist.

That reason is your catalyst.

Find the failure point, then map it to the lifecycle

A practical way to find your catalyst: trace where decisions are happening informally, where evidence isn't being captured, and where controls are unenforced. Most finance teams can identify two or three of these without much effort. The recurring ones tend to cluster around:

• Expense and card intake: receipts missing, policy applied inconsistently, no real-time visibility into budget impact
• Invoice capture and AP: manual keying, no duplicate detection, coding errors that compound at month-end
• Approvals: delegated authority rules exist but aren't enforced in the workflow
• Export and reconciliation: data that reaches Xero or MYOB Acumatica is already wrong, so the ERP just becomes a downstream error store

Each failure point maps to a stage in the spend lifecycle. Your catalyst is the one that, if fixed, changes the quality of everything downstream.

Integrations matter, but they're not the strategy

The objection worth addressing honestly: "Surely the integration with Xero or MYOB Acumatica is what makes this work?" Yes, and no.

Xero integration for spend management is table stakes now. Tools across the market, including Pleo, Payhawk, and others, all claim to sync corporate card transactions, receipts, invoices, and expenses to Xero. Payhawk describes its integration as syncing everything "in real-time to eliminate manual data entry." Pleo supports exporting card expenses, invoices, out-of-pocket claims, and reimbursements. The sync is real and it matters.

But the sync doesn't create policy discipline. It doesn't enforce PO matching before payment. It doesn't flag duplicate invoices before they're approved. It doesn't capture GST/FBT evidence at the point of spend. Integration moves data between systems; it doesn't govern the decisions that produced that data.

This is where a platform designed around the full spend lifecycle makes a practical difference. ProSpend connects expenses, supplier invoices, purchase orders, virtual cards, budgets, and approval workflows in one place, with controls like duplicate detection, supplier bank verification, delegated authority enforcement, and audit-ready records built into the process before anything reaches the ERP. The MYOB Acumatica integration, for example, is explicitly positioned to "automate expenses, invoice approvals, purchase orders and card spend before they reach your ERP" (ProSpend). That "before" is doing a lot of work. Earlier visibility before ERP is the outcome. The integration is how you get it there cleanly.

For ANZ finance teams specifically, where GST evidence and FBT compliance aren't optional, having audit-ready spend records isn't a nice-to-have. It's often the catalyst itself.

Stop treating symptoms as strategy

If you're about to start a spend management evaluation, pause the "we need a system" conversation for a moment. Ask instead: what specific outcome is currently failing, and what would it look like if it worked?

Name the control gap. Name the approval failure. Name the compliance risk. Build the program around that outcome, and use the technology, including Xero or MYOB Acumatica integration, to support it.

Without a catalyst, you'll buy tools and still drown in exceptions. With one, even a modest implementation can change how finance operates. The volume will still be there. But it'll stop hiding the real problem.