Claude + SAP Concur: What the Integration Can (and Can't) Do in 2026
Short answer: there’s no ready-made way to connect Claude to SAP Concur. Concur isn’t in Anthropic’s connectors directory, and there’s nothing Concur-built to install. SAP does publish APIs for Expense, Request, and Travel, but access is partner-gated: reading the docs doesn’t grant it, you generally need a partner arrangement, and each customer has to opt in before you can touch their data. The only Claude-side paths today are a third-party read-only connector (CData) or Zapier/Pipedream middleware pointed at whatever access you’ve been granted.
Here’s what’s actually available, the gate, the limits, and what to use if you want Concur work to happen without you.
The gate: partner status and per-client opt-in
Concur’s API isn’t a paste-your-key affair, and it isn’t self-serve like a modern startup API. Getting Claude to real expense data means clearing SAP’s access model:
- Docs access ≠ API access. SAP is explicit that browsing the developer center doesn’t grant you a working integration — that’s a separate authorization.
- Partner-shaped. Meaningful access (especially across a customer base) runs through SAP Concur’s partner program, with contracts in place. You sign in for a token, then call the Expense, Request, or Travel/Receipts services.
- Per-client opt-in. Even as an authorized partner, each Concur customer must opt in before their data is reachable. There’s no “connect my personal Concur in five minutes” flow.
So a “connect Claude to Concur instantly” claim doesn’t survive contact with SAP’s access model. This is enterprise software with enterprise gates.
What SAP ships — and what it doesn’t
The Concur APIs cover expense reports and entries, spend requests and approvals, and travel receipts — a real surface, once you’re past the gate. What you won’t find is anything Claude-native: nothing Concur-built to connect, and no listing in Anthropic’s directory.
SAP’s own AI story is Joule and Concur’s built-in expense automation (receipt capture, audit, categorization). Those are SAP features inside the SAP ecosystem — not connections to Claude, and they don’t touch your Claude account.
How you’d actually connect Claude to SAP Concur today
No first-party Claude path exists, so the options are third-party and gated. In Claude, the connection is called an MCP server — a small program that sits between Claude and Concur. Three ways to get one:
- CData’s read-only connector — a local option that lets you ask questions about the numbers in Claude Desktop. Read-only; full read/write goes through CData’s paid tier. Still needs your Concur API credentials.
- Zapier or Pipedream — connect Zapier (or Pipedream) to Claude and reach Concur through whatever middleware connection you can stand up. This inherits Concur’s partner/opt-in access.
- Your own connector — have someone technical point a connection at the APIs using your authorized credentials.
Any of these adds Concur as a custom connection. Remote connections on claude.ai require a paid Claude plan; local ones run through Claude Desktop or Claude Code.
The limit that matters: Claude only acts when you ask
Even past the gate, everything Claude does happens inside a conversation you start:
- It never notices anything. A new expense report submitted, a policy exception flagged, a travel booking made — there’s nothing on the Claude side catching that event and acting on it. No “when a report exceeds policy, ping the approver.”
- Close the chat and it stops. Claude pulls a report or a spend summary when you ask; it doesn’t sit on your Concur tenant watching submissions and following up. The moment you’re done, it’s done.
- “Scheduled” isn’t really automatic. Claude’s scheduled tasks fire on a fixed clock, on a preset timer rather than in response to a submission or exception, and have no inbox to receive work. That’s not an always-on expense-review agent.
And email? Claude’s built-in email drafts in both Gmail and Outlook but doesn’t send — you still hit send yourself, and only inside the chat. You could pay a developer to build sending in too, but it’s one more thing to maintain and it still only fires while you’re in the chat.
So Claude is good for “summarize this month’s out-of-policy expenses” and not built for “route every over-limit report to the right approver as it lands.”
If you want SAP Concur work to happen on its own: Carly
The moment you want something to happen around Concur without you in the chat — email an approver the instant a report breaks policy, chase a missing receipt, send a weekly spend digest — you’ve crossed past what Claude is for.
That’s where Carly fits. A custom Claude connection can clear Concur’s enterprise gate — the partner contract and per-client opt-in — and still only answer inside a chat. Carly clears the same gate once with your authorized credentials, then runs on the events:
- When an expense report breaks policy → Carly routes it to the right approver and drafts the flag.
- When an approval is waiting → Carly pings the approver and follows up until it clears.
- When a receipt is missing → Carly chases the submitter automatically.
- Every Friday → out-of-policy items and top-line spend roll up into one digest in your inbox.
Carly also drafts and sends email across Gmail and Outlook, updates tasks and records, and connects to 200+ tools natively (see integrations) or any app via your own API key — describe the workflow in plain English and Carly builds it with you. AI agents start at $35/month, and any step in a workflow that doesn’t use AI runs free and unlimited.
Claude vs Carly for SAP Concur
| Claude (with a third-party connector) | Carly | |
|---|---|---|
| Query expense reports | Yes (post-access) | Yes |
| Summarize spend | Yes | Yes |
| Acts the moment something happens (report submitted, exception) | No | Yes |
| Routes over-limit reports on its own | No | Yes |
| Has its own inbox to receive work | No | Yes (cloud) |
| Sends the emails itself, not just drafts | No — drafts only | Yes |
| What it takes to set up | Partner access + per-client opt-in + build & run your own connector | Same partner access, then paste your credentials |
| Pricing | Claude Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude with a third-party connector is a Concur lookup inside a chat. Carly is a teammate that acts on submissions and exceptions the moment they happen.
Frequently Asked Questions
Does Claude work with SAP Concur?
Not out of the box. There’s no Claude Concur connector and nothing Concur-built to install, and Concur isn’t in Anthropic’s directory. You can connect them through a third-party read-only CData connector or Zapier/Pipedream middleware — but SAP’s API access is partner-gated with per-client opt-in, and like everything Claude, it only runs inside a conversation you start.
Why can’t I just paste a Concur API key into Claude?
Because Concur doesn’t work that way. SAP states that access to the API documentation doesn’t grant access to the API itself — meaningful access runs through the partner program with contracts, and each customer opts in before their data is reachable.
Isn’t Joule a Claude integration?
No. Joule is SAP’s own AI, and Concur’s expense automation is a built-in feature. Neither connects to your Claude account.
What if I want SAP Concur to act on its own — route approvals, chase receipts?
That’s outside what Claude does; it responds inside a chat and doesn’t act on events. Carly fires on Concur events and schedules 24/7 in the cloud and can email approvers, chase receipts, update records, and send spend digests. AI agents start at $35/month.
More: Claude connectors · Claude + Expensify · Claude + QuickBooks · Can Claude send emails · Claude vs Carly · Best AI tools for executives
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
