The cost of the current state

It's easy to think staying with your existing system is the least expensive option. But you can’t ignore the invisible costs.

Manual work consumes employee time on both sides of cash flow. Delayed approvals and exceptions create friction around outgoing cash, while invoice, communication, and dispute delays slow the cash coming in

According to Ardent Partners, Best-in-Class AP organizations have 78% lower invoice processing costs and 82% faster processing times than other organizations. They also have a 59% lower invoice exception rate.

Processing cost is only one part. The harder costs to see are often buried in the work required to keep a fragmented process functioning.

Missing approvals, absent POs and invoices that cannot be matched cleanly all create exceptions someone has to investigate and resolve. Every duplicate supplier record or inconsistent coding decision increases the amount of checking required downstream.

They may not be a line item in your budget, but they are certainly part of what you’re paying. They show up as finance capacity consumed by rework, delays in closing, missed discount opportunities, avoidable exceptions and growing dependence on manual intervention as transaction volumes increase.

The same hidden cost appears in receivables. Hours may be spent creating customer communications and follow-ups, as well as spending as much time on low-dollar invoices as those that are high. Bottlenecks may form when a customer disputes an invoice or even has a question that needs resolving before payment is made. Even payment friction can cause challenges, if customers are not provided with convenient options to quickly submit payment. Each of these challenges can lead to late payments, bad debt, and customer frustration, which in turn can lead to churn, costing you even more money in the long term.

That is why the cheapest option on paper is not always the least expensive option in practice. A process that requires constant human effort to stay under control may avoid a technology investment while quietly consuming the capacity needed for higher-value finance work.

You need to stop thinking in terms of the cost of change and start looking at what the current process is costing in time, control, and missed opportunities. When those costs start getting increasingly closer, that is when you need to start rethinking your plan.

Rely on your ERP

Your ERP may already be considered the center of financial operations, handling invoice posting, payment, and reporting.

That makes extending the ERP a very appealing second path.

Extending those capabilities also has the practical advantage of fewer systems to integrate, maintain, and support. Your team already knows how to use it, and your organization has already invested in it.

The question is not whether your ERP has AP and AR capabilities. Most do. The question is whether those capabilities can provide everything you need without significant customization or workarounds.

Look beyond the modules

While an ERP may handle core accounting transactions extremely well, it is the handoff and coordination of the pieces around those areas that start to add to the complexity. You need to ask:

• Can purchases be initiated and approved without leaving finance to chase the process?

• Can commitments be seen before invoices arrive?

• Can PO, receiving and invoice information stay connected?

• Can it automate cash application and matching?

• Does it support advance credit and risk monitoring?

• Do you have a full view of what comes in and what goes out, at a point where you can take action?

If the answer is a clear “yes,” extending the ERP may be a real consideration. But if it is more of a “yes, but only after layers of customization, integrations and workarounds,” it’s time to start looking at what the trade-offs are going to be with this approach.

Configuration turns into customization quickly

The difference between turning on capabilities your ERP was designed to support and rebuilding it around what you need it to can be huge.

You can reconfigure a process to work within the product you already own, adjusting approval thresholds, enabling modules, or changing workflow rules.

When you start to need custom code, scripts, middleware, new integrations and extensions, you have very quickly made the swing to customization.

And customization adds up, quickly and expensively.

Panorama Consulting Group’s 2026 ERP research found that more than a quarter of organizations exceeded their ERP project budgets, with additional technology needs cited as the leading cause. Panorama says those needs often emerge when organizations discover fit gaps and respond with additional technology, expanded scope or custom builds.

The issue is not whether you can retrofit the ERP to support additional requirements. It is how much time, money and effort are going into building a patchworked system.

Watch the workaround layer

A custom workflow here, a spreadsheet there might all be manageable on their own, but when you add them all up, you run right back into the chaos you are looking to avoid.

Approvals happen in email. Purchase information lives in the ERP. Finance keeps a spreadsheet to track exceptions and late payments. Your team pulls data from multiple places to understand what has already been already committed, what is owed, and what is late.

They all work on their own and get the job done but only because people keep stitching it together.

And integrations are not all the same. A connection may be a supported connector, a custom interface, or something the organization itself has to maintain. The cost and burden of ERP integration can depend heavily on how those connections are built and supported.

The bigger patchwork you create, the easier it is for one string to pull and unravel everything, taking you data, controls and context from purchase through payment with it.

Customization has a long tail

The initial build is only part of the cost.

What happens when one system is upgraded…integrations need maintenance…new business requirements trigger another round of development and testing?

Extending an ERP can look straightforward on paper, but large ERP initiatives are notoriously difficult to get right. Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business-case goals, with as many as 25% failing catastrophically. Gartner also reports that 75% of ERP strategies are not strongly aligned with overall business strategy.

That doesn’t automatically make the ERP the wrong foundation. It means every new requirement needs to be tested against whether the ERP can support it cleanly, or whether the organization is starting to build around the system rather than use it.

The ERP may still be doing its job

None of this takes away from the value of your ERP. It does what it is designed to do well, serving as the financial system of record.

The difficulty comes when you start expecting it to stretch its capabilities. Your business needs may have evolved beyond the existing implementation’s support. Can your ERP support the workflows surrounding both incoming and outgoing cash without layers of customization and additional technology? Can it keep the information needed for purchasing, approvals, invoicing, collections, payments and cash application connected well enough for finance to act on it?

Gartner notes that no single ERP suite vendor delivers best-in-class capabilities in every area and recommends looking beyond ERP alone for automation and business-process orchestration where needed.

Closing your organization’s gaps with native functionality or straightforward configuration changes makes the ERP a perfectly logical choice.

But when each gap requires another custom build, integration or manual bridge, the situation can drastically change. You are no longer asking whether the ERP can do it, you are adding complexity to force it to work the way you want.