Home / Companies / Unified.to / Blog / Post Details
Content Deep Dive

Concur & Concur (Company) — Connection Guide

Blog post from Unified.to

Post Details
Company
Date Published
Author
-
Word Count
275
Language
-
Hacker News Points
-
Summary

The guide provides an overview of two available SAP Concur integrations, highlighting the differences between the Concur End-user and Concur (Company) options based on authentication methods and data object requirements. The Concur End-user integration utilizes OAuth 2.0 for user-based authentication, requiring a Client ID, Client Secret, and Redirect URI to grant individual account access for objects like expenses, invoices, and files. In contrast, the Concur (Company) integration employs a company token flow for server-to-server authentication, suitable for company-wide access and employee data management, involving additional fields like Company UUID and a Request Token. The guide advises using the Concur option for individual user access and the Concur (Company) option for broader company access, especially when dealing with employee data and backend integrations. It also provides instructions on obtaining necessary credentials and selecting the appropriate API region based on tenant location.