Expense (SAP)

SAP Concur is a cloud-based expense and travel management software solution that enables executives to manage travel expenses. It allows finance executives to monitor expenses and cash flows related to travel expenditures.

Information Stored
Minimum Permissions Required
Authentication Method
Credentials Required
Integrating SAP Concur with SaaS Management
API Endpoints

Information Stored

The following table describes the available integration tasks and stored data.

Available Integration Tasks

Integration Task

Information Stored

Application Roster

Employee ID/Login ID
Email
First Name
Middle Name
Last Name

Expense Discovery

Amount
Transaction Date
Expense Type Name
Currency
Merchant Name
Owner Login ID
Comments

Note:Expense data is sourced for the past 90 days on the initial run.

Note:The information stored is subject to change as enhancements are made to the product.

Minimum Permissions Required

Minimum API required permissions are based on the Scopes Required and User Role.

Scopes Required

Scopes Required

Scopes Required

Description

Integration Task Name

user.read

To read the list of users in Concur account. For details, refer to the List of Scopes for all SAP Concur APIs in SAP Concur’s documentation.

Application Roster

expense.report.read

To read the list of expense reports in Concur account. For details, refer to the List of Scopes for all SAP Concur APIs in SAP Concur’s documentation.

Expense Discovery

User Role

The access token owner (OAuth Consumer) must have the Web Services Admin role to use this parameter. For details, refer to the Expense Reports v3 section of SAP Concur’s documentation.

Authentication Method

OAuth2 with password grant type. For details, refer to the Company Level Authentication section of SAP Concur’s documentation.

Credentials Required

Geolocation
Username
Password
Client ID
Client Secret

Integrating SAP Concur with SaaS Management

To integrate SAP Concur with SaaS Management, perform the following steps.

To integrate SAP Concur with SaaS Management:

1. This integration uses SAP Concur’s new Oauth2 framework for authentication. In this version, the client ID, client secret, and geolocation cannot be obtained via the Concur UI and must be requested via a Concur support ticket. For more information, refer to Concur’s OAuth2 - Getting Started documentation.
2. The table below lists the location that SAP Concur currently supports with the corresponding geolocation code for integrating with an implementation account and production account.

Location

Production Account

Implementation Account

United States

us

us-impl

3. Add the SAP Concur application in SaaS Management. Refer to Adding an Application.

API Endpoints

The following API endpoints are used for production and implementation accounts.

Application Roster

https://www.concursolutions.com/api/v3.0/common/users
https://implementation.concursolutions.com/api/v3.0/common/users

Expense Discovery

https://www.concursolutions.com/api/v3.0/expense/entries
https://implementation.concursolutions.com/api/v3.0/expense/entries
https://www.concursolutions.com/api/v3.0/expense/reports 
https://implementation.concursolutions.com/api/v3.0/expense/reports