AP Automation Business Case: How to Build One Your CFO Will Sign

Why listen to us: ECIT Digital processes supplier invoices for finance teams every day. Our AI reads every invoice, our people check what the AI is unsure about, and we guarantee 99.8% accuracy on the data we deliver.

Last spring I wrote a four-tab business case to convince my partner we needed a $600 espresso machine. It had a cost-per-cup model and a slide called "Risks" [the risk was me, holding a spreadsheet at breakfast].

My partner read it, asked one question, and found the hole in about nine seconds. Your CFO will do the same to your AP automation business case, only faster and with less affection. This guide shows you how to build one that survives the question [the espresso machine will be back, it always is].

Building the case is part of our accounts payable automation best practices.

The AP automation business case on one page

The Association for Financial Professionals puts it plainly: "Winning senior managers' buy-in typically requires a solid business case or a clear ROI." Here are the five answers it needs, for the reader whose budget meeting is tomorrow [it is always tomorrow].

Step 1: Measure what your AP process costs today

Every business case starts with the number nobody has: what one invoice costs you today. Without it, your ROI is a vibe with a percentage sign [my espresso case had a vibe, it did not go well].

Cost per invoice is total AP cost (people, systems, overhead and outside fees) divided by invoices processed in the same period. Our guide to accounts payable metrics walks through the calculation, plus cycle time and exception rate, which you will want next to it [they come as a set, like socks].

For a sense check, Ardent Partners' State of ePayables 2025 puts the average at $9.84 per invoice and best-in-class teams at $2.65. APQC, the benchmarking research group, found top-quartile organizations spend $2.07 or less per invoice, against $10 or more for the bottom quarter.

Use those to check your number is believable, never in place of it. A CFO who sees "industry average" where your own number should be will smell it from across the room [CFOs have a very good nose for borrowed numbers].

Step 2: Count the benefits of AP automation

The benefits of AP automation fall into three buckets: time saved, money recovered and errors avoided. Then there is a fourth bucket, risk, which matters a lot and does not fit neatly in a spreadsheet [neither did my espresso machine's "joy" column].

Hours saved is usually the biggest number, and the one most people get wrong. Count every person who touches an invoice, including the managers who approve them, not just the AP clerk [the clerk is not the only one losing a Tuesday to invoices]. Include supplier calls too: Ardent found AP staff spend 21.9% of their time dealing with suppliers, much of it caused by exceptions.

Early payment discounts are the sneaky big one. The OpenStax finance textbook works through 2/10 net 30 terms and concludes "The annual cost to NAI of not taking advantage of the discount for quick payment is 36.73 percent." You can only take a discount if the invoice is approved within the window, so a faster cycle is literally money.

Late fees deserve a closer look if you buy from UK suppliers. They can charge "8% plus the Bank of England base rate" in interest, plus a fixed sum per late invoice [per invoice, not per supplier, which is where it hurts].

Duplicates are the quiet leak. APQC data shows even top performers report 0.8% of annual disbursements as duplicate or erroneous payments, and bottom performers 2%. Count only what you can show from your own records, because the CFO will ask where it came from [yes, again].

Fraud is the one to describe rather than price. The AFP 2026 Payments Fraud and Control Survey found 76% of US organizations experienced attempted or actual payments fraud in 2025. Put that in the risks section, with the controls automation adds, and leave it out of the ROI math [pricing a fraud you have not had yet is how spreadsheets get fan fiction].

Step 3: Add up what AP automation costs

AP automation cost is more than the price on the proposal. My espresso case forgot the beans, the milk jug and the descaler, and my partner found all three [the descaler alone cost more than my pride].

The AFP's guide to automating AP tells buyers to weigh "the total cost of ownership as well as the cost of the initial set-up, licensing, maintenance and potential upgrades". The pricing model matters as much as the price. License-based tools charge for seats whether invoices arrive or not, while transaction-based pricing scales with the volume you actually process [like paying per cup instead of buying the café].

Ask every provider for the same breakdown, then compare them line by line. Our comparison of the best AP automation software covers how the main options charge.

Step 4: Work out AP automation ROI and payback

Now the math, which is simpler than vendor slides make it look. Two formulas, both on one screen [I promise, no tab four].

Do not skip payback. In Graham and Harvey's survey of 392 CFOs, 56.7% said they always or almost always use the payback period, and smaller firms lean on it most.

Here is a worked calculation for a fictional company processing 1,250 invoices a month, the same one from our metrics guide. Its people spend $86,400 a year on invoices today.

Then run it three times. A single number looks like a sales pitch, while three numbers look like someone thought about it [my partner trusted the espresso case more once it had a "worst case" column].

Notice the cautious case loses a little money in year one. Show it anyway, because a business case with no downside is the first thing a CFO stops believing [and the last thing my partner believed].

AP automation ROI calculators: how to use one without being fooled

Every AP vendor has an ROI calculator, and every one of them somehow recommends that vendor [what are the odds]. They are still useful, as long as you check what is under the hood.

• It asks for your numbers. Invoice volume, hours and cost per invoice, not just company size.
• It shows its assumptions. If it assumes 80% of hours vanish, you should be able to see that and change it.
• It counts the cost. A calculator that only shows savings is a brochure with a slider.
• It gives a range. One precise number to the dollar is a warning sign, not a feature.

Use a calculator to get a first estimate in minutes, then rebuild the result in your own spreadsheet with your own baseline. That spreadsheet is what goes to the CFO, not a screenshot [ours is linked at the end, and yes, I see the irony].

The objections your CFO will raise

Only 39% of AP teams in Ardent's 2025 survey said their CFO approves AP's plan, so expect questions. They are usually the same five, and preparing the answers makes the meeting shorter [mine with my partner did not, but I had not read this guide].

The "why now" answer is your strongest card. Divide the expected net yearly benefit by 12 and you have the monthly cost of doing nothing [in our fictional company, $3,425 a month, or roughly six espresso machines].

A one-page AP automation business case template

CFOs read page one. Some of them read page two, and nobody has ever read page nine [I checked with my partner, who stopped at tab one].

Put the detailed spreadsheet in an appendix for the one person who asks. There is always one, and they always find the descaler.

What we see in the field

We usually meet AP teams just after the business case was approved, or just after it was sent back. Here is what the approved ones have in common [spoiler: none of them mention espresso].

• They price the whole process, not the clerk. Approvers' and controllers' hours are part of the real cost per invoice, and the easiest part to miss.
• They treat data quality as a cost line. A misread total becomes an exception, a slower cycle, a missed discount and sometimes a duplicate. That is why we guarantee 99.8% accuracy on the data we deliver.
• They pick a pricing model that fits their volume. Our clients pay per document, with no expensive license, and extra fields or features are priced on top.
• They keep the team out of the documents. Clients never touch the invoice: our AI reads it, our team checks what the AI is unsure about, and clean data lands in their ERP or AP tool.

"Construction invoices are complex and highly variable and ECIT provided a flexible and extensible data extraction model that worked wonderfully." - Terence Pua, CEO, Hinges AI

Want your first numbers before you open a spreadsheet? Run the free invoice health check: it scores your invoice process in about 3 minutes and estimates what you could save, based on your own numbers.

As for the espresso machine: version two of the business case had a cautious scenario, a full cost list and one page instead of four tabs. My partner signed it in a minute [the descaler is now in the budget, line three]. Build yours the same way, and your CFO might even sign it before the coffee gets cold.