Supplier Network Fees: What Vendors Pay to Get Paid

Supplier network fees are charges a vendor pays to receive a payment electronically through a buyer's AP or procurement network. They are usually a percentage of the payment plus a fixed settlement fee, and sometimes an annual subscription once the vendor crosses a document or dollar threshold. The buyer chooses the network. The supplier pays part of the cost.

This catches people out constantly. An AP team rolls out a new automation platform, migrates suppliers onto its payment network, and three weeks later the phone starts ringing: why is there a deduction on our payment? Nobody set out to charge their vendors. It is simply how most payment networks are funded, and it rarely comes up in the demo.

What supplier network fees actually are

When a buyer pays through a network rather than straight from their bank, the payment stops at an intermediary. That intermediary handles enrollment, holds the supplier's bank details, screens for fraud, delivers remittance data, and settles the funds. Someone has to pay for that layer. Depending on the network, the cost lands on the buyer, on the supplier, or on both.

Three charging models show up most often:

• Per transaction percentage. A cut of each payment received, often with a fixed settlement fee on top. This is the common shape for AP payment networks.
• Threshold subscription. Free until the supplier crosses a document count or spend level with a buyer, then an annual fee tiered by volume.
• Interchange on virtual cards. No explicit fee, but the supplier accepts a card payment and absorbs merchant processing costs, which are typically the most expensive option of the three.

What the major networks charge suppliers

These structures change and vary by agreement, so treat this as a map of the models rather than a rate card. Always read the current supplier agreement.

The pattern is consistent: the more service wrapped around the payment, the more likely the supplier funds it. Our AvidXchange pricing breakdown goes deeper on one specific example, including how the supplier fee sits alongside the buyer's own subscription and implementation cost.

Why am I being charged to receive a payment?

Because your customer chose a payment network, and that network bills the receiving side for the service it provides. From the network's perspective you are getting something real: faster settlement than a mailed check, fraud monitoring on the account holding your bank details, structured remittance detail so you can apply cash without guessing, and a support line when a payment goes missing.

Whether that is worth a percentage of every invoice depends entirely on your margins and your volume. A supplier sending two invoices a year will not care. A supplier sending 200 invoices a year on 6% margins is losing real money, and they are right to push back.

Can suppliers refuse to join a payment network?

Usually yes, though it is a negotiation rather than a switch you flip. Most buyers keep a fallback method, normally a mailed check or a plain bank ACH credit, because they cannot force every vendor to enroll. What you lose by refusing is the speed and the remittance detail, and sometimes you wait longer to get paid because the check run is less frequent than the electronic run.

The practical move for a supplier is to ask two questions: what is the fee free option, and what is the payment timing on it? If the answer is a check that arrives two weeks later, the fee may be cheaper than the financing cost of waiting.

Do virtual card payments cost the supplier more?

Almost always, yes. A virtual card payment runs over card rails, so the supplier pays merchant interchange and processing, which commonly lands in the low single digit percentages with no cap on large invoices. On a $50,000 invoice that is a meaningfully larger number than a percentage based ACH fee that caps out, or a flat bank transfer.

This is also why buyers are offered card rebates. The buyer earns a share of the interchange the supplier pays. That is not hidden, but it is worth understanding the flow before you build a business case on rebate income: the money is coming out of your vendors.

Does ACH have a fee?

Plain bank ACH is cheap and the cost sits with the sender, typically a few cents to under a dollar per item, with the supplier receiving the full amount. Network ACH is different. When ACH is delivered through a payment network with enrollment, fraud screening, and remittance services attached, the receiving supplier is charged a percentage plus a settlement fee. Same rails, very different economics, and the word ACH alone does not tell you which one you are looking at.

What this means if you are the buyer

Supplier fees are your problem too, even though you do not pay them, for three reasons.

Enrollment rates drive your business case. AP automation savings assume most suppliers move to electronic payment. If a third of them refuse because of fees, you are still running a check process, still handling exceptions, and the payback period you presented stretches out.

It affects vendor relationships. Your best suppliers notice deductions. Finding out from an angry controller that you quietly moved them onto a fee bearing network is a bad way to start a renewal conversation.

It changes the true comparison between vendors. A platform that charges you more but does not tax your suppliers may be cheaper across the relationship than one with a low subscription and an aggressive payment network. Work this into how you evaluate AP automation pricing, not just the license line.

How to handle it without burning vendors

1. Ask the vendor directly, in the sales cycle. What exactly will my suppliers be charged, in writing, for each payment method? Vague answers here predict awkward conversations later.
2. Segment your supplier list before rollout. High volume and thin margin vendors deserve a different conversation than the ones you pay twice a year. Sort by annual spend and invoice count first.
3. Tell suppliers before it happens. A short note explaining the change, the benefit, and the fee free alternative costs you nothing and prevents most of the friction.
4. Keep a genuine no fee path. Even one option matters. It turns a mandate into a choice, and it keeps your leverage in supplier negotiations.
5. Fold it into onboarding. The same packet that collects a W-9, remittance details, and often a certificate of insurance is the right place to capture payment method preference, so you are not renegotiating with 400 vendors after the fact.

The separate question worth asking

Payment networks and invoice automation get sold together, but they solve different problems. Capturing invoice data, coding it to the right GL accounts, and getting it approved is one job. Moving money to the supplier is another. Plenty of finance teams need the first badly and are perfectly happy paying suppliers from their existing bank.

If that describes you, splitting the two is worth pricing out. You keep your bank relationship and your ACH costs, your suppliers keep the full invoice amount, and you still get rid of the manual keying. That is roughly the shape of what we build: AI capture, line level GL coding so one invoice can split across jobs or properties, an approval threshold, and a record of the payments you make elsewhere. Work out your own starting point with cost per invoice, and see how the AP payment run changes once the approval step stops being the bottleneck.

Whatever you choose, go in knowing who pays for what. The fee schedule your suppliers sign is part of the total cost of your AP stack, even when it never shows up on your invoice.