Finance teams have more tools available to them than at any point in history. And yet, according to Ottimate research, 48% of finance leaders report little to no cost savings from their current AP automation tools. 

It’s not a technology problem. The problem is everything that happens after the contract is signed. It may have been a handoff to a team that wasn’t consulted, a training session that happened once with no follow-up, or a manager who never stopped approving invoices by email because no one made the new way easier than the old way.

Change management is the unglamorous work that determines whether a technology investment pays off. Here’s why it’s important for finance leaders to facilitate the process and how to best support their teams to maximize ROI.  

Why finance leaders should own change management

Change management is the process of planning, communicating, and supporting employees through transitions to new financial systems, tools, or workflows. To ensure the new technology delivers its intended ROI, AP teams must:

• Identify stakeholders
• Map current workflows
• Train users
• Track adoption milestones

Seems straightforward enough, but it’s where most rollouts fall apart.

An important distinction to make is the difference between technology implementation and change management. Implementation is configuring software. Change management is getting people to use it effectively. You can have flawless technical implementation and still fail the business if the AP team routes around the new system and reverts to email chains and manual processes because that’s what they’re comfortable doing.

Finance leaders need to own change management. You understand the workflow, the team dynamics, and what’s at stake. You know which team member has the institutional knowledge everyone relies on, which manager will push back the hardest, and what a late payment actually costs in terms of vendor relationships.

AP automation also touches multiple departments. Finance, procurement, operations, and even the C-suite all have a stake in how invoices move. That cross-functional reach makes alignment essential. (If you’re still building your foundation on what AP automation does, Ottimate’s AP Automation Guide covers the technology side in depth.)

Why finance technology rollouts fail

Most (89%) mid-market finance teams use partial automation, mixing manual and automated processes in ways that fragment workflows, create gaps, and often produce more work than a fully manual process would. For many teams, this partial adoption is costing them the savings they were promised. 

For more context on how this affects outcomes across the industry, see AP automation stats finance leaders should know.

The root causes behind failed rollouts tend to fall into one of the following patterns:

1. No stakeholder alignment before rollout. The finance leader and IT know the change is coming. The AP team finds out during go-live training. The result is resistance that could have been addressed weeks earlier with a 20-minute conversation.
2. No internal change champion. Someone needs to own adoption between kickoff and steady state. Without a designated internal owner who bridges leadership and end users, accountability diffuses and the rollout fizzles.
3. Treating training as a one-time event. A single training session before go-live doesn’t build competency. Workflows evolve, edge cases surface, and new team members join. Training needs to be ongoing rather than a box to check. 

There’s also a human factor that doesn’t show up in implementation timelines: inherent resistance. Employees aren’t trying to obstruct progress when they push back on a new system. They’re protecting workflows they built, roles they’ve defined around those workflows, and the comfort of familiarity in how they do things now. 

How to build a business case that gets buy-in

Before you can manage change, you have to create the conditions for it. That starts with a business case that speaks to what each stakeholder cares about.

What should a finance change management business case include?

A strong business case for AP automation should include:

• Current-state cost data: According to Ardent Partners, companies without best-in-class AP processes spend an average of $12.88 per manually processed invoice, with approval cycles averaging 17.4 days. What’s your volume? That math alone can anchor executive conversations.
• Risk exposure: Ottimate’s 2025 research found that four in 10 mid-market firms experienced invoice fraud or overpayment in the past year. That’s a number that gets attention in the boardroom.
• Workflow pain points your team already knows: Late payments, vendor complaints, month-end chaos, approval bottlenecks. Frame the change around problems people already feel.
• Outcome targets: What does success look like at 90 days? Name specific metrics like approval cycle time, exception rate, and on-time payment percentage.

Tailor the communication by audience. Executives need an ROI summary with clear numbers and clear risk. End users need a “what changes for you” brief that is honest about the transition period and focused on how the new processes will make their jobs easier.

A step-by-step change management framework for finance leaders

Use this as your checklist, adapting the steps to your organization’s pace. Don’t skip the ones that feel like overhead, as those can be the ones that save a rollout.

Step 1: Audit your current state

Before rolling anything out, document existing workflows, including where invoices enter, who touches them, where they stall, and where errors most often occur. This is useful for design training and compliance. For a structured lens on what to look for, check out our blog about potential compliance gaps hiding in your AP process.

Step 2: Appoint a change champion

Having someone in your corner to evangelize a new system goes a long way in getting the team excited (or at least less hesitant). Your change champion should be someone on the finance team who is respected by their peers, technically comfortable enough to troubleshoot basic issues, and willing to be the go-to person for questions during transition. 

Step 3: Map stakeholders and communicate early

Identify everyone the change affects (e.g., controllers, approving managers, procurement contacts, IT) and communicate the why before the how. Employees who understand the reason for a change and their role in it are more likely to adopt it. 

Step 4: Run a pilot before full rollout

Start with one location, one department, or one invoice type and actively collect feedback. Find where the friction is before you’ve scaled across the organization. Fix it, then expand.

Step 5: Design role-based training

Each member of the finance team will interact with the new system differently. One training session built for everyone teaches no one effectively. Build role-based training paths, keep them short and scenario-based, and schedule reinforcement sessions at 30 and 60 days.

Step 6: Celebrate early wins

Find the first metric that improves and make it visible. Share it in a team meeting or put it in a Slack channel. Early proof of success builds momentum and makes the transition feel less like a disruption and more like progress.

Step 7: Measure, iterate, and keep communicating

The work isn’t finished once the new workflow goes live. Set structured checkpoints at 30, 60, and 90 days and revisit training as processes evolve. Keep communicating outcomes, no matter how small they seem.

How to manage resistance when rolling out new finance technology

Acknowledge what people stand to lose when you implement new technology — before making the case for what they stand to gain. Change can be confusing and scary, so address concerns head-on instead of avoiding them.

How do you get the finance team buy-in for new AP software?

These are the most common objections, and how to respond:

“This will replace my job.” Reframe that honestly. AP automation eliminates tedious, repetitive tasks so the team can focus on the work that requires judgment, analysis, vendor relationships, and exception handling. These are all better use of their skills.

“Our current system works fine.” Bring data into the conversation. The hidden cost of “fine” can show up in invoice fraud exposure, slow approvals, payment delays, and end-of-month scrambles. 

“We don’t have time to learn a new system.” A phased rollout with role-based training reduces the time burden. Nobody learns a system in a single session, nor should they have to. Don’t expect everyone to absorb everything at once. Build training into the workflow in short, specific segments.

The finance leader’s role here is active support. Use the tool and reference its outputs in meetings. When you pull approval time data or exception reports in a leadership review, tell them where that data came from. 

To meaningfully reduce adoption friction, find an AP tool that doesn’t require a steep learning curve. Ottimate Copilot, for example, uses a conversational interface that lets AP teams ask questions and get answers in plain language; no training on query syntax or report navigation is required. 

How to measure change management success in finance

Adoption isn’t black and white; you’re somewhere on a curve and need to know where. 

Track these metrics at each milestone checkpoint:

• % of invoices processed through the new system (vs. manual workarounds or email routing)
• Time-to-approval (before vs. after, tracking by invoice type and department)
• Exception and error rate (declining errors signal both system performance and user confidence)
• User login frequency and workflow completion rates (are people actually using it, or logging in once and reverting?)
• Vendor payment on-time rate (the downstream signal that everything upstream is working)

The 30-day checkpoint is about technical stability: is the system working as configured?

The 60-day checkpoint is about workflow consistency; are people using it reliably?

The 90-day checkpoint is where you assess full adoption and identify optimization opportunities.

Change management is the ROI

Only 4% of mid-market finance leaders say they’ve fully automated AP from invoice to payment with no manual touchpoints. The gap between what technology can do and what teams actually adopt is a change-management problem, not a technology problem.

Finance leaders who spend time on the audit, appoint a champion, run the pilot, train by role, and measure adoption will see better outcomes.

Ottimate is built to support that process at every stage, from intelligent invoice capture that reduces the manual burden on your team to reporting that gives you visibility into adoption status.