SAP Concur Licensing Guide for CIOs and CTOs: Cost Control, Negotiation, and Governance

What CIOs and CTOs Need to Know About Concur Licensing

SAP Concur is one of the most widely deployed enterprise SaaS applications in the world — covering travel booking, expense management, and invoice processing for organisations from the Fortune 100 down to mid-market businesses. It is also consistently under-negotiated. The reason is simple: Concur is a line-of-business application that typically sits in Finance or HR's budget, managed by teams who do not regularly negotiate enterprise software contracts. When it comes up for renewal, the default is to renew on broadly similar terms, accept the SAP-proposed rate, and move on.

CIOs and CTOs who engage directly with Concur commercial strategy — treating it as part of the broader SAP relationship rather than a standalone SaaS line item — consistently achieve materially better outcomes. This guide is designed for that audience. It covers the pricing model in detail, the key negotiation levers, the governance disciplines that prevent cost drift, and the integration architecture decisions that have real licensing consequences.

How SAP Concur Pricing Works

Unlike most enterprise SaaS, which charges a flat per-seat subscription, SAP Concur uses a transaction-based pricing model. The specific metric depends on the module:

Concur Expense

Concur Expense is priced per expense report submitted. Every time an employee completes and submits an expense report through Concur, regardless of the report's value or the number of line items it contains, it counts as one billable transaction. Standard enterprise rates vary significantly, but starting rates often sit around $9 per report — significantly higher for standard contracts without negotiated discounts.

The practical implication is that two organisations with the same number of employees can have dramatically different Concur Expense costs depending on how frequently their employees travel and submit. A professional services firm with consultants submitting weekly expense reports will pay far more than a manufacturing company where only a small percentage of employees expense anything. The pricing model rewards high submitters (the marginal cost of each report becomes less significant at scale) and penalises organisations that negotiate a flat per-report rate without considering their actual submission frequency.

For organisations with 12 months of actual submission data — and most do — the correct negotiation approach is to anchor on total annual transaction volume, negotiate an enterprise flat-rate structure at a discounted per-report rate, and include volume bands that reduce the per-report rate above defined thresholds. Flat-rate structures become commercially superior to standard per-report pricing when employees average more than 8–10 expense reports per year. For organisations with road warriors submitting weekly, the saving from a properly negotiated flat rate can exceed 40% of the standard contract value.

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. The per-booking fee structure means that high-frequency travellers generate disproportionately high costs relative to lower-frequency peers. As with Expense, the correct negotiation approach is to model your actual booking volume by transaction type and anchor the commercial negotiation to that data.

A critical decision in Concur Travel licensing is whether to use SAP's native online booking tool (OBT) or connect a preferred third-party OBT through a Concur connector. Organisations with existing relationships with third-party booking tools — or organisations operating in regions where SAP's native OBT has limited coverage — may prefer a connected configuration. However, third-party OBT connectors typically add 20–40% to the effective per-booking cost through connector fees. Before choosing a connected architecture, the total cost comparison must include these fees.

Concur Invoice

Concur Invoice processes accounts payable documents and is typically priced per invoice processed or in defined annual bundles. For large enterprises processing thousands of invoices monthly, bundle pricing is almost always more favourable than per-invoice rates — but the bundle must be sized against actual volume, not projected volumes from the implementation pitch. Over-sized bundles create a similar dynamic to BTP credit agreements: you commit to a volume you cannot consume, the unused capacity expires, and the effective per-invoice cost exceeds what you would have paid on a smaller bundle.

The Hidden Costs of Concur

Beyond the headline per-report, per-booking, and per-invoice rates, several cost categories are commonly under-budgeted in Concur deployments.

Connector Fees

Concur's integration with third-party systems — HR systems for employee data, ERP systems for coding and posting, expense card programmes, and online booking tools — is managed through connectors. Some connectors are included in the base subscription; others carry additional per-connection fees, annual maintenance charges, or transaction-based fees. Before signing any Concur contract, require SAP to provide a complete schedule of connector fees for every integration planned in your architecture. This schedule is not included in the standard commercial proposal without being requested explicitly.

AI and Intelligent Audit Services

SAP Concur's Intelligent Audit service — which uses AI to flag non-compliant expenses, duplicate receipts, and policy violations — is available at an additional subscription cost above the standard Concur Expense license. For organisations with meaningful compliance exposure (financial services, pharmaceuticals, government contractors), Intelligent Audit provides genuine value. However, it should be negotiated as part of the initial contract, not added as a mid-term upgrade where the leverage for pricing is lower.

Implementation and Professional Services

Concur implementations are sold with a professional services component that typically covers configuration, integration testing, and user training. SAP's own professional services rates for Concur work are materially higher than those of certified Concur implementation partners — and the quality differential is not always in SAP's favour. For mid-to-large implementations, CIOs should require a separate competitive selection for implementation services rather than accepting the bundled SAP professional services proposal as a package.

Negotiation Strategy: How to Get the Best Concur Deal

Concur is a mature product with an established market. SAP has competed against Coupa, Expensify, Concur alternatives for travel-only, and other T&E platforms for long enough that meaningful discounts are available — but they are not volunteered. Here is the effective negotiation sequence.

Step 1: Build Your Transaction Baseline

Pull 12 months of actual expense reports submitted, travel bookings made, and invoices processed from your current system. If you are a new Concur buyer, this data comes from your legacy system. This baseline is the foundation of every commercial negotiation. SAP will propose a contract based on their assumptions about your usage; you should anchor every number to your actual data. Organisations that negotiate from actual transaction data routinely achieve 30–50% discounts off SAP's initial commercial proposal.

Step 2: Request an Enterprise Flat-Rate Proposal

Once you have established your transaction baseline, request two alternative commercial structures from SAP: a per-transaction rate card (SAP's standard proposal) and an enterprise flat-rate structure based on your total headcount or defined annual transaction ceiling. Model both against your actual and projected volume. For most mid-to-large enterprises, the flat-rate structure becomes financially superior above a moderate submission frequency, and it also provides cost predictability that per-report pricing does not.

Step 3: Use the Broader SAP Relationship as Leverage

The fact SAP's Concur sales team prefers you not to know: Concur is not commercially independent from the rest of your SAP relationship. Your SAP account executive has visibility across your entire SAP portfolio — RISE, Concur, Ariba, SuccessFactors — and the total annual contract value of your relationship determines the discretionary discount ceiling SAP is willing to apply to individual products. If you are in active RISE or S/4HANA negotiations, pulling Concur into the same commercial conversation — even if the renewal dates differ — gives your account team a reason to offer improved Concur pricing in exchange for progress on the ERP deal. This bundling leverage consistently produces better outcomes than treating Concur as a standalone renewal.

Step 4: Lock Auto-Renewal and Price Escalation

Concur contracts include auto-renewal provisions with defined cancellation notice windows. Unlike the broad enterprise SaaS market where 60–90 days is standard, some Concur contracts have shorter windows — and missing the cancellation window locks you in for another year at existing terms. Confirm your notice requirement in writing. Additionally, ensure your contract includes an explicit cap on price escalation at renewal — a clause limiting annual rate increases to CPI or a fixed percentage (typically 3–5%). Without this protection, SAP can apply material rate increases at renewal without breaching the contract.

Governance: Keeping Concur Costs Under Control Between Renewals

The commercial risk in Concur is not only at renewal. Several patterns cause cost to drift materially between renewal cycles.

Leavers and Joiners

In seat-based SaaS, removing inactive users is straightforward — unused seats create obvious savings. In transaction-based Concur pricing, the equivalent discipline is monitoring submission frequency rather than user count. However, orphaned user accounts — accounts for employees who have left the organisation but remain active in Concur — can still submit expense reports (sometimes fraudulently, sometimes through internal process failures). Monthly reconciliation of Concur active users against HR headcount data is the minimum governance standard.

Policy and Submission Frequency

Under per-report pricing, expense policy design has a direct cost implication. Organisations that require employees to submit one report per trip will pay more than organisations that consolidate receipts into monthly reports. Where per-report pricing is in place, aligning expense policy to minimise unnecessary report fragmentation can reduce billable transaction volume by 15–25% without any change to reimbursement practice.

Integration Governance

Concur integrations — to ERP, to HR, to card providers — require periodic review. Integration configurations that were correct at go-live can drift as the underlying systems evolve, producing duplicate records, mis-coded expense categories, or data quality issues that inflate audit costs. Annual integration audits should be a standard component of Concur governance, not an exception triggered by a problem.

Concur in the Context of an SAP Audit

SAP conducts licence audits across its product portfolio, and Concur is not exempt. For organisations running Concur alongside on-premise SAP systems, specific audit risks apply: named users in the on-premise system who also access Concur through integration interfaces, without clear contractual coverage for both access types; and integration flows between Concur and S/4HANA or ECC that generate document counts subject to Digital Access licensing.

The Concur–ERP integration for expense posting is the most common source of Digital Access exposure in Concur deployments. When expense reports posted in Concur create journal entries, cost centre postings, or purchase requisitions in S/4HANA or ECC through an automated interface, each of those documents may count under SAP's Digital Access licensing rules if the interface is not covered by the relevant contractual provision. Organisations that deployed Concur before the Digital Access model was introduced — i.e., before 2018–2019 — should have their current contract position reviewed against actual integration usage.

Client Pattern: The Unchallenged Renewal

A global logistics company we advised had been on the same Concur Expense per-report rate for six years. No one had renegotiated at renewal — the contract had been auto-renewed twice, each time with a 5% rate increase accepted without challenge. When we were engaged twelve weeks before the third renewal window, we pulled 24 months of actual submission data, modelled an enterprise flat-rate alternative, and benchmarked the current rate against market comparables for organisations of similar size and submission frequency.

The findings: the client was paying $11.40 per report — 27% above the market median for their volume tier. An enterprise flat rate based on actual submission volume would have reduced total annual Concur Expense cost by 38%. The third renewal was renegotiated before the auto-renewal window closed, converting to a flat-rate structure at a rate 31% below the existing per-report price. The savings across the three-year renewal term exceeded $2.1 million. The work took eleven weeks from engagement to contract signature.

Concur Roadmap Considerations for CIOs

SAP continues to invest in Concur's AI and automation capabilities. The Intelligent Audit product has expanded its AI-driven policy enforcement features; integration with SAP Business AI (Joule) is in active development, with certain expense categorisation and anomaly detection features expected to leverage BTP-based AI capabilities. For CIOs planning long-term Concur architecture, understanding how these AI features will be licensed — whether bundled, BTP-credit-consuming, or separately priced — is a commercial question to raise explicitly with SAP before signing or renewing.

The broader SAP Intelligent Spend Group — which includes Ariba, Concur, and Fieldglass — has been positioned as a consolidated spend management platform. SAP periodically proposes "Intelligent Spend Group" bundles that package Ariba, Concur, and Fieldglass together at a stated combined discount. These bundles can be attractive when all three products are genuinely needed; they are poor value when one product is purchased primarily to achieve the bundle discount on another. Always model the bundle against your standalone requirements before accepting a combined proposal.

Summary: The CIO's Concur Checklist

Before your next Concur renewal, complete the following: pull 12 months of actual transaction data by module; benchmark your current per-report, per-booking, and per-invoice rates against market comparables; model a flat-rate enterprise alternative; audit your connector schedule for undisclosed fees; review your integration configuration for Digital Access exposure; and confirm your auto-renewal notice window. If you are in parallel SAP negotiations on RISE, S/4HANA, or any other major SAP product, pull Concur into that conversation rather than treating it as a standalone renewal. The leverage compounds when SAP sees the full relationship at stake.

Redress Compliance provides SAP commercial advisory services exclusively for buyers. We have led Concur renegotiations for organisations from 2,000 to 200,000 employees across financial services, manufacturing, professional services, and public sector. Contact us before your auto-renewal window closes.