Concur Travel

(1)

Concur Travel

Concur Professional/Premium and Concur Standard

Month Audience

Release Date: July 17, 2021

Update 2: Monday, July 26, 12:00 PM PT SAP Concur Client FINAL

** FINAL **

The enhancements and changes described in this document may or may not be included in this release. SAP Concur reserves the right to postpone implementation of – or completely remove – any enhancement/change mentioned here.

The DRAFT and FINAL release notes contain information about Concur Professional/Premium and Concur Standard.

Each note contains a table that which indicates if the enhancement/change applies to Professional and/or Standard.

The information in this presentation is confidential and proprietary to SAP SE or an SAP affiliate company and may not be disclosed without the permission of SAP SE or the respective SAP affiliate company. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP SE or its

affiliated companies. SAP SE and its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP SE or an SAP affiliate company’s strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP SE and its affiliated companies at any time for any reason without notice. The information in this document is not a

commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of

merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP SE and its affiliated companies assume no responsibility for errors or omissions in this document, except if such damages were caused by SAP SE or an SAP affiliate company’s willful misconduct or gross negligence.

!

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

(4)

Release Notes

Administration

Accessibility Improvement for Travel Editions of Travel System Admin

Prof Stan   Edition

X X On: Impacts end users who use this feature/vendor; no configuration/setup by agency/

admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature) Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline) Other: Refer to the release note below

Does not apply to this edition Source / Solution Suggestion

GDS Direct Connect Solution ID Other

EMEA Data Center Scan impact

North America Data Center UI impact

China Data Center File finishing impact

X All data centers Profile/Profile API/3rd Party XML Sync Impact Affected Documentation

TSGs Fact Sheets

Admin Guides Travel System Admin User Guide Other

Overview

Concur Travel has updated its Travel System Admin page to help users better differentiate which travel configurations belong to Professional or Standard Travel editions.

USER/CUSTOMER BENEFIT

Users now have an accessible way to differentiate between professional and standard editions on the Travel System Admin page.

(5)

What the User Sees

A new column that identifies the Concur Travel edition has been added to the list of Travel Configurations displayed on the Travel System Admin page. This will help users identify the edition to which a configuration belongs. This is in addition to the current color indicators of blue (professional) and green (standard).

Configuration for Professional and Standard Travel

This feature is enabled by default. There are no configuration steps.



For more information, refer to the Travel System Admin User Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Travel E-mails Migration to Notification Services, Update Safe Sender List

X EMEA Data Center Scan impact

X North America Data Center UI impact

All data centers Profile/Profile API/3rd Party XML Sync Impact Affected Documentation

TSGs Fact Sheets Admin Guides Other

(6)

Overview

Since 2018, we have moved most of our e-mail notifications service to a new cloud platform. Because of this transition, companies who filter inbound e-mail based on the sending IP address must add new IP addresses to their Safe Sender list. This ensures that their users are able to receive e-mail from SAP Concur.

We are in the process of moving e-mails sent from Concur Travel for all customers to our e-mail notifications service running on a new cloud platform. Additionally, on the EMEA Data Center only, will make an IP address update for all SAP Concur solutions.

To ensure your organization is prepared, we recommend that you make any necessary changes immediately.

Customers on the North America Data Center using Concur Expense have already added the IP addresses to their allow-list and are not affected.

Customers on the North America Data Center using Concur Travel without Concur Expense will be affected by this change if they filter incoming e-mail based on IP addresses.

All customers on the EMEA Data Center filtering incoming e-mail based on IP

addresses are affected by the change. This includes customers that are using Concur Expense and have previously added IP addresses to their Safe Sender list.

SAP Concur is including additional IP addresses from which e-mails will be sent.

NOTE: This change affects only companies that filter incoming e-mail based on IP addresses.

This new service improves stability and security. It significantly speeds up the time to process and dispatch e-mails.

New IP addresses are not published but can be requested from SAP Concur support.

If your company filters incoming e-mail based on IP addresses, please work with your e-mail server management team to ensure that all required Safe Sender lists for IP addresses are updated. This will ensure that your users receive SAP Concur e-mail without interruption.

NOTE: This change does not require a software release update.

(7)

Authentication

Support for HMAC Now Deprecated

On: Impacts end users who use this feature/vendor; no configuration/setup by agency/

admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature) Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline) X X Other: Refer to the release note below

These changes are part of the SAP Concur continued commitment to maintaining secure authentication.

Overview

SAP Concur support for Hash-Based Message Authentication Code (HMAC) has been deprecated.

SAP Concur provides a Single Sign-On self-service option that enables client

administrators to set up their SAML v2 connections without involving an SAP Concur support representative.



For more information about the Single Sign-On self-service option, refer to the Shared: Single Sign-On Overview and the Shared: Single Sign-On Setup Guide. To locate, refer to Additional Release Notes and Other Technical

Documentation in these release notes.

NOTE: SAML v2 supports the use of multiple identity providers (IdPs).

This change provides better security and improved support for users logging in to SAP Concur products and services.

(8)

HMAC is now deprecated and can no longer be configured. Clients can use the Single Sign-On self-service option.



For more information about the Single Sign-On self-service option, refer to the Shared: Single Sign-On Overview and the Shared: Single Sign-On Setup Guide. To locate, refer to Additional Release Notes and Other Technical

Documentation in these release notes.

Cookie Preferences and User Consent

Explicit Cookie Consent and Zero Cookie Load Expanded to More Jurisdictions (July 1)

TSGs

Fact Sheets Cookie Preferences and User Consent Admin Guides

Other

Overview

To ensure that SAP Concur solutions meet the user cookie consent requirements of the European Union (EU), European Economic Area (EEA), European Free Trade Association (EFTA), the United Kingdom (UK), and Brazil, on July 1, 2021, SAP implemented explicit cookie consent and zero cookie load for SAP Concur solutions in those jurisdictions.

• Explicit cookie consent: The user must agree to allow cookies to be stored on their device by responding affirmatively to a request for consent.

• Zero cookie load: The user must provide explicit cookie consent before any

(9)

This change ensures that SAP Concur sites comply with the cookie consent

requirements of the listed jurisdictions and enables users to choose which cookies are downloaded to their devices by SAP Concur solutions.

The first time a user in one of the listed jurisdictions visits their SAP Concur site, the About cookies on this site page appears:

The user can click Accept All Cookies to accept all cookies and proceed or click View and change cookie preferences.

If the user clicks View and change cookie preferences, a page similar to the following appears:

On the About cookies on this site page, the user can choose which cookies can be downloaded to their device. The default setting is Required Cookies.

If a user does not consent to receive the minimum required cookies, they will not be able to proceed to their SAP Concur site.

(10)

NOTE: The page the user sees after they consent to receive cookies depends on how authentication is configured at their organization. For example, they might see the SAP Concur sign in page, or they might see the SAP Concur Home page.

There are no activation steps. The first time a user in one of the listed jurisdictions visits their SAP Concur site, they must consent to receive cookies in order to proceed to the site.



For more information, refer to the Cookie Preferences and User Consent Fact Sheet. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Flight

Ongoing CIBT – Retirement of Legacy Integration

Information First Published Information Last Modified Feature Target Release Date

February 2020 October 13, 2020 August 1, 2021

Any changes since the previous monthly release are highlighted in yellow in this release note.

TSGs CIBT – Visa and Passport Alert Service Travel Service Guide Fact Sheets

Admin Guides Other

(11)

Overview

In February 2020, SAP Concur and CIBT (CIBTvisas) launched a new integration method through the SAP Concur App Center, where the new CIBT app is available.

The legacy integration method with CIBT is still supported during a transition period but SAP Concur will eventually retire the Legacy Batch File protocol integration method, targeted for August 1, 2021.

With the new integration through the SAP Concur App Center, the CIBT service is available for additional countries. Travelers whose profiles are associated to a Concur Travel configuration based in Denmark, Finland, Ireland, Norway, or Sweden can now benefit from CIBTs visa services.



For more information on the new CIBT Integration and how to set it up, refer to the CIBT – Visa and Passport Alert Service Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

CIBT has integrated with the SAP Concur Itinerary API and Travel Profile API and has released an App Center Connector to facilitate the continuous, real-time flow of itineraries to better serve clients and travelers.

CIBT will be able to support clients and travelers in more countries and with a more stable, scalable integration. The new integration method also reduces the

configuration effort for admin users in Concur Travel.

There is no visible indication to the traveler at the time of booking that the feature is enabled or if action is required. Concur Travel automatically engages with CIBT in the background to begin the traveler experience. As to end user experience, there are no changes compared to the old integration method.



Examples of the e-mails received from CIBT after booking an international trip can be found in the CIBT – Visa and Passport Alert Service Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

With the planned retirement of the legacy integration method, existing configuration settings on the Concur Travel admin UI will be removed. This includes:

• In the Professional Edition, on the Travel Configuration page, the Send Profile/Travel Data to CIBT check box.

• In the Professional Edition, the Manage CIBT Configuration admin page.

• In the Standard Edition, the Visa / Passport Services tab on page/setup step Discounts and Travel Content.

(12)



To apply for the new integration method via the App Center:

1. Go to the SAP Concur App Center and select the CIBT App.

2. Click Connect.

NOTE: If the Connect button is not available, your user does not have Admin privileges in Concur Travel. Contact your company administrator for assistance.

3. Review and opt-in to the following elements in the displayed overlay:

 SAP Concur App Center End-User Terms & Conditions.

 Shared Information.

 Company Authorization to Link Services.

NOTE: Opt-in is required only once. If you enabled other App Center partners previously and accepted the electronic Company Authorization to Link Services, you may not be required to opt-in again.

(13)

4. Fill in the activation form in an overlay hosted by CIBT where CIBT will collect the following information:

 First Name, Last Name, and Email

 Company Entity (company or business name)

 Country

 Is this company an existing client? If the administrator is an active CIBT client, the CIBT account code for activation is captured.

 If you would like to activate CIBT for multiple countries or Travel configurations in Concur Travel, click Add another company entity, displayed near the bottom of the CIBT activation form. If you want to enable additional countries after already having enabled the

integration with CIBT through the SAP Concur App Center, contact your CIBT representative. CIBT will need your business name and the list of countries that you would like to be enabled.

(14)

5. At submission, an e-mail will be sent to [email protected]. The information in the previous step is collected via the Activation Form and will be sent through e-mail to CIBT.

6. CIBT will activate the client in the CIBT database system for Visa Alert. Only for customers that used the legacy integration method so far: CIBT will turn this integration method off from their end in favor of the new integration via the SAP Concur App Center.

Reconnection Required

!

This section applies only to customers who connected with CIBT prior to February 25, 2021.

While the new CIBT SAP Concur App Center integration has been available since February 15, 2020, all customers who connected with CIBT on or before

February 24, 2021 will need to reconnect. The version that you originally connected to has since been updated. Customers who connected after February 24, 2021 are using the newest integration and no action is required.

(15)



To reconnect the Integration:

1. Go to the SAP Concur App Center and locate the CIBT application.

2. Click Disconnect.

3. To reconnect, follow the steps as described in the section Setup of CIBT Integration in the SAP Concur App Center of the CIBT – Visa and Passport Alert Service Travel Service Guide.

Decommission the Search Both Primary GDS and the Southwest Direct Connect Feature

GDS Sabre, Apollo Direct Connect Southwest

Solution ID Other

X EMEA Data Center X Scan impact

TSGs Southwest Direct Connect Travel Service Guide Fact Sheets

(16)

Overview

Concur Travel will decommission the Search both primary GDS and the Southwest direct connect feature for customers that have both the GDS and Southwest Direct Connect (WNDC) enabled. Since the feature was built prior to the industry-standard branded fares concept, extensive code changes would be required to update this feature to work as expected with branded fares. SAP Concur has made the decision to decommission this feature to ensure Southwest branded fares

continue to be searchable and bookable in Concur Travel.

Targeted for July 26, 2021 the related settings will be disabled and removed for all customers. This means that after this update occurs, customers will see Southwest content only from the direct connect.

!

Concur Travel strongly recommends that customers coordinate with their agency fulfillment partner before making any changes to disable their Southwest direct connect settings. Operational updates will be required for agency fulfillment partners to support this type of change.



For more information on Southwest direct connect, refer to the Southwest Direct Connect Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

This change will simplify the setup for how Southwest Airlines’ flights and fares are sourced in Concur Travel when the direct connect is enabled. Customers will also see a reduction in scans to the GDS since these scans will no longer take place.

Configuration for Professional Travel

This feature will be decommissioned automatically; no changes are required by administrators. Once the change has been made, the Search both the primary GDS and the Southwest direct connect and the Cost savings threshold ($) settings will no longer be available.

Configuration for Standard Travel

The Search both the primary GDS and the Southwest direct connect feature is already disabled by default in Standard Travel.

(17)

FAQ

Q. I have the Southwest Airlines direct connect enabled but do NOT have the Search both the primary GDS and the Southwest direct connect setting enabled. Am I affected by this change?

A. No. Customers who have the Southwest Airlines direct connect enabled but do NOT have the Search both the primary GDS and the Southwest

direct connect setting enabled will see no change in behavior and do not need to make any changes to their current configuration.

Q. I have the Search both the primary GDS and the Southwest direct connect setting enabled and I wish to continue to use the Southwest direct connect. Do I need to make any changes?

A. No. No changes are required for customers who DO have the Search both the primary GDS and the Southwest direct connect setting enabled and wish to continue to use the Southwest direct connect. Concur Travel will remove this setting and default to only searching via the direct connect.

Southwest Airlines Full Participation in Sabre

GDS Sabre only Direct Connect

X North America Data Center X UI impact

TSGs Southwest via Travelport Travel Service Guide Southwest Direct Connect Travel Service Guide Fact Sheets

Admin Guides Other

Overview

Southwest Airlines will migrate from the current Basic Booking Request distribution model to a full content distribution model, Direct Connect Availability. This change only applies to Sabre subscribers with Point of Sale (POS) in the United States or US Territories that are approved by Southwest Airlines for ticketing.

(18)

In an effort to create a common experience for our customers, regardless of which GDS they choose, we are working with our partners, Sabre and Southwest Airlines (WN) to seamlessly migrate from the current Basic Booking Request functionality that exists today, to the full content participation functionality expected in July of 2021. The goal is to enable functionality like that which exists in our integration with Amadeus and Travelport.



For more information on the changes to Southwest in Sabre, refer to SAN16289 on Sabre.com.

CUSTOMER BENEFIT

There are several differences between the Southwest offering in Basic Booking Request and Direct Connect Availability with specific benefit to the user:

• Normal shop by price and shop by schedule paths, including branded fares content

• ARC electronic ticketing

• Pre-ticket change

• Post-ticket change

• Ticket Void

• Multi-city itineraries

• E-receipts

• Government fares for commercial customers

(19)

SEARCH RESULTS

Southwest Airlines with Sabre GDS will display brands post migration:

POST-TICKET CHANGE

Previously, Post-Ticket Change was not available for Sabre Southwest bookings. With these changes, Southwest ticket change functionality is now available for Sabre customers with the Post-Ticket Change feature enabled.



For more information on Post-Ticket Change, refer to the Post-Ticket Change Using Sabre Automated Exchanges Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation.

All functionality described in these release notes is automatically enabled for Professional and Standard Travel; no configuration is required.

(20)

Known Limitations

The following limitations have been identified to date:

• Flights to and from airports in Mexico are not yet offered in Sabre.

• Early bird check-in is not currently supported for Sabre GDS.

• Ability to shop and book mixed brands is not supported.

• Non-US POS will not see Sabre Southwest content.

FAQ

NOTE: Frequently Asked Questions may be updated as more information becomes available. Please be sure to check for updates.

Q. If we are not an ARC fulfillment agency (BSP), can we enable Southwest content in our Sabre GDS?

A. No. Southwest content will only be available for ARC agencies.

Q. Will Southwest-branded fares be available in Concur Travel?

A. Yes, branded fares functionality will be available for Sabre customers.

Q. Will Concur Travel support early bird check-in for Sabre GDS?

A. No, early bird check-in is not currently supported.

Q. If a customer currently uses Southwest Direct Connect and is interested in switching to the Sabre GDS, can their unused Southwest Direct Connect tickets be utilized for Sabre bookings?

A. No, unused ticket credits from Southwest Airlines Direct Connect cannot be settled through the ARC fulfillment process and therefore cannot be applied to Sabre GDS bookings. Customers should work with Southwest Airlines to manage the disposition of existing unused ticket credits.

Q. If a customer currently uses Southwest Airlines through Sabre Basic Booking Request, can their existing unused tickets be utilized for Sabre Direct Connect Availability bookings?

A. No, unused ticket credits from Southwest Airlines Basic Booking Request cannot be settled through the ARC fulfillment process and therefore cannot be applied to Sabre Direct Connect Availability bookings. Customers should work with Southwest Airlines to manage the disposition of existing unused ticket credits.

(21)

Q. If a customer has booked Southwest Airlines flight(s) in Concur Travel prior to their migration to full participation in Sabre, will they be able to use the new functionality available after the migration on the existing ticket(s)?

A. No, bookings made prior to the migration to full participation by Southwest Airlines in Sabre will retain the same limitations as were applicable at the time of bookings. All changes or updates to existing Southwest Airlines segments must be made by the TMC or directly with Southwest Airlines.

Travelport Seat Map Upgrade

GDS Apollo, Galileo, Worldspan Direct Connect

TSGs

Fact Sheets Travelport (Apollo/ Worldspan/ Galileo) Upgrades Fact Sheet Admin Guides

Other

Overview

Concur Travel now supports a new version of seat maps using the Travelport Universal API platform.

SAP Concur has run a pilot using pre-selected customers and TMCs. The pilot was successfully completed on June 30. Starting July 2, the new version of seat maps is available for all Travelport customers.

The new seat map user experience is accurate and reliable, considering the

customer’s Frequent Flyer status and the fare type selected. The old seat maps did not account for either of these.

The new seat map provides an improved seat selection success rate, as we now have better understanding of seat availability. The new seat map experience will be

available for more than 100 airlines via Apollo and Worldspan, and more than 140 airlines via Galileo.

(22)

The following screenshots demonstrate the current seat map display as compared to the enhanced seat map display that will be returned via the new Travelport

Universal API. The screenshots are for Air Canada between Los Angeles (LAX) and Toronto (YYZ) airports.

This new version does not change the behavior of seat maps functionality on the search results page and the users will still see a “View Only” version of the seat map for each flight option on the search results page.

The links on the Review and Reserve and post-booking Itinerary page are updated.

Current pre-booking seat map, which does not validate fare type and displays a generic seat map:

(23)

New pre-booking seat map, which validates fare type and displays an accurate seat map:

(24)

Current post-booking itinerary seat map, which does not validate fare type and displays a generic seat map:

(25)

New post-booking itinerary seat map, which validates fare type and displays an accurate seat map:

KNOWN LIMITATIONS

Like all other GDS customers, Travelport customers will not be able to purchase seats directly in Concur Travel. Users can, however, view and select seats that do not require payment and are included in the fare or the frequent flyer status. All paid seats will be shown as unavailable.

United Airlines, American Airlines, and Delta Air Lines do not use the Airline Tariff Publishing Company (ATPCO) standards, so their seat mapping may be inconsistent.

To avoid issues due to these inconsistencies, SAP Concur only applies these upgrades to the part of the process that occurs after booking is complete. Customers will still see the Select a seat link on the Review and Reserve page for these airlines, which has the same functionality as before this upgrade. American Airlines and Delta Air Lines customers will see the new experience from the Itinerary page onwards, after completing a flight reservation. Due to a third-party limitation, United Airline customers will not see the new seat map from the Itinerary page after completing a flight reservation. Concur Travel will update customers when this new experience is available for United Airline flights.

For Worldspan and Galileo customers, when users view and select seats for Air Canada flights, the seats will be shown as unavailable due to a content limitation.

(26)

No configuration change is required. There are no significant changes to the seat maps feature’s appearance and functionality.



For more information on the Universal API platform, refer to the Travelport (Apollo/ Worldspan/ Galileo) Upgrades Fact Sheet. To locate, refer to

Additional Release Notes and Other Technical Documentation in these release notes.

Profile

Allow Parentheses in Cell or Mobile Phone Numbers in User Profile

Overview

SAP Concur has modified the Mobile Phone field of the Profile page to accept parentheses in addition to dashes, spaces, and digits. Previously, parentheses were not allowed and resulted in an error. No other phone number fields, such as Work Phone and Home Phone, have been modified in this manner.

This change was made to make the user interface consistent with the Travel Profile 2.0 API, which was modified to allow parentheses in mobile phone data in

(27)

Parentheses no longer result in an error when saving the profile.

This feature is enabled by default. There are no configuration steps.

Select a Method of Payment Travel Configuration Setting (Professional Edition Only)

admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature) X Available for use: No impact to end users unless/until configuration/setup by

agency/admin (described below) (example: new rule, new Travelfusion airline) Other: Refer to the release note below

X Does not apply to this edition Source / Solution Suggestion

TSGs Fact Sheets

Overview

A new Select a Method of Payment configuration option enables companies to let users list their payment options by personal cards first, followed by company ghost cards. Previously, available of payment options listed ghost cards before personal cards by default.

The new configuration allows users to sort payment options to better match their most-often used credit cards, helping them move through the payment process more efficiently.

(28)

When the option is enabled, the sort order of credit cards in the Select a method of payment dropdown will list personal cards before ghost cards.

In the following screenshot, the first option is a personal card and the second is a ghost card. If the new setting is not enabled, the sort order defaults to ghost cards followed by personal cards.

Configuration for Professional Travel This feature is disabled by default.



To sort personal cards before ghost cards:

1. Click Administration > Travel (on the sub-menu) > Travel System Admin and select the desired client configuration.

NOTE: Depending on your permissions, this page may appear immediately after you click Administration or Travel.

2. Locate the Form Of Payment options section. Enable the In payment method selection lists, show personal (IBR) cards before ghost (CBA) cards option.



For more information, refer to the Travel System Admin User Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

(29)

TripLink

Decommission of [email protected] Functionality

TSGs Automated Emails Travel Service Guide Fact Sheets

Admin Guides

Other TripLink User Guide

Overview

As of July 22, 2021, the capability of forwarding confirmation e-mails to

[email protected] will be retired. The same functionality will continue to be available with [email protected]. Users must have their TripIt and Concur Travel accounts linked so that the confirmation e-mails sent to [email protected] are automatically synced to Concur Travel.

SAP Concur is retiring support for [email protected] because a richer service is provided through TripIt Pro. Forwarding travel plans to [email protected] will not only provide the same functionality as [email protected], but it will also improve traveler satisfaction when they use TripIt, a popular travel app and perk for business

travelers.

What the User Sees USER INTERFACE

User interface references to [email protected] have been removed.

(30)

1. Email Addresses > Travel Plans section:

2. Travel Alerts tooltip, displayed to users who are not connected to TripIt:

3. Travel Details > Add to your Itinerary menu:

(31)

AUTO REPLY EMAIL

Currently, until July 22, 2021, an email announcing the decommission (retirement) of [email protected] is being sent to users whenever email responses for success, failure or partial success email messages are sent. This email is available in

US English, UK English, French, German, and Japanese.

Hello,

We wanted to let you know that starting July 22, 2021, the option to add plans to your SAP Concur account using [email protected] will no longer be available. The most recent confirmation e-mail you forwarded is being processed as usual.

After July 22, there will still be two ways to add plans to your account:

Connect a TripIt Pro Account

Get started with TripIt Pro by signing into concursolutions.com. Under the App Center tab find the TripIt listing then select Connect to link a new or existing account. Once connected, you’ll be able to forward your confirmation e-mails to TripIt. The travel plans organized in TripIt will then sync with your SAP Concur account.

Learn more about using TripIt to manage your business travel in the TripIt listing.

If you’re arranging travel for someone else, the traveler will also need to follow the steps above to connect a TripIt account.

Manually Add Travel Plans

You can also manually add plans to your SAP Concur account on concursolutions.com.

If you have additional questions, please visit the SAP Concur Traveler Resources page, or reach out to your travel administrator.

Safe Travels, SAP Concur

After July 22, 2021 and until January 31, 2022 an email announcing that an itinerary was not imported successfully by [email protected] will be sent to users. This email will include additional instructions on alternative ways to import itineraries into

Concur Travel. This email is available in US English, UK English, French, German, and Japanese.

(32)

Hello,

The plans you forwarded were not added to your SAP Concur account.

Forwarding confirmation e-mails to [email protected] is no longer available. There are still two ways to add plans to your account:

Connect a TripIt Pro Account

Forward your confirmation e-mails to TripIt to have your travel plans organized for you.

The plans organized in TripIt will then sync with your SAP Concur account. To get started:

4. Connect an account

Sign into your SAP Concur account and connect a new or existing TripIt account in the SAP Concur App Center.

5. Verify your e-mail address

If you’re creating a TripIt account, you’ll receive an e-mail asking you to verify your e-mail address – make sure you follow these instructions to complete your set up.

6. Forward your confirmation e-mails

Once set up is complete, you can start forwarding your confirmation e-mails to [email protected]. Your plans will be imported into TripIt and synced with your SAP Concur account.

If you’re arranging travel for someone else, the traveler will also need to follow the steps above to connect a TripIt account.

Manually Add Travel Plans

You can also manually add plans to your SAP Concur account on concursolutions.com.

If you have additional questions, please visit the SAP Concur Traveler Resources page or reach out to your travel administrator.

Safe Travels, SAP Concur

(33)

Configuration for Professional and Standard Travel This feature is enabled by default with TripLink.

Beginning July 22, 2021, your travelers will need to forward business travel plans to [email protected]. Before they can do so, they will need to take a one-time action to connect a new or existing TripIt account to SAP Concur solutions (included with Concur TripLink).

NOTE: Travel arrangers will be able to forward their travelers itineraries to

[email protected] using the travelers e-mail address in the subject line, with the already existing arranger/traveler setup in the traveler’s Concur Profile.

Please make sure that the traveler has their Concur Travel and TripIt accounts linked.



For more information on TripLink, refer to the TripLink User Guide. For more information on e-mails, refer to the Automated Emails Travel Service Guide.

Miscellaneous

Ongoing Mandatory SFTP with SSH Key Authentication

April 9, 2021 April 16, 2021 Ongoing in 2021

TSGs Fact Sheets

Admin Guides File Transfer for Customers and Vendors User Guide Other

(34)

Overview

This release note is intended for technical staff responsible for file transmissions with SAP Concur products. For SAP Concur customers and vendors participating in data exchange through various secure file transfer protocols, SAP is making changes that provide greater security for those file transfers.

As of April 10, 2021, non-SFTP (Secure File Transfer Protocol) protocols and SFTP password authentication are not allowed to connect to SAP Concur for file transfers:

• Non-SFTP file transfer accounts must switch to SFTP with SSH Key Authentication.

• SFTP file transfer accounts that use password authentication must switch to SSH key authentication.

• SFTP password reset requests require the client to provide an SSH key for authentication.

!

IMPORTANT: If you are not using SFTP with SSH Key Authentication, you must take action to avoid disruption of your file transfer connections.

On April 12, 2021, SAP started disabling non-compliant file transfer connections. The process of disabling non-compliant accounts will continue throughout 2021. If you have multiple file transfer connections configured, this change applies to all of your file transfer connections.

This announcement pertains to the following file transfer DNS endpoints:

• st.concursolutions.com

• st-eu.concursolutions.com

• vs.concursolutions.com

• vs.concurcdc.cn USER/CUSTOMER BENEFIT

These changes provide greater security for file transfers.

If assistance is required, please contact SAP Concur support.



For more information, refer to the File Transfer for Customers and Vendors User Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

(35)

Ongoing Rotating PGP Key Available for File Transfers

TSGs Fact Sheets

Admin Guides File Transfer for Customers and Vendors User Guide Other

Overview

Files transferred to SAP Concur products must be encrypted with the SAP Concur public PGP key, concursolutionsrotate.asc.

• Key file is available in client’s root folder.

• Key ID 40AC5D35.

• RSA 4096-bit signing and encryption subkey.

• Key expires every 2 years.

• Client is responsible for replacing the key before it expires.

♦ Next expiry date: September 4, 2022.

♦ SAP Concur plans to replace the current rotating public PGP key in the client’s root folder 90 days before the expiration date.

The SAP Concur legacy PGP key (key ID D4D727C0) remains supported for existing clients but will be deprecated in the future.

SAP Concur strongly recommends that clients use the more secure rotating public PGP key for file transfers. To facilitate the use of the more secure rotating public PGP key for file transfers, SAP Concur added the key to existing client’s home folders on Friday, January 15, 2021.

(36)

• mft-us.concursolutions.com

• vs.concursolutions.com

• st-eu.concursolutions.com

• mft-eu.concursolutions.com USER/CUSTOMER BENEFIT

The rotating public PGP key provides greater security for file transfers.

What the Administrator Sees

An administrator with the required file transfer credentials can log into the file transfer site to retrieve the rotating public PGP key, concursolutionsrotate.asc, from the root directory.

Your internal file transfer administrator can add the key to their PGP keyring and start using it to encrypt any files being transferred to SAP Concur.

NOTE: If assistance is required, please contact SAP Concur support.



(37)

Ongoing SAP Concur Legacy File Move Migration

March 6, 2020 January 8, 2021 Ongoing until July 31, 2021

Overview

This release note is intended for the technical staff responsible for file migrations with SAP Concur solutions. For our customers and vendors participating in data exchange, SAP Concur solutions is maintaining our file transfer subsystem to provide greater security for those file transfers.

SAP Concur is in the process of migrating entities that currently use a legacy process for moving files to a more efficient and secure file routing process that relies on APIs.

Clients whose entities are currently configured to use the legacy process will be migrated to the more efficient process sometime between now and July 31, 2021.

After they are migrated to the more efficient process, clients will see the following improvement:

• With the legacy process, clients had to wait for the file move schedule to run at a specified time. With the more efficient and secure API-based process, extracts and other outbound files from SAP Concur solutions will be available within the existing overnight processing period shortly after the files are created.

(38)

These changes provide greater security and efficiency for file transfers.

If assistance is required, please contact SAP Concur support.



(39)

Planned Changes

The items in this section are targeted for future releases. SAP Concur solutions reserves the right to postpone implementation of – or completely remove – any enhancement or change mentioned here.

!

IMPORTANT: These Planned Changes may not be all of the upcoming

enhancements and modifications that affect this SAP Concur product or service.

The Planned Changes that apply to multiple SAP Concur products and/or services are in a consolidated document. Please review the additional Planned Changes available in the Shared Planned Changes Release Notes. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Flight

Planned Changes Support Southwest Post-Ticket Change via Travelport

July 2021 - October 2021

GDS Apollo, Worldspan Direct Connect

X North America Data Center X UI impact

TSGs Southwest via Travelport Travel Service Guide

Post-Ticket Change / Rapid Reprice (Apollo) Travel Service Guide

Post-Ticket Change / Rapid Reprice (Worldspan Native) Travel Service Guide Fact Sheets

Admin Guides Other

(40)

Overview

Currently, users are not able to make changes to Travelport Southwest flights after the ticket has been issued. Targeted for October 2021, Southwest Post-Ticket change functionality will be available for Travelport customers with the Post-Ticket Change feature enabled in configuration.

This change will enable users to change Southwest airline flights via Travelport through Concur Travel after a ticket is issued.

KNOWN LIMITATION

Travelport Post-Ticket changes will only be supported via Apollo and Worldspan.

Concur Travel will communicate if this functionality will be enabled for Galileo customers at a future date.

The Southwest Post-Ticket Change feature via Travelport must be enabled in your company configuration settings.



For more information, refer to the following documentation:

♦ Post-Ticket Change / Rapid Reprice (Apollo) Travel Service Guide

♦ Post-Ticket Change / Rapid Reprice (Worldspan Native) Travel Service Guide

To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

(41)

Profile

Planned Changes XML Profile Sync No Longer Available as of December 31, 2021

March 2021 -- December 31, 2021

All data centers X Profile/Profile API/3rd Party XML Sync Impact Affected Documentation

TSGs Travel Profile API Travel Service Guide Fact Sheets

Admin Guides Other

Overview

The XML Profile Sync, which is used to synchronize Concur Travel user profile data with TMC partners, will no longer be available, targeted for the end of 2021. We advise all partners to engage with SAP Concur representatives to adopt the Travel Profile v2 API for managing Concur Travel user profiles.

The XML Profile Sync was officially decommissioned in 2016 due to instability and other issues. The Travel Profile v2 API was built to replace this legacy

synchronization process. It has now reached a level of stability and maturity that there is no longer any reason to maintain multiple profile sync options.

Concur Travel

Concur Travel

Contents

!

Release Notes

Administration

Accessibility Improvement for Travel Editions of Travel System Admin



Travel E-mails Migration to Notification Services, Update Safe Sender List

Authentication

Support for HMAC Now Deprecated





Cookie Preferences and User Consent

Explicit Cookie Consent and Zero Cookie Load Expanded to More Jurisdictions (July 1)



Flight

**Ongoing** CIBT – Retirement of Legacy Integration







!



Decommission the Search Both Primary GDS and the Southwest Direct Connect Feature

!



Southwest Airlines Full Participation in Sabre





Travelport Seat Map Upgrade



Profile

Allow Parentheses in Cell or Mobile Phone Numbers in User Profile

Select a Method of Payment Travel Configuration Setting (Professional Edition Only)





TripLink

Decommission of [email protected] Functionality



Miscellaneous

**Ongoing** Mandatory SFTP with SSH Key Authentication

!



**Ongoing** Rotating PGP Key Available for File Transfers



**Ongoing** SAP Concur Legacy File Move Migration



Planned Changes

!

Flight

** Planned Changes** Support Southwest Post-Ticket Change via Travelport



Profile

**Planned Changes** XML Profile Sync No Longer Available as of December 31, 2021

Ongoing CIBT – Retirement of Legacy Integration

Ongoing Mandatory SFTP with SSH Key Authentication

Ongoing Rotating PGP Key Available for File Transfers

Ongoing SAP Concur Legacy File Move Migration

Planned Changes Support Southwest Post-Ticket Change via Travelport

Planned Changes XML Profile Sync No Longer Available as of December 31, 2021