Frequently asked questions
These are the questions readers send most often, answered directly. They cover cost, implementation, controls, and how to tell whether automation fits your team. If your question isn't here, the contact page takes new ones.
Where to start, what it costs, and who it fits
Each answer below is written for a small US team running its own books. Where a question depends on your volume or headcount, we say so instead of guessing a number.
Getting started
The most common question is where to begin. Start with the task that creates the most rework, which for most US SMBs is invoice capture and coding, followed by bank reconciliation. Approval routing usually comes third because it delivers control value more than time savings.
Don't try to automate everything at once. Pick one workflow, measure the current time cost, and compare after a month. A single honest before-and-after on one process tells you more than a vendor demo covering six modules.
Cost and budgeting
Pricing in this market varies widely and usually scales with volume, users, or both. Rather than quoting figures that change, we'd suggest asking vendors for pricing at your actual invoice volume and user count, and asking what happens to the price when volume grows. Include implementation and configuration time in your budget, since that's often a real cost even when the software is subscription-based.
For small teams, the lighter expense and capture tools usually cost less to run than a full AP platform. The trade-off is coverage: a capture tool handles the front of the process, while a platform also carries approval routing, payment runs, and reporting. Buy the coverage you can actually operate — an unconfigured rules engine costs more than it saves.
- Your monthly invoice and expense volume, and how much of it grows in a busy quarter.
- How many people will open the tool in a normal week, not how many seats are licensed.
- Whether implementation and configuration are included or billed separately.
- What the price does when volume doubles, and how much notice you get before it changes.
Read the answers with your own numbers in hand. A quote built on someone else's volume is not a budget.
Implementation and timeline
Configuration typically takes a few weeks, and a pilot on a subset of vendors adds more time before full rollout.
Route a subset of vendors through the new workflow while the old one still runs. Teams that skip this stage tend to find configuration problems at month-end, when nobody has time to fix them. A pilot also tells you whether the approval chain you drew on paper survives a week of real invoices — most do not, and it is cheaper to redraw it in week two than in month three.
Keep the pilot narrow enough that a single reviewer can watch every exception that lands. The exceptions are the useful output.
Some vendors include configuration, some hand you a guide and a support queue. The answer changes your internal workload for the first month, so get it in writing.
Ask who configures the approval chain, who maps your chart of accounts, and who tests the first vendor file. If those three answers are all "you", plan for a slower first month and staff it accordingly. If they are all "us", ask what happens when your chart of accounts changes next quarter.
Controls and auditability
Yes, AP automation can be auditable, provided the tool records approvals, timestamps, and changes, and lets you export that record. Ask to see an export before you buy — a screenshot of an approval screen is not the same thing as a file your accountant can open.
Segregation of duties is the harder question for small teams. Where full separation isn't possible, compensating controls like a second reviewer on larger payments and a monthly bank statement review by someone outside the process are generally accepted if documented and applied consistently. The word doing the work there is documented: a control nobody can point to is not a control.
Fit for small versus large teams
Small teams do better with tools that need little maintenance. There is nobody on a five-person book whose job is managing a rules engine.
- Low-maintenance capture and expense tools, configured once and left alone.
- Rules simple enough that the person who set them up can still explain them next quarter.
- One clear reviewer for larger payments, plus a monthly statement check from outside the process.
- Multi-entity support, so each set of books stays separate but rolls up together.
- Integration with the accounting system already in place, rather than a parallel ledger.
- Reporting that consolidates across entities without a spreadsheet rebuilt every month.
The same platform rarely serves both well, which is why the market splits into point solutions, mid-market products, and ERP-native options. The split is not marketing noise — it reflects genuinely different operating loads. If you are not sure which side you sit on, count the people who touch an invoice before it is paid, and count how many sets of books you close each month.
Working with this site
We publish explanations, not endorsements, and we don't accept payment for coverage. If you spot an error or want a topic covered, send it through the contact page. Questions that come up repeatedly get added here.
A useful question to send includes the workflow you are looking at, your rough monthly volume, and what you have already tried. That is usually enough for a specific answer instead of a general one.
- [email protected]
- Phone
- +1-408-555-9539
- Office
- 770 Innovation Way, San Jose, CA 95134, USA
- Hours
- Mon–Fri: 9:00 AM – 6:00 PM
Visit details, directions, and the contact form live on the contact page. This page stays open for reading.