The license fee on a finance software proposal is the number you’ll negotiate hardest and the one least likely to determine what the project actually costs you. Across AP automation, payments platforms, and broader finance tooling, the subscription is commonly half or less of the three-year spend once implementation, integration, internal effort, and change costs are counted. Two vendors quoting the same annual fee can differ by hundreds of thousands over a contract term.
So the practical question when you’re comparing proposals isn’t “what does it cost per year?” It’s “what will we have spent, in money and in our own people’s time, three years from now?” Here’s how to build that answer.
The cost categories most evaluations undercount
A workable total cost of ownership (TCO) model for finance automation has seven lines. The first is the license or subscription fee. The other six are where proposals diverge:
Implementation and configuration
Setup, workflow design, testing, and go-live support, whether charged by the vendor, a systems integrator, or both. Ask for a fixed-scope quote against your actual entity count, invoice or payment volumes, and country list, not a “typical customer” estimate. A number quoted without discovery is a number that will change.
Integration with your ERP and banks
This is the biggest swing factor, and it works differently for AP than for payments. For AP software, the question is how invoice data, approvals, and postings move between the platform and your ERP: pre-built, certified connectors keep costs predictable, while “flexible APIs” often translate to a consulting project. For payments software, add bank connectivity: each bank connection, host-to-host setup, and payment format has a cost to establish and a cost to maintain as banks change their requirements. Some providers absorb format maintenance in a service model; with others, every change is a billable request. Over three years, format maintenance alone can exceed the license fee, which is exactly the burden a Payments as a Service model is designed to take off your plate. Our overview of what ERP integration involves explains why this line item deserves more scrutiny than any demo.
Your own people’s time
Internal project management, IT involvement, testing by your finance team, and data cleanup. This never appears on a vendor quote and is rarely small. Estimate it in days, multiply by loaded cost, and put it in the model. Data cleanup deserves its own line: vendor master records and open item data are almost always messier than anyone expects.
Training and adoption
Initial training is usually included. Ongoing training for new joiners, refreshers after releases, and documentation upkeep usually aren’t.
Running costs beyond the subscription
Per-transaction fees above volume tiers, charges for additional entities or currencies, premium support plans, sandbox environments, and storage. Ask for the full price list, then model your growth against it. A price that scales badly with your volumes is a discount today and a problem in year two.
Change and upgrade costs
Regulations shift, e-invoicing mandates arrive, banks retire formats, and your business adds entities. Ask what last year’s regulatory changes cost existing customers. For cloud platforms updates are typically included; for heavily customized deployments, every upgrade can reopen the integration bill.
Where pricing models hide the differences
AP automation is usually priced per invoice volume, per user, or as a platform fee with volume tiers. Payments software adds pricing per bank connection, per format, or per transaction. None of these models is inherently better, but each shifts risk differently. Volume-based pricing is predictable if your volumes are stable and punishing if you’re acquiring companies. Per-user pricing gets expensive when you want broad access for approvers. The right question isn’t which model is cheapest today, but which one behaves best under the way your business will change.
It’s also worth asking what’s in the base product versus modular add-ons. A low platform fee with separately priced capture, archiving, supplier portal, and analytics modules can end up costing more than an inclusive suite. Sketch the capabilities you’ll need by year three and price that configuration, not the starter one.
Questions that separate vendors quickly
A handful of questions surface most of the hidden cost picture in a single meeting:
- What was the median implementation cost and timeline for your last ten customers of our size with a similar ERP environment?
- Which integrations to our ERP are pre-built and certified, and which would be built for us?
- What does adding a new bank connection, payment format, or company code cost after go-live?
- What did your existing customers pay to comply with the most recent regulatory change that affected them?
- What internal effort, in days, should our team budget for implementation and for ongoing administration?
- Which of the capabilities shown in the demo are included in the quoted price?
Vendors with good answers have them ready. Hesitation on question four or six is itself information. We’ve collected a fuller decision framework in our guide to choosing the right AP automation software, including how to structure demos around your own exception scenarios rather than vendor-scripted ones.
The mistake that costs the most
The most expensive TCO error isn’t underestimating any single line. It’s optimizing each purchase separately. Buying AP automation, a payments tool, and a cash visibility solution as three point decisions means paying for three implementations, three ERP integrations, three vendor relationships, and then, inevitably, for connecting the three to each other. The integration work between point solutions is a cost category all its own, and it recurs with every upgrade of every system involved.
This is why platform scope belongs in the TCO model even when today’s project is narrower. If payments, receivables, or treasury are on your roadmap, a platform that covers them on shared infrastructure changes the three-year math considerably, a point we examined in our comparison of integrated and point-solution approaches.
Build the model before you shortlist
Put the seven categories in a spreadsheet, three years across the top, and make every vendor fill in their columns with your volumes and your systems. The exercise takes an afternoon and reorders most shortlists. Serrala’s AP automation ROI calculator and AR automation ROI calculator can help you build the benefits side of the same model, so you’re comparing full costs against full returns.
Software that looks expensive on the license line and cheap on every other line is usually the bargain. The proposals to be wary of are the ones where the only number anyone can tell you with confidence is the subscription fee.
Frequently asked questions
What is total cost of ownership for finance software?
Total cost of ownership (TCO) is the full three-year cost of a system, well beyond its license or subscription fee. A workable model has seven categories: subscription, implementation and configuration, ERP and bank integration, your own team’s time, training and adoption, running costs beyond the subscription, and change or upgrade costs. The subscription is commonly half or less of the total.
How does AP automation software pricing work?
AP automation is usually priced per invoice volume, per user, or as a platform fee with volume tiers. Each model shifts risk differently: volume pricing is predictable if your volumes are stable but punishing if you acquire companies, while per-user pricing gets expensive when you want broad approver access. It’s also worth checking which capabilities are in the base product versus priced as add-on modules.
What questions should I ask an AP software vendor before buying?
Six questions surface most hidden costs: the median implementation cost and timeline for customers of your size and ERP, which integrations are pre-built versus custom, the cost to add a bank connection or company code after go-live, what existing customers paid for the last regulatory change, how much internal effort to budget in days, and which demo features are included in the quoted price. Hesitation on the last two is itself informative.
Why is integration the biggest cost factor?
Because “flexible APIs” often means a consulting project, while certified pre-built connectors keep costs predictable. For payments software, bank connectivity and format maintenance add further cost, and over three years, format maintenance alone can exceed the license fee. A service-based model that absorbs format upkeep changes this math considerably.
What is the most expensive mistake when choosing finance software?
Optimizing each purchase separately. Buying AP automation, a payments tool, and a cash visibility solution as three point decisions means paying for three implementations, three ERP integrations, and then the work of connecting them to each other, a cost that recurs with every upgrade. This is why platform scope belongs in the TCO model even when today’s project is narrower.
