---
title: "Concur & Concur (Company) — Connection Guide"
img: https://s3.us-east-2.amazonaws.com/unified-article-images/concur_and_concur_company_connection_guide-icon.png
date: 2026-04-10T14:21:00.000Z
tag: Guides
description: "There are two SAP Concur integrations are available. You will need to choose which one to use based off of the authentication type and required data objects."
url: "https://docs.unified.to/guides/concur_and_concur_company_connection_guide"
---

# Concur & Concur (Company) — Connection Guide
------
_April 10, 2026_

## Overview


There are two SAP Concur integrations are available. You will need to choose which one to use based off of the authentication type and required data objects.


### Integrations

- **Concur**
    - End-user OAuth (authorization code flow)
    - Categories: Accounting, Storage, Auth
- **Concur (Company)**
    - Company-level authentication
    - Uses credentials instead of user OAuth
    - Categories: Accounting, HRIS, Storage, Auth

---


## Concur vs Concur (Company)


### Concur

- **Authentication:** OAuth 2.0 (user-based)
- **Credentials:**
    - Client ID
    - Client Secret
    - Redirect URI
- **Supported Objects:**
    - Accounting — Expense
    - Accounting — Invoice
    - Storage — File
- **Use Case:**
    - User connects their own account and grants access

---


### Concur (Company)

- **Authentication:** Company token flow (server-to-server)
- **token_names:**
    - Client ID
    - Client Secret
    - Company UUID
    - Request Token
- **Supported Objects:**
    - Accounting — Expense
    - Accounting — Invoice
    - HRIS — Employee
    - Storage — File
- **Use Case:**
    - Company-wide access
    - Backend integrations
    - Employee data access

---


## When to Use Which

- **Use Concur**
    - When a user signs in and authorizes access
- **Use Concur (Company)**
    - When you need company-wide access
    - When working with employee data
    - When SAP requires Company UUID + Request Token

---


## OAuth Scopes


| Object  | Read   | Write  |
| ------- | ------ | ------ |
| Expense | EXPRPT | EXPRPT |
| Invoice | INVPMT | INVPMT |
| File    | IMAGE  | IMAGE  |
---


## Concur (Company) — Credential Details


### Required Fields

- **Client ID**From SAP Concur OAuth Application Management
- **Client Secret**From the same OAuth application
- **Company UUID**Unique identifier for your company in SAP Concur
- **Request Token**Temporary token generated via SAP Concur Company Request Token tool (Guide: [https://developer.concur.com/api-reference/authentication/company-refresh-tool.html](https://developer.concur.com/api-reference/authentication/company-refresh-tool.html))
    - Not long-lived
    - Must be regenerated when expired

---


## Region Reference


Select the correct API region based on your tenant:

- Production (US2 default)
- EU2
- APJ1
- US Government
- Sandbox / Implementation

If unsure, confirm with your SAP Concur administrator.


---


## Network Requirements


To ensure successful API communication, you may need to whitelist Unified IP addresses on your SAP Concur account.


You can find the list of IP addresses here:


[https://app.unified.to/apikeys](https://app.unified.to/apikeys)


Failure to whitelist these IPs may result in connection or data access issues.