SAP Concur is metered per transaction across Travel, Expense, Invoice, and Request. The renewal is won on the annual floor, not the headline rate. Read the playbook before the next Concur quote lands.
SAP Concur prices per transaction across Travel, Expense, Invoice, and Request. This guide covers the pricing mechanics, the bundle traps, the competitive frames from Coupa and Navan, and the buyer side moves that cut a Concur renewal.
SAP Concur is metered per transaction. An expense report, a supplier invoice, or a completed booking each counts as one billable event. The model rewards SAP when volume rises and penalizes buyers who commit to a minimum above real usage.
Each SAP Concur module counts a different event. Expense counts submitted reports. Invoice counts processed invoices. Travel counts completed bookings. You pay on the meter, subject to an annual minimum.
SAP sets an annual transaction minimum at signature. If real volume falls below it, you still pay the floor. If volume runs above it, the overage is billed at a higher rate unless you negotiated the band in advance.
On top of transaction fees, SAP adds a platform fee and an optional premium support tier. These lines are negotiable and are often left untouched by buyers who anchor only on the per transaction rate.
SAP Concur modules and typical 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 and Travel carry the largest spend in most estates. Invoice scales with supplier count. Request is small but is often priced as a separate line when it should sit inside Expense.
Expense is the anchor module. It meters on submitted reports, so a workforce that files monthly reports generates predictable volume. This is where the annual minimum is set and where most overcommitment happens.
Invoice sits inside SAP spend management and meters on processed invoices. It scales with supplier base, not headcount, so the right comparison is invoice volume, not employee count.
Travel meters on completed bookings. The blended rate depends on the split between online self booking and agent assisted booking. A higher online mix lowers the effective cost per trip.
Request handles pre trip approval. It adds little standalone value at a separate price. Push to bundle it into Expense at no incremental transaction fee.
Published list pricing is thin, so benchmarks come from signed orders. The contract terms that matter most sit in the SAP cloud agreements, not in the sales quote.
SAP responds to a credible alternative, not to a complaint about price. Two vendors give the most leverage in a Concur conversation.
Coupa competes hard on Invoice and broader spend management. A live Coupa evaluation reframes the Invoice line and pressures the platform fee.
Navan competes on combined Travel and Expense with a different commercial model. Even a proof of concept changes the SAP posture on the Travel meter.
The standard advice is to negotiate the per transaction rate as hard as possible and treat that number as the win. We disagree. In roughly six out of ten Concur renewals we benchmarked, 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. 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. The rate matters only after the minimum is honest.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A Concur deal is won on the transaction floor, not the per transaction rate. Fix the floor to real volume and the headline number stops mattering.
Start the renewal nine months out. The two levers that move the total are the transaction floor and the multi year term with price protection.
Pull trailing twelve month volume per module. Set the new minimum at real usage, not at the prior committed number. Carry the gap as the first ask in the renewal.
Trade a longer term for a capped uplift and a fixed per transaction rate. Never accept an uncapped annual increase on a multi year order.
SAP Concur is priced per transaction, not per seat. Each submitted expense report, processed invoice, or completed booking is a billable event, subject to an annual minimum commitment and a platform fee.
The transaction minimum is the annual floor you commit to at signature. If real volume falls below it you still pay the floor, which is the single largest source of avoidable Concur cost.
Observed pricing runs from about $1 to $8. Invoice tends to land at $1 to $4, Expense at $2 to $8, and Travel at $4 to $8, with large estates negotiating lower.
Yes. The platform fee and premium support tier are negotiable line items. Buyers who anchor only on the per transaction rate often leave these fees untouched.
Yes for Invoice and broader spend management. A live Coupa evaluation gives genuine leverage on the Invoice meter and the platform fee during a Concur renewal.
Navan competes on combined Travel and Expense with a different commercial model. Even a proof of concept changes SAP posture on the Travel meter and the bundle.
Be careful. Bundling removes line item visibility and tends to raise the blended rate. Unbundle to see each module rate before you sign, then decide what to combine.
Start nine months before expiry. Pull trailing twelve month volume, reset the floor to real usage, and open a competitive evaluation before SAP issues its first renewal quote.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
