Your pilot cut the time AP spends entering bills, but the department still has the same payroll. That can be a good result. It is just not a cash saving, and a business case that treats it as one will fall apart the first time the CFO asks which expense went away.
A defensible AP automation case has two separate numbers: the staff capacity the workflow returns, and the cash the company will actually stop spending. Build both from your own quote and your own measured bills.
Get quotes you can actually compare
Send each vendor the same invoice sample and ask for a written quote covering the same steps: capture, matching, approval, posting, and support. Give them your normal monthly volume and a peak month. Then check what each one counts as an invoice, because a repeated upload, a credit, and a posted bill can each count differently.
| Quote item | What to pin down |
|---|---|
| Subscription and usage | Included modules, entities, approvers, and invoice volume. How retries, credits, resubmitted documents, and overages are charged. |
| ERP scope | Supported versions, records, custom fields, and posting actions. Have the vendor demonstrate one exception in your workflow. |
| Setup and support | Who handles mapping, testing, training, and failed transactions. One-time charges separated from ongoing fees. |
| Rule maintenance | Who updates rules when a department reorganizes or a supplier changes its invoice format, and what that costs. |
| Payment and exit | Bank or transaction fees. What changes at renewal. How you export invoices and approval history if you leave. |
Get the demonstrated scope written into the quote. For a contractor, have the vendor show the job, commitment, and hold on a real bill. For a manufacturer, use a partial receipt or a price variance. ProcIndex, for reference, states connections to QuickBooks, NetSuite, and Sage Intacct; whichever vendor you evaluate, confirm the specific records and permissions your project needs.
Price the duplicate test
Feed the same invoice through the demo twice: once from the supplier and once forwarded by a department manager under a different filename. NetSuite’s Bill Capture documentation, for example, describes a duplicate warning on scanned bills after a bill with the same reference number has been created (Oracle’s Bill Capture prerequisites and duplicate detection). Then ask the pricing questions. Does the forwarded copy count as another bill? Does a failed attempt count again on retry? Put the answers in the quote.
Match each feature to something you can measure
| Feature on the quote | What to run | What to record |
|---|---|---|
| Invoice capture | A multi-page PDF with a credit line | Time to a correct draft, including corrections |
| Coding suggestions | A recurring bill with a changed department | Who checks the coding and whether it reaches the right account |
| PO matching | A bill for more than the warehouse received | Time to identify the discrepancy and get it to receiving |
| Approval routing | A bill whose usual approver is away | Time to reach someone with authority and enough evidence |
| Posting | A write that times out after submission | Time to confirm there is only one bill |
Price the features you will enable first. Price the rest separately and add them to the case once you have measured the work they address.
Measure the baseline the same way you will measure the pilot
Compare the same kinds of bills before and during the pilot. Count time from everyone who touches a bill, including receiving and approvers, not only AP. Keep time spent working separate from time a bill sits in a queue. If the tool saves time in AP but shifts review to the buyer, the buyer’s time goes in the case.
| Pilot result | What belongs in the budget |
|---|---|
| Less rekeying and fewer corrections | Hours returned to the team. Cash only if a specific cost is avoided. |
| Fewer bills waiting for approval | Shorter cycle time. Check whether payment dates or costs actually changed. |
| More eligible bills paid by the discount date | Incremental discounts actually taken, net of the cost of paying earlier |
| More support or exception work | Ongoing staff time and vendor services, with any new cash outlay |
Cost per completed bill
A vendor that charges per invoice read still charges for the invoice it sends back for manual entry. So measure cost against bills that actually finished. The FinOps Foundation’s unit economics guidance describes tying spend to a unit that reflects operational value (FinOps Foundation unit economics guidance). For AP, a good unit is a bill posted to the right entity and account with approval evidence attached.
| Cost | What to include |
|---|---|
| Vendor charges | Subscription, usage, and charges for repeated reads or retries |
| Review | Time checking fields, resolving uncertain matches, approving exceptions |
| Corrections | Rework after posting, reversals, reconciliation after failed writes |
| Operation | Rule maintenance, access review, support for changed document formats |
Add the attributable costs for the cohort and divide by transactions completed correctly. Keep incomplete transactions’ costs in the numerator.
Illustrative example. In a pilot month, vendor charges are $3,000. Review takes 60 hours, corrections 10 hours, and rule maintenance 5 hours, all at a loaded $40 an hour: $2,400 + $400 + $200 = $3,000 of staff time. Total cost is $6,000. The workflow attempted 1,600 bills and 1,500 posted correctly.
- Cost per attempted bill: $6,000 ÷ 1,600 = $3.75
- Cost per completed bill: $6,000 ÷ 1,500 = $4.00
- Completion rate: 1,500 ÷ 1,600 = 93.75 percent
The $3.75 figure flatters the tool. The 100 bills that did not complete still cost money and still need someone to finish them, so report completion rate alongside cost per completion. Run the same calculation on the baseline mix before comparing.
Cash payback and first-year ROI
| Input | What to include |
|---|---|
| One-time cost | Setup, integration, and training cash costs |
| Monthly operating cost | Subscription, support, and other new cash expenses |
| Monthly cash cost avoided | A cost you can name and remove: contracted processing, overtime, a temp, late fees |
| Staff time released | Measured hours the team can use elsewhere, reported separately |
The formulas:
- Monthly net cash benefit = monthly cash cost avoided − monthly operating cost
- Simple payback (months) = one-time cost ÷ monthly net cash benefit, if the benefit is positive
- First-year cash ROI = (first-year cash cost avoided − first-year total cash cost) ÷ first-year total cash cost
The National Laboratory of the Rockies illustrates simple payback by tracking cumulative savings until they recover the initial cost (payback period methodology).
Worked example 1: capacity versus cash (illustrative)
You handle 2,000 invoices a month and the pilot shows six handling minutes saved on each. That is 12,000 minutes, or 200 hours. At $40 an hour, it is $8,000 a month of staff capacity.
Now the cash side. Suppose you can actually avoid $5,000 a month in expenses, and the software plus administration costs $3,500 a month. Net cash benefit is $1,500 a month. An $18,000 implementation pays back in $18,000 ÷ $1,500 = 12 months at that steady rate. If you cannot remove the $5,000 expense, the 200 hours still matter, but the cash payback disappears.
Worked example 2: a small team (illustrative)
Setup costs $6,000. The tool costs $500 a month. You can stop paying $1,250 a month for contracted processing immediately.
- Net cash benefit: $1,250 − $500 = $750 a month
- Simple payback: $6,000 ÷ $750 = 8 months
- First-year cost avoided: $1,250 × 12 = $15,000
- First-year total cost: $6,000 + ($500 × 12) = $12,000
- First-year cash ROI: ($15,000 − $12,000) ÷ $12,000 = 25 percent
If the contract stays in place, the same tool produces no positive cash payback on these assumptions.
Worked example 3: the ramp (illustrative)
Simple payback assumes savings arrive at full rate from month one. They rarely do. Take example 1 again, but the avoided cost ramps: $2,000 in month 1, $3,500 in month 2, then $5,000 from month 3.
| Month | Cost avoided | Operating cost | Net | Cumulative (after $18,000 setup) |
|---|---|---|---|---|
| 1 | $2,000 | $3,500 | −$1,500 | −$19,500 |
| 2 | $3,500 | $3,500 | $0 | −$19,500 |
| 3 | $5,000 | $3,500 | $1,500 | −$18,000 |
| 4 onward | $5,000 | $3,500 | $1,500 | rises $1,500 a month |
After month 3 you still need $18,000 ÷ $1,500 = 12 more months, so payback lands in month 15 rather than month 12. If the staffing budget only changes at a contract renewal, start the cash benefit at that date, and have the budget owner confirm it.
Timing benefits are not cost savings
Paying earlier to capture a discount, or later to hold cash, changes when money moves. Keep it in a separate line from cost avoided.
For discounts, start from actual terms. Oracle documents that an eligible vendor bill can receive a terms discount when paid by its discount date (Oracle’s guide to payment terms discounts). Count only the incremental discounts the workflow made possible, not the ones the team already took, and check the timing against treasury’s cash plan.
On 2/10 net 30 terms, taking the discount means paying 20 days early to save 2 percent. The implied annual rate is 2 ÷ 98 × 365 ÷ 20, about 37.2 percent. That is well above what a revolving credit line typically costs, so the discount is usually worth taking when cash allows. The early payment discounts guide covers the decision in detail.
What changes the decision
Put one risk into the monthly schedule at a time:
- Exceptions rise. If the next supplier group lacks electronic receipts, increase review hours and keep the cost in the forecast.
- Volume grows. Rerun with your peak month and check overage pricing.
- Rollout slows. Push the ramp out two months and see where payback moves.
- The avoided expense is not real. If the case depends on a cost nobody can name, take it back to the pilot.
Use the AP ROI calculator or download the worksheet, and replace the examples with your quote and measured handling time. The AP automation implementation guide explains how to collect pilot measurements that hold up, and the AP automation guide maps each feature to the stage of the process it touches.
Before the case goes to the CFO
- Each vendor’s written definition of a billable invoice, including duplicates, retries, and credits
- Each avoided cost named, with an owner and a start date
- Monthly schedule with ramp, not a single steady-state payback
- Discount and payment-timing effects in their own line