SAP Concur (travel and expense management) and SAP SuccessFactors (cloud HCM) sit in a unique commercial position: they are SAP products but operate largely independently of the core SAP ERP licence. Both use subscription pricing per employee or transaction. Understanding how these products are priced, how they interact with your broader SAP relationship, and how to use bundling as leverage is essential for reducing your total SAP spend.
SAP Concur is a cloud-based travel and expense (T&E) management platform. Unlike core SAP ERP which uses named-user licensing, Concur pricing is primarily transaction and employee-based. The platform manages corporate travel bookings, expense claim submissions, invoice processing, and pre-trip purchase approvals — each with its own cost driver.
Employee-based SaaS: Concur's primary pricing model is monthly per-active-user, typically in the range of $10–25 per user per month depending on module access, deployment scope, and negotiated volume discounts. The critical negotiating point is what "active user" means — many organisations contract for all employees but have only a fraction actually submitting expenses or booking travel.
Transaction-based: Some Concur modules, particularly Concur Invoice, can be priced per transaction or document processed. This makes the cost highly variable depending on invoice volume, supplier count, and approval workflow complexity.
Module pricing: Concur Travel, Concur Expense, Concur Invoice, and Concur Request are separately priced. Most enterprises subscribe to 2–3 modules but contract for capabilities they deploy only partially. Module bundling within Concur itself can create apparent savings that are offset by unused entitlements.
| Concur Module | Primary Function | Pricing Basis | Common Overpayment Risk |
|---|---|---|---|
| Concur Expense | Expense claim submission and approval | Per active user/month | High — many users with zero claims counted |
| Concur Travel | Corporate travel booking and policy enforcement | Per active traveller/month | High — booking patterns vary seasonally; extended leave reduces active count mid-year |
| Concur Invoice | AP invoice capture and approval | Per transaction or user | Medium — transaction volume misestimated at procurement; seasonal variation |
| Concur Request | Pre-trip and purchase request approval | Per user/month | Low — but often bundled unnecessarily |
SAP SuccessFactors is SAP's cloud Human Capital Management (HCM) suite, covering recruitment, onboarding, performance management, learning, succession planning, analytics, and payroll. Licensing is employee-based — you pay a subscription fee per employee per module, regardless of whether that employee actively uses the module. This creates significant overpayment exposure in most deployments.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
Employee Central: The foundational module — all other SuccessFactors modules require Employee Central licensing. Pricing typically ranges from $6–12 per employee per month (PEPM) depending on contract scope, volume, and negotiation leverage. Employee Central contains the authoritative employee and organisational data, compensation and benefits setup, and role/competency definitions.
Talent modules: Recruiting, Onboarding, Performance & Goals, Succession, Learning, and Workforce Analytics are licensed separately, each at $3–8 PEPM. The critical negotiating point: do you actually deploy all of these, or are some planned but undeployed? Many organisations contract for the "full HCM suite" during an ambitious transformation, then deploy only 2–3 modules, leaving 3–4 modules undeployed yet accruing cost annually.
Payroll: Country-specific payroll modules are generally higher-cost add-ons, ranging from $5–12 PEPM depending on complexity (US payroll is simpler than multi-country European payroll, for example).
Headcount-based, not active-user-based: SAP's licensing is based on all employees in the system, including inactive employees, those on unpaid leave, and contractors. A company of 10,000 employees pays for all 10,000 in Employee Central, even if only 7,000 are actively working. This is significantly different from Concur, which can be negotiated on active-user basis.
Contractors and contingent workforce: If your contingent workers are loaded into Employee Central, they count as licensed employees. This often surprises organisations during renewal negotiations when they realise temporary workers, freelancers, and consulting staff have been licensed at full employee rates.
Talent module licensing flexibility: Unlike Employee Central (mandatory), talent modules can be licensed on a role-based or selective basis. You do not need to license all 10,000 employees for Recruiting if only 200 are hiring managers or recruiters. However, SAP sales teams often position this as requiring separate "named user" licensing, which introduces complexity and often results in over-purchasing.
Many SuccessFactors contracts include auto-renewal of all contracted modules even if deployment is partial or planned but incomplete. A contract signed in 2024 for "Employee Central + full talent suite" may still be renewing all six modules in 2026 even though only three were deployed. Review your actual deployed footprint before negotiating renewal.
SAP actively promotes bundled pricing for Concur + SuccessFactors + core SAP ERP as part of broader commercial frameworks like RISE with SAP or enterprise HANA licensing deals. The pitch: buy everything together, get a blended discount. The commercial reality is more nuanced.
Separate commercial organisations: Concur has its own SAP division with semi-independent sales, product, and pricing authority. SuccessFactors similarly operates with considerable commercial autonomy. Bundling deals must often be assembled across these business units by the SAP account team — this coordination takes time and requires escalation to senior SAP commercial leadership.
Inflated list prices: The "bundle discount" is often fabricated from what were already inflated list prices. SAP's published list pricing for Concur and SuccessFactors is typically 20–30% higher than the effective rates achieved by informed negotiators. The "bundle discount" is often just bringing list price down toward market reality, not a genuine additional concession.
Hyperscaler and ERP leverage: If your Concur and SuccessFactors renewals align with a RISE subscription, core ERP renewal, or hyperscaler infrastructure decision (AWS, Azure, GCP), you can use the total contract value under discussion to negotiate better terms across all products. A $5M ERP + $800K SuccessFactors + $600K Concur bundle gives you far more leverage than negotiating Concur and SuccessFactors separately.
The real leverage in bundling is not the discount SAP offers — it is the competitive threat you create when negotiating each product separately, then using competitors for each product to pressure the bundle price down further. When you can credibly demonstrate that Workday pricing for SuccessFactors capabilities and Coupa pricing for Concur are both lower than SAP's bundled offer, SAP's negotiating position weakens significantly.
Five primary areas where enterprises consistently overpay for Concur and SuccessFactors:
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
SuccessFactors counts all employees in the system. A 10,000-person company with a significant contingent workforce (contractors, temporary staff, interns) is effectively licensing 10,000+ people for Employee Central. When negotiations begin, you should have an accurate headcount breakdown: full-time employees, part-time, contractors, contingent workers. Negotiate a reduced headcount that reflects only permanent, full-time employees, and carve out contractors to lower-cost contingent-worker licensing if available.
During transformation planning, organisations often contract for the "full talent suite" (Employee Central + Recruiting + Onboarding + Performance & Goals + Succession + Learning). Implementation timelines slip, budgets are re-prioritised, and by contract renewal, only 2–3 modules have been deployed. Yet all six modules continue to accrue cost. Before renewal, audit your actual deployed footprint and exclude undeployed modules from the renewal contract.
Both Concur and SuccessFactors contracts typically include automatic annual price escalations of 3–5% (sometimes higher if tied to inflation or SAP's own cost-of-living adjustments). Over a 3-year term, a 4% annual escalation compounds to a 12.5% total cost increase. Negotiate escalation caps at CPI (Consumer Price Index) or a fixed 2% per year, whichever is lower.
Headcount-based contracts signed during optimistic growth phases (or post-acquisition) become overcommitted when actual headcount does not materialise. A company that signed a SuccessFactors contract for 12,000 employees but has only 9,500 after restructuring is paying for 2,500 unused licences. Negotiate annual true-ups that allow headcount reduction with 30–60 days notice, or better yet, include a headcount adjustment mechanism at each anniversary.
Both platforms sell "success packages" (premium implementation support), managed services, and training bundles that often auto-renew annually unless explicitly cancelled. These are frequently unnoticed budget items. Before renewal negotiation, audit your actual consumption of professional services and renegotiate or eliminate auto-renewal where value is unclear.
Before entering bundling discussions, get competitive quotes for each product independently. Request pricing from Workday (strongest SuccessFactors competitor for HCM functionality) and Coupa or Expensify (Concur competitors for T&E). Share these alternatives with the SAP account team early, signalling that you are evaluating competitors. This creates immediate competitive pressure and anchors SAP's negotiating position downward before bundle discussions begin.
If Concur and SuccessFactors renew on different dates, work to align them contractually. SAP is far more motivated to offer bundle discounts when both products are at stake simultaneously. If one renewal is in March and the other in August, you lose negotiating leverage on the August renewal (SAP has no immediate pressure to concede). Request amendment of one contract to synchronise renewal dates.
If your core SAP ERP renewal or RISE subscription renewal is approaching within 6 months of Concur/SuccessFactors renewal, explicitly link all three into a single commercial negotiation. The larger the total contract value under discussion, the more senior the SAP commercial leadership gets involved, and senior leadership tends to have more flexibility on bundled pricing. A $10M negotiation (ERP + RISE + SuccessFactors + Concur) involves SAP's VP of Enterprise Accounts; a $1M negotiation (Concur alone) involves SAP's regional sales team.
Concur is not strictly employee-count-based like SuccessFactors — it can be negotiated on an active-submitter or active-user basis. Challenge SAP's assumption that all employees will be Concur users. Provide 12 months of actual Concur submission data showing how many unique expense submitters and travel bookers your organisation actually has. Negotiate pricing based on that active-user baseline plus a buffer (say, 115% of your 12-month average active users). This can reduce Concur costs by 20–40% if your actual usage is significantly below your headcount.
Do not accept a "full suite" default. Go through each module (Employee Central, Recruiting, Onboarding, Performance, Succession, Learning, Analytics, Payroll) and explicitly state: deployed, planned for deployment, or exclude from contract. Exclude all planned-but-undeployed modules. This reduces SuccessFactors cost and creates a clear baseline for renewal negotiations — you cannot be surprised by undeployed modules continuing to accrue cost.
Push back on any escalation clause above inflation. Negotiate a cap of 2–3% per year or CPI (whichever is lower). Over a 5-year term, this saves 5–10% vs. uncapped 4% escalations. This is particularly important for SaaS products like Concur and SuccessFactors where underlying technology costs (cloud infrastructure, security patching) are often declining, not rising.
For new SuccessFactors modules you intend to deploy (e.g., moving from Employee Central–only to Employee Central + Recruiting + Learning), push for implementation credits — SAP pays for or subsidises the deployment. SAP is often more willing to flex on services pricing (implementation) than on licence cost, and implementation credits effectively reduce your cost of deploying new modules. This creates incentive alignment: SAP wants modules deployed because deployed modules are stickier and harder to replace.
SAP's fiscal year ends September 30. Concur (historically a separate company before SAP acquisition) operates on calendar-year internal metrics. Both have strong quota pressure at different times: SAP enterprise team at September quarter-end, Concur commercial team at December year-end. If your renewal is approaching in August or November, signal to SAP and Concur that you can accelerate closure in exchange for price improvement. The urgency of meeting FY targets creates negotiating leverage.
SAP pushes for longer terms (5 years) to lock in recurring revenue. Shorter 3-year terms preserve your renegotiation leverage in a fast-moving market. Concur and SuccessFactors are cloud products where feature releases, competitive positioning, and pricing models evolve rapidly. A 5-year lock-in at fixed escalation is risky. Negotiate 3-year terms with optional renewal pathways. If SAP offers a discount for a 5-year commitment, ensure it is material (15%+), which offsets the loss of flexibility.
Never pay for multiple years upfront. Always negotiate annual or quarterly payment terms. Multi-year upfront payments remove your leverage for mid-contract renegotiation (if SAP makes a major price cut to a competitor threat, you cannot benefit). Annual payment keeps SAP motivated to maintain service quality and competitive terms throughout your contract.
If your Concur or SuccessFactors deployment is phased (e.g., rolling out SuccessFactors Recruiting in year 1, Learning in year 2, Succession in year 3), negotiate ramp pricing that reflects the phased rollout. Pay lower licence fees in years 1–2, stepping up to full pricing in year 3. This aligns your costs with your actual deployment timeline and creates mid-contract checkpoints for re-evaluation.
Include explicit clauses on data export and migration rights. Concur stores travel, expense, and invoice data; SuccessFactors stores employee, payroll, and talent data. Ensure your contract includes 30-day post-termination data export in standard formats (CSV, XML). The threat of switching to Workday or Coupa is only credible if you can demonstrate it is operationally feasible.
You do not need to complete a full RFP for these alternatives — simply requesting pricing from Workday and Coupa, sharing that you are evaluating alternatives with the SAP account team, creates immediate commercial movement. SAP's account managers understand that losing a customer to Workday or Coupa is a strategic threat; pricing improvement often follows quickly once competitive alternatives are explicitly on the table.
Begin internal usage audit of both platforms. For Concur: pull reports on unique expense submitters, travel bookers, and invoice approvers over the prior 12 months. For SuccessFactors: audit employee headcount (breakdowns by FT/PT/contingent), actual module usage (log in counts by module), and identify undeployed modules still appearing on contract. This data becomes your anchor point for renegotiation.
Request competitive quotes from Workday (for SuccessFactors), Coupa and Navan (for Concur). You need pricing on comparable feature sets — not bare-bones alternatives. Share intent to evaluate alternatives with SAP proactively. Send a message like: "We are conducting an RFI with Workday and Coupa to ensure we are getting competitive value. We prefer to stay with SAP if the economics work."
Engage with SAP account team on bundled renewal discussion. Share your usage audit data (actual active users on Concur, actual deployed modules on SuccessFactors). Establish internal BATNA (best alternative to negotiated agreement): what is the maximum acceptable all-in cost for Concur + SuccessFactors for the next 3 years? This BATNA becomes your walk-away threshold.
Submit formal commercial proposal to SAP with target contract structure: (a) active-user count for Concur (with supporting data), (b) deployed-only modules for SuccessFactors, (c) 3-year term with 2% annual escalation cap, (d) annual payment, (e) implementation credits for any new module deployment. Explicitly ask for SAP's response within 14 days.
Finalise contract terms. Do not sign until escalation clauses, minimum commit provisions (if any), and exit rights are resolved. Request Concur's minimum transaction/user commit language be tied to your 12-month average (plus reasonable buffer), not an arbitrary inflated number. For SuccessFactors, ensure headcount adjustment rights are clearly stated (e.g., "Licensee may reduce licensed headcount annually by 10% with 60 days' notice").
For expert guidance on SAP cloud product bundling and renewal strategy, see our ranking of the best SAP negotiation consulting firms.
Our panel includes SAP contract specialists who have restructured Concur, SuccessFactors, and ERP bundles for global enterprises. Expect 15–25% savings through strategic bundling and active-user optimization.