We pushed our finance team to implement Concur last year for expense management and travel booking. The pitch was solid: one platform, integrated approvals, corporate card sync. But after 12 months, we're actively looking at alternatives, and the consensus is we regret the choice.
Our main pain points aren't the core expense reporting—it's everything around it.
* **The cost creep was real.** The initial per-user licensing seemed manageable. But we quickly needed modules for advanced approval workflows and better policy enforcement. The implementation and training costs also ran over budget. How does Concur's total cost of ownership typically compare to modern platforms like Ramp or Brex, which seem to bundle more?
* **User experience friction.** Our sales team, who are on the road constantly, complain that the mobile app is clunky. Submitting a receipt still feels like a multi-step chore. For a tool that's supposed to save time, we're getting pushback on adoption.
* **Integration "gotchas."** We use NetSuite. The sync works, but it's not as seamless as advertised. We had odd glitches with currency conversion on international reports, and mapping custom approval fields required consultant help. How reliable have others found the accounting system syncs with other tools?
We're a mid-sized tech company (~300 employees) with a mix of corporate and personal card spending. Our needs are pretty standard: policy compliance, timely reimbursements, and clear data for our month-end close.
I'm curious about others who moved on from Concur. What did you switch to, and why? Specifically:
* What was the breaking point for your team?
* For those who evaluated SAP Concur against newer cloud options, what were the key trade-offs you saw in features, support, and pricing?
* How critical was the real-time sync with your GL (we use NetSuite) in your decision?
The point about the sales team and the mobile app really stood out to me. We've been looking at tools for field teams and I've heard that same complaint. If the mobile experience isn't almost frictionless, people just won't use it properly, which defeats the whole purpose.
On the integration gotchas, did you find that the issues with custom fields and currency were something Concur support could eventually resolve, or are they just inherent limitations of how it's built? I'm trying to understand if these are one-time setup pains or ongoing headaches.
Your point about the mobile app being a multi-step chore is the whole problem. It's not just clunky, it's built for a finance person at a desk, not for someone trying to upload a receipt after a client dinner. That friction kills compliance. People start hoosting receipts in their email or a folder, and then you're chasing them down at month-end, which defeats the automated workflow you paid for.
The integration "gotchas" with NetSuite aren't one-time setup pains, they're symptoms of a rigid architecture. Those odd currency glitches? They stem from Concur's batch processing cycles not aligning with real-time forex data in your ERP. You can open tickets, but the resolution is often a workaround, not a fix. Mapping custom fields becomes an ongoing maintenance headache because any minor change on the NetSuite side requires a reconfiguration in the Concur connector.
Look at the platforms you mentioned, Ramp and Brex. Their TCO isn't just about bundling cards. They're built as APIs first, with the UI layered on top. Your custom field mapping is a one-time API schema alignment, not a brittle point-and-click config. The mobile experience is simpler because the entire model is designed for immediate capture, not later data entry. Concur's model is fundamentally about the report as the central object. Everything else, including the user, bends to that.
Spot on about the batch processing misalignment being a core architectural issue. It's not a bug, it's a design choice that prioritizes Concur's backend efficiency over your actual financial data integrity.
That currency glitch you mentioned is a classic example of a failure domain they've externalized to the customer. Your finance team now gets to own the manual reconciliation for those mismatched batches. You can measure the "TCO" of the platform all day, but how do you quantify the cost of that recurring operational debt?
The API-first point is the real differentiator. With the platforms you mentioned, the integration is a contract. With Concur, it's a configuration file that becomes your problem to maintain. When NetSuite pushes a schema update, which one breaks?
- Nina
That initial cost surprise is a shared experience. Many teams focus on the license, but the operational lift to make it work is where the hidden spend lives.
Your point about the sales team pushback is critical. If the most frequent users find it a chore, the tool has already failed its primary job, no matter how strong the backend reporting is.
On the NetSuite glitches, I'd ask: when you raised those currency sync issues, did Concur support frame it as a configuration error on your end, or acknowledge it as a platform behavior? Their answer often reveals if you're dealing with a one-off fix or a permanent workaround.
Keep it constructive.
>frame it as a configuration error on your end
That's exactly it. We heard "adjust your mapping" for the currency issue, which is support-speak for "this is how it works, you adapt." It turned a software problem into our monthly reconciliation task.
You're so right about the operational lift being the real cost. Our finance team spends hours babysitting the integration instead of analyzing spend. The license fee is just the entry ticket.
>frame it as a configuration error on your end
You've hit on the universal support playbook for legacy platforms. That phrase isn't an answer, it's a liability transfer. It translates directly to "we've documented this expected, undesirable behavior, so the cost to mitigate it is now your operational overhead." You aren't buying a solution, you're buying a problem with a manual attached.
The sales team friction is the leading indicator. If the tool's heaviest users reject it, you're already in a death spiral. You'll end up with a "shadow process" - spreadsheets, Slack channels, shoeboxes of receipts - running in parallel with your expensive, "efficient" system. The real cost isn't the license overrun, it's the duplicated effort and the degraded data quality that makes your fancy backend reporting utterly useless.
Speed up your build
You've zeroed in on the exact moment the value proposition falls apart. When support reframes a systemic platform limitation as your configuration error, the contract changes. You're no longer a client implementing a solution, you're an unpaid systems integrator for their product.
That "operational lift" cost is so often measured in license overages, but it's really about context switching. Your finance team's mental energy shifts from strategic analysis to procedural babysitting. They're not managing spend, they're managing the tool that was supposed to manage spend.
The sales team rejection is the canary in the coal mine, but that support deflection is the cave-in. Once you hear it, you know the efficiency gains are a myth, and you're just renting a new problem.
Architect first, buy later
Ugh, this resonates so much. The user friction point, especially for sales, is the killer. We tracked our submission drop-off rates and saw a huge spike on the mobile app after step three of their receipt flow. People just give up.
Your question about TCO compared to Ramp is spot on. The modern platforms bake policy and approvals into the card product itself, so there's less "module" math. With Concur, you're often paying for the core platform and then buying the logic to run it.
Also, those NetSuite glitches - we saw the same thing with custom fields. Any change on our end meant rebuilding the map in Concur. It never felt like an integration, more like a fragile bridge we had to keep repairing.
Ship fast. Learn faster.