Fax Feature

In a future release, the Concur Fax Feature will be decommissioned. This change is targeted for the latter half of 2022. The Fax feature was retired in 2020. Clients onboarded after 15 July 2020 do not have access to this feature. Among clients with access, very few use the feature regularly and, among those that use it, use has declined steadily. Removal of the Fax feature improves the security, performance and scalability of SAP Concur solutions. In addition, The Concur Fax Feature attaches files only at the header level of expenses and invoices. As a result, clients who use the Fax Feature cannot take advantage of recent innovations that apply only to images and attachments at the line-item level.

Release Notes

RELEASE: **Planned Changes** Admin Summaries Streamlined Delivery (Products: Expense, Invoice, Request, Travel)

Beginning in January 2022, the implementation of shared and core features and changes to existing shared and core features will be documented in the new Shared Changes Release Notes. This will apply both when they are planned changes and when they are officially released. The release notes will no longer be distributed to product-specific release notes.

Changes that are specific to one product and that impact that product's functionality or UI for admins or for end users will continue to be documented in that product's release notes.

This change reduces duplication of information, ensures that the product-specific release notes contain product-specific information, and provides a single source for SAP Concur shared changes and changes to core technologies.

SAP Concur Support

Targeted for Q1 2022, the Solution Suggestions platform that SAP Concur provides will be migrated into the SAP Continuous Influence – Improvement Requests program. This change will provide a better user experience and a single place for Authorised Support Contact (ASC) users to engage with all SAP Concur Customer Influence programs.

To support this change, SAP Concur will no longer review suggestions submitted to the Solution Suggestions platform after 1 December 2021.

In addition to offering a better tool with more functionality, SAP Concur is improving the entire process of how ASC user ideas will be reviewed, considered, and implemented.

Security

**Planned Changes** Some TLSv1.2 Ciphers No Longer Supported (1 Feb 2022) (Products: Expense, Invoice, Request, Travel)

Beginning on 1 February 2022, SAP Concur solutions will no longer support connections to *.concursolutions.com and *api.concursolutions.com that use the following TLSv1.2 ciphers:

The following ciphers included in the ak-akamai-2020q1 cipher profile are supported:

To ensure that connections to *.concursolutions.com and *api.concursolutions.com are not disrupted, clients and partners who connect to *.concursolutions.com and *api.concursolutions.com through an application that uses an unsupported cipher must update the application to a supported cipher before 1 February 2022.

This update provides ongoing security for our products and services.

Supported Configurations

On 1 January 2022, SAP Concur plans to begin transitioning away from support for Internet Explorer 11 (IE 11). This change is in line with other SAP solutions, industry best practices and Microsoft’s lifecycle policy for IE 11.

Until Cognos 11 has been rolled out for all Analysis and Intelligence customers, we will provide support and allow exceptions for investigation to issues related to Cognos 10 and IE 11. For more information, refer to the Cognos 11 User Interface Update FAQ.

After 1 January 2022, SAP Concur development teams will not design new features, user interface enhancements or security or bug fixes with IE 11 in mind. Over time, new functionality and existing functionality might not work properly on IE 11.

SAP Concur users will not be blocked from access when using IE 11. They will still be able to sign into their SAP Concur solutions. However, to ensure their users can continue to work successfully and securely with SAP Concur solutions, SAP recommends that clients move away from allowing use of SAP Concur solutions on IE 11 and move to a more modern, supported browser.

This change enables SAP to speed up adoption of the latest browser innovations and provide a stronger security posture.

Test Entities

RELEASE: Test Entity Data Maintenance and Entity Deletion (Products: Expense, Invoice, Request)

This feature/change has been targeted for release. For information about this feature/change, refer to the applicable product release notes as indicated.

**Planned Changes** Audit Trail for Supplier Manager Not Migrated (Products: Invoice)

Some SAP Concur users use test entities to set up, test and provide training for new configurations prior to deploying them to their live production entity. SAP Concur plans to migrate test entities as part of our move to Amazon Web Services (AWS).

When test entities are migrated, the supplier audit trail associated with suppliers in Supplier Manager will not be migrated. The audit trail will be rebuilt as changes are made to supplier information after migration.

These changes apply to test entities once they are moved or created in the AWS environment, which will occur at a future date.

Once in AWS, test entities will benefit from the same stability, monitoring capabilities and level of performance as production entities.

**Planned Changes** Email Verification (Products: Expense, Invoice, Request)

Some SAP Concur users use test entities to set up, test and provide training for new configurations prior to deploying them to their live production entity. SAP Concur plans to migrate test entities as part of our move to Amazon Web Services (AWS). For more information, refer to the SAP Concur Cloud Platform Strategy FAQ.

When test entities are migrated to the AWS production environment, verified emails from the existing test entity will not carry over to the new test entity. As a result, when users test verified email functionality in a future test entity, it is recommended that the employee uses an email that is different from the email configured in their production entity. This process is required as the email in the existing test entity was most likely already verified in production and, therefore, cannot be verified in another entity.

With respect to user email addresses, the Receipt Recognition service validates user email addresses and as such, only one instance of an email address can be associated with a user account. To test in production, clients will be required to utilise alternate email addresses that are not currently associated with any production user account. If a client attempts to set up a test account in production using an email address already associated with a corresponding user profile, it will fail the validation process.

Once in AWS, test entities will benefit from the same security, stability, monitoring and performance as production entities.

**Planned Changes** Test Entity Login Updates (Products: Expense, Invoice, Request)

Some SAP Concur users use test entities to set up, test and provide training for new configurations prior to deploying them to their live production entity. SAP Concur plans to migrate test entities as part of our move to Amazon Web Services (AWS). For more information, refer to the SAP Concur Cloud Platform Strategy FAQ.

Today, a user can maintain the same login ID for their test and production entities because they are in separate environments. With the plan to migrate both test and production entities to the same AWS production environment in the future, this will no longer be possible since each login ID must be unique.

While there is no action required for customers regarding this update, we want to ensure customers are aware of it because the change will be visible in certain areas of test entities. To account for this change, SAP Concur will append all test entity login IDs with a ".uat” domain during both migration and user creation to ensure they are unique and do not conflict with existing production login IDs. For example, “johnsmith@123.com” will become “johnsmith@123.com.uat”.

This change will help to safeguard against any conflicts with production login IDs.

**Planned Changes** Most Recently Used Lists Not Migrated (Products: Expense, Invoice, Request)

Some SAP Concur users use test entities to set up, test and provide training for new configurations prior to deploying them to their live production entity. SAP Concur plans to migrate test entities as part of our move to Amazon Web Services (AWS). For more information, refer to the SAP Concur Cloud Platform Strategy FAQ.

Due to the architectural changes that SAP Concur must make to support this move, when test entities are migrated to the new environment, some Most Recently Used (MRU) list items within the test entity will not be migrated.

MRU lists consist of recent selections made by the user. These lists are generated over time as users interact with various menus and other defined lists, and they will be regenerated after the test entity is migrated to the new environment. These changes apply to test entities once they are moved or created in the AWS environment, which will occur at a future date.

Once in AWS, test entities will benefit from the same stability, monitoring capabilities and level of performance as production entities.