Platform comparison · Total cost of ownership

SAP Concur + Legacy TMC vs. All-in-One Cloud T&E Platforms: Total Cost of Ownership Audit

A SAP Concur program is a stack: Concur Travel and Concur Expense licences, a TMC that fulfils and services the bookings, and an integration layer into ERP and HR. An all-in-one cloud platform sells booking, servicing and expense as one contract. The first stack is more configurable; the second is cheaper to run when the program is simple enough to fit it.

The comparison most buyers get wrong is the online fee. In a Concur stack the real online cost is two fees, the OBT per-booking charge and the TMC online fee, and it is usually $10–$18 per trip combined.

Updated 6 Nov 2026 · 6 min read · Independent TMC Head-to-Head Comparisons & Merger Teardowns

$10–$18Stacked online cost per trip, Concur + TMC
$4–$8OBT per-booking licence range seen in invoices
$25K–$150KTypical multi-entity implementation range
3 yearsTCO horizon to compare, not year one

A stack of three contracts vs. one platform

SAP acquired Concur in 2014, and Concur remains the reference T&E stack for large enterprises. A typical Concur program has three commercial layers:

  1. SAP Concur licences — Concur Travel (often on the redesigned Concur Travel experience), Concur Expense, and optional modules such as Concur Request and TripLink, which captures bookings made directly with suppliers.
  2. A TMC — Amex GBT, BCD Travel, FCM or another agency, which tickets, services and supports the bookings made in Concur and charges its own fee schedule.
  3. Integration — ERP, HR feed, card feeds and policy configuration, maintained by an internal admin, a systems integrator or both.

An all-in-one cloud platform, such as Navan or TravelPerk combined with an expense product, collapses these into one vendor. The result is fewer invoices and one data model, but less configurability and a single point of lock-in. The SAP Concur licensing and per-booking fee audit guide covers the Concur side line by line.

Normalized 12-row Fee & SLA Comparison Table

Typical contracted ranges we see in RFP responses, licence renewals and invoices for $2M–$25M programs. Concur pricing is negotiated per customer, so treat every row as a question for your own order form.

Cost or SLA lineSAP Concur + legacy TMCAll-in-one cloud platformContract target
Online cost per trip, all-in$10–$18 (licence + TMC fee)$0–$10≤ $10 all-in
OBT per-booking licence$4–$8IncludedItemized, no charge on voids
Expense licence$6–$12 per active user / month equiv.$0–$8 per user, lower with cardActive users only, true-down yearly
Agent-assisted booking$28–$45$25–$40$18–$28
Exchange, refund or void$20–$40$20–$35$15–$25, voids free
Implementation and configuration$25K–$150K multi-entity$0–$50KFixed price, vendor-funded migration
Annual admin and integration upkeep0.25–1.0 FTE or SI retainer0.1–0.5 FTEIncluded change requests per year
Off-channel booking captureTripLink (optional module)Card and inbox capture; verify≥ 90% of trips visible for duty of care
NDC content and servicingDepends on Concur Travel and TMC; verify per carrierPlatform NDC; verify exchangesIn-channel exchange, same fee
Unused ticket credit syncTMC mid-office feed; gaps commonNative in platform; verify limits< 0.8% of air forfeited
Hotel commission returned0%–50% via TMCPlatform margin; verify80%–100% or disclosed margin
Term and exitSeparate licence and TMC termsOne term; card coupling riskCo-terminous, decoupled, free export

Rows 1, 3 and 7 explain most TCO gaps. A buyer comparing a $6 TMC online fee against a $6 cloud fee is ignoring the Concur per-booking licence on top; a buyer comparing licences is ignoring the internal admin time a configurable stack consumes.

Interactive tool · Fee & leakage simulator

Head-to-Head Annual Fee & Leakage Simulator

Compare the annual run cost of a SAP Concur plus legacy TMC stack with an all-in-one cloud T&E platform on the same travel basket and user count.

1 Annual total T&E spend
$
$250K$50M
2 Online (self-booked) adoption
%
20%Top quartile 88%95%
3 Active travelers
1020,000

Modeled annual cost of service + leakage

Annual lineSAP Concur + legacy TMCAll-in-one cloud T&E platform

 

  • SAP Concur + legacy TMC: Online line stacks the OBT per-booking licence and the TMC online fee; fixed line is integration upkeep.
  • All-in-one cloud T&E platform: One contract; fixed line is year-one migration on the buyer side, which drops away in year two.

Figures are normalized benchmark assumptions from Business Travel Consulting 2026 benchmarks, not SAP Concur or vendor quotes; per-user lines are expense licences, and fixed lines are integration upkeep (stack) or year-one migration (cloud).

Where the Concur stack leaks and where the cloud suite leaks

Concur stack leakage

  • Double-charged touches. A booking started in Concur and finished by a TMC agent can attract both the OBT per-booking fee and the TMC agent-assisted fee. Match a sample of PNRs across both invoices.
  • Unused ticket blind spots. Credits are tracked in the TMC mid-office; if that feed does not reach the booking flow, travelers never see them. This is why stacked programs often forfeit 2%–3% of air. See the unused ticket recovery calculator.
  • Licence drift. Expense licences sized on headcount at signature rarely shrink. Audit active users against billed users at every renewal.

Cloud suite leakage

  • Bundled economics. Expense pricing discounted against card adoption ties three products together; leaving one reprices the others.
  • Policy fit. Complex multi-entity policies, cost-center rules and approval chains may need workarounds that bring back manual work.
  • Migration cost on your side. Profiles, negotiated rates, ERP mappings and historical data have to move. Vendor-funded migration should be a contract line, not a promise.

The exact contract clauses to demand on each side

From SAP Concur and your TMC

Concur order form · Billable booking definition

A billable booking is one completed, ticketed or confirmed trip. No per-booking fee applies to voided, duplicate or TMC-cancelled bookings, or to bookings completed by the TMC after an online session was abandoned.

TMC agreement · Clause 8.4 · Unused credit synchronization

The TMC shall feed all unused ticket credits to the Client’s booking tool daily so they display at the point of sale, and shall report credits issued, reused and expired by carrier each quarter. Credits expiring unused because of a feed failure shall be credited against TMC fees.

From an all-in-one cloud platform

Clause 5.1 · Price hold and true-down

Subscription and per-user fees are fixed for 36 months. Billed users are trued down quarterly to users with at least one booking or expense report in the quarter.

Clause 12.3 · Migration and exit data

The Provider shall fund profile, policy and negotiated-rate migration, and on exit shall deliver all travel and expense records, receipts and audit trails in a documented machine-readable format compatible with the Client’s ERP within 30 days at no charge.

When each model fits

SAP Concur + TMC fits
SAP ERP organizations, multinationals with several legal entities and different TMCs by country, complex approval and cost-allocation rules, and audit-heavy sectors such as defense contractors under FAR 31.205-46 or pharma programs tracking HCP spend.
All-in-one cloud fits
$1M–$10M programs with one or two entities, simple policy, mobile-first travelers and finance teams that want card, expense and travel in one data set, as compared in Navan vs TravelPerk vs Spotnana.
Hybrid
Keep Concur Expense for ERP and audit, and move booking to a cloud TMC or a Spotnana-based stack. Price the integration before assuming the savings.

Running a neutral platform TCO benchmark

  1. Week 1 — Inventory every contract. Concur order forms, TMC agreement, SI retainers and internal admin time. Count billed users against active users.
  2. Week 2 — Reconcile one quarter. Match OBT per-booking charges to TMC invoice lines and ARC/BSP tickets to find double-charged touches, using the forensic audit method.
  3. Week 3 — Price the alternative. Ask two cloud platforms to price your basket, migration and three-year term, with the clauses above.
  4. Week 4 — Decide on three-year TCO. Compare stack vs. suite on cost, policy fit and exit cost. Use the outcome to renegotiate the Concur renewal even if you stay; see the TMC RFP guide for scoring.

Executive FAQ

Questions procurement teams ask about this

Does SAP Concur charge a per-booking fee on top of the TMC fee?

In most Concur Travel programs, yes. Concur Travel is licensed by SAP Concur, often per booking, and the TMC that tickets and services the trip charges its own online transaction fee. The combined online cost is typically $10–$18 per trip. Ask both parties for the billable booking definition, and reconcile a quarter of invoices to make sure voids, duplicates and agent-completed bookings are not charged twice.

Is an all-in-one cloud platform cheaper than SAP Concur?

For simple $1M–$10M programs it is usually cheaper to run, because there is one fee instead of two per trip and less admin work. For multi-entity enterprises on SAP ERP with complex policies, the integration and control benefits of Concur can outweigh the fee gap. Compare on a three-year TCO that includes implementation, licences, admin time, migration and exit cost, not on year-one fees.

Does the new Concur Travel support NDC?

SAP Concur has been adding NDC content to its redesigned Concur Travel experience, but what you can book and service depends on the carrier, your configuration and your TMC’s ability to service NDC tickets. Test booking, exchanging and refunding NDC fares on your top carriers, and contract for exchange servicing in the same channel at the same fee as EDIFACT tickets.

Why do Concur programs lose unused ticket credits?

Unused credits are held by the airline and tracked in the TMC mid-office. If the TMC does not feed them into the booking flow, travelers do not see them when they book their next trip, and the credits expire. Stacked programs commonly forfeit 2%–3% of air spend this way. A daily synchronization clause with fee credits for feed failures moves that risk back to the TMC.

Executive briefing

Bring this page’s numbers. Leave with a recovery plan.

A 30-minute call with a senior consultant, not a sales rep. We review the result you just modeled, tell you which savings are real for your program, and quote a fixed fee or contingency basis on the call.

  1. 01 We reply within one business day.
  2. 02 Mutual NDA before any invoice or contract is shared.
  3. 03 Written scope and fee basis within 48 hours of the call.

Request an executive briefing

We use your details only to reply to this request. No mailing lists, no resale. Privacy.