people gathered in office meeting room
Article

Best Practices in Streamlining Global Concur Implementations

To streamline global SAP Concur implementations, make sure to ensure team readiness, plan for deployment, review your corporate card provider, create a global model, standardize documentation, and leverage your network.

Home

Our Thinking

Best Practices in Streamlining Global Concur Implementations

1) Ensure team readiness

For the core team:
  • Is there executive sponsorship to support local country buy-in?

  • Who is assigned to oversee communications and training?

  • Are resources available to support IT/Interface development?

  • Is project related travel in-scope and budgeted for?

For the local country teams:
  • Is there local buy-in?

  • Are local resources able to commit to the project?

  • What will the end-user support model be?

  • Are there any competing projects that may impact resources or the timeline?

  • What is the status of the local corporate card program?

  • Is the necessary hardware in place (e.g., scanners, access to broadband connections)?

  • If planning on using mobile, will smart phones be issued or is bring your own device (BYOD) permitted?

  • Is translation to local language required? If so, have resources been selected to complete the translation?

  • Have local works councils been informed?

2) Plan for deployment

Group similar markets

Group similar markets in the same phase to ensure project discussions and requirements gathering efforts are more efficient. Grouping criteria include:

  • Languages/Time zones

  • Shared service support locations

  • Same HR Information System and/or ERP

  • Similar T&E policy, statutory travel allowance or VAT regulations

  • Same corporate card program/provider

  • Same travel management company

Decide on a deployment approach
  • Are there IT or other black-out periods for the project or go-live?

  • Is there a target date for completing the roll-out across markets?

  • Will you follow a big bang or phased approach?

  • Will you pilot in each country or region?

3) Review corporate card provider

Pick a corporate credit card provider that allows a regional contract instead of a separate contract for each market. This eliminates the need to wait for a new contract / card feed setup.

4) Create a global model

Create a simple global model configuration which sets the groundwork for future scalable implementations.

The global model helps define configuration specifics and ward off scope creep for markets. This reduces requirements gathering
timelines, decision making, and complexity of system maintenance.

Having a consistent design also enables scalability for training
materials.

5) Standardize documentation

Develop global template worksheets using a global model that markets can use as a basis for requirements gathering. These worksheets should include available expense types, workflows, audit rules, related GL account structure, VAT requirements, and available expense type forms.

6) Leverage your network

Reach out to peers at other companies who have implemented Concur in your target markets (via Concur user groups on LinkedIn), and ask for tips and their best-practices.

Attend events like conferences, trade/industry meetings, and webinars to gain relevant insights.

Want to learn more?

Reach out to the Acquis team

Contact

Tags:

Technology Implementation
Corporate Travel
Change Management
SAP Concur
Technology
Experience Management
Transformation Management

Share

Keep Reading

A man presents to a group of colleagues seated around a table with laptops and documents in a bright meeting room.
Article

Nine Reasons “Successful” Technology Implementations Disappoint

Does your "successful" technology implementation feel like a failure? It's more common than you think. This article covers nine reasons technology implementations leave organizations wanting more.

Read More

People in a modern conference room having a meeting; one person presents data on a laptop and a whiteboard.
Article

The Power of Leading Indicators in Driving Execution

Lagging indicators dominate performance conversations because they're clear and defensible. But by the time they surface a problem, the window to act has closed. Leading indicators tell you whether you're on track while there's still time to adjust. One encourages evaluation. The other encourages action.

Read More

A group of five people sitting in a circle, discussing and taking notes in a scenario planning meeting with colorful sticky notes on the wall.
Article

Rehearsing Change: How Scenario Planning Turns Process into Performance

The gap between a well-designed future state and a successfully adopted one is almost always human. Scenario planning addresses that gap directly. It gives teams the chance to practice operating in the future state before it goes live, surfacing friction, building confidence, and creating shared understanding in a low-risk environment.

Read More