SAP Concur

SAP Concur + Konnectify

SAP Concur Integration with Konnectify

Connect SAP Concur to Konnectify to manage users, lists, budgets, and financial transactions—so your finance and travel operations stay consistent across systems.

Users Budgets Transactions Lists 0 Triggers 24 Actions

ON THIS PAGE

→ What is SAP Concur? → API & Authentication → How to connect → Triggers (0) → Actions (24) → Popular automations → FAQ

What is SAP Concur?

SAP Concur is a spend management platform that helps organizations manage travel, expenses, invoices, and related user governance. By integrating SAP Concur with Konnectify, you can automate user lifecycle updates, keep budgets and lists in sync, and streamline downstream processing of financial documents.

This integration is especially useful when you need to connect Concur data to HRIS/IdP systems, ERPs, accounting platforms, or internal data warehouses with consistent, auditable workflows.

New to SAP Concur?

Learn about Concur’s travel and expense products and choose the right plan for your organization.

Explore SAP Concur

New to Konnectify?

Create workflows that connect SAP Concur to your ERP, HR, identity, and finance stack—without maintaining custom code.

What you can automate

• Create and update unified Concur user profiles

• Retrieve Identity/Spend/Travel user details for audits and provisioning

• Create and manage fiscal years for budgeting cycles

• Create, update, and delete budget categories and budget items

• Search and process financial transactions and postings

• Manage Concur lists and list items for controlled values

API & Authentication

Authentication: OAuth 2.0 authorization

Konnectify connects to SAP Concur using OAuth 2.0. During connection setup, you’ll be redirected to SAP Concur to approve access, and Konnectify will exchange the authorization code for access credentials. Your Client ID and Client Secret are used only to establish the secure OAuth connection.

API capabilities used in this connector

User profile management across Identity, Spend, and Travel
Budget configuration (fiscal years, budget categories, budget items)
Financial transaction retrieval and document acknowledgements/confirmations
List and list item administration for controlled data values

Important SAP Concur API availability, entitlements, and rate limits can vary by tenant, product (Spend/Travel/Invoice), and plan. If an action fails with a permissions error, verify API access is enabled and your Concur app registration has the required scopes.

Official docs: SAP Concur Developer Center

How to connect SAP Concur to Konnectify

Prerequisites

An SAP Concur tenant with API access enabled
A Concur app registration with a Client ID and Client Secret
Permission to authorize OAuth access for the required Concur products (Identity/Spend/Travel)
A Konnectify account with permission to create connections and workflows

Add SAP Concur to a Workflow

In Konnectify, open Workflows and select Create workflow.
Search for SAP Concur and add it as a step.

Authorize via OAuth 2.0

Click Connect and enter your Client ID and Client Secret.
Complete the SAP Concur authorization prompt in the new window.

Configure the Trigger or Action

Select the SAP Concur step you want to run (for example, Create Profile).
Map inputs from earlier steps (or from constants) into the action fields.

Field mapping tip Many SAP Concur endpoints require unique identifiers (for example, Concur User ID or UUID). If you don’t already have these IDs, add a lookup step such as Find Identity User before update or confirmation actions.

Test the Workflow

Run a test with a known user/document ID in a non-production context when possible.
Review step outputs to ensure Concur returned expected objects and statuses.

Activate the Workflow

Turn on the workflow and monitor the first few executions.
Add alerts or logging steps for finance-critical flows (posting/payment confirmations).

Triggers 0

This connector currently does not include any triggers. Use Konnectify triggers from other apps (webhooks, schedules, database events, HRIS changes, etc.) to drive SAP Concur actions.

Actions 24

Use SAP Concur actions in Konnectify to manage users, budgets, lists, and financial documents.

Users 5 actions

Create Profile

Creates a new, unified user profile across Identity, Spend, and Travel.

Update Profile

Updates an existing, unified user profile across Identity, Spend, and Travel.

Find Identity User

Retrieves user details by their unique Concur User ID.

Get Spend User

Fetches the complete spend-related profile for a user, including roles, approvers, and custom data, using their unique UUID.

Get Travel User

Fetches the complete travel-related profile for a user, including rule classes, groups, and custom fields, using their unique UUID.

Budgets 9 actions

Create Fiscal Year

Creates a new fiscal year which defines the financial time periods for budgets.

Get Fiscal Year

Retrieves the details of a single fiscal year by its unique ID.

Delete Fiscal Year

Permanently deletes a fiscal year configuration by its unique ID.

Create or Update Budget Category

Creates a new budget category or updates an existing one if the ID is provided.

Get Budget Category

Retrieves the details of a single budget category by its unique ID.

Delete Budget Category

Permanently deletes a budget category by its unique ID.

Create Budget Item

Creates a new budget item, including its periods and expense type categories.

Get Budget Item

Retrieves the full details of a single budget item by its unique ID.

Delete Budget Item

Permanently deletes a budget item by its unique ID.

Transactions 4 actions

Find All Transactions

Retrieves a list of financial transactions based on document type and other filters.

Acknowledge Financial Document

Sends an acknowledgement to SAP Concur for one or more financial documents (like expenses or invoices) that have been posted to an external system.

Confirm Financial Payment

Sends a payment confirmation to SAP Concur for a financial document, updating its payment status within the system.

Confirm Financial Posting Transaction

Sends a processing confirmation to SAP Concur for a financial document, updating its status.

Lists 6 actions

Get List Item by ID

Retrieves the full details of a single list item by its unique ID.

Create List Item

Creates a new item and adds it to a specified list.

Update List Item

Updates the details of an existing list item.

Remove List Item from List

Removes a list item's association from a specific list without deleting the item itself.

Get List by ID

Retrieves the details and configuration of a single list by its unique ID.

Create List

Creates a new list to hold list items.

Configurations 3 actions

Update List

Updates the configuration of an existing list.

Delete List

Permanently deletes a list and all of its items from the system.

Delete List

Permanently deletes a list and all of its items from the system.

Note: List configuration actions are separated here to keep list content (items) distinct from list-level configuration changes.

Configurations 3 actions

Update List

Updates the configuration of an existing list.

Delete List

Permanently deletes a list and all of its items from the system.

Get List by ID

Retrieves the details and configuration of a single list by its unique ID.

Action list note List-related actions are split across Lists (creating items and list content) and Configurations (list-level configuration). Ensure you use the correct action for your use case.

Popular automations

Here are a few common workflow patterns teams build with SAP Concur actions. (This connector has no native triggers, so your workflow will typically start from another app or a scheduler.)

Provision Concur users from HR

When a new employee is created in your HRIS/IdP, automatically create their unified Concur profile, then verify their Spend/Travel setup.

New employee (HRIS trigger) → Create Profile → Get Spend User

Roll out a new budget cycle

On a schedule (or when finance approves), create the fiscal year and ensure budget categories and items are set up consistently.

Scheduled run → Create Fiscal Year → Create or Update Budget Category

Post Concur financial documents to ERP and acknowledge

Fetch eligible transactions, post them to an external system, then acknowledge and confirm posting/payment back in Concur.

Scheduled run / ERP event → Find All Transactions → Acknowledge Financial Document

Keep Concur lists in sync with master data

When a cost center, project code, or department changes in your source system, update Concur lists and list items to match.

Master data updated → Update List Item → Get List Item by ID

FAQ

How does authentication work for SAP Concur in Konnectify?

The connector uses OAuth 2.0. You provide a Concur Client ID and Client Secret, then complete an authorization prompt in SAP Concur. Konnectify uses the resulting OAuth credentials to call Concur APIs on your behalf.

Which SAP Concur plans/editions are supported?

Most Concur tenants can use the integration as long as API access is enabled and your organization’s Concur products include the relevant endpoints (Identity/Spend/Travel/Budget/List/Financial). If a specific action is not available, it’s usually due to tenant entitlements or API scope restrictions.

How do triggers work for this connector?

This SAP Concur connector currently provides no native triggers (no polling/webhooks packaged in the connector). Start workflows using triggers from other connectors (for example, HRIS “employee updated”, ERP “invoice posted”, or a scheduled trigger), then use SAP Concur actions to apply changes or confirmations.

Does this connector support upsert/deduplication?

Yes—budgets include a Create or Update Budget Category action, which behaves like an upsert when an ID is provided. For user profiles, it’s best practice to run a lookup (for example, Find Identity User) to determine whether to call Create Profile or Update Profile.

How are rate limits handled?

SAP Concur enforces API rate limits at the tenant/app level. If requests are throttled, Konnectify workflows may temporarily fail or retry depending on your workflow settings. For high-volume syncs, use batching patterns in your source system, add delays, and avoid unnecessary repeated lookups.

Can I connect multiple SAP Concur accounts/tenants?

Yes. You can create multiple SAP Concur connections in Konnectify (for example, separate production and sandbox tenants, or different business units). Then select the appropriate connection at the workflow step level.

What’s the difference between acknowledging, confirming posting, and confirming payment?

In many finance integrations, Concur expects status updates as documents move through downstream processing:

Acknowledge Financial Document: tells Concur you received/posted one or more documents to an external system.
Confirm Financial Posting Transaction: confirms processing/posting status updates for a document.
Confirm Financial Payment: confirms payment completion and updates payment status.

Always align these calls with your ERP/accounting workflow to avoid mismatched document states.

Ready to automate your SAP Concur workflows?

Connect SAP Concur to Konnectify and streamline spend, user provisioning, and finance operations across your tools.

Get started free →