SAP Concur integrations

SAP Concur integrations

→

AFAS Profit → SAP Concur

AFAS to SAP Concur integration: expense users from AFAS, approved expenses back into the payroll run

→

Nmbrs → SAP Concur

Nmbrs to SAP Concur integration: expenses as a variable wage component in the right period

→

Visma Raet YouForce → SAP Concur

YouForce to SAP Concur integration: approved expenses paid out through the payroll run

→

Workday → SAP Concur

Workday to SAP Concur integration: workers as Concur users with approver, cost centre and reimbursement currency

→

ADP iHCM → SAP Concur

ADP iHCM to SAP Concur integration: out-of-pocket expenses from Concur reimbursed through the ADP iHCM NL payroll run

→

Loket → SAP Concur

Loket to SAP Concur integration: out-of-pocket Concur expenses reimbursed through Loket, with payment status back in Concur

Systems you can connect SAP Concur with

How KoppelHet connects to SAP Concur

User Provisioning Service v4, based on SCIM 2.0, with POST /Users, PATCH /Users/{userId} and POST /Bulk for up to 100 operations per request. Processing is asynchronous; the response returns a provisionId to track the status.

Authentication: Company-level access token met OAuth 2.0-scopes zoals user.provision.write en user.provision.read

Objects we connect

• Users (core and enterprise)
• Spend extension including the reimbursement currency (reimbursementCurrency)
• Travel extension

What a SAP Concur integration does

• Workday, SAP SuccessFactors, AFAS Profit → to SAP Concur

  Expense user from day one

  A new employee from Workday, SAP SuccessFactors or AFAS becomes a Concur user with the spend extension and the right reimbursement currency.

  Workday → SAP Concur integrationSAP SuccessFactors integrationsAFAS Profit → SAP Concur integrationAccounts in applications

• Workday, HiBob → to SAP Concur

  Changes in bulk

  The day's changes go through POST /Bulk in batches of up to 100 operations, and the integration follows each provisionId until processing is done.

  Workday → SAP Concur integrationHiBob → SAP Concur integrationAccounts in applications

• Workday, AFAS Profit → to SAP Concur

  Deactivate on leaving

  After the last working day the integration sets active to false, so no new expenses or trips are added.

  Workday → SAP Concur integrationAFAS Profit → SAP Concur integrationAccounts in applications

What to watch for

• The userName must be unique across all SAP Concur products. We therefore use the business email address or a fixed derivative of it.
• Because processing is asynchronous, the integration checks the provisionId, so a failed creation does not go unnoticed.

In your IT landscape

• Runs as a managed integration on the KoppelHet platform, next to your existing integration layer. No VPN into your network.
• Only the fields in the design you approve are transferred. The platform keeps no register of its own.
• Tested first in the test or acceptance environment where there is one. You choose the go-live moment.
• ISO 27001 certified, hosted in Amsterdam. When the contract ends you receive the configuration and the audit logs.

Implementation, architecture and compliance

Processes with this system

• Payroll to finance
• HR to ERP