# SAP Concur integrations: expense reports

> Create a report and create a purchase order in SAP Concur. Connect SAP Concur to the rest of your finance stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/sap-concur-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

SAP Concur is travel, expense and invoice management software that tracks employee expense reports, receipts, travel bookings and supplier purchase orders. Tray.ai connects to SAP Concur through the HTTP Connector, so your workflows can call the SAP Concur API alongside the rest of your stack. API access comes through SAP Concur's partner program or API plan, so you need approved credentials first.

## Use cases

### Expense reports

Read, create, and update expense reports in SAP Concur from any Tray.ai workflow. The SAP Concur API covers calls such as get a report and create a report.

- Get a report
- Create a report
- Update an unsubmitted report

### Purchase orders

Read, create, and update purchase orders in SAP Concur from any Tray.ai workflow. The SAP Concur API covers calls such as create a purchase order and update a purchase order.

- Create a purchase order
- Update a purchase order
- Get a purchase order

## Challenges Tray.ai solves

### Keeping SAP Concur credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store SAP Concur credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the SAP Concur API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the SAP Concur API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to SAP Concur?

Yes. Tray.ai connects to SAP Concur through the HTTP Connector, which calls the SAP Concur API directly. Any call the SAP Concur API documents can run as a step in a Tray.ai workflow. API access comes through SAP Concur's partner program or API plan, so you need approved credentials first.

### How does Tray.ai authenticate with SAP Concur?

The SAP Concur API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated SAP Concur connector?

SAP Concur runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated SAP Concur connector from the SAP Concur API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/