Your SAP Concur renewal quote usually assumes you re-commit to the transaction volume and add-ons you signed for last time. That default is rarely your best deal. Concur isn't priced on seats: its core fees are transaction-based. SAP Concur's own pricing page prices Expense per report with unlimited users, and SAP's published Concur supplemental terms describe a committed block of base transactions paid in advance, with incremental transactions above it billed in arrears. Most of the money in a Concur renewal is decided by three things: whether that committed base still matches what you actually file and book, which add-ons are really in use, and whether Concur Travel is negotiated alongside your travel management company's fees.
This guide walks the shape of an SAP Concur renewal from the buyer's side. It comes from Fortune 500 sourcing experience and thousands of renewals worth of pattern recognition — not from SAP, and not from a reseller taking a referral fee. It teaches you where the cost really comes from and the levers that move it.
Every figure below is directional and estimated, drawn from public pricing and aggregated practitioner experience. It is not anyone's confidential contract and not a promise of savings. Treat the ranges as leverage on flexibility, not a rate you should expect to hit.
Directional and estimated ranges from public pricing and aggregated renewal experience — not any organization's confidential terms, and not a promise of savings. Normalize your own order form to the same basis before comparing.
| Cost line | Typical unit | Directional range |
|---|---|---|
| Concur Expense (core fee) | Per transaction (typically a submitted expense report) | Public list starts ~$7 (Base) / ~$11 (Plus) per report; enterprise rates quote-based and lower with committed volume |
| Committed base transactions | Volume block, invoiced in advance | Paid whether or not reports are filed — size it to 12–24 months of actuals |
| Incremental (overage) transactions | Per transaction above the base, billed in arrears | Separate rate on the order form — aim for at or near the base rate |
| Concur Travel | Per booking / travel transaction | Quote-based; separate from TMC service fees and GDS-related costs |
| Concur Invoice | Volume-based, per invoice processed | Quote-based and volume-tiered — no reliable public rate |
| Add-ons (ExpenseIt, Drive, Budget, Detect, Intelligent Audit, Tax Assurance, Intelligence…) | Varies by add-on | Each a separate recurring line — carry only what's adopted |
| Termination notice | Days before term end | SAP's published default: at least 90 days unless your order form says otherwise |
How SAP Concur pricing drives your renewal cost
The meter is the transaction. SAP's published 2017 Concur supplemental terms defined an Expense transaction as a submitted expense report (re-submissions of the same report counted once) and, for Travel & Expense, also counted a travel booking not matched to an expense report within 120 days. Today the definitions sit in the Service Description Guide your order form references, so confirm yours before you model anything. Your order form sets a committed number of base transactions per billing cycle, invoiced in advance, and an incremental rate for volume above it, invoiced in arrears.
Concur Expense comes in a Standard edition for simpler configurations and a Professional edition built for large organizations with complex needs; SAP Concur's public pricing page also shows Base, Plus, and Premium packages that bundle items such as ExpenseIt, Reporting, User Support Desk, Travel, and Intelligence. Beyond Expense, Concur Travel, Concur Invoice, and Concur Request are separate service lines with their own meters, and add-ons such as Drive, Budget, Concur Detect by Oversight, Intelligent Audit, Concur Tax Assurance by Blue dot, and Analytics each add a recurring fee. Implementation and set-up fees are billed separately from the subscription.
The pattern to internalize: the per-report rate is only part of the picture, and the size of your committed transaction base moves your cost far more than the headline rate.
Where the money hides: the traps in an SAP Concur renewal
The renewal quote is engineered to look like a continuation of what you already have. The cost usually hides in five places:
- The stale commitment. A base transaction volume set at signature rolls forward even after reorgs, divestitures, travel-policy changes, or headcount shifts. You pre-pay for unused base transactions.
- Overage on top of unused base. Volume that swings by month or region can leave you paying for unused base in one period and overage in another.
- Loose transaction definitions. Which reports, bookings, cancellations, and invoices count — if it isn't pinned down, the count works in the vendor's favor.
- Add-on shelfware. Audit, analytics, mileage, budgeting, and VAT tools bought in the original deal and never fully adopted still renew at full price.
- Evergreen terms and the Travel/TMC blind spot. SAP's published default lets the service continue unless either party gives at least 90 days' written notice, and Concur's booking fees and your TMC's service fees are negotiated separately, so no one sees the full cost per trip.
The levers that actually work
A handful of moves do most of the work in an SAP Concur renewal:
- Rebuild the baseline from your own data. Pull 12 to 24 months of actual reports, bookings, and invoices by month, entity, and country, and reconcile them to your order forms, amendments, and invoices — including every overage charge.
- Re-base the commitment. Size the committed base to actual volume, get the overage rate at or near the base rate, and secure a true-down right at defined points.
- Pin the transaction definition. Confirm in writing what counts — re-submissions, cancellations, unmatched bookings, rejected invoices — against your current Service Description Guide.
- Drop what isn't used. Measure adoption of every add-on and remove the dormant ones before the quote is finalized.
- Negotiate travel as one cost and cap the uplift. Model Concur Travel fees with your TMC contract by booking channel, reconcile affiliate and country scope, and push for a renewal cap across the term.
Timing and leverage: when to start
Leverage is a function of time, data, and alternatives. SAP Concur's own pricing page says the more you commit, the less you pay per report — which is leverage only if you commit to a number you'll actually use. A credible alternative costed at a high level, such as Navan, Emburse, Coupa, or Workday Expenses, disciplines the conversation.
Start six to nine months out, and find your termination-notice date first: SAP's published Concur terms default to at least 90 days' written notice unless your order form says otherwise. Use that window to rebuild your transaction baseline, measure add-on adoption, and line the review up with your TMC contract. A buyer who shows up two weeks before the notice deadline with no analysis has no leverage. The team that started early, knows its real volumes, and knows exactly what it will and will not commit to sets the terms of the conversation.
Gather these three things before a triage call
- Your executed order form(s), amendments and the Concur supplement version they reference
- The latest invoice or renewal quote, including base versus incremental transaction charges
- 12–24 months of actual transaction volumes (expense reports, travel bookings, invoices) from Concur reporting
With those in hand, a 15-minute call can tell you where your leverage is. Nothing needs to be shared before the call.
Walk into your SAP Concur renewal prepared
This guide is the shape of the problem. For a second set of independent, buyer-side eyes on your specific renewal — where the leverage is, before your notice deadline — book a free 15-minute triage, grab the free prep checklist, or get the free SAP Concur renewal playbook.
Book a free 15-min renewal triage → Get the free 15-point renewal checklist → Get the free SAP Concur renewal playbook →Frequently asked questions
When should I start negotiating my SAP Concur renewal?
Start six to nine months out. First find your termination-notice requirement: SAP's published Concur supplemental terms provide that, unless your order form says otherwise, the service continues after each term and either party may terminate with at least 90 days' written notice. Use the lead time to pull 12 to 24 months of actual transaction volumes, reconcile them to invoices, and line the review up with your travel management company contract so travel is negotiated as one cost.
How is SAP Concur priced?
Concur's core fees are transaction-based rather than per seat. SAP Concur's public pricing page prices its Expense packages per report with unlimited users, and SAP's published Concur supplemental terms describe a committed block of base transactions invoiced in advance, with incremental transactions above that block billed in arrears at a rate set on your order form. Concur Travel, Concur Invoice, Concur Request, and add-ons are separate lines with their own meters. Your order form and current Service Description Guide define exactly what counts.
What does SAP Concur cost per expense report?
SAP Concur's public pricing page lists its Base package starting at about $7 per report and its Plus package starting at about $11 per report, with custom pricing for its Premium package, and says price varies with your commitment. Treat those as directional list signals only: enterprise rates are quote-based and fall as committed volume rises. The bigger lever is usually sizing the committed base to what you actually file, not the headline rate.
What is the biggest overspend in a Concur renewal?
Usually a stale volume commitment. A base transaction volume set years ago rolls into the renewal unchanged, even after reorgs, divestitures, travel-policy changes, or headcount shifts. You pre-pay for unused base transactions and pay overage separately when you exceed them. Add-ons that never reached adoption — audit, analytics, mileage, budgeting, or VAT tools — are the second most common source of waste.
How do Concur Travel fees relate to my TMC's fees?
They are separate. Concur charges for travel bookings under your Concur agreement, while your travel management company bills its own service fees under its own contract, so neither negotiation sees the full cost per trip. SAP's published Concur terms also allow Concur to pass through changes in third-party travel costs, such as GDS fees, with at least 30 days' notice. Model Concur and TMC fees together, by booking channel, before you renew either.
Key takeaways
- Concur is priced on transactions, not seats: a committed base of transactions paid in advance, plus overage billed in arrears — so the volume commitment is the number that matters most.
- Rebuild the baseline from 12–24 months of actual reports, bookings, and invoices by entity and country, reconciled to what you were invoiced, before you accept any renewal quote.
- Confirm what counts as a transaction in your current Service Description Guide, and get the overage rate, a true-down right, and a renewal cap in writing.
- Drop add-ons without measured adoption, and model Concur Travel fees together with your TMC's fees by booking channel.
- Find your termination-notice date first — SAP's published default is at least 90 days — and start six to nine months out.