SAP Concur Expense

Name: SAP Concur Expense
Brand: SAP
Rating: 4.1 (10433 reviews)

Leader

We bring out the best in every business.

Est 1972|Valuation $254.5B|Raised $495.9M|178 Ref Customers

LinkedIn 180K|Website|Web traffic 12.5M|FTEs 2,432|HQ Walldorf, Germany

MarketsSource-to-Pay Procure-to-Pay ERP Financial Consolidation

Platform CoversExpense Management

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where Concur is overkill - Early-stage startups and small businesses with occasional expenses and limited policy complexity will often get better ROI from simpler tools. - Use cases where competitors are superior - When tight integration of corporate cards, real-time spend controls, and a simple UX are primary requirements, alternatives such as Ramp or Navan may be more appropriate depending on region and specific requirements. - If user adoption requires a modern consumer-like UX and minimal friction, products focused on lightweight workflows (e.g., Expensify or Navan) may be preferred. - Technical requirements Concur may not meet (or may require heavy effort) - If a clean, API-first integration story across many non-SAP systems with minimal consulting is required, Concur deployments can require more integration effort. - Budget constraints - If procurement requires predictable per-user published pricing and minimal add-ons, Concur’s variable and contract-based pricing approach can be a mismatch. - Workflow/integration red flags - If the primary reimbursement delay in an organization stems from internal accounting review bottlenecks, implementing Concur alone will not resolve that process constraint. - Current limitations acknowledged by the vendor - SAP Help Portal materials indicate ongoing UI changes (e.g., previewed new Expense Report UI), which implies the product is evolving and user experience may vary during rollout. - Features on the roadmap / ongoing change - SAP Concur publishes release notes and planned updates through the SAP Help Portal (monthly release notes are available). - Scale limitations - No explicit public "break point" volumes were identified in the accessible sources; Concur is widely used in large enterprises, but performance depends on configuration, integrations, and tenant region. - Security/compliance gaps - Penetration test results are not publicly released by SAP, which can slow vendor risk reviews; SOC reports are available via SAP Trust Center under appropriate agreements. - API limitations / integration constraints - Integration complexity is a recurring practical constraint; buyers should validate specific ERP export formats, multi-entity posting, and reconciliation needs in a proof-of-concept.

Deal disqualifiers (poor fit)

Very small teams with low travel volume.
Organizations that require transparent self-serve pricing and fast trial-first onboarding.
Teams with low tolerance for complex configuration or high administrative overhead.

02Why they buy

- Competitive advantages validated by customer feedback (not just vendor claims) - Enterprise adoption is supported by strong integration patterns with SAP finance ecosystems, as cited by multiple users and implementers. - Mobile receipt capture and corporate card matching are commonly cited functional strengths by users. - Unique features/capabilities competitors may lack - Extensive partner ecosystem via SAP Concur App Center (breadth of travel and spend integrations). - Established enterprise compliance processes with SOC reporting mechanisms accessible through SAP’s Trust Center (reports provided under NDA). - Areas where competitors clearly have advantages - User experience and speed-to-value (several competitors emphasize simpler onboarding and fewer steps for end users). - Pricing transparency and self-serve purchasing for smaller organizations (some competitors publish clearer starting prices for SMB-focused plans).

03Field reports

- Review platform signals (themes) - G2 - G2 indicates a large review volume and includes summaries showing some users cite ease of use and simplified expense management workflows; this is an aggregated platform summary rather than a controlled study. - TrustRadius - TrustRadius shows SAP Concur is used for travel and expense management; reviewers frequently cite reimbursements, card expenses, and travel booking use cases. - Capterra - Capterra hosts SAP Concur reviews and can be useful for scanning recurring pros and cons at scale. - Trustpilot - Trustpilot shows a lower TrustScore snapshot for Concur, which can be a signal of end-user dissatisfaction in that channel; note Trustpilot tends to skew toward consumer-style complaint behavior and may not represent enterprise administrators’ views. - Community / social feedback (direct quotes) - Strong negative sentiment examples (UX / frustration) - Hacker News user quote: - "I use Concur as part of my job. It is stunningly, stupefyingly awful." (Hacker News comment) - Reddit venting sentiment: - "After a long travel day, the absolute last thing I want to do is fight with an expense report just to get my own money back." - "Between the shoddiness of the product itself (it intermittently not syncing reports to Netsuite) and the horrendous and slow customer service, I find it hard to recommend Concur…" - Positive / pragmatic sentiment examples (mobile capture, automation, pragmatic adoption) - Reddit user perspective: - "I like the app for taking pictures of receipts for expense reporting." - Hacker News counterpoint: - "We used Excel based expense reporting for years, it takes me much less time to assemble my reports on Concur; I rather like it, it's the least of all evils." - Common criticisms and complaints (from reviews/community patterns) - UX friction and workflow complexity (frequent in Reddit/HN threads). - Slow or poor customer support (frequently mentioned in negative Reddit posts). - Integration/sync issues in certain ERP/accounting environments (e.g., NetSuite sync complaint reported in community threads). - Complexity and customization challenges (noted in analyst and community snippets). - Why customers chose this product over alternatives - Enterprise requirements and SAP ecosystem integration are repeatedly cited as reasons companies retain Concur despite end-user experience complaints. - In multi-entity or global organizations, integration cost and process standardization can outweigh end-user UX considerations. - Why some customers left for competitors (churn reasons) - Cost sensitivity and preference for simpler tools is a common theme on review platforms and community threads; some reviewers switch to alternatives like Expensify or Certify for perceived cost savings. - SMB or low-travel organizations may not realize ROI relative to lighter-weight tools. - Specific outcomes customers achieved (with metrics when available) - A community thread mentioned a reported travel-spend reduction over a short period attributed to improved visibility; this metric appears in vendor-amplified or community contexts and is not independently validated in the accessible sources. - Deal-breakers and reasons customers didn't purchase - Public deal-breakers commonly mentioned across channels: - Pricing opacity and quote-based contracts. - Per-report pricing that can become expensive at scale. - End-user frustration leading to lower compliance (people delay filing reports).

Vendor-published / vendor-amplified examples

- SAP Concur marketing materials describe automation features and time-savings use cases; vendor case studies often report reduced cycle times and lower manual work. - Critical evaluation: - Vendor-provided case study metrics may not include methodology details (baseline definitions, sample size, or confounding process changes). - Buyers should request before/after process maps, measured cycle times (submission-to-reimbursement), exception rates, and adoption/compliance metrics when evaluating vendor case studies.

Independent verification gaps

In the accessible sources, customer metrics are mostly relayed through vendor channels or community quotes; there is limited independently audited ROI evidence.

04Best fit

Company sizes

Best fit tends to be:
- Mid-market to enterprise organizations, especially where travel-and-expense (T&E) volume is meaningful.
- Companies with high traveler frequency or significant corporate card transaction volume.

Industries and verticals

Broad enterprise adoption across:
- Professional services
- Technology
- Manufacturing
- Healthcare/pharma (where policy compliance and auditability are important)
- Public sector/higher education (often via procurement contracts)

Roles and personas

Decision makers
- CFO, VP Finance, Controller
- Travel manager / procurement
- IT leadership (SSO, integrations, security review)
End users
- Frequent travelers (sales, consulting)
- People managers approving expenses
- Accounts payable, expense auditors, and accounting operations

Pain points addressed

Reduce manual entry via card feeds and receipt capture.
Improve policy compliance and approvals.
Centralize spend data for reporting and audits.

Qualification criteria (great fit)

Need for complex policy enforcement and approvals.
Need for SAP-centric integration and enterprise controls.
Multi-country or multi-entity requirements.

05The pitch

What the product does (core value proposition in objective terms)

- SAP Concur Expense is an enterprise expense management system used to capture, categorize, route for approval, audit, and export employee expenses into finance/accounting systems. - Core workflows include: - Expense report creation and submission via web and mobile. - Receipt capture (mobile photo/PDF upload) and association with expense line items. - Corporate card feed ingestion and automated matching to expenses. - Policy controls (alerts, required fields, validation rules) and multi-step approvals. - Accounting exports (GL coding via expense types and account mapping). - SAP describes Concur as part of a broader travel, expense, and invoice spend-control suite (Expense, Travel, Invoice), with an integration ecosystem via the App Center.

Target market and market positioning

- Primary fit appears to be mid-market and enterprise organizations with: - High travel volume and/or significant corporate card usage. - Complex approval policies, cost allocations, multi-entity accounting, or multi-country requirements. - Strong need for integration into ERP (particularly SAP ERP landscapes). - Many user discussions describe Concur as functionally adequate for enterprise needs but often not praised for end-user experience, suggesting a positioning driven by control, integration, and compliance rather than UX.

Get a comprehensive analysis of SAP Concur Expense including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →