Discover untapped potential: KPS Health Check for SAP Concur

Discover untapped potential: KPS Health Check for SAP Concur

KPS Health Check for SAP Concur

Is your SAP Concur really delivering all the value you paid for?

Implementing SAP® Concur® is a success decisive digitization step for your company. This makes the tailored integration and optimal use of the Travel & Expense solution even more important. The KPS Health Check examines the fitness of the business processes in which SAP Concur is involved. The detailed inspection reveals possible application problems and hidden optimization potential. In doing so, the diagnostics capture the organism of your company as a whole and consider not only technical but also strategic and organizational aspects.

SAP Concur KPS Health Check

The KPS Health Check for SAP Concur provides a comprehensive diagnostic. Configuration and integration of the overall system are evaluated in a review based on best practices and long-term experience. The findings allow for the tailored optimization of your SAP Concur solution.

Why health-checking your SAP Concur is crucial

Health Check

Why health-checking your SAP Concur is crucial

Imagine the KPS Health Check like a routine medical examination for your SAP Concur. Even if there are no obvious complaints now, a closer look at the status can reveal serious signs of impending efficiency losses and cost risks. That's why it's even more important to have a thorough inspection preventively ensuring that necessary SAP Concur optimizations are carried out in time before consequential damage becomes obvious. When checking the health of SAP Concur, we perform a targeted review of how your organization is using the Travel & Expense solution and how it could make even better use of it in terms of proven best practices.
How does the diagnotics work?

Diagnostics

How does the Diagnostics Work?

For a complete picture of your SAP Concur status, our analysis looks at the situation from two different perspectives. We

  1. examine the processes and configuration setup and
  2. review the end user usage via the SAP Concur Reporting Tool 

This dual analysis structure is based on our specially designed reports which we are running in the SAP Concur Reporting Tool. Through this approach, we ensure that we precisely measure process efficiency and understand exactly where to improve it. Working with our reports is a powerful way to verify the process behavior after having implemented the necessary improvements.

Because standard reports provided by the SAP Concur Reporting Tool offer little detailed focus on specific industries, markets, countries, and company types. KPS, on the other hand, draws on its own field-tested industry experience and therefore achieves a meaningful and realistic representation of your SAP Concur status with its reports.  By building on our deep international experience, we defined the 20 most relevant reports and include them in our health check toolbox. These 20 provide comprehensive results that serve as a reliable basis for your decisions.
Including a more business-related and strategic approach

Strategic approach

What happen when companies skip health checks?

Our experience shows that many SAP Concur solutions have been implemented with a strong technical focus. Although this focus seems to be obvious at first glance, we still saw clear benefits from including a more business-related and strategic approach. 

By auditing their SAP Concur landscape our clients successfully managed to secure these benefits and avoid the risk of inefficiencies in different areas of the business. On the other hand, companies that omit the health check may have to struggle with business threatening disadvantages sooner or later:

  • Costs may be inefficiently managed and not adequately audited.
  • End users might wait too long to get reimbursed.
  • Precious time may be wasted for back-office employees sending expense reports back to end users.
  • Compliance issues and lack of acceptance can prevent the system from being used profitably.
What makes KPS Health Check so valuable?

Benefits

What makes KPS Health Check so valuable?

KPS incorporates experience from more than 30 major international SAP Concur projects into its Health Check. We provide plenty of know-how and offer a strategic perspective, that standard checks with a predominantly technical focus lack. We attach great importance to the context of the client considering the market, the industry, and the type of company. The level of expertise from other clients helps us give the proper recommendations. By accumulating the relevant knowledge, we contribute to users helping each other.

Documentation

How are health check results documented?

The KPS Health Check for SAP Concur on the one hand results in an abstract of the findings which we present as a screenshot. On the other hand, we provide a long list of findings which we are taking the client through. It illustrates in detail the areas of investigation, recommendations, and comments.

There is much to learn from the KPS Health Checks.

SAP Concur offers a lot of possibilities to manage your travel expenses efficiently, cost-saving and process optimized. Use this potential to 100%! Health Check from KPS shows you specifically where you are already using SAP Concur optimally and where there is yet untapped potential. Given the software configuration is perfectly tailored to your industry and market, SAP Concur can be a valuable tool to improve business agility and performance. 

Learn more

How KPS Concur can increase your efficiency and compliance when using SAP Concur

Post implementation services

Booking

Book your Health Check for SAP Concur here

Book now

More Insights

These topics could be interesting for you

SAP Concur solutions | KPS certified implementation partner

Download now!

Whitepaper: SAP Concur benefits People and processes

In this whitepaper you will learn about the benefits of SAP Concur and mistakes you should avoid. It includes information about the most important functional and customisable components and how your company can benefit from it. 
SAP Concur benefits people and processes
SAP Concur benefits people and processes

Instant Insight

SAP Concur benefits people and processes

An overview of the most important functional components shows the versatility of the solution and gives an impression of how comprehensively digital transformation works with SAP Concur.

Read more
Instant Insight Travel & Expense Management

Instant Insight

The 4 biggest mistakes and how to avoid them

Regardless of industry and size, the sources of errors that hinder companies on their transformation journey are the same. If you are planning a digitisation project with SAP Concur in your company, these premises will help you embark on a successful transformation path.

Read more

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