SAP Concur Licensing Guide: Travel, Expense and Invoice Costs, Connectors and Optimisation

SAP Concur: Product Landscape and Module Structure

SAP Concur is not a single product. It is a portfolio of integrated applications covering travel booking, expense management, and invoice processing, which SAP acquired from Concur Technologies in 2014 for approximately $8.3 billion. The portfolio is structured around three primary modules — Concur Travel, Concur Expense, and Concur Invoice — each with its own pricing model, its own renewal timeline (unless co-termed), and its own commercial team within SAP.

Organisations can deploy any single module, any combination, or all three. The commercial terms for each are negotiated independently unless you explicitly push for a combined proposal — and SAP's default is to present modules separately, because doing so typically produces a higher aggregate contract value than a bundled proposal would. Understanding this dynamic is the starting point for effective Concur negotiation.

Beyond the three primary modules, the Concur portfolio includes Concur Audit (intelligent automated expense audit), Concur Drive (mileage tracking), Concur Detect (fraud and compliance analytics), and various integrations with travel management companies (TMCs), corporate card programmes, and ERP systems. Each of these generates additional cost either as a separate subscription or as a transaction-based add-on. Many are presented to buyers as standard inclusions; the contract will often reveal they are not.

Concur Expense: Pricing Model and Cost Drivers

Concur Expense is the most widely deployed module in the portfolio. It handles expense report submission, receipt capture, policy enforcement, approval workflows, and posting to the underlying ERP or financial system. The pricing metric is the expense report — not the employee, not the reimbursement value, and not the number of receipt lines.

The standard commercial model charges a per-report fee for each expense report submitted through the system. Market benchmarks suggest base rates in the range of $7–$12 per report for enterprise accounts without negotiated discounts, declining as annual submission volume increases. A 10,000-employee professional services firm where consultants submit weekly expense reports generates a very different Concur Expense cost than a 10,000-employee manufacturing firm where only 15% of employees ever expense anything. SAP's initial proposal will typically apply a rate based on assumed submission frequency; your actual submission data almost always tells a different story.

The critical negotiation decision is whether to remain on per-report pricing or convert to an enterprise flat-rate structure. Under per-report pricing, your annual cost is variable — it rises when travel increases and falls when it decreases, which provides some natural alignment with actual business activity. Under a flat-rate structure, you pay a fixed annual sum for Concur Expense regardless of submission volume. Flat rates become commercially superior when your employees average more than 8–10 expense reports per year. For organisations with substantial field sales, consulting, or executive travel populations, this threshold is typically exceeded. For back-office-heavy organisations, it may not be.

The analysis is simple with 12 months of actual data: divide your total annual Concur Expense invoice by the number of reports submitted to get your effective per-report rate. Then model the flat rate SAP is willing to offer. If the flat-rate breakeven is below your actual submission frequency, convert. If not, stay on per-report but negotiate the rate down using your volume as leverage.

Concur Travel: Pricing Model and the OBT Decision

Concur Travel is the online booking tool (OBT) component of the suite. It allows employees to search, compare, and book flights, hotels, and car hire within a single interface, with the organisation's preferred suppliers, negotiated rates, and travel policy embedded in the booking experience. Pricing is per transaction — per airline segment booked, per hotel night reserved, per car hire day processed. Transaction fees vary by booking type, by channel (GDS vs direct connect), and by negotiated volume.

The Concur Travel booking fee is separate from the GDS (Global Distribution System) fee charged for flight bookings. Most organisations using Concur Travel also pay GDS fees — Amadeus, Sabre, or Travelport — on top of the Concur platform fee. Both should be included in the total cost of ownership analysis. For organisations booking significant international itineraries, the combined Concur platform fee plus GDS fee per booking can exceed $30–$40 per trip, making it material against the total T&E programme budget.

The most consequential decision in Concur Travel architecture is whether to use SAP's native booking tool or connect a preferred third-party OBT through a Concur connector. Third-party OBT connectors are available for major platforms including Egencia, BCD Travel Online, and others. The commercial case for a connector configuration — retaining the preferred OBT while connecting reporting and compliance data to Concur — can be strong for organisations with established TMC relationships or travel programmes that have specific regional OBT requirements. However, third-party OBT connectors typically add 20–40% to the effective per-booking cost through Concur's connector fee. This cost is almost never in the headline commercial proposal and is frequently not in the implementation scope documentation either. Request a complete connector fee schedule before committing to an architecture decision.

Connector Fees: The Invisible Cost Category

Connector fees deserve specific attention because they represent one of the most consistently underbudgeted cost categories in Concur deployments. A "connector" in Concur terminology is any integration between Concur and a third-party system — your TMC's booking platform, your corporate card provider's transaction feed, your HR system for employee data, your ERP system for expense coding and posting. SAP's Connector Marketplace lists hundreds of pre-built connectors, with varying commercial models. Some are included in the base Concur subscription; others carry annual connection fees ranging from a few thousand dollars to $50,000 or more for high-volume, enterprise-grade integrations.

The critical mitigation is straightforward: before signing any Concur contract, request a formal connector fee schedule from SAP covering every integration in your planned architecture. SAP will provide this if asked; they will not provide it automatically. Map every connector against your integration requirements, confirm which are included and which carry fees, and include all fees in your total cost of ownership model. In our experience, organisations that complete this exercise before contract signature routinely discover that their actual total Concur cost is 25–40% higher than the headline subscription number SAP quoted.

Concur Invoice: Pricing and Bundle Structure

Concur Invoice manages accounts payable processing — capturing supplier invoices, routing them for approval, and posting approved payments to the ERP or financial system. It is the least well-known of the three primary modules but can represent significant value for organisations that currently handle AP through manual or semi-automated processes. Pricing is per invoice processed or, for higher volumes, through annual bundles that provide a defined number of invoice transactions per year.

Bundle pricing is almost always more cost-effective than per-invoice pricing for organisations processing more than a few hundred invoices per month. The critical sizing discipline is the same as for BTP credits: bundle at your actual or conservatively estimated annual volume, not at your aspirational or projected volume. Over-sized Invoice bundles create the same expired-capacity problem as over-committed BTP credit agreements — you pay for capacity you cannot consume, and SAP's standard terms do not provide for rollover of unused invoice entitlements.

Integrating Concur with SAP ERP: Licensing Considerations

For organisations running Concur alongside on-premise S/4HANA or ECC, the integration between the expense management platform and the ERP core carries important licensing implications. When expense reports submitted in Concur generate journal entries, cost centre postings, or purchase requisitions in S/4HANA through an automated interface, each document created in the ERP may count as a Digital Access document under SAP's current licensing rules.

SAP's Digital Access model, introduced as part of the 2018–2019 indirect access settlement framework, licenses certain document types by volume rather than by user. If your Concur–ERP integration generates documents that fall within the Digital Access scope, and your existing contract does not cover those documents through a DAAP (Digital Access Adoption Programme) agreement, you may have an uncontracted exposure. The magnitude depends on your transaction volume and the specific document types generated. Organisations posting tens of thousands of expense items per year through an automated interface should have their Digital Access position reviewed before their next SAP audit cycle.

Negotiation Playbook: Getting the Right Concur Deal

Effective Concur negotiation follows a consistent sequence. The first step is data collection: 12 months of actual transaction data by module, covering expense reports submitted, travel bookings made by type, and invoices processed. This data is the negotiation anchor — it tells SAP you are operating from facts, not assumptions.

The second step is market benchmarking. SAP does not publish list prices, but the market has produced sufficient intelligence about enterprise Concur rates to benchmark against. Organisations at comparable size and submission frequency serve as reference points. The target is to land in the bottom quartile of the market range — which is consistently achievable for organisations that negotiate proactively rather than accepting the renewal default.

The third step is model selection. Decide before entering the negotiation whether you want per-report pricing with a volume-based rate reduction, an enterprise flat-rate structure, or a hybrid — flat rate for predictable expense volume plus a lower per-report rate for overages. Present this as your preferred commercial framework and ask SAP to price against it, rather than accepting their default proposal as the starting point.

The fourth step — and the one most often missed — is using the SAP relationship as leverage. Concur is not commercially separate from your RISE, S/4HANA, or other SAP product agreements. If you are in active negotiation on any other SAP product, your Concur renewal should be explicitly included in the same commercial conversation. Account executives with incentives tied to total SAP deal value will find ways to improve Concur pricing when doing so accelerates closure of a larger ERP deal. Organisations that treat Concur as a standalone renewal forfeit this leverage entirely.

Concur Optimisation: Reducing Cost Between Renewals

The renewal negotiation is the largest single opportunity to reduce Concur cost, but it is not the only one. Several operational optimisation levers reduce cost between renewal cycles.

Submission frequency management: Under per-report pricing, aligning expense policy to consolidate submissions reduces billable transaction volume. Requiring bi-weekly rather than weekly submissions, or establishing a minimum value threshold for solo-item reports, reduces report count without reducing employee reimbursement. The saving is direct and immediate. For a 5,000-employee organisation submitting 18 reports per employee per year at $9 per report, a policy change that reduces average submissions from 18 to 14 saves over $180,000 annually without any contract change.

User account hygiene: Active Concur accounts for former employees represent a governance risk and a potential cost source. Monthly reconciliation of active Concur accounts against the HR employee master should be a standard process, not an annual cleanup exercise.

Mobile receipt capture optimisation: SAP Concur's ExpenseIt mobile capture feature reduces processing time and improves receipt quality. Organisations that have not deployed ExpenseIt to mobile users typically have higher audit failure rates and higher manual processing costs than those that have. The feature is included in standard Concur Expense subscriptions — if it is not deployed, deploy it.

Intelligent Audit utilisation: For organisations paying for Concur's AI-driven Intelligent Audit service, audit effectiveness metrics should be reviewed quarterly. If the audit rules are not catching the exposure categories relevant to your policy, the configuration needs updating — not the subscription renewal.

Client Pattern: The Per-Report Trap

A UK-headquartered professional services firm with 4,200 employees had been on a per-report Concur Expense structure for five years. Their consulting population submitted expense reports at a frequency of approximately 22 per employee per year — significantly above the flat-rate breakeven threshold. Twelve months of data showed 92,400 reports submitted at an effective rate of $10.20 per report — an annual Concur Expense cost of $942,480.

An enterprise flat-rate proposal modelled at the same total transaction count came in at $610,000 annually — a reduction of $332,000, or 35%, with no reduction in functionality or user experience. The conversion was completed at renewal. The SAP account team initially resisted, arguing that per-report pricing was "more aligned with your actual usage" — which is technically true and commercially backwards when actual usage exceeds the flat-rate breakeven. The flat rate was agreed within three negotiation cycles.

Summary: What to Prioritise in Your Concur Strategy

The priorities differ by where you are in your Concur lifecycle. For organisations entering a new Concur contract, the priorities are: model total cost including connector fees before signing, choose the right commercial model based on actual submission data, and secure price escalation caps and auto-renewal terms that prevent SAP from compounding costs quietly year after year. For organisations already in a Concur contract, the priorities are: assess whether your submission frequency has crossed the flat-rate breakeven, audit your connector schedule for undisclosed costs, and identify whether the Concur–ERP integration creates Digital Access exposure.

In every case, the renewal date is the most important commercial event in your Concur lifecycle. The window before that date is when you have leverage. Contact us at Redress Compliance's SAP advisory team at least 12 weeks before your renewal to ensure you have time to prepare properly.