Updated 6 November 2026 How we make money
Payables Brief Payables Brief.

What AP automation software costs at 1,000, 5,000 and 25,000 invoices a month

Every cost record on Payables Brief shows the prices a vendor lists and what they mean in dollars at three invoice volumes: 1,000, 5,000 and 25,000 invoices a month. Every vendor is held to the same rules. This page is the full method: what we count, what we leave out, and why.

How a price becomes a figure

Vendors with list prices set them by user seats, by team size, by a flat platform fee, or by usage credits, and none lists a breakpoint anywhere near 1,000, 5,000 or 25,000 invoices. AvidXchange ties its fees to invoices and payments processed and Yooz to documents processed, and neither lists a dollar rate. Turning a seat price or a platform fee into a monthly cost at a stated invoice volume takes a small number of stated assumptions. None of them is a number from a vendor. They are Payables Brief’s modeling choices, open to challenge and open to change if a better one turns up.

The full table of assumptions, with the reasoning behind each one, is below in Assumptions. Change any of them and the figures change: every cost record names the plan and the line items behind its number, so a different assumption can be tried by hand against the same list prices.

Each figure includes the listed per-user or per-plan subscription fee for the plan in use at that tier, plus the listed per-transaction payment fee for ACH, check and international wire, weighted by the headline mix above. The full list of what counts and what does not is below in What a figure includes.

Card payments: a separate scenario, never a zero

Card payments do not appear in the monthly or per-invoice figure for any vendor. Instead, a computed record can carry a card scenario: what a 5 percent card share would add, where the vendor lists a card rate. Where a vendor lists no card fee, the scenario says so in words and shows no number. A missing card fee is a gap in that vendor’s disclosure. It is never shown as free, and it is never averaged into the headline next to a vendor that does list a rate. The same rule covers any other fee type: if a vendor lists no fee for one of the three headline methods, that method’s share is left out of the headline for that vendor and the record says so.

What’s excluded

Implementation and onboarding fees, per-plan fees with no list price (a vendor can advertise a feature like “a platform fee based on team size” with no dollar amount), ERP connector fees that are not itemized in dollars, and negotiated discounts, multi-year commitments or any other custom quote term that only shows up after a sales conversation.

Full price, partial and quote only, in full

A full price record has every figure the computation needs: a plan price and a fee for each of the three headline payment methods. Its monthly figure is a complete total under the stated assumptions, not counting the separate card scenario.

A partial record has some of the needed figures and not others, most often a base subscription price with no transaction-fee schedule. A tier can also turn partial on its own if a vendor is missing one of the three headline methods. A partial record’s figure covers only the listed part. The record shows “Base fee only” in place of a cost per invoice, because the base fee leaves out a real cost component and cannot be compared with a full price record’s cost per invoice.

A quote only record’s vendor lists no dollar figure. The record states what is known instead: the pricing model, the named plans without prices, listed payment fees if any exist, ERP integrations and segment. No number is estimated for a quote-only record. The For vendors page explains how a vendor sends its own numbers. The pricing index of 19 AP vendors applies the same states to all 19 AP vendors, including those without a cost record.

Marketplace listings stay separate

Some vendors list a price on AWS Marketplace, Microsoft Marketplace or a vendor-provided G2 listing, while listing no price of their own. Where that listing carries a dollar figure, the record shows it next to the vendor’s listed numbers, labelled as a marketplace price, and it is never folded into the list total. A vendor’s list price and a marketplace price can differ, and the two are always kept apart.

How often records are rechecked

Every vendor’s prices are rechecked at least once a quarter, and immediately whenever a reader or a vendor flags a change. Every recheck adds a dated entry to that record’s change log, whether or not a figure moved.

The cost per invoice calculator

The cost per invoice calculator uses the same figures as every cost record. Between the three stated volumes it keeps the plan and seats of the nearest tier and scales per-invoice and per-payment fees to the volume you type.

Where pages disagree

If a vendor gives two different prices for the same plan, the record states both and computes no total from either until the vendor resolves it.

Sending real numbers

A vendor with no list price can send its price list and have it carried on its record, computed with this same method. That is a paid verified pricing listing. The For vendors page has the detail.

The three volume tiers

What a figure includes

Not included:

Price disclosure tiers

Full list price
Every fee needed for a cost per invoice has a list price.
Base fee only
Only the base fee has a list price, so no cost per invoice can be worked out.
Quote only
The vendor has no dollar list price.

Where the numbers come from

Assumptions

Assumption Value Why
AP users per tier 2 at 1,000 invoices, 4 at 5,000, 20 at 25,000 One AP user is assumed to process about 1,250 invoices a month inside AP automation software. A floor of two keeps a second person on every team, for separation of duties: one preparer, one approver.
Invoices per payment 1.15 Most payment runs cover one invoice to one vendor, but AP software lets a finance team batch a minority of repeat vendors into a single payment a cycle. This ratio converts invoices a month into payments a month before any per-transaction fee applies.
Headline payment mix ACH 75 percent, check 20 percent, international wire 5 percent ACH is the dominant payment rail for US business payments. Checks are a shrinking but real minority. International wire is a small share for a typical US company at these volumes. The same mix is applied to every vendor's listed per-transaction fees, so the comparison is like for like.
Card payments Not in the headline mix. A separate, labelled scenario at a 5 percent share A card fee is usually a percentage of the payment amount, and vendors disclose it inconsistently. Folding card payments into the headline made a vendor that discloses a card fee look far more expensive than one with no card fee listed. A missing card fee is a disclosure gap and does not mean a lower cost.
Average payment amount $1,500, used only inside the card scenario None of the three headline methods is priced as a percentage, so the headline total never needs this number. It exists only to turn a listed percentage card fee into a dollar figure for the card scenario.
Plan used at each tier The cheapest plan with a dollar list price, unless the vendor states a user or invoice cap the tier would exceed Where a vendor states a cap, the tier moves to the next priced plan, or to quote only at that tier if none exists. Where no cap is stated, the plan stays the same across tiers rather than guessing when a company would be asked to upgrade.

Methodology change log

  1. , version 1.0: First version: three volume tiers, included and excluded costs, and the pricing disclosure labels.