SAP Concur Licensing Guide
Travel, Expense, Invoice — Costs, Connectors & Optimisation

SAP Concur’s Licensing Model: Three Modules, Three Fee Structures

SAP Concur comprises three separately licensed modules — Concur Expense, Concur Travel, and Concur Invoice — each with a distinct pricing mechanic. Unlike most enterprise software sold on a per-user-per-year basis, Concur’s transactional modules accumulate costs based on activity volume. This makes your total cost of ownership difficult to predict at deal signature and easy for SAP’s account team to understate during initial positioning.

SAP does not publish Concur list prices. All enterprise quotes are custom, based on a combination of user count, transaction volume, module selection, contract term, and the existing commercial relationship between your organisation and SAP. This opacity benefits SAP during negotiation — enterprise buyers without independent benchmarks regularly overpay by 20–40% compared to what comparably sized organisations in the same industry segment achieve.

The starting point for any Concur negotiation is a clear definition of your actual requirements: which modules, how many active users (distinct from total employees), projected transaction volumes per annum, and integration requirements. Buyers who define these parameters before engaging SAP’s account team consistently achieve better commercial outcomes than those who accept SAP’s initial sizing. Book a contract review with Redress before you begin the Concur renewal or expansion process.

Concur Expense: Cost Drivers and Optimisation

Concur Expense is typically priced on a per-expense-report basis — meaning you pay a fee for each expense report your employees submit through the platform, regardless of the report’s value. Some enterprise agreements convert this to a hybrid model: a base subscription covering a defined number of annual reports, plus an overage rate for submissions above that threshold.

The per-report model penalises high-volume low-value submitters disproportionately. A field sales organisation submitting 12 reports per person per year generates a very different cost profile than a head office team averaging two reports per year — even if both groups have the same headcount. SAP’s standard sizing uses average submission rates across all users, which systematically underestimates cost for transaction-heavy business units.

Optimisation tactics that reduce Concur Expense cost without reducing adoption:

• Negotiate an enterprise flat-rate structure rather than per-report pricing once you have 12 months of actual submission data. Flat-rate contracts become cheaper than per-report above approximately 8–10 reports per employee per year.
• Exclude infrequent or inactive users from the contracted user base. SAP includes all provisioned users in the baseline; you pay for the allocation regardless of use. Audit and remove dormant accounts quarterly.
• Negotiate a submission-rate cap for the first contract year that reflects conservative projections, with an agreed expansion rate for subsequent years once actual volumes are established.

Concur Travel and Concur Invoice: Module-Level Costs

Concur Travel

Concur Travel is priced per booking transaction — typically a fee per airline ticket, hotel reservation, or car hire itinerary processed through the Concur booking tool. For enterprises with centralised travel programmes and volume commitments with preferred suppliers, the per-booking fee adds a layer of cost that travel managers rarely account for when calculating total programme spend.

Organisations booking 10,000–50,000 annual travel transactions can negotiate a tiered rate structure where the per-booking fee decreases as volume increases. SAP also offers a monthly flat-rate option for high-volume programmes — typically attractive once annual booking volume exceeds 30,000 itineraries. If your organisation is considering connecting Concur Travel to an existing online booking tool (OBT) via a third-party integration rather than using SAP’s native booking engine, confirm whether the connector fee structure makes this commercially viable — third-party OBT connectors typically cost 20–40% of the first-year subscription in implementation fees.

Concur Invoice

Concur Invoice (accounts payable automation) uses a per-invoice pricing model similar to Concur Expense’s per-report structure. Each invoice processed through the platform generates a transaction fee. For high-volume AP operations — organisations processing more than 100,000 invoices annually — the per-invoice model quickly makes a flat-rate enterprise agreement the more economical option. SAP will not volunteer this option; it must be requested explicitly during negotiation.

Concur Invoice integrations with ERP systems — SAP ECC, S/4HANA, Oracle, or third-party platforms — require certified connectors. SAP’s native S/4HANA connector is included in RISE with SAP agreements but is separately priced for ECC customers. Given that SAP ECC mainstream maintenance ends December 2027, ECC customers renewing Concur Invoice now should negotiate transition rights to the S/4HANA connector as part of the current deal rather than paying for it again post-migration.

Connector Fees: The Hidden Cost of SAP Concur Deployments

Concur’s SaaS architecture connects to HR systems (for employee master data), ERP systems (for cost centre coding and GL posting), credit card providers (for automated transaction import), and travel management companies (for itinerary data). Each integration point incurs implementation and, in some cases, ongoing connector subscription fees.

SAP maintains a Concur App Center with certified third-party integrations. App Center connectors are typically priced as annual subscriptions ranging from a few thousand to tens of thousands of dollars depending on the integration type and volume. For large enterprises deploying Concur alongside an S/4HANA migration — relevant context given the RISE with SAP commercial model — negotiate inclusion of the native SAP integration connector in the RISE bundle rather than purchasing it separately.

Key connector cost management principles:

• Map every integration requirement before signing. Each connector added post-signature is priced at standard rates with no negotiation leverage.
• For HR data integration (employee records, cost centres, reporting lines), SAP’s native SuccessFactors connector is cheaper to maintain long-term than a third-party middleware integration, but only if you already have SuccessFactors in scope.
• Credit card feed connectors — from Amex, Visa, Mastercard — are typically free from the card issuer’s side but may require a Concur-side configuration fee. Clarify before go-live whether this is included in your base subscription.

Concur negotiations that also cover SAP Ariba (for purchase-to-pay) benefit from bundling both products into a single SAP Spend Management agreement, which creates leverage on both sides of the deal and typically generates 10–15% better combined commercial terms than negotiating each product separately.

SAP Concur Negotiation Tactics for Enterprise Buyers

Concur negotiation is distinct from S/4HANA or RISE negotiation because the primary lever is volume — not the technology transition urgency that drives SAP’s behaviour in core ERP deals. SAP needs Concur retention to protect a revenue stream that is relatively independent of the S/4HANA migration cycle. That creates different commercial dynamics.

• Use renewal timing strategically. SAP’s Concur sales team operates on calendar-year targets. Renewals scheduled to close in October–December consistently achieve better terms than those signed in January–February. If your contract renewal date falls in Q1, consider requesting a short-term extension to move the negotiation into SAP’s Q4 window.
• Reference Expensify, Coupa, and Workday Expenses. These platforms have won enterprise accounts specifically from SAP Concur at renewal. Documented engagement with at least one credible alternative gives SAP’s account team the internal justification to offer improved pricing. SAP does not respond to implied competitive pressure; it responds to evidence of it.
• Lock in multi-year pricing at current rates. SAP Concur standard contracts include annual price escalation of 3–5%. A three-year deal with a 2% cap saves materially compared to three one-year renewals at standard escalation. Multi-year commitments also give SAP the revenue certainty it needs to approve discounts above 25% from standard rates.
• Negotiate transaction volume floors, not ceilings. SAP prices Concur based on projected volume. Negotiate a floor — the minimum you will pay regardless of actual submission volume — and ensure overage rates above that floor are pre-agreed at a discount to standard per-transaction rates. Do not accept contracts where overage rates reset to standard list pricing.
• Address connector fees as part of the subscription negotiation. SAP will default to pricing connectors separately. Bundling two or three key connectors into the base subscription is a standard negotiated outcome for large enterprise deals — it must be requested explicitly, not assumed.