Passenger at the airport observes the display

The instant track to SAP Concur implementation.

Travel & Expense Management

Simultaneous engineering: The instant track to SAP Concur implementation.

Reaching the goal in the shortest possible time, in a targeted and straightforward, cost-effective, and sustainable manner: This is our principle of action when implementing SAP® Concur®. To support companies in the best possible way, we work with the KPS Initial Release Method. I've already outlined the strategy behind the process. Here I would like to go into more detail about the implementation of SAP Concur.

In our SAP Concur projects, the initial release strategy sets the implementation plan.

  1. Implementation starts with defining the transformation goal. It is about aligning the functional area of SAP Concur and determining the selection of KPS best practice processes.
  2. Subsequently, the validation of the prototype defines the quality expectations and the roadmap for the next steps.
  3. The first go-live serves as a pilot run for supplementary implemented processes and applications.
  4. One or more roll-in runs enable individual adjustments and introduce further components. At the same time, the level of competence in using the technology increases continuously.
  5. Setting up proactive business and IT monitoring serves to increase efficiency and effectiveness and supports the final optimization of the solution.

In all phases of realization, simultaneous engineering allows working on the target definition and on the implementation at the same time.

This allows development cycles to be significantly shortened. Accordingly, the KPS initial release strategy is clearly superior to other methods like the waterfall model or agile methods in terms of efficiency and effectiveness.

A comparison

KPS Initial Release, Waterfall Model and Agile Approach: A comparison

In each project step, all aspects of the implementation are always addressed, regardless of whether it is the introductory alignment, prototyping, completion of the pilot application, function additions in further roll-ins, or optimizations during ongoing operation. We start with the strategy and the target operating model, then focus on the business processes involved and the underlying data model. Finally, we take care of the technical and application-specific details as well as environment-typical features of the IT infrastructure.

Holistic approach

Instead of incremental project progress, which proceeds from defining the strategy to creating a blueprint to implementation as in the waterfall model, our initial release method takes a holistic approach and parallelizes the various work packages.

Executable model 

The KPS initial release method does not involve the time-consuming production of blueprints in paper form. Instead, the implementation starts with an executable model that makes SAP Concur's functionality tangible to all stakeholders early on.

Conserving the company's recources

The integrative approach with only one implementation partner bundles the requirements from the very beginning, coordinates the expectations of business and IT, prevents misunderstandings and loss of information, and conserves the company's resources by significantly shortening the project duration.

Solution with a high degree of maturity

Based on the initial release, the implementation is focused on quickly providing a first functional SAP Concur version. In addition to learning success, this also promotes employee acceptance of the new technology. Starting the project, a solution with a high degree of maturity is already available as a vivid basis for development.

Success right from the start

The solution features a high degree of maturity right from the start and the project success does not depend too much on the input and committed participation of the business departments. The danger of the as-is state becoming entrenched on the new platform is adverted.

Reduced risk of quality delays

With the initial release method, the documentation precedes the development and is thus available from the beginning. The risk of quality defects, delays and budget overruns is reduced.

The preconfigured system is immediately ready for use in the company: Integrated process chains that map all T&E scenarios are available right from the start. We clarify supplementary, environment-specific requirements together with our customers in compact and focused workshops.

 

Individual features are implemented through successive roll-ins into the operational platform:

SAP Concur Implementation IPCs

The unique platform strategy is based on the intelligent combination of experience-based quality factors and measures that accelerate the roll-out.

The effect is a rapid, resource-saving transformation process with high acceptance in the company.

 

At the same time, integration into enterprise-wide change management offers our customers clear competitive advantages:

SAP Concur Implementation

KPS Initial Release for SAP Concur is based on a largely prefabricated solution.

This means that our customers have a platform that is 80% complete just one month after the order is placed. Accordingly, there is no need for tedious tuning of basic functions. It is sufficient to add a few individual adjustments to the system. The KPS implementation strategy for SAP Concur is unique. Its stringent structure follows the principles of the Instant Transformation Method and is therefore strictly goal-oriented as well as resource-saving. Based on best practices, this results in a customized solution that is perfectly integrated into the target environment.

More Insights

Everything that is important and becomes important.

Instant Insight Travel & Expense Management

Instant Insight

Integrating SAP Concur smarter: the KPS initial release strategy

We have developed the Initial Release Strategy for the goal-oriented and instant implementation of travel expense processes. It is based on the KPS Instant Transformation method and is optimized specifically for the use case. 

 

Read part 1 of our blog story about the KPS initial release strategy written by Andreas Pagh Andersen.
Instant Insight Travel & Expense Management

Instant Insight

Is now the right time to deal with travel and expense management?

Once business travel is in demand again, there will be a much higher demand for up-to-date information among your employees than before the pandemic. Another reason to think about it: More transparency in travel and expense management will make it easier to cut costs.
Man with luggage in airport terminal

SAP Concur

Travel & Expense Management

Mobile, user-friendly, cost-efficient. Go 100% digital:

With SAP Concur, organisations not only meet compliance guidelines, they now manage all information and receipts transparently and in a single app. Travel policies, variances, automatically uploaded receipts, hotel and travel bookings - all on one platform.

We focus on fast implementation, user-friendliness, mobility and compliance with regional and global policies and financial targets.

Privacy settings

We use cookies on our website. Some of them are essential, while others help us to improve this website and your experience. With your consent, we use cookies to analyse the usage of our website.

We also use cookies for marketing to help us measure the success of our marketing efforts. In the settings you will find detailed information about the individual cookies, and you can refuse the use of cookies.

You can change or revoke your selection at any time on any KPS.com page in the footer under Privacy Settings.

Essential Cookies

Essential cookies enable basic functions and are necessary for the proper functioning of the website.

Cookie Banner

  • Cookie Name: kps-privacy-settings
    Value: PrivacyLevel_0#a
    Storage Duration: 4 weeks
    Description: This cookie is required to save cookie settings. It is a purely technical cookie.

HubSpot:

  • Cookie Name: __hs_opt_out
    Storage Duration: 6 months
    Description: This cookie is used by the opt-in privacy policy to prompt the visitor to accept cookies again. It is set when you allow visitors to disable cookies. It contains the string "Yes" or "No."

  • Cookie Name: __hs_d_not_tracking
    Storage Duration: 6 months
    Description: This cookie can be set to prevent the tracking code from sending information to HubSpot. It contains the string "Yes."

  • Cookie Name: _hs_initial_opt
    Storage Duration: 7 days
    Description: This cookie is used to prevent banners from being displayed every time visitors access your website in strict mode. It contains the string "Yes" or "No."

  • Cookie Name: __hs_cookie_cat_pref
    Storage Duration: 6 months
    Description: This cookie is used to capture the categories a visitor has consented to. It contains data about those categories.

  • Cookie Name: __hs_gpc_banner_dismiss
    Storage Duration: 3 months
    Description: This cookie is used when the Global Privacy Control banner is dismissed.

  • Cookie Name: hs_ab_test
    Storage Duration: Until the end of the session
    Description: This cookie is used to ensure that visitors see the same version of an A/B test page they were shown previously. It contains the ID of the A/B test page and the ID of the variant selected for the visitor.

  • Cookie Name: __cfruid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cfuvid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cf_bm
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

Functional cookies

Functional cookies are used by third parties or publishers to display personalised advertisements. They do this by tracking visitors across websites.

Google Analytics

Cookie Name: _ga
Storage Duration: 2 years
Description: Used to distinguish between users.

Cookie Name: _gid
Storage Duration: 24 months
Description: Used to distinguish between users.

Cookie Name: _gat
Storage Duration: 1 minute
Description: Used to throttle the request rate. If Google Analytics is provided via Google Tag Manager, this cookie is named dc_gtm<property-ID>.

Cookie Name: hide-cookieinfo
Storage Duration: 30 days
Description: Cookie set for querying the cookies.

HubSpot

Cookie Name: __hstc
Storage Duration: 6 months
Description: The main cookie for visitor tracking. It contains the domain, the user token (hubspotutk), the first timestamp (of the first visit), the last timestamp (of the last visit), the current timestamp (for this visit), and the session count (increases with each subsequent session).

Cookie Name: hubspotutk
Storage Duration: 6 months
Description: This cookie tracks the identity of a visitor. This cookie is passed to the HubSpot software when submitting a form and is used for deduplicating contacts. It contains an opaque GUID to represent the current visitor.

Cookie Name: __hssc
Storage Duration: 30 minutes
Description: This cookie tracks sessions. It is used to determine whether the HubSpot software needs to increment the session count and timestamps in the __hstc cookie. It contains the domain, the number of page views (viewCount, increases with each page view in a session), and the session start timestamp.

Cookie Name: __hssrc
Storage Duration: End of session
Description: Whenever the HubSpot software changes the session cookie, this cookie is also set. It determines whether the visitor has restarted the browser. If this cookie is not present when HubSpot manages cookies, it is considered a new session. It contains the value "1" if present.

External media

Content from video platforms and social media platforms is blocked by default. If cookies from external media are accepted, access to this content no longer requires manual consent.

LinkedIn Tag

Cookie Name: bcookie
Storage Duration: 365 days
Description: Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform and for diagnostic purposes.

Cookie Name: bscookie
Storage Duration: 365 days
Description: Used for remembering that a logged-in user is verified by two-factor authentication and has previously logged in.

Cookie Name: JSESSIONID
Storage Duration: Session
Description: Used for Cross-Site Request Forgery (CSRF) protection and URL signature validation.

Cookie Name: lang
Storage Duration: Session
Description: Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings.

Cookie Name: lidc
Storage Duration: 1 day
Description: To facilitate data center selection.

Cookie Name: sdsc
Storage Duration: Session
Description: Signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission.

Cookie Name: li_gc
Storage Duration: 180 days
Description: Used to store consent of guests regarding the use of cookies for non-essential purposes.

Cookie Name: li_mc
Storage Duration: 180 days
Description: Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side.

Cookie Name: UID
Storage Duration: 720 days
Description: Cookie used for market and user research.

Cookie Name: UserMatchHistory
Storage Duration: 30 days
Description: LinkedIn Ads ID syncing.

Cookie Name: AnalyticsSyncHistory
Storage Duration: 30 days
Description: Used to store information about the time a sync took place with the lms_analytics cookie.

Cookie Name: lms_ads
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for advertising.

Cookie Name: lms_analytics
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for analytics.

Cookie Name: li_fat_id
Storage Duration: 30 days
Description: Member indirect identifier for Members for conversion tracking, retargeting, and analytics.

Cookie Name: li_sugr
Storage Duration: 90 days
Description: Used to make a probabilistic match of a user's identity.

Cookie Name: _guid
Storage Duration: 90 days
Description: Used to identify a LinkedIn Member for advertising through Google Ads.

Cookie Name: BizographicsOptOut
Storage Duration: 10 years
Description: Used to determine opt-out status for non-members.

Cookie Name: li_giant
Storage Duration: 7 days
Description: Indirect identifier for groups of LinkedIn Members used for conversion tracking.

Cookie Name: oribi_cookie_test
Storage Duration: Session
Description: To determine if tracking can be enabled on the current domain.

Cookie Name: oribili_user_guid
Storage Duration: 365 days
Description: Used to count unique visitors to a website.

Cookie Name: ln_or
Storage Duration: 1 day
Description: Used to determine if Oribi analytics can be carried out on a specific domain.

Cookie Name: ar_debug
Storage Duration: Session
Description: Supports Google attribution reporting API integration to mitigate signal loss.

Lead Forensics

Cookie Name: __lfluuid
Storage Duration: 10 years
Description: The _lfuuid cookie allows a website to track visitor behavior on the sites on which the cookie is installed. Tracking is performed anonymously until a user identifies himself by submitting a form.

Changing privacy settings

Imprint

Data protection statement