Our pre sales team hears the same thing in almost every industry. A manufacturer says invoices are a major pain, but supply chain pressures mean there may be no budget. A university knows accounts payable is a problem, but expects the chief financial officer to say no. A financial services firm loves the product, but cannot show the return to its business head.
The pain is rarely in doubt. What is missing is a business case that turns that pain into numbers leadership will fund. These five steps, refreshed for 2026, take you from a list of complaints to an approved project.
Step 1: measure what manual processing really costs
Begin with your own numbers. Leadership trusts figures from its own ledgers more than any vendor claim. Gather answers to these questions over a representative period, ideally a few months:
- What does it cost finance and accounts payable to process one invoice?
- How many invoices do you process each month, and through which channels?
- How long does an invoice take from receipt to approval, and from approval to payment?
- How much staff time goes on exceptions, supplier queries and corrections?
- How many early payment discounts did you miss, and what late fees did you pay?
- How many duplicate or incorrect payments were recovered, or not?
If you do not track some of these today, start now. The five accounts payable KPIs give you formulas for the core measures.
Step 2: compare with industry benchmarks
Next, find out how organizations of similar size and industry perform. Research firms and industry bodies publish benchmarks for cost per invoice, cycle time and exception rates. Use only sources you can cite, and note the year, since benchmarks age quickly.
Benchmarking does two jobs. It shows leadership where you stand against peers, and it gives the project measurable goals that every stakeholder can sign up to. A quantified gap between your current state and a credible benchmark is often the most persuasive line in the whole case.
Step 3: define the benefits and core requirements
Your team already uses a set of tools. Before proposing a change, agree internally what the new solution must do and how it fits what exists. Questions to settle early include:
| Question | Why it matters |
|---|---|
| How much training will users and approvers need? | Adoption drives every other benefit |
| Does it integrate with our enterprise resource planning and other systems? | Integration is often the largest hidden cost |
| Cloud, on a platform we already run, or standalone? | Affects security review, cost and timeline |
| Can it become the single source of truth for invoices? | Partial coverage keeps the old problems alive |
| Can it apply our validation rules and check invoices against contracts? | Catches price drift and fraud before payment |
If your company already runs ServiceNow, a native app can avoid a separate security review and reuse existing roles and approvals. See Invoiceflow.
Step 4: show the return and the need to act now
With costs, benchmarks and requirements in hand, build the return on investment and add urgency. Leaders will ask three questions, so answer them in the case itself.
Why now, not later?
Quantify the cost of waiting: missed early payment discounts, late fees, payment terms you cannot standardize and exposure to invoice fraud, each month the current process continues.
Why fix something that works?
Set your current performance against the benchmarks. Where there is a gap, show the savings automation can capture and what the team could do with the time it frees.
Will it grow with us?
Show how the solution scales, from capturing and matching invoices today to contract compliance checks, fraud detection and supplier self service later, so leaders see it fits the roadmap.
Step 5: align stakeholders and win buy-in
A strong case with weak support rarely gets funded. Your stakeholders typically include IT, finance leadership, procurement, business approvers and your own manager. You need a champion in each group.
- Involve each stakeholder early, during research and requirements, not at the end
- Show each one what they gain, for example fewer approval chases for business users
- Address IT concerns on security, integration and support upfront
- Agree the success measures together, so everyone owns the result
- Present both the numbers and the qualitative benefits when you ask for funding
Funding is the critical step, so spell out both the quantitative and qualitative gains: lower cost, faster cycle time, stronger controls, better supplier relationships and a team freed for analysis. For a view of the chief financial officer's priorities, read the future of finance and the chief financial officer's role.
What mistakes sink a business case?
Three mistakes come up again and again. The first is relying on vendor figures instead of your own measured costs, which leadership rightly discounts. The second is promising savings without saying how they will be tracked after go live. The third is leaving IT until the end, so security and integration questions surface late and stall approval. Avoid all three by measuring first, agreeing the success measures with finance upfront and bringing IT into requirements from the start.
The bottom line
A fundable business case combines your own measured costs, credible benchmarks, clear requirements, a reason to act now and champions across the business. Build it in that order, and the conversation moves from whether to automate accounts payable to how fast.