SAP Concur is a leading cloud-based travel and expense management platform, but its licensing model is unusually complex: predominantly usage-based rather than flat per-user, with per-expense-report fees, per-booking charges, hybrid base-plus-overage structures, and optional add-ons that can significantly increase costs. Unlike most SaaS products, Concur's pricing is entirely custom-quoted with no public price list, making benchmarking and negotiation critical for every enterprise buyer.
SAP Concur's usage-based pricing model means the relationship between licensing cost and business value is direct, but only if you actively manage both sides of the equation. Organisations that treat Concur as a "set and forget" SaaS subscription consistently overpay by 20-30% through inactive users, volume overages, add-on creep, and overlapping systems. See also: SAP Concur Negotiation Guide and SAP Licensing Guide.
| Module | What It Does | Licensing Metric | Key Consideration |
|---|---|---|---|
| Concur Expense | Employee expense reports and receipt capture. Mobile app receipt OCR, expense report submission, manager review with automated policy compliance checks. Core module and most widely deployed. | Per expense report submitted. Every report incurs a fee regardless of line item count. Some contracts use per-user or hybrid models. | Entry point for most deployments. Organisations frequently start here and add modules later. Includes standard mobile app, receipt OCR, credit card feed integration, and basic reporting. |
| Concur Travel | Corporate travel booking within company policy. Flights, hotels, car rentals, and rail. Employees book through the Concur platform rather than directly through airline/hotel websites. | Per booking/transaction made through the system. | Adoption is the key risk. If employees continue booking directly through airline and hotel websites, you pay for a tool with low utilisation. Assess whether travel policy can enforce booking through Concur before licensing. TripLink add-on captures external bookings. |
| Concur Invoice | Vendor invoice processing and accounts payable automation. Captures, routes, and processes vendor invoices through approval workflows. | Per invoice processed. | Evaluate overlap with existing AP automation. If you already use SAP Ariba for invoicing or have AP automation in your ERP, adding Concur Invoice may create redundancy and double-cost. Be aware of indirect/digital access implications when Concur creates journal entries in the ERP. See SAP Digital Access Guide. |
| Add-ons and premium features | Concur Detect (AI fraud detection), Intelligent Audit/Verify (outsourced expense auditing), TripLink (external booking capture), Concur Drive (mileage tracking), Budget (spend governance dashboard), advanced analytics. | Additional per-transaction or flat fees depending on the add-on. | Often appear as surprise charges on renewal invoices if not explicitly controlled. Governance: approve any feature activation with licensing implications before deployment. Contract should list each optional service with its price (or $0 if included). |
| Licensing Model | How It Works | Pros | Cons |
|---|---|---|---|
| Per expense report | Pay a fee for each expense report submitted. List price ~$8-$9 per report. Negotiated enterprise rates typically $4-$6. | Aligns cost to actual usage. Scales down if employees file fewer reports. | Costs escalate with heavy usage. Budgeting less predictable with variable volumes. |
| Per active user | Monthly fee per active Concur user. ~$6-$10 per user/month. Less common as standalone model. | More predictable spend based on headcount. Easy to forecast. | Overpay if many users file infrequent or no reports. Requires strict user management. |
| Hybrid (base + overage) | Fixed base fee covering a set number of reports/users, plus smaller fee per additional report beyond quota. | Cost certainty up to included volume. Volume discounts built into overage rates. | Complex contract terms. Need to track usage vs. limits. Over/under quota risks. |
| Enterprise flat fee | Negotiated flat subscription for unlimited or high-threshold usage. Available for large deals only. | Simplified billing. No overage risk. Cost-effective at very high volumes. | Typically priced for worst-case. Overpay if actual usage is lower. Hard to adjust downward. |
| Tier | What It Includes | Pricing | When to Choose |
|---|---|---|---|
| Automate (Base) | Core expense automation: receipt capture, expense report creation and submission, approval workflows, policy enforcement. Standard mobile app, receipt OCR, credit card feed integration, basic reporting. | ~$9 per report average list price. Enterprise discounts bring this to $4-$6. | Organisations that primarily need expense report processing without advanced analytics or managed services. Most common starting point. |
| Insights (Enhanced) | Everything in Automate plus enhanced analytics, dashboards, and spend visibility. Deeper reporting on spending patterns, policy violation trends, vendor concentration, budget tracking. | Premium above Automate per-report rate or additional fixed fee. Variable based on requirements. | Organisations wanting to use expense data strategically for cost management and policy refinement. Evaluate whether ERP or BI tools can provide equivalent analytics before paying the Insights premium. |
| Optimise (Premium) | Everything in Insights plus fully managed support and optimisation services. Dedicated SAP resources for policy configuration, adoption maximisation, and continuous improvement. | Highest-cost tier. Pricing based entirely on custom requirements. | Large enterprises wanting SAP to actively manage the Concur environment as a service. Assess whether managed services justify the premium. Many organisations achieve equivalent results through internal programme management. |
| Cost Driver | Why It Matters | How to Control It |
|---|---|---|
| Transaction volume | The primary cost determinant. Number of expense reports, travel bookings, and invoices processed directly drives fees. Higher volume = higher cost. | Analyse historical expense report counts and growth projections. Negotiate tiered pricing with predefined volume bands. Enforce internal policies: one expense report per employee per month (not per trip) consolidates expenses and directly reduces per-report costs. |
| Number of users and user management | Many contracts include a component tied to active user accounts, even for users who rarely submit reports. Rolling out company-wide incurs fees for every enabled user. | Targeted deployment: start with frequent travellers and corporate cardholders. Integrate user management with HR offboarding: deactivate Concur accounts immediately when employees leave. Quarterly account audits typically recover 5-10% of user licences by eliminating dormant accounts. |
| Module selection and overlap | Costs increase with each additional module. Adding Concur Travel and Invoice alongside Expense may create redundancy with existing systems (Ariba, ERP-native AP). | Map your spend management architecture. Only licence modules that fill a genuine gap. Evaluate adoption likelihood before licensing Concur Travel. Bundle discounts are available when licensing multiple modules, but only if you genuinely need them all. |
| Contract length and support level | Multi-year commitments (3-year deals) receive better discounts but reduce flexibility. Support tiers (Essential, Advanced, Select Care) range from basic to dedicated teams with faster SLAs. | Ensure multi-year contracts include provisions for adjustment if major changes occur (M&A, divestitures, workforce changes). For global deployments, verify whether the quote covers all regions or if separate fees apply. See SAP Contract Negotiation Service. |
| Negotiation Lever | What to Do |
|---|---|
| Leverage competitive quotes | Even if set on Concur, obtain pricing from alternatives (Expensify, Coupa, Zoho Expense, Navan). Competitors typically charge $5-$10 per user/month flat. Showing comparative TCO creates negotiation pressure. SAP sales teams routinely offer larger discounts when customers present credible competitive evaluations. |
| Bundle strategically with other SAP products | If you use S/4HANA, SuccessFactors, or Ariba, consider bundling Concur into a larger enterprise agreement. SAP often provides cross-product discounts. Negotiate carve-out clauses: the ability to drop Concur without affecting pricing on other SAP products if it does not deliver value. |
| Negotiate volume and overage terms | Predefined price tiers for higher volumes written into the contract. If expense reports exceed forecast by 20%, the per-report fee drops to a lower band. Include a "true-down" clause or flex-down option if usage is consistently below contracted volume. Apply credits at renewal for sustained underuse. |
| Cap annual price increases | Limit renewal increases to 3-5% maximum per year, documented in the contract. Clarify renewal pricing explicitly: does the price remain the same or revert to list? Get renewal rate commitments in writing. See SAP Negotiation Strategies. |
| Include implementation services and add-ons | Ask for training sessions, initial configuration assistance, or premium add-ons (Intelligent Audit, Concur Drive, TripLink) at no additional cost as part of the deal. Document all "free" inclusions in the contract with the duration they apply. |
| Request a pilot or phased deployment | Insist on a pilot phase or POC before committing to a large multi-year deal. A one-year initial contract with option to extend to multi-year at negotiated rates gives you an exit if the solution does not meet expectations. Use the pilot to validate integration, adoption, and ROI. |
| Clarify definitions and fine print | How does the contract define "active user" (monthly login? any expense created? profile exists?)? Does third-party access (external accountants, contractors) require a licence? What are auto-renewal terms and cancellation notice periods? Iron out all definitions to prevent disputes. |
| Address integration and indirect access risk | If Concur integrates with your SAP ERP (creating journal entries, posting to GL), discuss whether this constitutes indirect/digital access under SAP's licensing model. Ensure digital access for Concur documents is addressed in the contract. See SAP Digital Access Guide. |
| Pitfall | What Happens | How to Avoid |
|---|---|---|
| Paying for inactive users | Departed employees or non-travellers retain active Concur accounts. Ongoing per-user charges for zero-value accounts accumulate to thousands annually. | Integrate with HR offboarding. Quarterly account audits. Deactivate 90-day inactive accounts. Typically recovers 5-10% of user licences. |
| Underestimating volume | Actual expense reports exceed contracted forecast. Overage fees at premium rates. Budget overrun. | Build 15-20% buffer into forecasts. Negotiate tiered overage pricing. Enforce one-report-per-month policy to consolidate submissions. |
| Overlapping systems | Concur Invoice duplicates existing AP automation (Ariba, ERP). Double-paying for same function. Integration complexity between overlapping tools. | Map spend management architecture before licensing. Only licence modules that fill genuine gaps. Eliminate redundancy. |
| Add-on creep | Premium features activated during implementation without licence awareness. Surprise charges on renewal invoices for unapproved add-ons. | Governance approval for all feature activation. Contract lists all optional services with prices. Review invoices quarterly for unexpected charges. |
| Poor adoption | Employees resist using Concur. Manual processes continue in parallel. Full licensing cost with fraction of expected value. | Invest in change management and training. Enable mobile, SSO, auto-populated card feeds. Monitor adoption metrics. Address barriers proactively. |
| Integration/indirect access risk | Concur creates journal entries in SAP ERP, triggering digital access licensing. Separate SAP digital access licence requirement. Potential audit finding. | Address with SAP account team during licensing. Bundle digital access documents. Get written confirmation that the integration will not trigger additional licence requirements. See SAP Audit Trends 2026. |
| Bundle lock-in | Concur bundled with other SAP products in all-or-nothing deal. Cannot drop Concur without losing discounts on other SAP products. | Negotiate carve-out clauses. Keep Concur on separate order form if possible. Maintain exit plan. See SAP Contract Negotiation Service. |
When Concur integrates with SAP S/4HANA or ECC, creating journal entries, posting approved expenses to the general ledger, or generating purchase orders, this constitutes an external system creating documents in SAP. Under SAP's digital access licensing model, this may require separate document licences. This is a hidden licensing risk that many organisations overlook.
| Integration Scenario | SAP Licensing Implication | Mitigation |
|---|---|---|
| Concur Expense to SAP GL | Approved expense reports posted as journal entries in SAP ERP. Each journal entry may count as an indirect access document under SAP's Digital Access model. | Discuss explicitly with SAP during contract negotiations. SAP may bundle digital access for Concur-generated documents or include it in existing user licensing. Get written confirmation. |
| Concur Invoice to SAP AP | Processed vendor invoices creating AP documents in SAP. Invoice documents may trigger SAP's nine document types for Digital Access counting. | Clarify whether Concur Invoice integration falls under existing SAP contract coverage. If not, negotiate inclusion as part of the Concur deal. See SAP Digital Access Advisory. |
| Concur Travel to SAP commitments | Travel bookings creating commitment documents or purchase orders in SAP. Less common but possible in organisations with tight procurement integration. | Map the complete data flow between Concur and SAP ERP. Identify every document type created. Address each in the contract. See SAP Indirect Access Playbook. |
The critical step: get written confirmation from SAP that your Concur integration will not trigger an additional SAP digital access licence requirement. This should be documented in the contract, not left to verbal assurances. Discovering this compliance gap during an SAP audit is significantly more expensive than addressing it during the initial Concur negotiation. See SAP Audit Defence Service.
| Recommendation | What to Do |
|---|---|
| Assess needs before buying | Audit your company's expense report, travel booking, and invoice volumes before engaging SAP. Only licence the modules and capacity you realistically need in Year 1. Start with core functionality (Concur Expense) and add extras once demonstrated need arises. Model expected usage across 3 years and understand how volume changes affect cost. |
| Negotiate aggressively | Never accept the first quote. Use usage data to advocate for the pricing model that favours your pattern (per-user for infrequent filers, lower per-report for heavy users). Aim for 30-50% off list price as a minimum. Obtain multiple scenarios. Real-world example: one mid-market organisation negotiated from ~$3.20 to ~$2.45 per transaction by pushing back with competitive alternatives and usage data. |
| Optimise user management | Establish automated processes to manage Concur user accounts. Tie access to HR provisioning so new hires are added appropriately and leavers are promptly removed. Periodically review user activity and eliminate dormant accounts. Target deployment to frequent travellers and expense-heavy roles first. Quarterly audits typically recover 5-10% of user licences. |
| Monitor usage and costs continuously | Assign someone to track monthly usage vs. contract allowances. If trending over or under, engage SAP early about adjusting terms. Review invoices quarterly for unexpected charges. Enforce internal expense policies (one report per month, batch expenses) to control transaction volume. Monitor adoption metrics. See SAP Licence Optimisation Services. |
List pricing starts at approximately $8-$9 per expense report for the base Automate tier, but actual pricing is entirely custom-quoted with no public price list. Enterprise discounts of 30-50% off list are common, bringing effective per-report costs to $4-$6 in negotiated deals. The actual price depends on transaction volume, modules selected, contract length, and your negotiation. Always model your expected annual report volume and calculate the total annual cost under the proposed pricing structure before signing.
Concur primarily uses a usage-based (per-transaction) model rather than a simple flat per-user fee, which is what makes it unusual among SaaS products. However, the actual pricing structure can be per expense report, per active user, hybrid (base fee + overage), or enterprise flat fee depending on the negotiated contract. Many enterprise deals use a hybrid model. When evaluating quotes, clarify exactly which model is proposed and model the cost under your expected usage scenarios (best case, expected case, and worst case).
Discounts of 30-50% off list price are common in enterprise deals, particularly when you have substantial transaction volume, bundle Concur with other SAP cloud products (SuccessFactors, S/4HANA, Ariba), commit to multi-year terms, and present credible competitive alternatives with documented TCO comparisons. Never accept the first quote, always present competitive data, and negotiate aggressively on per-unit pricing, overage terms, and renewal rate caps.
Potentially, yes. When Concur integrates with SAP S/4HANA or ECC, creating journal entries, posting approved expenses to the general ledger, or generating purchase orders, this constitutes an external system creating documents in SAP. Under SAP's digital access licensing model, this may require separate document licences. Discuss the integration scenario explicitly with SAP during contract negotiations and get written confirmation that your integration will not trigger additional licence requirements. See SAP Digital Access Guide.
Five practical controls: enforce internal expense policies that consolidate submissions (one report per employee per month), manage user accounts actively (deactivate departed employees immediately, audit quarterly), negotiate tiered volume pricing with predefined bands, monitor monthly usage against contract allowances and engage SAP early if trending over or under, and evaluate module utilisation periodically (if Concur Travel adoption is low, consider dropping it and redirecting spend).
Bundling can deliver meaningful discounts, as SAP often provides cross-product pricing advantages. However, bundling creates lock-in risk: if Concur does not meet expectations, you may not be able to drop it without jeopardising discounts on your other SAP products. Negotiate carve-out clauses that allow you to adjust or remove Concur from the bundle after a defined period. Alternatively, keep Concur on a separate order form. Bundle for discount, but protect your flexibility to exit.
Primary alternatives include Expensify (simpler, lower cost, strong mobile experience), Coupa (broader procurement platform with expense management), Zoho Expense (cost-effective for smaller deployments), Emburse (Abacus/Certify/Chrome River for various segments), and Navan (combined travel and expense with modern UX). Alternatives typically charge $5-$10 per user per month flat (not per-transaction). Even if you ultimately choose Concur, obtaining competitive quotes strengthens your negotiation position. See SAP Discount and Pricing Benchmarks.
Redress Compliance provides independent SAP licensing advisory. We help enterprises negotiate Concur contracts, benchmark pricing against market rates, optimise module selection, address indirect access risks, and reduce total Concur costs by 20-40%. Fixed-fee engagements. No vendor affiliations.
SAP Contract Negotiation ServiceIndependent Concur licensing assessment, pricing benchmarking, contract negotiation, and indirect access risk advisory. Fixed-fee engagements. No vendor conflicts.