Rippling +

SAP Concur

Connect Rippling to SAP Concur to automate account provisioning and keep expense approval hierarchies aligned with your live org chart as it changes.

What the Rippling +

SAP Concur

 Integration Does

  • Automated account provisioning: New hires get Concur accounts created automatically based on their Rippling role and department.
  • Approval hierarchy mapping: Concur's approval chains use Rippling's manager and department structure, keeping routing accurate as the org chart changes.
  • Jurisdiction-specific policy configuration: US and Canadian expense policies can be configured distinctly to reflect different tax treatment.
  • Automated deprovisioning: Employee offboarding in Rippling triggers automatic suspension of Concur access.

What Mid-Market Teams Get Wrong

  • Not mapping approval hierarchy to Rippling's live org chart: Static approval chains in Concur drift out of sync as the company grows; mapping to Rippling keeps routing accurate automatically.
  • Applying identical expense policies across jurisdictions: US and Canadian reimbursements have different tax treatment; a single policy applied to both can create compliance issues.
  • Manual deprovisioning: Relying on manual account suspension after departures leaves expense platform access allocated to former employees unnecessarily.
  • Underestimating Concur's policy engine complexity: Concur's more extensive policy configuration options mean setup takes longer than simpler expense tools; scoping it like a lightweight integration often leads to rework.

How thePeopleStack Configures This

We configure account provisioning so new hires get Concur access automatically, with expense policy assignment based on their Rippling role and department.

We map Concur's approval hierarchy to Rippling's manager and department structure, ensuring expense reports route to the correct approver automatically even as the org chart changes through promotions, transfers, or reorganizations.

For companies with both US and Canadian entities, we configure distinct expense policies reflecting each jurisdiction's tax treatment of reimbursements and per diem rules.

USA & Canadian Operations Note

SAP Concur is widely used by US mid-market and larger companies needing robust travel and expense management with detailed policy enforcement.

Canadian and cross-border operations: Canadian employees provisioned through Rippling get the same automated Concur access, with thePeopleStack confirming expense policy configurations reflect Canadian tax treatment of reimbursements distinctly from US policy.

FAQs

How does Rippling provision new users into SAP Concur?

New hires get a Concur account created automatically based on their Rippling role and department, with expense policy assignment tied to the same provisioning event.

Does this integration support Concur's approval hierarchy?

Yes — Concur's approval hierarchy can use Rippling's manager and department structure, so expense reports route to the correct approver automatically as the org chart changes.

Is deprovisioning automatic when an employee leaves?

Yes — offboarding an employee in Rippling triggers automatic suspension of their Concur account, while any outstanding expense reports remain accessible to finance for processing.

Does this integration support different expense policies by country?

Yes — Canadian and US expense policies can be configured distinctly within Concur to reflect different tax treatment of reimbursements and per diem rules across jurisdictions.

How long does configuration take?

A standard setup covering account provisioning, approval hierarchy mapping, and policy configuration typically takes 4–6 hours given Concur's more extensive policy engine.

Ready to Connect Rippling with

SAP Concur

We implement and configure Rippling integrations for mid-market teams across North America. Most integration setups are completed within a single implementation engagement.

Book a Free Discovery Call