SAP Concur is acquired by most large enterprises as part of a broader SAP or travel management procurement, often without the detailed commercial scrutiny applied to core ERP licences. The result is that Concur is one of the most consistently over-purchased SaaS products in the enterprise portfolio. In our SaaS licence optimisation engagements, Concur is among the top five products for identifying immediate cost reduction opportunities — with average savings of 22% at first review and 30–35% at renewal with structured negotiation.
Concur's Commercial Structure
SAP Concur uses a modular, per-user subscription model. The core modules are Concur Expense, Concur Travel, and Concur Invoice. Each module is licensed separately, and users who require access to multiple modules require licences for each. This modular structure creates over-spend risk when organisations provision users for modules they don't actively use — a common occurrence when Concur is rolled out enterprise-wide and later adoption by certain user populations falls below expectations.
Core Concur Modules
| Module | Primary Function | Typical Annual Per-User Cost | User Measurement |
|---|---|---|---|
| Concur Expense | Expense reporting, approval, reimbursement | £60–£120 | Active submitters or approvers |
| Concur Travel | Travel booking, policy compliance, itinerary | £80–£160 | Active travellers or travel arrangers |
| Concur Invoice | AP invoice processing, PO matching | £50–£100 | Invoice processors and approvers |
| Concur Request | Pre-trip approval, travel requests | £25–£60 | Requestors and approvers |
| Concur Detect | AI-powered expense audit and compliance | Additional service fee | Volume-based |
These are indicative ranges based on enterprise-scale agreements. Actual pricing varies significantly based on total user count, contract term, the specific Concur edition (Standard vs Professional), and whether Concur is purchased as part of an SAP bundle or standalone. List pricing for Concur Travel and Expense combined typically runs £150–£240 per user per year for smaller organisations; enterprise agreements with 10,000+ users can achieve pricing in the £80–£120 combined range with proper negotiation.
The Active User Problem
One of the most common Concur over-spend drivers is the gap between provisioned users and genuinely active users. Concur contracts are typically structured around a "provisioned user" count — all users with active Concur accounts — rather than users who have submitted at least one expense, made a booking, or processed an invoice within a defined period.
For large enterprises with significant workforce variation — project-based organisations, seasonal businesses, or companies with high staff turnover — the provisioned user count can exceed active users by 20–40%. Employees who have left the organisation, employees on extended leave, and employees who were provisioned for anticipated travel that never materialised all contribute to provisioned-but-inactive populations that continue generating licence fees.
Commercial Insight: Negotiating your Concur contract on an "active user" metric rather than a "provisioned user" metric can reduce Concur spend by 15–25% in organisations with typical workforce variability. SAP Concur resists this metric shift because it reduces revenue predictability, but it is achievable as part of a structured renewal negotiation — particularly if you can demonstrate your actual vs provisioned user delta from system data. Advisory firms including Redress Compliance and Atonement Licensing regularly secure active-user based pricing in enterprise Concur negotiations.
Concur Standard vs Professional Edition
SAP Concur is available in Standard and Professional editions. The distinction has significant cost and capability implications that are not always clearly explained in the initial sales process.
Concur Standard
Concur Standard is SAP's simplified, mid-market edition. It provides core expense and travel management functionality with limited customisation capability and a more constrained integration framework. Standard edition is typically appropriate for organisations with 50–1,000 employees, straightforward travel and expense policies, and limited integration requirements. Standard edition pricing is typically 20–30% lower than Professional on a per-user basis but offers meaningfully less flexibility.
Concur Professional
Concur Professional is the enterprise-grade edition with full customisation, extensive integration capabilities (including deep SAP ERP integration through the SAP Concur App Centre), configurable workflow, complex policy rules, and the full Concur Detect audit capability. Professional is required for most large enterprise deployments — particularly organisations that need Concur to integrate with SAP ERP for posting expense data and GL allocation.
Organisations that have been sold Professional edition when Standard would meet their requirements are paying a 20–30% premium without the corresponding benefit. Conversely, organisations running Standard that have genuinely outgrown its capabilities should evaluate the Professional upgrade economics carefully before committing — the functionality gap can generate substantial operational costs that far exceed the licence price difference.
Concur Pricing Benchmarks
Understanding the market for Concur pricing helps organisations assess whether their current agreement is competitive. Based on our enterprise Concur negotiation engagements, the following benchmarks represent achievable pricing for well-negotiated multi-year enterprise agreements:
| Organisation Size | Expense Only | Travel Only | Travel + Expense Bundle |
|---|---|---|---|
| 1,000–5,000 users | £75–£100/user/yr | £90–£130/user/yr | £140–£180/user/yr |
| 5,000–15,000 users | £60–£85/user/yr | £75–£110/user/yr | £110–£150/user/yr |
| 15,000+ users | £45–£70/user/yr | £60–£90/user/yr | £85–£120/user/yr |
These benchmarks are for Concur Professional edition, active-user metrics, three-year commitments. Standard edition pricing is approximately 20–25% lower. If your current Concur contract pricing falls above these ranges, you are likely overpaying and should initiate a renegotiation conversation before your next automatic renewal date.
Concur Renewal Negotiation Strategy
Concur renewal negotiation differs from core SAP ERP negotiation in several important respects. Concur's competitive landscape has evolved significantly — while SAP Concur retains dominant market position, credible alternatives from Workday (Expenses), Expensify, TripActions Liquid, and Chrome River provide genuine switching optionality for mid-sized organisations. For large enterprises, the switching cost from Concur is substantial (deep ERP integrations, historical data, global travel programme dependencies) but the threat of alternative evaluation is a valuable negotiation signal even if actual switching is unlikely.
Effective Concur Negotiation Levers
The most effective levers in Concur renewal negotiations are: active user metric conversion (as discussed above); competitive pricing benchmarking with documentation; contract term flexibility (Concur strongly prefers three-year terms; negotiate annual break clauses in return for pricing concessions rather than accepting a long term without exit optionality); module rationalisation (review whether all provisioned modules are genuinely needed and remove unused module licences before renewal); and bundling leverage when Concur is part of a broader SAP renewal conversation.
For organisations that run SAP ERP alongside Concur, timing the Concur renewal to coincide with an SAP ERP renewal or S/4HANA migration negotiation provides meaningful additional leverage. SAP's account teams value total relationship revenue — a combined SAP ERP and Concur negotiation creates pricing flexibility that a standalone Concur renewal does not.
Concur and SAP Integration Licensing
The integration between SAP Concur and SAP ERP (whether ECC or S/4HANA) involves specific technical connectors that have their own licensing implications. The standard SAP Concur Connector for SAP ERP is available through the Concur App Centre and does not require separate BTP licensing for basic GL posting integration. More complex integrations — real-time cost object validation, project-based expense allocation, multi-system approval workflow — may draw on BTP Integration Suite services and generate BTP credit consumption. See our SAP BTP Licensing guide for the integration cost framework.
For organisations on RISE with SAP, the standard Concur integration content is typically available through the bundled BTP Integration Suite entitlement, but complex customisations may require additional BTP credits. Validating your integration architecture against the RISE BTP entitlement before go-live avoids unexpected consumption overruns.
Key Concur Cost Reduction Actions
Before your next Concur renewal, take these actions to maximise your negotiation position: audit your provisioned vs active user count and calculate the gap; identify any modules provisioned but not actively used; benchmark your current per-user rates against the market ranges above; document any competitive alternatives you have evaluated; and time your renewal negotiation to begin at least 90 days before contract expiry — Concur's auto-renewal clauses typically activate 30–60 days before expiry and remove your negotiation leverage if triggered.
Our SaaS licence optimisation practice provides Concur-specific negotiation support, and our SAP vendor practice covers the full SAP portfolio including Concur, SuccessFactors, Ariba, and core ERP. See also our complete SAP Licensing Guide and the SAP Negotiation Playbook for downloadable frameworks.