SAP Concur
Connect AI agents and workflows to SAP Concur: expense reports, entries and receipts, invoices and payment requests, users, lists and trips.
Book a demo
SAP Concur for AI agents and workflows.
engini lets your AI agents and workflows work in SAP Concur: read expense reports, entries and receipts, upload receipts, read and create invoice payment requests, keep users and cost-center lists in step with HR and the ERP, read travel itineraries, act in Concur's own report workflow, and start a workflow when a report is submitted or reaches a step. Spend reaches the general ledger coded and on time. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
What your agent can do in SAP Concur. Every tool is one you allow or leave out.
The SAP Concur tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read reports, their entries, amounts and status.
Read receipt images and their data.
Read supplier invoices in Concur Invoice.
Read people and the lists behind fields such as cost center.
Read travel itineraries.
Write
Add a receipt image for a user.
Enter a supplier invoice in Concur Invoice.
Provision people from HR.
Keep cost centers, projects and other list values in step with the ERP.
Act in Concur's own report workflow. Give these only to the agents that should.
Any endpoint
Call any SAP Concur API, with the sign-in added for you.
Triggers
Concur's Event Subscription Service sends the event.
Reports that cleared Concur's workflow and wait to post.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to SAP Concur. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your SAP Concur connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of SAP Concur tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects SAP Concur and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every SAP Concur tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to SAP Concur through engini
{
"mcpServers": {
"engini-sap-concur": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your SAP Concur connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the SAP Concur tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on SAP Concur. Agents and workflows, across systems.
Expenses posted in the ERP
Reports that clear Concur's workflow post as journal entries or payables in SAP S/4HANA, NetSuite or Sage Intacct, coded by cost center.
Users that follow HR
New hires in Workday or SuccessFactors get a Concur user with the right manager and cost center. Leavers are deactivated.
Lists that match the ERP
New cost centers and projects in the ERP appear in Concur lists the same day, so nobody codes to a closed project.
Spend questions answered
An agent in Teams answers what is waiting, what was spent and by whom. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between SAP Concur and another system engini connects is available.
You decide what each agent may do in SAP Concur. engini enforces it on every call.
Only the tools you allow
A toolset lists the SAP Concur tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own SAP Concur account and engini acts as that person, with their SAP Concur permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect SAP Concur in three steps. Then decide what each agent may do.
Sign in to SAP Concur
Register an app for engini in SAP Concur with only the scopes the workflows need, then add a Concur connection for your company and sign in.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in SAP Concur from Claude, ChatGPT, Cursor or your own code.
SAP Concur and engini. Straight answers.
Can an AI agent write to SAP Concur, or only read?
Both. engini has tools to upload receipts, create payment requests, create and update users, update list items and act in Concur's report workflow. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Can an agent act on expense reports?
engini has tools to approve a report or send it back in Concur's own workflow, as the user behind the connection. Give them only to the agents that should use them, and every call is recorded.
Does the agent act as me in SAP Concur?
It acts as the Concur user or company app behind the connection, with the scopes it was granted. Every run is recorded under the person who started it.
Can a change in SAP Concur start work?
Yes. Concur's Event Subscription Service tells engini when reports are submitted or change workflow step, and a scheduled trigger checks for reports ready to post. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any SAP Concur API endpoint through the same connection, and give it only to the agents that need it.