Concur TravelConcur Professional/Premium

(1)

Concur Travel

Concur Professional/Premium and Concur Standard

Month Audience

Release Date: June 19, 2021

Update 1: Friday, June 25, 3: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

APIs

Travel Profile v2 API - Allow Parentheses in Cell or Mobile Phone Numbers

Please refer to the SAP Concur Developer Center Release Notes for complete details, available June 18, 2021.

Car

Car Rental Search Matrix Filter Adjustments

Prof Stan   Edition

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 Other: Refer to the release note below

X Does not apply to this edition Source / Solution Suggestion

GDS X Direct Connect X

Solution ID Other

EMEA Data Center Scan impact

North America Data Center X UI impact

China Data Center File finishing impact

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

Affected Documentation

TSGs Hertz Direct Connect Travel Service Guide Sixt Direct Connect Travel Service Guide Fact Sheets

Admin Guides Other

Overview

Concur Travel currently allows travelers to filter by car type on the search results page, within the off and on-airport car rental workflows.

OTE: Users select between off-airport and on-airport rental car searches in the

(5)

Every rental car offer is connected to a four-letter code (ACRISS) that indicates the car category, car type, transmission type, and fuel type. Concur Travel previously used a self-defined list of car types/classes that represented a mixture of these four criteria, based on historical usage.



For more information on all existing values per ACRISS code letter, please review the ACRISS car classification code.

Targeted for this release, a revised hardcoded car class list is applied to the search result matrix. Each car category displayed in the filtered search results is connected to the equivalent first ACRISS code letter, which reflects existing car categories.

For example, when a user filters for compact cars, all car offers that fall under the car category Compact (first ACRISS code letter C and D) are displayed in the search results list. This applies to all car body, transmission, and fuel types in combination with the Compact car category.

As the car images previously displayed in the search results are not a correct indicator of the car category, these will be removed.

USER/CUSTOMER BENEFIT

This change improves car rental search usability.

What the User Sees

Prior to this release, the search results displayed car classes, a combination of car category and car type (e.g., Intermediate SUV) in the top row of the matrix.

(6)

With this release, the search results include only car categories (e.g., Economy) in the top row of the matrix.

Configuration for Professional Travel Only

These changes only impact the user interface on the search results matrix.

No additional action is required by administrators to support this change.

(7)

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.

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

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 CIBT – Visa and Passport Alert Service Travel Service Guide Fact Sheets

Admin Guides Other

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.

(8)

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.

Configuration for Professional and Standard Travel



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.

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

(9)

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.

OTE: 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.

(10)

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.

(11)

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.

(12)



To reconnect the Integration:

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

7. Click Disconnect.

8. 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.

Ongoing Travelport Seat Map Upgrade

March 2021 June 2021 July 2021

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

GDS Apollo, Galileo, Worldspan Direct Connect

TSGs

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

Other

(13)

Overview

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

SAP Concur is currently running a pilot with pre-selected customers and TMCs. The pilot is targeted for completion by the end of the second quarter. If no further issues are discovered, the new seat map experience could be generally available to all Travelport customers in early July. An updated release timeline will be provided in the July release notes, potentially as an after-the-fact notification.

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 90 airlines via Apollo and Worldspan, and more than 140 airlines via Galileo.

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.

(14)

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

(15)

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

(16)

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

(17)

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,

(18)

FAQ

Q. How long do we run the pilot?

A. The pilot for will be run for two months. We will start with a select group of customers for the first month and add more customers afterwards.

Q. How is the feature enabled?

A. Customers interested in participating in the pilot may speak to their account managers, who will see that the feature is enabled.

Q. Do customers need any additional setup to test this feature?

A. No.

Q. How do I contact Concur Travel support?

A. Customers and TMCs can open tickets on Salesforce for any issues found during the pilot. It is strongly recommended that you include the text

“Travelport UAPI seat map pilot” in the title, which will enable the SAP Concur support team to clearly identify tickets related to the pilot and involve the appropriate team(s).

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

As this is a controlled pilot release, the SAP Concur Development team will enable the feature for selected customers.



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.

(19)

Ground

Park ‘N Fly Decommission

GDS

Direct Connect Park “N Fly Solution ID

Other

X North America Data Center X UI impact

TSGs

Park 'N Fly Travel Service Guide

Trip Cancel and Voids Travel Service Guide Multi-User Clone Trip Travel Service Guide Fact Sheets

Admin Guides

Other Travel Setup Guide For Concur Standard

Overview

Concur Travel currently provides travelers the capability to purchase Park ‘N Fly off-airport parking near certain airports with a discounted rate at the time of booking.

This feature was provided to offer a cost-effective alternative to on-airport parking at many airports in the United States.

For the June release, this feature is decommissioned for the following reasons:

 Continued pre-pandemic declines in usage of Park ‘N Fly booked via Concur Travel, combined with requirements to maintain the service and necessary functional updates (such as airport locations due to permanent Park ‘N Fly location closings) makes future investment in this feature uneconomical.

 Other discounted off-airport parking options are available to travelers in

(20)

In the future, Concur Travel and Park ‘N Fly will assess the viability of re-introducing the Park ‘N Fly product as an app center product, independent of the corporate booking tool.

SAP Concur has disabled this feature for all travel configurations.

No additional action is required by administrators to support this change. However, SAP Concur recommends that clients provide messaging within Concur Travel to indicate that travelers must book parking directly on the Park ‘N Fly website.

Security

Ongoing Changes to Some E-mail Subdomains

June 11, 2021 -- June 1, 2021 – TBD

TSGs Fact Sheets Admin Guides Other

(21)

Overview

SAP is adopting the Domain-based Message Authentication (DMARC) e-mail security protocol for all e-mail sent from SAP. As a result, the e-mail addresses for some e-mail sent from SAP Concur organizations will no longer be sent from the @sap.com root domain but will instead be sent from a subdomain of sap.com, such as

@example.sap.com where “example” is the subdomain.

If your organization maintains an allow list for e-mail addresses, update your allow list to include e-mail from the following domains. This will ensure that you receive e-mails sent from the sap.com root domain and its subdomains:

 @info.sap.com

 @mail.sap.com

 @*sap.com

 Add @*sap.com to minimize the need for future updates. This will allow all e-mails from the sap.com domain and its subdomains. For example, if your allow list includes @*sap.com you do not need to add @info.sap.com or

@mail.sap.com because @*sap.com encompasses those subdomains.

!

IMPORTANT! Consult with your IT department before adding

@*sap.com to your allow list as some configurations might not permit the use of this entry.

The following types of e-mail communications from SAP Concur solutions are not impacted by this change:

 1:1 e-mail communication that you have with your SAP Concur account team or other SAP representatives. These e-mails will continue to come from

@sap.com.

 System e-mails (for example expense report approvals and travel bookings) that come from concursolutions.com, tripit.com, or other SAP Concur products and solutions.

 SAP Concur Support updates (such as case notifications).

DMARC compliance provides better security for e-mails sent from SAP to its customers.

(22)

Miscellaneous

Ongoing Deprecation of HMAC Initiates Migration to SSO Self- Service

July 12, 2019 November 25, 2020 Phase I: July 2020

Phase II: July 1, 2021 Any changes since the previous monthly release are highlighted in yellow in this release note.

North America Data Center UI impact

Affected Documentation TSGs

Fact Sheets Admin Guides Other

OTE: These changes are part of our continued commitment to maintaining secure authentication.

Overview

SAP Concur support for Hash-Based Message Authentication Code (HMAC) is being deprecated. Travel Management Companies (TMCs) and SAP Concur personnel are currently assisting customers who use HMAC to migrate to SAP Concur SAML v2 SSO (SAML v2).

SAP Concur provides a Single Sign-On self-service option that enables client admins to setup 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 Single Sign-On Overview and the Single Sign-On Setup Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

(23)

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

The HMAC deprecation includes two phases:

Phase I:

 Clients must have an identity provider (IdP) or a custom SAML 2.0-compliant solution.

 Clients begin testing authentication using SAML v2.

 TMCs prepare to onboard new SAP Concur clients to SAML v2.

 Customers will be notified via release notes about the official deprecation date of HMAC. As of the official deprecation date, no new clients can be onboarded using HMAC; new clients must be onboarded to SAML v2.

 Existing clients using HMAC must migrate to SAML v2.

Phase II:

 TMCs have migrated all existing SAP Concur clients from the HMAC service to SAML v2.

 The HMAC service is deprecated. Phase II is targeted to end mid-year in 2021.

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

Configuration for Professional and Standard Travel MIGRATIONFOR TMCS

TMCs will be significantly impacted and should begin testing now to prepare for migration to SAML v2.

TMCs must set up SAML v2 instead of HMAC for their new clients. Setting up SAML v2 now allows more time for TMCs to test SAML v2 and to train internal staff to assist clients.

To prepare for Phase I of the HMAC deprecation:

 TMCs must support SAML 2.0 compliant SSO. TMCs must contract for or

(24)

To prepare for Phase I of the HMAC deprecation:

 Clients must have an Identity Provider (IdP) or a custom SAML 2.0 compliant solution.

 Clients can coordinate with SAP Concur support now to complete migration to SAML v2.

 Clients can choose to use the Single Sign-On self-service option.



For more information about the Single Sign-On self-service option, refer to the Single Sign-On Overview and the Single Sign-On Setup Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Ongoing Rotating PGP Key Available for File Transfers

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.

(25)

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.

This announcement pertains to the following file transfer DNS endpoints:

 st.concursolutions.com

 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.

OTE: 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.

(26)

Ongoing SAP Concur Legacy File Move Migration

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

Fact Sheets Admin Guides Other

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.

This announcement pertains to the following file transfer DNS endpoints:

 st.concursolutions.com

(27)

These changes provide greater security and efficiency for file transfers.

Configuration for Professional and Standard Travel 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.

Updated Naming Convention for Sub-URLs

Fact Sheets Admin Guides

Other SAP Concur Cloud Platform Strategy FAQ

Overview

As part of our overall cloud platform strategy, SAP is implementing a more consistent naming convention for the URLs used to connect to SAP Concur solutions, based on data center. Users will continue to be able to access www.concursolutions.com and

(28)

OTE: SAP is planning to remove eu1.concursolutions.com. There is currently no target date for this removal. Most clients will not be impacted by the removal of this URL. They will be able to sign in using the same method they use today. Future

communications will provide more information on the removal of this URL.

TARGETEDFORMID-JUNE 2021

 SAP will deploy us2.concursolutions.com and eu2.concursolutions.com and plans to use these URLs for future customer migration to the AWS cloud platform.



For more information, refer to the SAP Concur Cloud Platform Strategy FAQ.

 SAP will update www.concursolutions.com to automatically redirect users to the appropriate URL or SSO. Users will be directed to their established home data center (for example, eu.concursolutions.com, eu2.concursolutions.com, us.concursolutions.com, or us2.concursolutions.com). No customer data is planned to leave the North America or EMEA regional data center to which it is assigned at any time before, during, or after this change.

RESTRICTED ACCESS / ALLOW LISTS

In rare cases, clients who restrict or filter access from their corporate network to specific URLs, might need to update their configuration to enable users to connect to the new URLs. For example, clients who have an allow list configured might need to add the new URLs to their list. The information in this release note should be provided to your technical resource so that they can take appropriate action to allow access to these new URLs.

OTE: It is not a best practice to only allow specific URLs. If restricted access is a requirement, SAP recommends allowing *.concursolutions.com to avoid having to make these adjustments in the future.

This change supports future URL consistency across all global regions, and a central URL that redirects users to the appropriate data center.

Users who connect to an SAP Concur entity by navigating to

www.concursolutions.com will be redirected to the appropriate URL or single sign-on (SSO) as part of their sign-in process.

These changes occur automatically; there are no configuration or activation steps.

However, in rare cases, clients who restrict or filter access from their corporate network to specific URLs, might need to update their configuration to enable users to

(29)



For more information about our overall cloud platform strategy, refer to theSAP Concur Cloud Platform Strategy FAQ.

(30)

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.

Administration

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

May 2021 - July 2021

TSGs Fact Sheets Admin Guides Other

(31)

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.

In 2021, we plan to move 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 (DC) only, we plan to make an IP address update for all SAP Concur solutions. To ensure your organization is prepared, we recommend making any changes by July 1, 2021.

Initially, this transition affected only companies using Concur Expense. Now, e-mail from Concur Travel will also use the new e-mail infrastructure.

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.

OTE: 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

(32)

Flight

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

June 2021 June 18, 2021 July 26, 2021

GDS Sabre, Apollo Direct Connect Southwest

X EMEA Data Center X Scan impact

TSGs Southwest Direct Connect Travel Service Guide Fact Sheets

Admin Guides Travel System Admin User Guide Other

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.

(33)



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 set-up 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.

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

(34)

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 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.

(35)

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



For more information, refer to the Travel Profile API Travel Service Guide and to the SAP Concur Developer Center, Travel Profile v2 - Resource. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Travel Operations / Technical Essentials

Planned Changes PNR Queue Processing – Required ID Remarks

April 2021 April 2021 August 2021

GDS Sabre, Amadeus, Worldspan, Galileo/Apollo Direct Connect

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

Fact Sheets Admin Guides

Other Agency Partners – GDS Worksheets – PNR Acquisition (Formerly Reporting Requirements)

Overview

(36)

However, while all of these have historically been required, SAP Concur did not always reject PNRs when required fields were missing. With this update, these requirements will be enforced. Any Sabre, Amadeus, or Worldspan PNRs missing required information will be rejected and placed in the error queue. Galileo and Apollo PNRs missing required information will be rejected.



For more information, refer to the Agency Partners – GDS Worksheets – PNR Acquisition (Formerly Reporting Requirements). To locate, refer to

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

Concur Travel uses the Travel Configuration ID to match trips to the correct configuration. This information will also be used to identify Compleat-integrated customers. Without it, Concur Travel/Compleat integration features will not be available.

Configuration for Professional and Standard Travel GDS FORMAT – SABRE

Company ID

Add an invoice remark to the company level profile (Level 1 STAR) as a mandatory move line.

The format should read as follows:

5.Z*CLIQCID-<Company_ID>

Examples:

5.Z*CLIQCID-999 5.Z*CLIQCID-999 Travel Configuration ID

Add an invoice remark to the user-level profile (Level 2 STAR) as a mandatory move line. The format should read as follows:

5.Z*CLIQCONFIGID- Examples:

5.Z*CLIQCONFIGID-99999 5.CLIQCONFIGID-99999 Login ID

Add an invoice remark for the user-level profile (Level 2 STAR) as a mandatory move line. The format should read as follows:

5.CLIQUSER-<Login_ID>

(37)

OTE: In Sabre, invoice remarks do not accept the “@” sign; filter/parsers in templates should take this into consideration.

GDS FORMAT – AMADEUS

Company ID

Add an accounting remark to the company-level profile as a mandatory move line. The format should read as follows:

RM*CLIQCID-<Company_ID>

Example:

RM*CLIQCID-12345 Travel Configuration ID

Add an accounting remark to the user-level profile as a mandatory move line.

RM*CLIQCONFIGID-<TRAVEL_CONFIG_ID>

Example:

RM*CLIQCONFIGID-123456 Login ID

Add an accounting remark to the user-level profile as a mandatory move line.

RM*CLIQUSER-<Login_ID>

Example:

RM*[email protected]

Any of the following remark types are acceptable:

 Alpha-coded remarks (RMC, RMH, RMS, RMB, RMZ, RMO, RMX, etc.)

 Accounting remark (RM*)

 General remark (RM) GDS FORMAT - WORLDSPAN

Company ID

(38)

Add an invoice remark to the user-level profile (Level 3 Worldfile) as a mandatory move line. The format should read as follows:

5XX-<agency-specific-prefix>/CLIQCONFIGED-<TRAVEL_CONFIG_ID>

Example:

5IR-U25/CLIQCONFIGID-123456 Login ID

Add an invoice remark to the user-level profile (Level 3 Worldfile) as a mandatory move line. The format should read as follows:

5XX-<agency-specific-prefix>/CLIQUSER-<Login_ID>

Example:

5IR-U30/[email protected] GDS FORMAT – GALILEO

Company ID

Add a ticketing remark to the company-level profile (BAR) as a mandatory move line. The format should read as follows:

DI.FT-<agency-specific-info>-CLIQCID-<Company_ID>

Example:

DI.FT-S80-CLIQCID-12345 Travel Configuration ID

Add a ticketing remark to the user-level profile (PAR) as a mandatory move line. The format should read as follows:

DI.FT-<agency-specific-info<-CLIQCONFIGID-<TRAVEL_CONFIG_ID>

Example:

DI.FT-S90-CLIQCONFIGID-123456 Login ID

DI.FT-<agency-specific-info>-CLIQUSER-<Login_ID>

Example:

DI.FT-S96-CLIQUSER-william.never//concur.com

OTE: In Galileo, ticketing remarks do not accept the @, _(underscore), or ¤ (pillow)symbols; filters/parsers in templates should take this into consideration.

GDS FORMAT – APOLLO

(39)

Add a ticketing remark to the company-level profile (BAR) as a mandatory move line. The format should read as follows:

T-<agency-specific-info>-CLIQCID-<Company_ID>

Example:

T-S80-CLIQCID-12345 Travel Configuration ID

T-<agency-specific-info>-CLIQCONFIGID-<TRAVEL_CONFIG_ID>

Example:

T-S90-CLIQCONFIGID-123456 Login ID

T-<agency-specific-info>-CLIQUSER-<Login_ID>

Example:

T-S96-CLIQUSER-william.never//concur.com

OTE: In Apollo, ticketing remarks do not accept the @ sign; filters/parsers in templates should take this into consideration. Also, only // or [] (pillow) can be used in the CLIQUSER line. All other changes cause the information not to parse into Concur Travel.

(40)

TripLink

Planned Changes Retirement of [email protected] Functionality

May 2021 -- July 22, 2021

TSGs Fact Sheets Admin Guides

Other TripLink User Guide

Automated Emails Travel Service Guide

Overview

Targeted for 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.

(41)

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).

OTE: 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.

(42)

Client Notifications

Accessibility

Accessibility Enhancements

SAP implements changes to better meet current Web Content Accessibility Guidelines (WCAG). Information about accessibility-related changes made to SAP Concur

solutions is published on a quarterly basis. You can review the quarterly updates on the Accessibility Updates (English only) page.

Browser Certifications and Supported Configurations

Monthly Browser Certifications and Supported Configurations

The SAP Concur Release Notes – Monthly Browser Certifications document lists current and planned browser certifications. The document is available with the other SAP Concur monthly release notes.

The Concur Travel & Expense Supported Configurations – Client Version guide is available with the setup guides, user guides, and other technical documentation.



For information about accessing all release notes, browser certifications, setup guides, user guides, other technical

documentation, and supported configurations, refer to the Additional Release Notes and Other Technical Documentation section in this document.

Subprocessors

SAP Concur Non-Affiliated Subprocessors

The list of non-affiliated subprocessors is available here: SAP Concur list of Subprocessors

If you have questions or comments, please reach out to: Privacy- [email protected]

(43)

Additional Release Notes and Other Technical Documentation

Online Help – Admins

Any user with any "admin" role can access release notes, setup guides, user guides, admin summaries, monthly browser certifications, supported configurations, and other resources via online Help.

(44)

SAP Concur Support Portal – Selected Users

Access release notes, webinars, and other technical documentation on the SAP Concur support portal.

If you have the proper permissions, the Contact Support appears on the Help menu. Click to access the SAP Concur support portal, then click Resources.

 Click Release/Tech Info for release notes, technical documents, etc.

 Click Webinars for recorded and live webinars.

Concur TravelConcur Professional/Premium

Concur Travel

Contents

Release Notes

APIs

Travel Profile v2 API - Allow Parentheses in Cell or Mobile Phone Numbers

Car

Car Rental Search Matrix Filter Adjustments



Flight

**Ongoing** CIBT – Retirement of Legacy Integration





!



**Ongoing** Travelport Seat Map Upgrade



Ground

Park ‘N Fly Decommission

Security

**Ongoing** Changes to Some E-mail Subdomains

!

Miscellaneous

**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self- Service





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



**Ongoing** SAP Concur Legacy File Move Migration



Updated Naming Convention for Sub-URLs





Planned Changes

!

Administration

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

Flight

**Planned Changes** Decommission the Search Both Primary GDS and the Southwest Direct Connect Feature

!



Profile

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



Travel Operations / Technical Essentials

**Planned Changes** PNR Queue Processing – Required ID Remarks



TripLink

**Planned Changes** Retirement of [email protected] Functionality



Client Notifications

Accessibility

Accessibility Enhancements

Browser Certifications and Supported Configurations

Monthly Browser Certifications and Supported Configurations



Subprocessors

SAP Concur Non-Affiliated Subprocessors

Additional Release Notes and Other Technical Documentation

Online Help – Admins

SAP Concur Support Portal – Selected Users

Ongoing CIBT – Retirement of Legacy Integration

Ongoing Travelport Seat Map Upgrade

Ongoing Changes to Some E-mail Subdomains

Ongoing Deprecation of HMAC Initiates Migration to SSO Self- Service

Ongoing Rotating PGP Key Available for File Transfers

Ongoing SAP Concur Legacy File Move Migration

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

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

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

Planned Changes PNR Queue Processing – Required ID Remarks

Planned Changes Retirement of [email protected] Functionality