A Practical Change Management Guide for Finance and Operations Workflows

Summary: Why do new finance and operations workflows get quietly abandoned a few months after launch? This blog explores how workarounds creep back in, why fixing the process comes before announcing it, and how to time go-live around your close calendar. Learn how to brief the executive sponsor, approvers, managers, and daily users at the right moments, answer the four most common objections, and use 30-, 60-, and 90-day check-ins to make the change stick.

Two of the top three challenges CFOs name with AI and automation are about people, not software: 64% cite a lack of skills and 44% cite employee adoption. The software usually does its job, and the trouble tends to start a few months after launch, when approvals drift back to email and a tracking spreadsheet returns to someone’s desktop.

Q4 is a smart moment to get ahead of that pattern. Budgets are settling, and teams across finance and operations are deciding which processes to change before the new year. In Deloitte’s Q4 2025 CFO Signals survey of large North American companies, 49% of CFOs named automating processes to free up employees for higher-value work as their top finance talent priority.

Here’s a practical framework for the human side of a rollout, covering what to say, when to say it, and who needs to hear it, so your new workflow is still running long after launch week.

Why Good Workflows Get Quietly Abandoned

Nobody announces that a rollout has failed. A notification gets buried, a department head emails the controller to keep things moving, and the controller replies “approved” because the invoice is due Friday. AP keys the decision into the system by hand, and now two processes are running side by side.

Each of those moments makes sense on its own. People protect deadlines, and a familiar path feels safer than an unfamiliar one, especially when nobody explained what the new path was for. The trouble is that workarounds creep back in one reasonable exception at a time, until the visibility and control the project promised are gone.

Picture the controller’s view three months in. The dashboard shows half the invoices moving through the workflow while the rest sit in inboxes nobody can search. Then an auditor asks who approved a $14,000 equipment invoice, and the answer lives in a reply buried in someone’s sent folder.

A workflow has to earn its place. It does that by being the easiest path to a decision, and people choose it when they understand why it exists and know who to ask when something looks off. That means the work starts well before the launch email goes out.

Fix the Process Before You Announce It

Start by looking at how the work actually flows today, including the side doors, and decide what should be true every time.

That order matters more than it seems. In McKinsey’s latest global survey on AI, nearly three-quarters of AI high performers (companies attributing 5% or more of EBIT to AI) said they had fundamentally redesigned workflows, compared with about a quarter of everyone else. Automating a seven-step approval chain without questioning it just gets you seven steps that move faster.

Sit down with the people who run the process, ask which steps exist for a reason and which exist only because nobody ever removed them, and trace the finance-to-operations handoffs where the process usually breaks down.

The side doors are where the real process lives, so go looking for them on purpose. Ask who approves invoices by email, who keeps a personal tracking spreadsheet, which vendors send invoices straight to a department head instead of the AP inbox, and who codes certain invoices from memory. Each answer points to a rule nobody wrote down, and the new workflow needs to either build that rule in or retire it deliberately.

This is the heart of business process management. Here you decide the rules the workflow will enforce: approval routing by amount and department, spending thresholds, forms that collect the right details up front, and who owns exceptions like a missing PO or a price mismatch.

Pick a Go-Live Date Your Close Calendar Can Handle

A launch in the last week of the month lands on top of close, and approvers will route around anything that slows them down while the controller is chasing accruals. Year-end adds holiday vacations, which leave approval queues unattended, and 1099 prep is waiting right behind them in January.

That makes Q4 a strong time to do the groundwork. Map the process, set the approval rules, and pilot with one department or one location that has predictable invoices, such as recurring facilities or utility bills. Then schedule the full go-live once year-end close and 1099s are behind you, typically February for calendar-year companies, and ahead of audit fieldwork if you can. Set up delegation for anyone who will be out.

Talk to the Right People at the Right Time

A rollout involves four audiences: the executive sponsor, approvers, their managers, and daily users. The sponsor comes in at kickoff, approvers and managers two to three weeks before go-live, daily users the week before, and everyone gets a check-in at 30, 60, and 90 days after.

Start with the executive sponsor

The first conversation covers the business reason for the change, the one or two numbers that will show it’s working, and the decisions the sponsor owns along the way, such as approval limits by role and who covers when a limit holder is out. It belongs at the very beginning, before configuration starts. Capture today’s baseline before anything changes, including invoice cycle time, the share of approvals that happen outside the system, and how many days close takes, because you’ll want those numbers to compare against later.

A sponsor who can explain why this matters now gives every later conversation its authority.

Brief approvers and managers early

Approvers in operations often carry the most change, since the new workflow changes their routine before it saves them time. Department heads, service and parts managers, and location managers all fall in this group. Give them a preview two to three weeks before go-live, using real invoices from their own department. Show them what lands in their queue, how delegation covers vacations, and what happens when a request sits too long. Someone who approves six invoices a month should be able to finish each one on a single screen, and that goal belongs in the design from the start.

Managers deserve extra attention here. In Gallup’s workplace research on AI, employees who strongly agree their manager actively supports their team’s AI use are 1.7 times as likely to use AI a few times a week or more. A ten-minute huddle led by someone’s own manager will outperform a company-wide email almost every time.

Walk daily users through real work

AP specialists, purchasing teams, and requesters need hands-on time in the week before launch. Run short sessions with real documents instead of sample data, because people trust what they recognize. Walk through the invoices that cause the most trouble, such as a missing PO, a price that doesn’t match, a possible duplicate, or a credit memo, and show who owns each exception and how quickly it should be resolved.

Name a go-to person on each team who has already tried the workflow and can answer quick questions at their desk, which keeps small questions from turning into workarounds.

Close the loop after launch

The 30-, 60-, and 90-day check-ins are where a workflow sticks or slips, and the first month-end close is the real test. Share results against the baseline you captured, such as approval cycle time, the share of invoices approved outside the workflow, and the number of exceptions still open after a week. Review exceptions weekly for the first month, fix what feels clunky, and tell people which changes came from their feedback.

Keeping approvals on the record inside the workflow also makes the next audit conversation calmer, which gives everyone one more reason to keep using it.

Answer the Pushback Before It Arrives

Some pushback will show up no matter how well you brief people, so have answers ready. These four come up most often.

• “Email is faster.” It feels faster to the approver and slower to everyone else, since the approval lives in a reply that never gets attached to the invoice. Routing sends each invoice to the right approver with automatic reminders, and cycle time data settles the debate quickly.
• “I’ll lose visibility.” Controllers and AP leads raise this one most. Every step carries a status and a timestamp, so anyone can see which invoices are waiting, and on whom, without asking around.
• “This threatens my job.” Say plainly that the work shifts from keying and chasing toward exceptions, vendor conversations, and analysis. Teams hear that more credibly from their own leaders than from a vendor.
• “Our vendors won’t change.” Tell vendors early where invoices should go, and have the team redirect strays to a single address for the first few weeks. Vendor habits change too, just more slowly.

Write these answers down, rehearse them with managers before launch, and add to the list as real questions arrive. They land best when the technology backs them up.

Give the Change Plan Something Solid to Stand On

Change management works best when the technology makes the right behavior the easy one. Approval routing applies the same rules to every invoice, so a department head in one location gets the same experience as a peer across the country. Approval limits and separation of duties become embedded controls in the routing instead of depending on anyone’s memory. Forms capture the right information at the start, which cuts the back-and-forth that frustrates requesters, and an audit trail builds itself as work moves.

Accounts payable is often the best place to prove it, because the volume makes results visible fast. Intelligent document capture pulls invoice data in, workflows route it for approval by rules, and payments follow the approvals with a clear record behind each one.

Fix the Process, Time the Message, Share the Results

Boiled down, the plan comes to three habits. Fix the process before you announce it, brief each audience at the moment they need it, and keep sharing results long after go-live.

Pick one workflow, bring the right voices in early, and you’ll head into the new year with a lot less to untangle. For help choosing that first workflow and capturing the baselines that make your results believable, Business Process Automation: A Complete Guide walks through each step. The teams that thrive treat a rollout as a people project first, with the technology in a supporting role. At onPhase, we’ve spent more than 25 years helping finance and operations teams build that supporting role.