A Concur deal is won on the transaction floor, not the rate
SAP Concur prices per transaction across Travel, Expense, Invoice and Request, so volume forecasting drives the bill. The headline per-transaction rate is rarely the problem: the annual minimum and the platform fee carry the cost, and most Concur overspend is invisible on the invoice because it hides in a transaction floor set above the volume the business actually runs. Fix the floor to real usage and the headline number stops mattering.
Prepared by Redress Compliance · August 9, 2026 · SAP advisory. Based on roughly 30 to 45 SAP Concur renewals benchmarked 2024 to 2025.
Executive summary
Concur meters per transaction, not per seat, so the annual minimum is where the money is decided.
An expense report, a supplier invoice, or a completed booking each counts as one billable event, and the model rewards SAP when volume rises and penalizes a buyer who commits to a minimum above real usage: fall below the floor and you still pay it.
Run above it and the overage bills at a higher rate unless the band was negotiated in advance.
Across the renewals we benchmarked, annual transaction minimums were set 20 to 35 percent above actual volume, so buyers prepaid for transactions they never ran. The floor, not the rate, is the single largest source of avoidable Concur cost.
Bundling the modules removes line-item visibility and raises the blended rate 10 to 18 percent. Travel, Expense, Invoice and Request are separate modules, each with its own transaction meter, and folding them into one order hides which module carries which price when the renewal quote arrives.
Observed per-transaction pricing runs from about 1 to 8 dollars depending on module and volume, Expense at 2 to 8 on submitted reports, Invoice at 1 to 4 on processed invoices, Travel at 4 to 8 on completed bookings.
And Request often priced as a separate line when it should sit inside Expense at no incremental fee.
Unbundle to see each module rate before signing, then decide what to combine, because the platform fee and premium support tier are negotiable lines buyers who anchor only on the rate leave untouched.
A credible Coupa or Navan alternative moved SAP off its first quote 15 to 30 percent.
SAP responds to a credible alternative, not to a complaint about price, and two vendors give the most leverage: Coupa competes hard on Invoice and broader spend management, so a live evaluation reframes the Invoice line and pressures the platform fee.
And Navan competes on combined Travel and Expense with a different commercial model, so even a proof of concept changes SAP's posture on the Travel meter.
The right comparison for Invoice is invoice volume, not employee count, because it scales with the supplier base, and the Travel blended rate depends on the split between online self-booking and agent-assisted booking, so a higher online mix lowers the effective cost per trip.
The buyer-side move is to ignore the rate first, model trailing twelve-month volume, and negotiate the floor down to actual usage.
In roughly six out of ten renewals the headline rate was already near market while the annual minimum was set well above real volume, so negotiating the rate hard and treating that number as the win missed where the money was.
Pull trailing twelve-month volume per module, set the new minimum at real usage with a defined overage band, and carry the gap as the first ask; the rate matters only after the minimum is honest.
Then trade a longer term for a capped uplift and a fixed per-transaction rate, never accepting an uncapped annual increase on a multi-year order, and keep clean data-export rights and a termination clause.
The modules and their pricing signals
| Module | Billable event | Typical per transaction | Main lever |
|---|---|---|---|
| Expense | Submitted expense report | $2 to $8 | Annual report minimum |
| Invoice | Processed supplier invoice | $1 to $4 | Volume band breakpoints |
| Travel | Completed booking | $4 to $8 | Online versus agent mix |
| Request | Pre-trip approval | Bundled or $1 to $2 | Fold into Expense |
Expense is the anchor module: it meters on submitted reports, so a workforce that files monthly reports generates predictable volume, and it is where the annual minimum is set and where most overcommitment happens.
Invoice sits inside SAP spend management and scales with the supplier base, not headcount, so the right comparison is invoice volume, not employee count.
Travel meters on completed bookings, and the blended rate depends on the online-versus-agent split, so a higher self-booking mix lowers the effective cost per trip.
Request handles pre-trip approval, adds little standalone value at a separate price, and should be pushed into Expense at no incremental transaction fee.
Published list pricing is thin, so real benchmarks come from signed orders, and the contract terms that matter most sit in the SAP cloud agreements, not the sales quote: mid-market Expense lands near 3 to 5 dollars per report after discount, Invoice at 1 to 3.
Travel at 5 to 7 where online booking dominates.
The wider estate context sits in the indirect access pillar and the audit posture in the SAP audit defense framework.
The competitive frames and the renewal levers
- Coupa on Invoice and procurement: a live Coupa evaluation reframes the Invoice line and pressures the platform fee, because Coupa competes hard on Invoice and broader spend management.
- Navan on Travel and Expense: even a proof of concept changes SAP's posture on the Travel meter and the bundle, because Navan competes on combined Travel and Expense with a different commercial model.
- Reset the transaction floor: pull trailing twelve-month volume per module, set the new minimum at real usage rather than the prior committed number, and carry the gap as the first ask in the renewal.
- Term and price protection: trade a longer term for a capped uplift and a fixed per-transaction rate, and never accept an uncapped annual increase on a multi-year order, capping any uplift at or below a named index.
- Unbundle and protect the exit: restore line-item visibility before signing, keep data-export rights and a clean termination clause, because bundling removes visibility and raises the blended rate. The RISE-wide tactics sit in the RISE negotiation tactics.
The SAP Concur negotiation guide
The six buyer-side levers that cut a Concur deal: the per-report fee, module bundling, true-ups, and the renewal cycle.
Get the white paper →How to run the renewal
Start the renewal nine months out, because the two levers that move the total are the transaction floor and the multi-year term with price protection, and both need time and evidence.
Reset the floor first: pull trailing twelve-month volume per module, set the new minimum at real usage rather than the prior committed number, define an overage band so growth does not bill at a punitive rate, and carry the gap between the committed floor and real usage as the first ask.
Then take term and price protection: trade a longer term for a capped uplift and a fixed per-transaction rate, cap any annual increase ideally at or below a named index, unbundle the modules to restore line-item visibility before signing.
And keep data-export rights and a clean termination clause so the exit stays real.
Open a credible Coupa or Navan evaluation before SAP issues its first renewal quote, because SAP responds to a credible alternative rather than a complaint about price, and the evaluation reframes the Invoice line and the Travel meter respectively.
The rate matters only after the minimum is honest, so the sequence is deliberately floor first, alternative second, rate last, which inverts the instinct to negotiate the headline number hardest.
The wider RISE estate negotiation sits in the RISE negotiation guide, and the TCO modelling in the RISE TCO calculator.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across SAP Concur engagements, 2024 to 2025
Across roughly 30 to 45 SAP Concur renewals we benchmarked between 2024 and 2025, the headline per-transaction rate was rarely the problem, the annual minimum and the platform fee carried the cost, and the common advice aimed at the wrong number.
The standard advice is to negotiate the per-transaction rate as hard as possible and treat that number as the win. We disagree:
Renewals where the headline rate was already near market while the annual minimum was set well above real volume, so the buyer prepaid for transactions that never happened.
Median minimum overcommit removed by modelling trailing twelve-month volume and resetting the floor to actual usage with a defined overage band.
The buyer-side move is to ignore the rate first, model trailing twelve-month volume, and negotiate the floor down to actual usage with a defined overage band, because the rate matters only after the minimum is honest.
Three patterns recurred: annual transaction minimums set 20 to 35 percent above actual volume so buyers paid for transactions they never ran, bundling Travel, Expense and Invoice into one order removing line-item visibility and raising the blended rate 10 to 18 percent.
And a credible Coupa or Navan alternative moving SAP off its first quote by 15 to 30 percent.
Most Concur overspend is invisible on the invoice because it hides in an annual transaction minimum set above the volume the business actually runs, which is why the floor, not the rate, is where the deal is won.
Pull trailing twelve-month volume for every module, separate the per-transaction rate from the annual minimum in the current order, model the gap, and open the competitive evaluation before the renewal window. The SAP-wide negotiation library sits in the SAP practice.
Your first five moves
- Pull trailing twelve-month transaction volume for every Concur module, because the floor is set against volume and you cannot negotiate a minimum you have not measured.
- Separate the per-transaction rate from the annual minimum in the current order, and model the gap between the committed floor and real usage, the first and largest ask.
- Open a credible Coupa or Navan evaluation before the renewal window, because SAP moves 15 to 30 percent for a real alternative and not at all for a complaint.
- Reset the floor to actual volume with a defined overage band and unbundle the modules to restore line-item pricing visibility before signing.
- Cap the annual uplift and fix the rate across the term, keeping data-export rights and a clean termination clause, and engage independent advisory before signing. The SAP practice runs the renewal with you.
Frequently asked questions
How is SAP Concur priced?
Per transaction, not per seat. Each submitted expense report, processed supplier invoice, or completed booking is a billable event, subject to an annual minimum commitment and a platform fee.
Travel, Expense, Invoice and Request are separate modules, each with its own transaction meter, and observed per-transaction pricing runs from about 1 to 8 dollars depending on module and volume.
Because the model meters volume, forecasting drives the bill, and the annual minimum is where most avoidable cost sits.
What is the SAP Concur transaction minimum?
The annual floor you commit to at signature. If real volume falls below it you still pay the floor, and if it runs above, the overage bills at a higher rate unless the band was negotiated in advance.
It is the single largest source of avoidable Concur cost: across the renewals we benchmarked, minimums were set 20 to 35 percent above actual volume, so buyers prepaid for transactions they never ran. Reset it to trailing twelve-month actuals with a defined overage band.
What does SAP Concur cost per transaction in 2026?
Observed pricing runs from about 1 to 8 dollars. Invoice tends to land at 1 to 4 dollars per processed invoice once volume bands are negotiated, Expense at 2 to 8 per submitted report, and Travel at 4 to 8 per completed booking, lower where online self-booking dominates.
Published list pricing is thin, so real benchmarks come from signed orders, and large estates negotiate below these bands, but the rate is not where the deal is won, the floor is.
Can you negotiate the SAP Concur platform fee?
Yes. The platform fee and the premium support tier are negotiable line items, and buyers who anchor only on the per-transaction rate often leave these fees untouched.
A live Coupa evaluation is the most effective pressure on the platform fee, because Coupa competes on Invoice and broader spend management.
Unbundle the modules to restore line-item visibility first, because a bundled order hides the platform fee alongside the module rates and raises the blended cost 10 to 18 percent.
Is Coupa or Navan a real alternative to SAP Concur?
Yes, on different modules. Coupa competes hard on Invoice and broader spend management, so a live Coupa evaluation gives genuine leverage on the Invoice meter and the platform fee.
Navan competes on combined Travel and Expense with a different commercial model, so even a proof of concept changes SAP's posture on the Travel meter and the bundle.
SAP responds to a credible alternative rather than a complaint about price, and a real evaluation moved SAP off its first quote by 15 to 30 percent.
When should you start an SAP Concur renewal?
Nine months before expiry. Pull trailing twelve-month volume per module, separate the rate from the annual minimum in the current order, model the gap between the committed floor and real usage, and open a credible Coupa or Navan evaluation before SAP issues its first renewal quote.
The floor reset and the multi-year term with a capped uplift are the two levers that move the total, and both need the runway to model the volume and stand up a real competitive alternative.
