Supplier Enablement: How Much of Your Payables Can Actually Go on a Card

Supplier enablement in payments is the work of moving suppliers from one payment method to another, usually from check to virtual card or ACH. It's a conversion problem with distinct stages, and volume falls out at each one.

Card programs get approved on a rebate model. That model contains an assumption about what share of payables will convert, the assumption is rarely written down, and six months later the program is being judged against a number nobody ever defended. The useful thing isn't a bigger promise; it's a model that predicts where a program stalls before it stalls.

Key Takeaways

• Supplier enablement means two different things. In procurement it's onboarding suppliers to a sourcing platform. In payments it's converting them to a payment method. This piece is about the second.

• Total payables is the wrong denominator. Card-eligible spend is a much smaller number, and the shrinkage happens before anyone contacts a supplier.

• The gap between offer and enrollment is relational rather than technical. AFP finds 43% of financial professionals naming difficulty convincing counterparties to pay digitally as their most-cited major barrier.

• Some suppliers should stay on ACH or check. A model that treats every decline as a failure will push a program into supply risk.

• Sustained enrollment at twelve months is the number that matters. Enrollment at launch is the number vendors quote.

What is supplier enablement, and why does the word mean two different things?

Supplier enablement in payments is the process of getting suppliers to accept a different payment method, typically virtual card or ACH rather than paper checks. Supplier enablement in procurement is something else, meaning getting suppliers registered, catalogued, and transacting on a sourcing platform.

Both are legitimate uses of the phrase, and searching for it returns mostly the procurement meaning because procurement suites have owned the term for a decade. If you arrived here from a procurement context, the payments version is a narrower problem with harder economics, because it asks a supplier to absorb a cost rather than to fill out a form.

A few adjacent terms worth separating while we're here:

• ePayables is the treasury-side name for the whole electronic-payables category, card and ACH together.

• Vendor enrollment is the specific act of a supplier agreeing to a payment method and providing the details to receive it.

• Card acceptance is the supplier's side of the same decision, and it carries a cost the buyer doesn't see.

• Buyer-initiated payments are transactions the buyer pushes rather than the supplier pulls, which changes who does the work.

Who owns enablement inside the buyer's organization?

Usually nobody, and that's the first stage failure. AP thinks it's a treasury program, treasury thinks it's an AP program, procurement thinks it's a payments program, and the supplier calls whoever they already know.

Programs that work name an owner who has both the authority to talk to suppliers and the time to do it. That person is rarely available, which is the honest reason so many programs stall between the contract and the first conversion. The capacity isn't arriving as headcount either. Bookkeeping, accounting, and auditing clerks held 1,532,400 jobs at a median wage of $50,670 in 2025, with employment projected to decline 6% from 2025 to 2035, a loss of 85,600 jobs, according to the Bureau of Labor Statistics' Occupational Outlook Handbook.

What does the enablement waterfall actually look like?

Five stages, and each one removes volume for a different reason. Naming them consistently is what lets you diagnose a stalled program instead of arguing about whether it's working.

1. Total payables spend. Everything that leaves the building.

2. Card-eligible spend. What remains after removing payroll, taxes, rent, intercompany transfers, utilities on direct debit, and anything under a contract that forbids card payment.

3. Suppliers offered. Those actually contacted, which is always fewer than those eligible.

4. Suppliers enrolled. Those who said yes and provided details.

5. Enrollment sustained at twelve months. Those still accepting after the first repricing conversation, the first surcharge attempt, and the first change of AP staff on either side.

Published conversion rates for each stage are not included here. The figures that circulate in vendor material generally measure enrollment at launch rather than sustained acceptance, which makes them incomparable.

That last note is deliberate. Every stage rate you'll be quoted in a sales process comes from a different denominator, and until someone publishes a rate with its denominator attached, the taxonomy is more useful than the numbers.

Why does eligible spend shrink so much before anyone is asked?

Because a large share of what a company pays out can't go on a card at all. Payroll and payroll taxes are usually the single biggest line in the file, and they're gone immediately. So are income and sales taxes, most rent under commercial leases, intercompany transfers, and debt service.

Then come the contractual exclusions, which are less visible and frequently larger than people expect. Master services agreements often specify payment by ACH or wire, and a card program can't override the contract that's already signed. Those clauses only come off at renewal, which means eligible spend grows slowly and by negotiation rather than by campaign.

A business case built on total AP spend is wrong before it starts, and the error is usually large enough to swallow the whole projected rebate. Run the exclusions first, then model.

What happens between offered and enrolled?

The stage turns relational, and that's where most programs actually lose. The constraint isn't technical, and it isn't really about the card either.

The evidence is unambiguous. AFP's 2025 Digital Payments Survey found that same 43% barrier figure climbing from 30% three years earlier. Difficulty convincing counterparties got worse while the technology got better.

Friction at the enrollment step compounds it. PYMNTS research on supplier enablement found that 50% of suppliers name registering on a new customer's supplier portal as one of their most frequent payment challenges. Every portal is another login, another set of banking details to re-enter, and another vendor relationship to maintain for the privilege of getting paid. What a supplier portal does and does not solve is worth understanding before you assume the portal is the answer.

Meanwhile the rail itself is no longer novel. By 2024, 70% of U.S. corporations had adopted virtual cards, up from 55% in 2022, with large companies reaching 76% adoption for procurement and vendor payments, according to Mastercard's The State of Commercial Card Acceptance. Buyers have adopted. Supplier acceptance is the lagging half.

Best practices for a virtual card program

Learn the internal strategies that make a virtual card program succeed — from program design to driving the vendor acceptance that determines how much of your AP spend earns rebates.

Download the guide

Why do suppliers say no, and when are they right to?

Because acceptance costs them money and the buyer is the one who benefits. That's the whole argument, and treating it as an objection to overcome rather than a real cost is what turns an enablement campaign into a supply problem.

The specific reasons are worth knowing individually:

• Acceptance cost against that account's margin. A supplier running 4% net margin on your account cannot absorb a processing cost of 2% or more without losing money on you.

• Cash-flow timing that already works. A supplier you pay in 20 days on ACH has no timing problem for the card to solve.

• Systems that can't handle the remittance. Card settlements arrive as a lump with remittance detail elsewhere, and a small supplier's AR system may not reconcile it.

• A controller who was burned before. Somebody ran a card program at them badly once, and that memory is durable.

• A calculation that the discount isn't worth it. Sometimes they've done the math and they're right.

The supplier side isn't uniformly resistant, which is the part buyers miss. Mastercard's commercial card acceptance research found 93% of B2B suppliers say digitizing payment processes is a top business priority, and two thirds say they fall short of buyer payment expectations. Suppliers want out of paper. They want out of paper on terms that don't cost them their margin.

Here's the rule I'd use for identifying suppliers to leave alone. If the account is strategic, single-sourced, or running thin margins, and the supplier has declined once with a reason attached, leave them on ACH and move on. The rebate on one account is never worth a supply interruption, and avoiding damage to supplier relationships is a real constraint rather than a soft one.

What does forcing acceptance actually cost you?

More than the program earns, in the cases where it goes wrong. A supplier who concludes that card acceptance is a condition of doing business can absorb it, surcharge it back, or stop supplying. All three are bad for the buyer, and the third one is a genuine operational event.

The surcharge response is the most common and the most corrosive, because the buyer ends up paying the acceptance cost back through invoice pricing and keeping the rebate on paper only. Anyone modeling a program should assume some share of converted spend comes back as price.

Where does supplier-side economics belong in the decision?

Adjacent to this decision rather than inside it. The full treatment of interchange, Level 2 and Level 3 data, and surcharging is its own subject, and where interchange and rebates meet covers the mechanics.

What matters at the enablement stage is simply that acceptance cost is real, it varies by supplier and by transaction data quality, and pretending it's zero makes every conversation harder. What the rebate is actually worth on the buyer's side is the other half of the same ledger.

How do buyer-initiated payments change the shape of the waterfall?

They move the work from the supplier to the buyer, which changes where volume falls out. In a buyer-initiated payment, the buyer pushes funds and the supplier receives them without running a card transaction on their own terminal or gateway.

That removes a specific friction at the enrollment stage, because a supplier who can't process a card in their own systems can still be paid. The cost question and the remittance-reconciliation question both survive it. Suppliers still need to know what the payment covers, and a settlement without clean remittance data creates work on their side that they'll eventually push back on.

The mechanics of the rail are covered in how virtual card payments work in B2B, and what a virtual card is sets the baseline if the concept is new to the team.

How do you forecast conversion before you sign?

Run the model on your own payables file before the business case is written, rather than accepting a vendor's percentage applied to your total spend. The work takes a day and it's the single highest-return hour in the whole evaluation.

Four steps:

1. Segment the file. Group spend by supplier concentration, industry, current payment method, and contract terms. A file where most spend sits with a dozen suppliers behaves nothing like one spread across 800.

2. Apply the exclusions. Strip payroll, taxes, rent, intercompany, and contractually prohibited spend to get card-eligible spend.

3. State your stage assumptions out loud. Write down what share of eligible suppliers you'll actually contact, what share you expect to enroll, and what share you expect to still be enrolled in a year. Wrong assumptions that are written down get corrected. Unwritten ones get argued about.

4. Build the rebate case on the sustained line. Not on eligible spend, not on enrollment at launch. The number that pays you in year three is the sustained one.

Checks are still the thing being displaced, and they're declining slowly. Checks fell to 26% of B2B payments in 2025 from 33% in 2022, while virtual card adoption sits at 23% across organizations, according to AFP's 2025 Digital Payments Survey. The spread between those two numbers is the room a program has to grow into.

What should you ask a vendor to commit to?

Four diagnostic questions, and the answers tell you more than any case study:

• Which stages do you actually operate? Some vendors provide a portal and call it enablement.

• What happens to a supplier who declines? Is there a second attempt, and who makes it?

• What is your twelve-month sustained enrollment rate, not your enrollment rate at launch?

• Who talks to my strategic suppliers, and what do they say?

A vendor who can answer the third question with a number and a denominator is operating the funnel. A vendor who redirects to the rebate projection is not. Ask for a reference customer of roughly your size and supplier mix, and ask that customer what happened in month nine.

Capacity is the other reason to ask. The Hackett Group's 2025 Digital World Class Matrix: Accounts Payable Provider Perspective found companies whose touchless invoice-processing rate clears the 30% mark run 3.5 times higher AP productivity, with evaluated platforms' customers averaging a 60% touchless rate and cycle times improving 59% after implementation. An AP team drowning in manual invoices has no hours left for supplier conversations, which is why enablement and invoice automation tend to succeed or fail together. How supplier payment automation works covers the upstream half.

One data point worth holding loosely: PaymentWorks, which sells enablement software, reports that virtual card adoption can move from zero to 20% of vendors in the first month of digital vendor onboarding, and that one organization saw 75% of onboarded vendor spend shift from check to ACH or virtual card. Treat that as vendor-reported rather than as an independent benchmark, because the publisher has an interest in the number. It's still the closest thing to a published stage rate in the public record, which tells you how thin that record is.

Why run the enablement operation instead of assigning it?

The stages a buyer can't staff are exactly the stages where programs die, and that's the argument for having someone else run them.

Corpay's virtual card program runs supplier enablement as a managed operation rather than handing it back as a project plan. We contact suppliers, make the case, and collect and validate the details. We also handle the declines and go back a second time. Single-use virtual cards close after one transaction, so the number a supplier receives is worth nothing to anyone who intercepts it afterward.

That work sits on top of fully managed AP across virtual card, ACH, and check, because a real program needs all three rails and a defensible rule for which supplier goes on which. Customers see about 40% time saved on the AP cycle, and implementations go live in weeks. We pay out more than $800M in rebates per year to customers on card spend.

Reconciliation runs back into the accounting system rather than into a spreadsheet, with 100+ ERP integrations including NetSuite, Sage Intacct, Business Central, and Acumatica. For the surrounding operational picture, the vendor lifecycle around all of this covers day-to-day management, why enrollment decides the program makes the case at greater length, and the same decision from the supplier's side is worth reading before you write your outreach. If you're running several payment providers at once, the cost of that is its own line item, and what suppliers actually want from electronic payments is the research worth reading first.

Frequently Asked Questions

What is supplier enablement in payments?

It's the process of moving suppliers from one payment method to another, usually from paper check to virtual card or ACH. It covers identifying eligible suppliers, contacting them, making the case, collecting payment details, and keeping them enrolled over time.

What percentage of AP spend can realistically move to virtual card?

There's no reliable published figure, and any single percentage hides the denominator. Model it yourself. Strip payroll, taxes, rent, intercompany, and contractually excluded spend to find card-eligible spend, then apply your own stage assumptions for contacted, enrolled, and sustained.

What is commercial card supplier enablement?

The same process specific to commercial card programs, where the goal is moving supplier payments onto a corporate or virtual card so the buyer earns rebate on spend already going out. It's distinct from procurement-platform enablement, which registers suppliers on a sourcing system.

Why do vendors refuse virtual card payments?

Acceptance cost against the margin on that account is the main reason. Others include cash-flow timing that already works for them, AR systems that can't reconcile card settlements cleanly, and a prior bad experience with a card program run badly.

Should you ever pressure a supplier to accept a card?

No. A supplier who treats acceptance as a condition of business will absorb the cost, surcharge it back through pricing, or reduce service. The rebate on one account never justifies supply risk, and strategic or single-sourced suppliers should be left on their preferred rail.

What are buyer-initiated payments?

Payments the buyer pushes to the supplier rather than the supplier pulling through their own card processing. That removes the need for the supplier to run a card transaction, which resolves one specific enrollment barrier without addressing acceptance cost or remittance reconciliation.

How long does supplier enablement take?

It depends on supplier concentration, contract terms, and how many people are assigned to outreach. A file concentrated in a few dozen large suppliers moves on a different schedule than one spread across hundreds, and contractual exclusions only clear at renewal.

What is the difference between supplier onboarding and supplier enablement?

Onboarding establishes the supplier relationship through records, tax forms, banking details, and compliance checks. Enablement changes how that supplier gets paid. Onboarding is a prerequisite, and a clean vendor master makes enablement far easier, but they're separate programs with separate owners.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Virtual Card

Payments Automation