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

Four colleagues discussing work around a table with laptops, in a modern office setting with a brick wall backdrop.
Article

What Coupa R44 Means for Finance and Procurement Teams

Coupa’s January 2026 Release (R44) isn’t chasing headlines. While the platform continues to move toward its longer-term vision of autonomous spend management, this release focuses on something more immediate: reducing the everyday friction that slows finance and procurement teams down.

Read More

Businessman in a suit presenting stock market data on a large screen to a group of colleagues in a conference room.
Article

Will AI Agents Collapse the PE Tech Stack?

AI agents that can read, write, and act across systems are making traditional integration obsolete. The question many firms are now asking: Should we maintain 20 specialized systems when AI agents can deliver comparable capabilities using 5-7 core platforms? The economics increasingly suggest the answer is no.

Read More

A person holding a tablet inspects servers in a dimly lit data center, with glowing lights on the equipment.
Article

An Industry in Transition: Early Signals Shaping Life Sciences in 2026

At the end of 2025, we were closely monitoring three trends we believed would shape the next phase of biopharma’s operating model changes in 2026: data pipelines, the role of AI in due diligence, and the next-generation value chain. The J.P. Morgan Healthcare Conference offered the first opportunity to pressure-test those assumptions.

Read More