Airport landing pad and a woman checking into a hotel

The right timing: When to optimise Travel and Expense Management?

Travel & Expense Management

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

We are still struggling with constraints due to the pandemic. In fact, it is a good time to look at travel and expense management, not only because we cannot wait to travel any longer: 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.

It will take some time for travel to be as carefree as we knew it before the pandemic.

When we travel for business again, we will probably want to be more prudent and have a higher need for information and security. We want to be able to react to travel changes, and we want to be flexible.

How can we use SAP® Concur® to provide our employees with more information and guidance? Support during travel preparation and, of course, during the trip is vital. Viewing safety ratings, flight delays, or maintaining direct contact with staff while on the road are understandable requests.

Uncertainties can relate, for example, to the hygiene and safety measures of airlines, car rental companies or hotels. Confidence in travel is enhanced by having this information available - if you as a company ensure that this information is easily accessible in one place, in an app, you simultaneously strengthen confidence in the company's management.

Securely managed travel planning has a very positive impact on employees' willingness to travel.

If you provide clear guidelines and understandably communicate them and provide insurance in case of illness, you let your employees travelling on business take control and make travelling "easy".

Young woman at the airport

Communicate clearly and understandably.

A travel booking system for your employees that is uniform and consistent is ideal for communicating your policies clearly and understandably. Imagine using the same technology to approve or book travel, having a single TMC (Traffic Message Channel), and being able to update your employees at any time via an app.

Crucial and fundamental to your business management is also the option to save costs: With an app for your employees, you can pre-select offers and options. Travelling employees have the choice, of course - and you can suggest alternatives, highlight and specify important and unimportant details.

A holistic approach simplifies the process and is less prone to error.

With SAP Concur, organizations meet compliance guidelines and manage all information and receipts transparently: the entire process is unified. This allows travelers to view policies, request, and book travel, manage bookings, and get support and assistance when changes occur - all in one app.

Final note: My focus on Travel and Expense Management is on quick implementation and high user-friendliness.  What is important for me is more agility in terms of regional and global policies and, of course, your financial goals.

 

In the next article, I will write about making expense management more manageable and more consistent with SAP Concur: Errors and delays can be reduced to a great extent through automation.

More Insights

Everything that is important and becomes important.

Cleaning machine in building forum

News

Nilfisk implements SAP Concur on a global scale

Copenhagen, 21 January 2021 - Nilfisk implements SAP Concur on a global level, gaining full visibility of expenses and paperless processes across the company in APAC and EMEA. The company is using the time during the Covid crisis to start with unified global and more efficient processes when travel reopens.
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.
Engineer with hard hat in maintenance room

News

KPS and Grundfos simplify travel expense reporting process worldwide

Copenhagen, 10 September 2020, KPS is helping Grundfos implement SAP Concur to make travel expense reporting simpler and faster. The global solution was successfully developed and implemented in two stages for six countries. In parallel, the knowledge transfer to the Grundfos team took place, so that they can now take over the roll-out of the solution to the remaining countries themselves.

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