AP Automation Contract Terms to Negotiate

The AP automation contract terms worth negotiating are the per-transaction payment fees, the card rebate share, implementation scope, service levels, data ownership and exit rights, and renewal escalators. Treat each one as a question to settle in writing.

Most finance teams spend their negotiating energy on the subscription price, because it's the number on the first page of the proposal. It's rarely the number that hurts. The other terms are better handled as questions to put to the vendor and to your own counsel. None of this is legal advice, and your lawyer should read the final paper.

Key Takeaways

• The subscription fee is usually the smallest lever in an AP automation contract; payment fees, rebates and renewal terms move the multi-year total more.

• Fix every per-payment fee by rail in the contract, including check printing, reissues and returned payments.

• A rebate clause should state the calculation basis, the payout schedule, any minimums and what happens to earned rebates if you leave.

• Write implementation as deliverables with acceptance criteria, and decide in advance who pays for change orders.

• Settle data ownership, export format, transition help and renewal caps before signing, while you still have leverage.

Which AP automation contract terms matter most?

The terms that matter most are the ones that scale with your payment volume or survive the first renewal. Payment fees, rebate terms and price escalators fit that description, and the subscription fee usually doesn't.

The quote tells you what AP automation costs under a given pricing model, and the contract decides whether those prices hold. Each term in the table comes with the question to settle and what a good answer looks like.

Questions to settle, not legal terms. Have counsel draft the language.

It's a common pattern. A team wins a hard-fought discount on the subscription and then pays more than the whole subscription in check fees and reissues by the second year, because nobody read the fee schedule sitting in an exhibit at the back.

What should "fully managed" mean in writing?

"Fully managed" should mean the provider's own staff does named work, written into the contract as services with service levels. At a minimum that covers supplier enrollment, payment delivery across rails, exception follow-up with suppliers, and bank-detail verification.

The phrase gets used loosely. Some providers mean they'll host the software, while others mean they'll make the supplier calls, and the difference shows up the first time 400 suppliers need to be moved off checks. The comparison of fully managed AP automation and BPO explains where the work sits in each model. Corpay's fully managed AP, for example, includes supplier enrollment and follow-up as part of the service, which is the kind of commitment worth asking every finalist to put in the statement of work. If a vendor won't write its managed services down, assume they're optional.

How should you negotiate payment and per-transaction fees?

Negotiate payment fees as a schedule by rail, fixed for the initial term, and model them at the volume you expect in two years rather than today. Per-payment fees are often the largest variable in the total.

The economics differ sharply by rail. AFP's 2022 Payments Cost Benchmarking Survey put the median cost of issuing a paper check at $2 to $4, against $0.26 to $0.50 for an ACH payment. ACH is where most of the dollars are heading, with Nacha reporting close to 8.1 billion B2B payments on the ACH Network in 2025. Checks are sticky, though. According to AFP's 2026 Payments Fraud and Control Survey, 72% of check users plan to keep writing them, and 68% of those cite vendor requirements, so your check fee will stay on the bill for years.

Which payment fees should be fixed in the contract?

Fix every fee you can name in advance. The short list:

• Check printing and mailing, including postage and positive pay files

• ACH and same-day ACH origination

• Wire transfers

• Virtual card payments, which often carry no payer fee

• Returned payments, stop-payments and voided checks

• Reissues and payment tracing requests

Ask for the schedule to hold for the full initial term, and ask whether a change in your payment mix can trigger a repricing. Some contracts tie fees to minimum card volume, which matters if your suppliers enroll more slowly than the vendor's forecast.

Who pays when a payment fails or is reissued?

The contract should say who pays when a payment fails, and the answer should depend on why it failed. If the provider's file was wrong, the provider should cover the reissue. If your vendor master was wrong, that's on you.

That distinction sounds obvious, and it's often missing. Ask the vendor to walk through its last three payment failures and show you who paid for each. The Federal Reserve's 2025 payments study found ACH reached almost three quarters of noncash payment value in 2024 for the first time, which means most of your exposure to a bad file now sits in electronic payments that move fast and can be hard to pull back.

How do card rebate terms work in an AP automation contract?

Card rebate terms set how much of the card revenue on your supplier payments comes back to you. The supplier's card acceptance fee funds interchange, and the card issuer shares part of that with the paying company as a rebate.

The rate behind it isn't fixed. Visa's US interchange schedule, with rates effective April 18, 2026, lists 2.70% + $0.10 for a commercial card-not-present transaction and 1.30% + $35.00 for a commercial large-ticket transaction. Large invoices often qualify for the lower large-ticket rate, so a rebate quoted as a flat percentage of all spend can look better on paper than it pays on your actual invoice mix. The guide to interchange fees and card rebates covers the mechanics in more detail.

Rebate programs at scale are real money. Corpay pays its customers more than $800M in rebates each year, which is why the rebate clause deserves the same attention as the fee schedule.

What should the rebate calculation say?

The rebate clause should state the formula, the spend it applies to and the payout schedule in plain numbers. Ask the vendor to settle these in writing:

1. Whether the rate applies to all card spend or varies by transaction type, including large-ticket transactions.

2. Which spend is excluded, such as refunds, disputes or specific merchant categories.

3. Whether there's a minimum annual spend before any rebate is paid.

4. How often rebates are paid, and in what form.

5. Whether the rate is tiered by volume, and when tiers reset.

Then ask for a rebate projection built on your own supplier file, not on an average customer's. Rebate optimization depends on which suppliers accept cards, and only your vendor list can answer that.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper

What happens to earned rebates if you leave?

Earned rebates should be paid out on exit, on the normal schedule or sooner. Ask directly whether rebates earned in the final period are forfeited when you terminate or don't renew, because some agreements say so.

It's an easy clause to miss. A team that leaves mid-year on a quarterly or annual payout can walk away from a meaningful check if nobody read the termination section.

What should implementation scope cover, and who pays for it?

Implementation scope should list the deliverables and the ERP work, each with an owner and an acceptance test. Agree on a fixed fee where you can, and on how change orders get priced where you can't.

The vague version of a statement of work says "standard implementation." The useful version names five things:

• The ERP and its version

• The number of entities

• The approval workflows to be configured

• The supplier file to be loaded

• The number of enrollment campaigns the provider will run

Ask who builds and maintains the ERP connector and whether it's covered when your ERP is upgraded. Get the provider's implementation timeline as a contract exhibit, not a slide.

Short implementations are possible, and any provider quoting a short timeline should be willing to tie fees or credits to it.

What counts as go-live?

Go-live should be defined as live payments processed through the system for an agreed set of suppliers, not as the date the software was turned on. Tie the final implementation payment to that definition.

Write down what happens if go-live slips because of the provider. A credit, a fee holdback or a free extension of the first term are all reasonable asks, and the vendor's reaction to the request tells you how confident it is in its own plan.

Which service levels and controls belong in the contract?

Service levels for uptime, payment cutoffs and support response belong in the contract, with service credits that apply automatically. So do the fraud controls you were shown in the demo, written as obligations.

Ask what's measured, who measures it and how a credit is claimed. Credits that require a written claim within ten days of an outage rarely get paid. The evaluation of AP services providers covers how to judge support before you sign; the contract is where you make the promises enforceable.

Who carries the loss if a fraudulent payment goes out?

The contract should say who carries the loss when a payment goes to a fraudster, based on whose control failed. If the provider skipped its own bank-change verification, it should bear that loss.

The scenario is common. AFP's 2026 survey found 74% of organizations were affected by business email compromise in 2025, and the FBI's 2025 Internet Crime Report counted 24,768 business email compromise complaints with $3,046,598,558 in reported losses. Nacha's fraud monitoring rules, effective March 20, 2026 and June 19, 2026 by phase, also require originators, third-party service providers and third-party senders to run risk-based processes to identify entries authorized under false pretenses, reviewed at least annually. If your provider sends ACH files on your behalf, ask which of those obligations it carries and how it will evidence them. Pair that with a written vendor bank verification process the provider is bound to follow.

What audit rights should you ask for?

Ask for the provider's SOC 1 report every year, plus a bridge letter for any gap between report periods. The AICPA describes a SOC 1 as "an examination of controls at a service organization that are likely to be relevant to user entities' internal control over financial reporting," which is what your auditors will need once payments run through someone else.

Ask too for notice of material security incidents within a set number of days, and for the right to review remediation. AP automation security reviews usually cover the technical side; the contract makes the reporting a duty.

How do you protect your data and your exit?

Protect your exit by settling data ownership, exit help and renewal terms before you sign. Leverage is highest before signature and lowest in the last 60 days of the term.

Start with the renewal. Gartner research published in October 2025 found enterprise SaaS costs often rise 10% to 20% or more at renewal, which is why the escalator matters as much as the starting price.

How should renewal and price escalators be written?

Write the escalator as a capped annual increase, tied to a published index or a fixed percentage, and require written notice of any increase well before the renewal notice deadline. Auto-renewal is fine if the notice window is long enough for you to act.

Put the renewal notice date in your contract calendar the day you sign. Teams miss it more often than anyone admits, and a missed window can mean another full term at the new price.

What should an exit clause include?

An exit clause should cover your data, your suppliers and your open payments. Ask for these in writing:

• Full export of invoices, payments, approvals, audit logs and supplier records in a standard format, at no extra charge

• Supplier bank and enrollment data returned to you, verified

• Transition assistance for a defined period, at a set rate

• Payment of all earned rebates

• Deletion certification once the export is confirmed

It's an awkward conversation to have with a vendor you're about to choose. Have it anyway. A provider that's confident you'll stay doesn't need to make leaving hard.

Fully managed AP from Corpay, with the terms in writing

The terms above are where a fully managed AP provider either backs its promises or doesn't. Corpay is built to put them on paper.

Corpay AP automation pays suppliers by virtual card, ACH or check from one approval flow, with Corpay's team handling supplier enrollment, payment delivery and follow-up as part of fully managed AP. Card payments use single-use virtual cards and earn rebates. It connects through 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central and Acumatica. AP teams save about 40% of the time they spend on processing, and most customers are live in weeks.

Frequently Asked Questions

What should a fully managed AP automation contract include?

It should name the services the provider performs, such as supplier enrollment, payment delivery, exception follow-up and bank verification, with service levels for each. It should also fix payment fees, define the rebate formula and set exit terms.

Can you negotiate the rebate share on card spend?

Often, yes. Rebate rates usually depend on annual card volume, payment timing and transaction mix, so a buyer with meaningful card spend can negotiate the rate, the tiers and the payout schedule. Get the formula in writing.

Who usually pays for AP automation implementation?

The buyer usually pays an implementation fee, though some providers waive or reduce it. Either way, the contract should list what's included, who owns the ERP work, and how change orders are priced.

Should you sign a multi-year AP automation contract?

A multi-year term can lower the price and lock in fees, which helps if the escalator is capped and the exit terms are clear. Avoid long terms with uncapped renewals or minimum card-volume commitments you can't control.

Do you need a lawyer to review an AP automation contract?

Yes. An AP automation contract covers payment liability, data rights and banking obligations, so counsel should review the final paper. Finance should settle the business questions first so the legal review goes faster.

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.

AP Automation

Payments Automation