SAP Concur Pricing:
Module Costs, Active-User Billing & Negotiation

How SAP Concur Pricing Works

Unlike most ERP or cloud SaaS platforms that rely on per-user or subscription models, SAP Concur employs a blended pricing approach combining active-user counts, transaction volumes, and travel & expense spend thresholds. This hybrid model reflects Concur's role as a workflow engine—it processes transactions (expense submissions, travel bookings, invoice approvals) rather than serving simply as a database or configuration tool.

Concur's three core products each carry distinct pricing mechanics:

• Concur Expense — Per-active-user or per-transaction fees based on monthly active employee counts submitting expense reports.
• Concur Travel — Booking fees tied to the volume of travel reservations booked through the platform, plus online/offline booking splits.
• Concur Invoice — Transaction-based pricing on the number of invoices processed through the approval workflow.

SAP bundles these modules into volume tiers and applies discount multipliers based on annual T&E spend, employee count, and contract term length. Renewal negotiations often hinge on defining "active user," proving actual usage, and leveraging competitive alternatives like Expensify, Coupa, or TravelPerk.

Concur Expense Pricing — Active User & Per-Transaction Model

Concur Expense is Concur's largest revenue stream and the module most organizations implement first. It handles employee expense submissions, receipt scanning, approval workflows, and reimbursement integration with finance systems.

Active-User Billing remains the dominant model. SAP defines an "active user" as any employee who submits at least one expense report in a measurement period (typically a 12-month period or rolling calendar year). Organizations pay a per-user-per-month (PUPM) fee multiplied by the peak active-user count observed in the contract year.

PUPM rates typically range from £6 to £22 depending on:

• Module bundle scope (Expense alone vs. Expense + Travel + Invoice)
• Employee count and T&E spend volume
• Contract term (3-year agreements attract 15–25% discounts vs. annual)
• Concur feature tier (Expense Standard vs. Expense Plus, which includes advanced approvals and custom workflows)

A 5,000-person organization with £2m annual T&E spend might pay £10–14 PUPM for Concur Expense Standard (approximately £50k–70k annually). The same organization using Expense Plus with advanced features could pay £16–22 PUPM (£80k–110k).

The Active-User Definition Problem creates ongoing disputes at renewal. SAP's contract language typically counts any user who submitted a report during the measurement period, but seasonal employees, contractors on fixed-term assignments, and users with sporadic travel can inflate peak counts. Sales teams often propose "committed" active-user baselines (e.g., "800 committed users") with overage fees above that threshold, capping your exposure.

Concur Travel Pricing — Booking Fees & TMC Integration

Concur Travel is priced on a per-booking basis. When an employee books a flight, hotel, or car rental through the Concur platform, SAP charges a transaction fee to the organization (not the employee).

Typical booking fees run £2–£8 per transaction depending on booking type and volume discounts:

• Online bookings (employee self-service through Concur's search interface) — typically £2–£4 per booking
• Offline bookings (via Travel Management Company (TMC) routed through Concur) — typically £4–£8 per booking (higher fee reflects TMC service delivery)
• Ancillary bookings (hotel-only, car-only, rail) — typically £2–£5 per transaction

Organizations making 10,000 travel bookings annually at an average £4 per booking would pay ~£40k/year for Concur Travel. Large multinational companies with 50,000+ annual bookings negotiate volume discounts that reduce per-booking fees to £1.50–£3.

TMC integration creates additional complexity. Many enterprises maintain relationships with TMCs for managed travel, duty-of-care compliance, and corporate rate negotiation. Concur supports TMC integration but SAP often charges premium fees for custom integrations or requires the TMC to route all bookings through Concur, potentially creating duplicate fees.

Concur Invoice Pricing — Per-Transaction Processing

Concur Invoice (formerly Concur Spend Visibility) handles three-way matching (PO, receipt, invoice), approval routing, and GL coding. Pricing is transaction-based: you pay per invoice processed through the system.

Per-invoice fees typically range from £0.30–£1.50 per invoice depending on volume and configuration:

• Volume tier 1 (up to 50,000 invoices/year) — £1.00–£1.50 per invoice
• Volume tier 2 (50,001–150,000) — £0.70–£1.00 per invoice
• Volume tier 3 (150,001+) — £0.30–£0.70 per invoice

Organizations processing 100,000 invoices annually might pay £50k–70k for Concur Invoice. At Tier 3 volumes (200,000+ invoices), costs can drop to £60k–80k, achieving sub-£0.50 per-invoice pricing through volume discounts.

Advanced features (machine learning-based coding suggestions, optical character recognition for manual invoices, multi-entity consolidation) carry premium add-ons of 10–20% above base transaction fees.

Concur Module Pricing Reference Table

The Active-User Definition Problem & Measurement Disputes

The single greatest source of cost variance and contract disputes in Concur arrangements centers on defining and proving "active users." SAP's standard definition is simple: any employee who submitted a report in the 12-month contract period counts as an active user. At renewal, SAP identifies the peak month active-user count from the previous year and applies that to your new PUPM rate.

However, organizations often see dramatic spikes in this metric due to:

• Seasonal workforce activation — Consultants, contractors, temporary roles in Q4 can inflate active-user counts by 20–40%.
• One-time reportable expenses — A business transition, office relocation, or acquisition can trigger unusual expense activity in a single month.
• New employee onboarding campaigns — Some organizations "audit" or "amnesty" old unsubmitted expenses, spiking active-user counts in a single month.
• Poorly managed deactivation — Terminated employees whose Concur access isn't immediately disabled can artificially inflate counts.

SAP's position: peak counts should be honored, as they represent the platform's maximum capacity demand. Your position: peak counts should be averaged or capped at a committed baseline to avoid paying for temporary spikes.

Effective negotiation strategies include:

• Proposing a "committed active user" baseline (e.g., 500 committed users at PUPM rate) with modest overage fees above that level (typically 30–50% of base PUPM for each additional 100 users).
• Excluding contractors and temporary workers from active-user counts, paying instead a separate per-contractor fee (typically £40–£80 per contractor per year).
• Negotiating a 12-month "measurement true-up" that allows you to demonstrate actual usage patterns and adjust subsequent-year fees downward if peak counts don't repeat.
• Implementing strict access controls and deactivation procedures to prevent terminated employees from inflating counts.

Bundle vs. Standalone Pricing & Volume Discounts

SAP incentivizes bundling Concur Expense, Travel, and Invoice into a single contract through volume discounts. Organizations purchasing all three modules typically receive 10–15% discounts on the combined cost versus purchasing each module independently.

Example:

• Concur Expense (1,000 active users × £10 PUPM × 12 months) = £120,000
• Concur Travel (12,000 bookings × £3.50 per booking) = £42,000
• Concur Invoice (80,000 invoices × £0.85 per invoice) = £68,000
• Total standalone pricing: £230,000
• With 12% bundle discount: £202,400 (savings of £27,600)

However, bundling locks you into Concur for all three use cases. If your Travel or Invoice usage is lower than expected, you may overpay. Conversely, some organizations use "best of breed" strategies—Concur for Expense and Travel, Coupa for Invoice—to optimize cost and feature fit. This typically results in 5–10% higher total cost but may deliver superior functionality in invoice processing.

Bundle Dynamics & Contract-Term Incentives

SAP applies aggressive discounts for multi-year commitments. A 3-year Concur agreement typically receives 15–25% cumulative discount versus annual renewal pricing. This incentivizes longer commitments but also locks you into fixed costs during a period when feature preferences, employee counts, or vendor alternatives may shift.

Best practice: Negotiate annual reviews within 3-year contracts that allow pricing adjustments based on demonstrated active-user counts or travel volumes, preventing you from being surprised at year 3 renewal.

Negotiation Strategy for Concur Renewal

SAP's Concur renewal strategy assumes organization inertia and usage growth. Most renewal proposals include 5–10% price increases, upward adjustments to active-user baselines, and minimal module consolidation. Effective negotiation reverses these assumptions through data, alternatives, and competitive pressure.

Step 1: Baseline Your Usage

Extract 24 months of usage data from Concur analytics (Expense Reports Dashboard, Travel Booking Report, Invoice Processing Dashboard). Document:

• Monthly active-user counts for Expense (not peak, but average and 75th-percentile)
• Quarterly travel booking volumes by type (online, TMC, ancillary)
• Monthly invoice volumes processed through Concur Invoice

This data forms the foundation of your counter-proposal. If your actual average active users are 600 but the previous contract's peak was 800, you're carrying £120k in unnecessary annual costs at renewal.

Step 2: Map Competitive Alternatives

Obtain quotes from three credible alternatives:

• Expensify — £3–£8 PUPM for Expense alone; strong mobile, receipt capture, and integration; weaker T&E reporting than Concur.
• Coupa — £8–£15 PUPM for Expense + Invoice; best-in-class Invoice processing and supplier management; moderate Travel integration.
• TravelPerk — £1.50–£4 per booking plus PUPM for Expense; strong ESG positioning and travel-first workflow; invoice capability still maturing.

Obtain formal pricing proposals from at least two; SAP will view these as credible threats. A proposal from Expensify for £50k/year (if you downgrade from Concur Expense Plus to Expense Standard) or Coupa for £180k (Expense + Invoice bundled) creates meaningful leverage at renewal.

Step 3: Quantify Redirection Value

Calculate switching costs and benefits. If Expensify can deliver Expense for £50k vs. Concur's £80k, but requires 2 months of implementation and user training (£15k cost), the net 3-year NPV of switching is (3 × £30k) − £15k = £75k. Present this to SAP: "We're financially justified in switching unless you reduce Expense to £60k PUPM-equivalent."

Step 4: Propose a Committed Baseline Structure

Rather than paying peak-count pricing, propose a committed user baseline with modest overage fees:

• "500 committed Expense users at £10 PUPM (£60k/year), plus 50 overage users at £8 PUPM (£4,800/year), for a total of £64,800 if we hit 550 peak users."
• This protects SAP from abandonment (you're committing to a 500-user baseline) while protecting you from seasonal spikes.

Step 5: Negotiate True-Up Clauses

Propose an annual true-up mechanism: at contract anniversary, if your actual average active-user count was 15% lower than the committed baseline, you receive a credit toward the following year's fees. This aligns risk and incentivizes both parties to forecast accurately.

Step 6: Consolidate Modules Strategically

If you're bundling Expense + Travel + Invoice, quantify the 12–15% bundle discount and use it as leverage: "We'll commit to a 3-year Expense + Travel + Invoice bundle if you apply the full 15% discount and honor our committed-user baseline."

T&E Spend as a Negotiation Lever

SAP's Concur team often references total organizational T&E spend as a factor in PUPM pricing. Organizations with higher per-capita spend are viewed as lower-risk (more likely to invest in travel and expense management) and may receive slight PUPM discounts. Conversely, organizations with flat or declining T&E spend can negotiate lower rates or shorter contract commitments.

If your organization's T&E spend is £5m+ annually, you're a "key account" in SAP's view. Use this: "Our £6m annual T&E spend makes Concur valuable, but only if pricing reflects that volume. Competitors are proposing 15–20% lower rates at our spend level. Match their pricing, or we'll evaluate alternatives."

Renewal Timing & Competitive Pressure

Begin renewal negotiations 120–180 days before contract end. Early engagement gives you time to evaluate alternatives without the pressure of a contract gap. SAP's sales team is highly incentivized to retain customers and will often offer improved pricing 90–60 days before expiration, when switching costs become meaningful to you.

Openly discuss alternatives in RFP or negotiation communications. Phrases like "We've obtained competitive proposals from Expensify and Coupa and are evaluating all options" signal that you're serious about alternatives and encourage SAP to be aggressive on pricing.

Next Steps: Get Expert Advice

Concur's complexity—blending active users, transaction volumes, bundle economics, and spend thresholds—makes professional negotiation guidance valuable. Organizations often leave 15–25% savings on the table at renewal by accepting SAP's initial proposal, failing to challenge active-user counts, or underestimating competitive alternatives.

For deeper exploration of SAP licensing strategy across SuccessFactors, S/4HANA, and BTP, see our Complete SAP Licensing Guide. For broader SaaS cost optimization, review our SaaS License Optimization service.