SAP Concur transition insight

Taking SAP Concur through a merger, acquisition, or divestiture.

When a company splits or combines, SAP Concur is rarely the headline. But it touches every employee who travels or spends, every corporate card, and every expense that has to land in the right ERP. Get it wrong and the first people to notice are employees waiting to be reimbursed.

Why it matters

The deal closes on a date. Concur has to be ready by then.

Mergers, acquisitions, and divestitures run on legal and financial deadlines. SAP Concur usually gets planned late, after the entity structure, the ERP, and the card program decisions are already made.

That leaves little time to rebuild approval chains, move employees to the right entity, transition corporate cards, and confirm that every expense still flows to the correct ledger.

Meanwhile, employees keep traveling and spending. They don't care that a transaction is happening. They care about getting reimbursed on time.

The transition plan

Six workstreams to plan before the deal closes.

Work through these with Finance, AP, IT, and your travel management company. Each one needs an owner and a date.

Ownership

One plan, one timeline

The technical work is the easy part. Coordination is the hard part.

  • Name one owner for the Concur transition, not one per department.
  • Put Finance, AP, IT, and the travel management company on a single schedule.
  • Agree on who makes decisions before cutover week, not during it.

Organization

Map the new structure

Every entity, company, and cost center change has to show up in Concur.

  • Confirm which legal entities, companies, and cost centers move, merge, or retire.
  • Update employee groups and policies for the new structure.
  • Plan for employees who change entities in the middle of an expense cycle.

Approvals

Rebuild approval chains

Approvers change when organizations change.

  • Review approvers and delegates for every affected group.
  • Replace approvers who will not be part of the new organization.
  • Test approval routing before cutover, not after the first stuck report.

Corporate cards

Transition the card program

Card changes are where charges most often get lost.

  • Confirm the new card program timeline and when the new feed goes live.
  • Set a firm cutoff for expensing charges on the old cards.
  • Reconcile the old card program to zero before it closes.

ERP and reconciliation

Prove the numbers match

Reconciliation is where trust is won or lost.

  • Map the Concur extract to the new ledger, entities, and accounts.
  • Reconcile the first cycles after cutover line by line.
  • Agree who resolves mismatches and how fast.

Employees

Protect reimbursements

Employees do not care about the deal. They care about getting paid back.

  • Communicate key dates early and more than once.
  • Clear open reports before cutover wherever possible.
  • Coordinate booking changes with your travel management company and give employees one place to ask for help.

From the field

Three lessons from a 20,000-user separation.

Duwana led a global SAP Concur separation for more than 20,000 users: splitting the system, moving to a new corporate card program, and keeping expense data flowing into JD Edwards. These lessons still apply to every transition.

  1. 01

    Coordination beats configuration

    The system changes are well understood. What slows a transition down is four teams working from four different plans.

    One owner, one timeline

  2. 02

    Reconciliation earns trust

    If the numbers don't match the ERP, nobody cares how clean the configuration is. Prove the first cycles before calling it done.

    Match every line

  3. 03

    Reimbursements come first

    Employees judge the whole transition by one thing: whether they got paid back on time. Protect that above everything else.

    Keep employees whole

Every transition is different. Entity structures, card programs, and ERP timelines vary, so build the plan around your deal calendar.

Planning a transition?

Bring SAP Concur into the plan early.

Whether you're separating, acquiring, or changing card programs, DJC can help you map the Concur workstreams to your deal timeline, then keep the program running through cutover and beyond with managed services. Book 20 minutes and we'll walk through what your transition needs.

Led by Duwana Jones, former SAP Concur solutions leader, who ran SAP Concur for more than 20,000 users before joining Concur.

Book a 20-minute fit call See managed services plans

Prefer email? info@duwanajconsulting.com

Not ready to talk? Follow Duwana on LinkedIn for practical SAP Concur tips.