What to Actually Look For in Accounts Payable Software

Most accounts payable software demos start in the middle. You see an approval flow with tidy arrows, a dashboard of invoices by status, and a payment run going out on Friday. It looks finished.

Ask a different question first: what happened to the invoice before any of that? Somebody, or something, had to read it. The supplier name, the invoice number, the dates, the line items, the VAT and the total all had to come off the page and into a system. Every step in that demo runs on those values.

Why the read comes first

If the read is wrong, everything after it is wrong too, just faster. A misread invoice number becomes a duplicate payment that nobody catches. A wrong total fails the match against the purchase order and lands in someone's exception queue. A supplier matched to the wrong record gets paid late, then phones to ask why.

Exceptions are where AP time goes. In Ardent Partners' AP Metrics That Matter in 2025 report, the best-performing AP teams flagged 9% of invoices as exceptions. Everyone else flagged 22%. Not every exception starts with a bad read: missing POs and price disputes cause plenty. But a misread field produces an exception that looks like a supplier problem and costs just as much to chase.

So whether you're searching for account payable software, AP automation software or the best AP automation software for a small team, the advice is the same. Test the read before you look at anything else.

What this guide covers, and where we fit

Accounts payable automation usually covers several jobs: capturing the invoice, coding it, matching it to a PO, routing it for approval, paying it and posting it to your ledger. Some products do all of these. Others do one part well and hand off to the next tool.

We'll be upfront about our part. Foxello does the first step: it reads invoices, extracts the data, and exports it to wherever it goes next. We don't do approval routing or payments. A later section explains where those tools fit and how they connect.

The checks, in order:

1. How accurately it reads your invoices
2. How the data gets into your accounting system
3. Review and audit trail
4. Pricing model
5. Where your data is stored

Check 1: how accurately it reads your invoices

Ask where the number came from

Every vendor has an accuracy figure, usually somewhere around 99%. Before it goes into anyone's slides, ask three questions:

1. On which documents? Clean sample PDFs, or invoices like yours?
2. Measured how? Per character, per field or per invoice? These give very different numbers.
3. Measured by whom? The vendor, or you, on your own files?

The second question matters more than it looks. Per-field accuracy sounds reassuring, but your team experiences accuracy per invoice. One wrong field means somebody has to touch that invoice.

Why line items change the maths

The table shows how per-field accuracy turns into per-invoice accuracy. It assumes each field is independent, which is a simplification, but the pattern holds.

Every line item adds four or five fields: description, quantity, unit price, line total, sometimes a tax code. That's why a system that handles headers well can still produce a review queue full of invoices once real line items show up.

How to test it yourself

You don't need a vendor's benchmark. You need an afternoon and 30 invoices.

1. Pull 30 real invoices from last quarter. Include your top suppliers, a few one-off suppliers, a scan, a phone photo, a multi-page invoice, a credit note and anything in a second language.
2. Decide the fields before you start. For example: supplier, invoice number, invoice date, due date, net amount, VAT, total, currency, PO number and line items.
3. Score every field, not every invoice. Use a simple spreadsheet with invoices as rows and fields as columns, and mark each cell right or wrong.
4. Check the line items on their own. Is the row count right? Did two lines merge into one? Did a description wrap into the next row?
5. Check the arithmetic. Do the lines add up to the net amount, and does net plus VAT equal the total? A system that reads well should get this right without being told.
6. Look at what it does when it's unsure. This is the most important test. For every wrong value, check whether the system flagged it as doubtful or presented it with full confidence.

The result you want isn't zero errors. It's errors that come with a warning. A system that's wrong 3% of the time and tells you exactly where beats one that's wrong 1% of the time and won't say where, because you only find the second kind when a supplier calls about a payment.

How this works in Foxello

Every extracted field gets a confidence score. New workflows start in confidence-based review with a 90% threshold. If any field on an invoice scores below it, the whole invoice goes to review, where the reviewer sees the uncertain fields and their scores. Invoices where every field clears the threshold go straight through. You can move the slider once you've seen your own results.

Mark the fields you can't do without as Required, such as invoice number, total and supplier. If a Required field comes back empty, the invoice goes to review regardless of how the other fields scored.

The 30-day trial includes 100 pages, which is enough to run the 30-invoice test above. For the details of how extraction handles invoices, see how invoice extraction works and our invoice use case.

Check 2: how the data gets into your accounting system

Extraction that ends in a downloads folder hasn't automated much. If someone still opens the spreadsheet and types the totals into your accounting system, you've moved the typing, not removed it. So the second check is the route from "data extracted" to "bill in the ledger".

Four routes, each with a trade-off

None of these is the right answer for everyone. A three-person bookkeeping firm can run a weekly CSV import for years. A BPO feeding several clients' systems will want the API.

Questions to ask any vendor

• "Integrates with" which product, exactly? The desktop and online versions of the same accounting brand are different integrations. So are different ERP editions.
• What does it create on the other side? A draft bill, a posted bill, or a PDF attached to nothing? Those are three very different amounts of work left for your team.
• How does it match suppliers? The name on the invoice rarely matches your supplier record exactly. Ask what happens with a new supplier, or one that trades under two names.
• What happens when a sync fails? Is there a visible error and a retry, or does the invoice quietly never arrive?
• Can you control the format? Field names, date format and decimal separator all need to match what your system expects to import.
• What stops duplicates? If the same invoice is emailed twice, or a sync is retried, will it become two bills?

Where Foxello stands today

We don't connect directly to accounting systems yet. Direct QuickBooks export is coming soon. If your process depends on a named ERP connector, such as NetSuite or SAP, today we're not the right fit, and it's better to know that before you start.

What works now:

• Download results as JSON or CSV on every plan, or Excel on Growth and above
• API and webhooks on Growth and above, to push results as JSON to your own endpoint or pull them on demand. Webhooks are signed and retried, and every event has an ID so a retry can't create a duplicate.
• Google Drive and FTP export on Growth and above
• Zapier on every plan, available on request. An n8n connection is coming soon.

Field names are whatever you call them when you describe the fields, so you can name them to match your accounting system's import columns. Any accounts payable automation software should make that part easy.

Check 3: review and audit trail

Every AP process has a human checkpoint somewhere. Automation can't remove it. What it can do is make that checkpoint fast, and leave a record that it happened.

What good review looks like

Ask for a live demo of the review screen with one of your own invoices, not a slide. Then check:

• The original sits next to the extracted data. Nobody should flip between two windows to compare a total.
• The doubtful fields are already marked, with their confidence. If the reviewer has to recheck all 30 fields to find the two that matter, review takes as long as typing.
• Fixing a value means pointing at it. Clicking the right number on the page is faster and safer than retyping it.
• It works from the keyboard. At 50 invoices a day, the mouse is the bottleneck.
• You set how sure is sure enough. The confidence threshold should be yours to move, not fixed by the vendor.
• Two people can't edit the same invoice at once. This matters as soon as there's a second reviewer.

What an audit trail should answer

When an auditor or your accountant asks about a payment, the trail should answer four questions:

1. Who approved this invoice, and when?
2. What did the system read, and what did a person change?
3. Where is the original document?
4. Who has access to do any of this?

Ask vendors to show you the trail rather than describe it, and ask specifically whether individual field changes are logged. Some trails record approvals and other activity but not edits to values. Ours is one of them today, as explained below.

The control no system replaces

Bank details deserve their own rule. In the 2025 AFP Payments Fraud and Control Survey, 79% of organizations reported attempted or actual payments fraud in 2024. Business email compromise was the top route, cited by 63%, and vendor impostor fraud rose to 45%.

Extraction reads a fake bank account exactly as faithfully as a real one. That's its job. So treat any change to a supplier's bank details as a process question, not a feature: confirm it by phone, using a number you already had, never the one in the email or on the new invoice.

How review works in Foxello

• One uncertain field sends the invoice to review. If any field scores below your threshold, the whole invoice goes to the queue. The reviewer sees its fields split into Needs review and Confirmed, each with its confidence score.
• Document and data side by side. The field being edited is highlighted on the page. Line items appear as a grid below the document.
• Point to correct. Click the right word on the page, or drag a box around it, instead of retyping the value.
• Keyboard-driven. E jumps to the next field that needs review, and Cmd/Ctrl+Enter approves the invoice and opens the next one.
• Edit locks. While one reviewer has an invoice open, others see who has it.
• Audit Trail on the Scale plan records most user actions in the account. It doesn't record field and document edits yet, and logging of individual changes is coming soon. Role-based access on Scale controls who can approve and who can only view.
• Originals stay with the data. Files are retained for one to three years depending on the plan.

Check 4: pricing model

AP pricing is hard to compare because vendors count different things. One charges per invoice, another per page, another per user. A fourth quotes a yearly figure only after two calls and a "discovery workshop". Before comparing prices, work out what you're actually being charged for.

The common models

None of these is a scam. They just suit different buyers. A predictable flat price matters most to a small team. A BPO pricing its own client work needs a per-document cost it can quote with confidence.

Questions that expose the real price

• What counts as one unit? One invoice, one page, or one file that might hold several invoices?
• What happens at month-end? If volume doubles in the last week, do you pay a higher overage rate, top up at the normal rate, or stop?
• Do unused units carry over? Some allowances reset every month, some don't.
• Which features sit on which tier? API access, export formats, extra users, audit trail and multiple workflows are commonly gated.
• What's the minimum commitment? Monthly, annual, or multi-year, and what does leaving cost?
• Are there setup or onboarding fees? And who does the setup work: you, or the vendor's team?
• Is the price published? If you need a sales call to learn the number, the number usually needs a sales call to justify it.

When you compare an extraction solution with a full AP suite, compare like with like. A suite's price includes approvals and payments. Extraction plus a separate approval tool might cost more or less, but only the total is a fair comparison. The section on approvals and payments below covers how those pieces fit together.

Foxello's pricing, worked through

Our prices are published in euros, and one token processes one page. Harder documents processed in Deep mode use two tokens per page.

API and webhooks, Excel export and email import start on Growth. Audit trail and role-based access are on Scale. Extra users are €4.99 a month, and token packs start at €9.99 for 100 tokens. Monthly tokens reset each billing cycle and don't carry over. Token packs you buy separately don't expire, which makes them a cheap way to cover a busy month.

A worked example: a team receives 300 invoices a month, averaging 1.5 pages each, which is 450 pages. If a fifth of those pages need Deep mode, that's about 540 tokens, which fits inside Growth. That works out to roughly €0.13 per invoice on monthly billing, or €0.11 billed annually. Plug in your own volume and page count, because those two numbers decide the answer.

Every account starts with a 30-day trial that includes 100 pages, with no card required. There are no contracts, and you can cancel anytime. See the full pricing page, or our post on self-serve versus enterprise pricing.

Check 5: where your data is stored

Invoices carry more personal data than people expect. They hold the names and addresses of sole traders, bank account numbers, the occasional employee name on an expense claim, and sometimes a signature. Under GDPR that's personal data, even when every invoice is business to business. So where your data is kept, and who else touches it, is a real buying question, not a box to tick at the end.

Six questions to ask any vendor

1. Where are documents stored, and where are they processed? These are two separate questions. A vendor can store files in the EU and still send every page to an AI service in another region for reading. Ask for every subprocessor that touches document content, and the region each one runs in.
2. Is your data used for training? Ask about the vendor's own models and about any AI provider it uses. Get the answer in the terms or the data processing agreement, not just on the homepage.
3. Who at the vendor can see your documents? "Support can access your account" and "nobody sees a document unless you grant access for a specific request" are very different policies.
4. How long is data kept, and can you delete it? Ask about the retention period, deleting individual documents, and what happens to your data after you cancel.
5. Is there a DPA? GDPR requires a written agreement with any processor handling personal data for you. A vendor that serves EU businesses should have a standard one ready.
6. Which certifications apply? Ask which certifications the vendor holds itself, which ones belong to its hosting provider, and whether it can send you its security documentation for your vendor review.

Where Foxello stands

• Everything stays in the EU. Documents are stored and processed in EU regions, including the AI services that read them. Every subprocessor is listed on our privacy page.
• No training on your documents. Neither we nor our AI providers use your documents to train models.
• No one looks without permission. Our team doesn't open your documents or extracted data unless you grant access for a specific support request.
• Encrypted in transit (TLS 1.2 or higher) and at rest.
• Retention you can see. Data is kept for one, two or three years depending on the plan, plus 30 days after cancellation so you can export it. You can delete documents yourself at any time.
• A DPA on request from privacy@foxello.com
• Certified infrastructure. We run on cloud infrastructure certified for SOC 2 and ISO 27001, and we can send our security documentation for your vendor review on request.

More detail on our security page.

The separate tools: approvals and payments

This part of the buyer's guide is where it's easiest to be misled, so we'll be precise. Accounts payable is a chain of jobs. Some products do all of them, some do one, and the marketing rarely makes clear which is which.

The jobs in the chain

One word means two things

Foxello has an Approve button in the review screen. It means the extracted data is correct. It doesn't mean this invoice is OK to pay. Those are different decisions, often made by different people, and a good AP setup keeps them apart.

What invoice approval software does

Approval routing decides who has to sign off before money leaves. Good invoice approval software lets you:

• Set rules by amount, department, supplier or cost center, for example a manager signs off up to €5,000 and finance above that
• Delegate approvals when someone is on holiday, so invoices don't wait two weeks
• Send reminders and escalate when an approval sits too long
• Record who approved what, and when
• Keep duties separate, so the person who changes a supplier's bank details can't also approve the payment to that supplier

Before buying a separate tool, check what you already have. Some accounting systems include basic bill approvals and payment runs, and for a small team that may be enough.

How the pieces connect

If you pair extraction with a separate approval or payment tool, the question that matters is whether the second tool accepts data from outside. Some approval and payment tools only work with invoices captured by their own capture module. Ask whether they take a CSV import, an API call or an automation-platform connection, and test it with real data before you commit.

In a typical setup, Foxello reads the invoice and a reviewer checks any uncertain fields. The clean data then goes by file, API, webhook or Zapier into your accounting system or approval tool, where approval, payment and posting happen.

AP automation for small business: what you actually need

Most AP buyer's guides are written for companies with a finance department. A small business usually has one person doing the books between other jobs. The right setup depends mostly on two numbers: how many invoices arrive each month, and how many people need to touch each one.

A rough guide by size

The thresholds are rules of thumb, not research findings. A business with 40 invoices a month, all of them handwritten delivery-note invoices, may well need extraction before a business with 200 clean PDFs does.

Signs you've outgrown your current setup

• Invoices wait in one person's inbox until they're back from holiday
• Month-end means evenings of catch-up typing
• You've found a duplicate payment, or a supplier found it first
• Suppliers phone to ask where their payment is
• Two people have entered the same invoice, each thinking the other hadn't

If none of these sound familiar, you may not need to change anything yet. That's a perfectly good outcome for a buyer's guide.

Matching Foxello's plans to the sizes above

At an average of 1.5 pages per invoice, Starter's 150 pages a month covers roughly 100 invoices. Growth covers about 380, and Scale about 1,300. Count your own average page length, because a business whose invoices run to three pages gets half those numbers.

One detail matters for small teams. Forwarding invoices to a dedicated email address, the simplest way to get them in, needs the Growth plan. On Starter you upload files yourself, or send them in through Zapier (available on request).

For more on getting started as a small business, see our guide for small businesses. If you're a firm handling several clients' books, see our page for accounting firms.

FAQ

What is accounts payable software?

Software that handles some or all of the steps between receiving a supplier invoice and paying it: capture, coding, matching, approval, payment and posting. Some products cover the whole chain. Others do one step and connect to tools that do the rest.

What should I look for in AP software?

Start with how accurately it reads your invoices, because every later step runs on that data. Then check how the data reaches your accounting system, how review works and what the audit trail records, how pricing is counted, and where your data is stored.

What is the best AP automation software?

It depends on which job you need done. A full AP suite suits a finance team that wants capture, approvals and payments from one vendor. A small team whose accounting system already handles approvals and payments may only need the capture step done well. Whichever you choose, test it on 30 of your own invoices before you sign.

Is AP automation worth it for a small business?

Once invoice volume outgrows the person typing them, usually yes. Under about 50 invoices a month, a good routine in your accounting system may be enough. The signs you've outgrown it are invoices waiting on one person, month-end catch-up evenings, and duplicate payments.

How do I test invoice extraction accuracy?

Take 30 real invoices, including scans, phone photos and multi-page ones. Score every field rather than every invoice, check the line items and the arithmetic, and note whether each wrong value was flagged as uncertain or presented with full confidence.

Does Foxello approve or pay invoices?

No. Foxello reads invoices, extracts the data and exports it. The Approve button in Foxello confirms the extracted data is correct. Approval for payment, the payment itself and posting to your ledger happen in your accounting system or approval tool.

Does Foxello connect to QuickBooks?

Direct QuickBooks export is coming soon. Today you can export JSON, CSV or Excel files to import into your accounting system, or connect through the API, webhooks or Zapier (available on request).

How much does AP automation software cost?

Pricing ranges from a few euros a month for self-serve solutions to annual contracts with setup fees for enterprise suites. Compare what each one counts: invoices, pages, users or credits. Foxello starts at €12.49 a month billed annually (€14.99 monthly), with one token per page and a 30-day trial that includes 100 pages.

Where is my invoice data stored?

With Foxello, documents are stored and processed in the EU, encrypted in transit and at rest, and never used to train AI models. For any vendor, ask separately where documents are stored and where they're processed.

Run the 30-invoice test

Pull 30 invoices from last quarter, including the scans and the awkward ones, and run them through Foxello. You'll see exactly which fields it reads confidently, which it flags, and what your review queue would look like. The trial includes 100 pages, so it costs nothing.

Start free - no card