SAP Concur's Mobile App: January 2021 Release Notes



|SAP Concur Release Notes |

|SAP Concur's mobile app |

|Month |Audience |

|Version 9.87 - Associated web release: January 2021 |Client – DRAFT |

|Update #4: Wednesday, February 24, 12:00 PM PT | |

|** DRAFT ** |

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

Contents

Summary 4

Android 4

iPhone / iPad 4

Planned Changes 4

Version Information 5

Supported Phone OS 5

Supported Mobile Versions 5

Deprecating Mobile Versions 5

Latest Supported Mobile Versions 5

Release Notes 7

Android / iPhone / iPad – Fapiao Receipt Integration for China 7

Overview 7

What the User Sees 8

Android / iPhone / iPad – Multi-Leg Trips and Cash Advances Options Supported for Concur Request 31

**Ongoing** Android / iPhone / iPad – Retirement of Auto Sign-In Setting 32

Overview 32

**Ongoing** Android / iPhone / iPad – Redesign of the Sign In Page 35

Overview 35

**Ongoing** Android / iPhone / iPad – Retirement of Mobile PIN 37

Overview 38

**Ongoing** Android / iPhone / iPad – New Report Entry Experience 41

Overview 41

Enable / Disable Experience 42

Android 43

iOS 44

**Ongoing** Android / iPhone / iPad – Direct Connect Content Access 47

Overview 47

Planned Changes 49

**Planned Changes** Android / iPhone / iPad – Travel Allowance Calendar Updated 49

Overview 49

Android 50

**Planned Changes** Android / iPhone / iPad – Simplified Manual Mileage Expense Creation 51

Overview 51

**Planned Changes** Android / iPhone / iPad – Expense Report Experience Updated for e-Bunsho Users 52

Overview 52

What the User Sees 53

**Planned Changes** Android / iPhone / iPad – Mobile Deprecation Policy Update 57

Overview 57

Legal Disclaimer

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.

Summary

Android

• Android / iPhone / iPad – Fapiao Receipt Integration for China

• Android / iPhone / iPad – Multi-Leg Trips and Cash Advances Options Supported for Concur Request

• **Ongoing** Android / iPhone / iPad – Retirement of Auto Sign-In Setting

• **Ongoing** Android / iPhone / iPad – Retirement of Mobile PIN

• **Ongoing** Android / iPhone / iPad – Redesign of the Sign In Page

• **Ongoing** Android / iPhone / iPad – New Report Entry Experience

• **Ongoing** Android / iPhone / iPad – Direct Connect Content Access

• Minor issue fixes

iPhone / iPad

• Android / iPhone / iPad – Fapiao Receipt Integration for China

• Android / iPhone / iPad – Multi-Leg Trips and Cash Advances Options Supported for Concur Request

• **Ongoing** Android / iPhone / iPad – Retirement of Auto Sign-In Setting

• **Ongoing** Android / iPhone / iPad – Retirement of Mobile PIN

• **Ongoing** Android / iPhone / iPad – Redesign of the Sign In Page

• **Ongoing** Android / iPhone / iPad – New Report Entry Experience

• **Ongoing** Android / iPhone / iPad – Direct Connect Content Access

• Minor issue fixes

Planned Changes

• **Planned Changes** Android / iPhone / iPad –Travel Allowance Calendar Updated

• **Planned Changes** Android / iPhone / iPad – Simplified Manual Mileage Expense Creation

• **Planned Changes** Android / iPhone / iPad – Expense Report Experience Updated for e-Bunsho Users

• **Planned Changes** Android / iPhone / iPad – Mobile Deprecation Policy Update

Version Information

Supported Phone OS

|Device |Operating System |

|Apple iPhone |Version 12.0 or greater – users will be able to upgrade to the current version |

|Apple iPad |Version 12.0 or greater – users will be able to upgrade to the current version |

|Google Android |Version 7.0 or greater – users will be able to upgrade to the current version |

Supported Mobile Versions

Note the following:

• Applicable for 9.84 and newer: If the current mobile app on your mobile device is older than the two latest versions, you will be notified - through a Message Center message and push notifications – that you should update the app to the latest version.

• If you have a version of the app older than the last 4 versions on your mobile device, you will see an upgrade notice on the login page and will need to update the app to the latest version or you will no longer be able to access the SAP Concur mobile app on your device.

N The SAP Concur mobile app will not be removed from mobile devices that have a version of the app older than the last 4 versions.

← For more information on the retention policy, refer to this FAQ.

Deprecating Mobile Versions

|Platform |Deprecating Version |

|iPhone/iPad |9.80, 9.81, 9.82, 9.83 |

|Android |9.80, 9.81, 9.82, 9.83 |

Latest Supported Mobile Versions

|Platform |Latest Version |Available |How to Update |

|iPhone/iPad | | |Update via App Store |

|Android | | |Update via Google Play |

Locate Version Information on the iPhone

To check the version number on the iPhone:

[pic]

Locate Version Information on the Android

To check the version number on the Android:

[pic]

Release Notes

Android / iPhone / iPad – Fapiao Receipt Integration for China

Overview

With the January (9.87) Mobile release, mobile users – whose SAP Concur deployment is on the China Data Center – now have the ability to capture and upload fapiao into Concur Expense via the SAP Concur Fapiao Capture mini app - within the WeChat™ app. The SAP Concur Fapiao Capture mini app provides the ability to capture and upload a fapiao to an expense according to Chinese regulatory or government authorities.

A fapiao is a legal receipt required for business transactions, employee reimbursement and VAT deduction. A fapiao is issued by the State Taxation Administration of the People's Republic of China but provided by the merchant.

N The SAP Concur Fapiao Capture mini app is only available to users whose SAP Concur deployment is on the China Data Center. Other datacenters are not included at this time.

The Fapiao Receipt Integration feature includes:

• Offering a fapiao solution in compliance with State Taxation Administration of the People's Republic of China and as provided by the merchant

• Providing reimbursement and VAT reporting process efficiency, reducing time to perform these tasks

• Capturing of VAT fapiao and non-VAT fapiao documents via the SAP Concur Fapiao Capture mini app embedded in the WeChat™ mobile app

• Supported fapiao and documents include:

• General VAT fapiao in paper form

• Special VAT fapiao in paper form

• General VAT fapiao in electronic form as stored in WeChat™ Wallet

• Official China Rail tickets

• Official airline tickets issued by China Aviation

• Official taxi fapiao

• Uploading of fapiao and documents to Concur Expense:

□ For VAT fapiao, a validation is performed against State Taxation Administration of the People's Republic of China prior to the fapiao upload

□ For VAT fapiao, a duplication check is performed prior to the fapiao upload

□ Additional documents, such as itemized receipts, can also be uploaded with each fapiao submission

• Improving efficiency when capturing and merging multiple documents into one e-receipt transaction

← For more information about regulations on capturing a fapioa, refer to the State Taxation Administration of the People's Republic of China.

Unsupported fapiao or documents for the initial feature release include:

• Electronic VAT fapiao in OFD format, including both general and special VAT

• Fixed amount fapiao

• Vehicle sales fapiao

• Freight Special fapiao

• Traffic fee fapiao

• Secondhand vehicle fapiao

Business Purpose / Client Benefit

This feature provides mobile users with a paperless receipt option that adheres to requirements and regulations for China for paper into electronic tax receipt processing and compliance.

N Users must use the SAP Concur Fapiao Capture mini app embedded in the WeChat™ mobile app - which was specifically built for fapiao capture - to capture a fapiao. The SAP Concur Fapiao Capture mini app is the only compliant means of fapiao capture and upload to Concur Expense. For VAT fapiao, captured fapiao in the WeChat™ app satisfies government requirements on fapiao authenticity and uniqueness.

What the User Sees

To capture legal copies of original paper receipts, you must use the SAP Concur Fapiao Capture mini app – embedded in the WeChat™ mobile app. You can also upload fapiao information from the WeChat™ Wallet.

You can take a picture of a paper receipt in the SAP Concur Fapiao Capture mini app. Once the picture is taken, the mobile app uploads the image to an approved third-party vendor for validation. Once the validation process is complete, you will receive a message - in SAP Concur Fapiao Capture mini app - indicating success or failure.

Capture

Capture a Fapiao With the Camera - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To capture a fapiao in the SAP |

| |Concur Fapiao Capture mini app: |

| |1) On the SAP Concur 发票助手 |

| |screen, tap [pic] (lower-left |

| |corner). |

| |2) On the camera screen, tap |

| |[pic]. |

|[pic] [pic] |3 On the next camera screen, tap |

| |Use Photo (lower-right corner). |

| |4) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, |

| |Fapiao Capture verifies and |

| |extracts the fapiao information |

| |from the captured photo. |

|[pic] [pic] |Once the system has finished |

| |verifying the fapiao, the verified|

| |fapiao appears on the To be Sent |

| |tab on the SAP Concur发票助手 |

| |screen. |

| |For VAT fapiaos, the【验】stamp |

| |implies that a validation has been|

| |performed against the State |

| |Taxation Administration of the |

| |People's Republic of China. |

| |5) On the To Be Sent tab, tap on |

| |the desired verified fapiao. |

| |6) On the Detail screen: |

| |Fill in the fields (if any) and |

| |make the desired selections. |

| |Tap Send to Concur (bottom of the |

| |screen). |

| |NOTE: You can edit the transaction|

| |date on the Detail page, only if |

| |the verified fapiao is a non-VAT |

| |fapiao (for example, taxi, air |

| |tickets, train tickets etc.). |

|[pic] |7) When done, tap Send to Concur |

| |to submit the verified fapiao to |

| |Concur Expense. |

Capture a Fapiao From Existing Photos - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To capture a fapiao from existing |

| |photos on the Receipts screen: |

| |1) On the SAP Concur 发票助手 |

| |screen, tap [pic]. |

| |2) On the Recents screen, you can |

| |do the following: |

| |Tap the desired existing photo |

| |Tap Preview to preview the |

| |selected fapiao photo |

| |Tap Done to capture the existing |

| |fapiao photo |

| |Tap Cancel to exit the Recents |

| |screen |

|[pic] [pic] |3) Once the desired fapiao photo |

| |is selected on the Recents screen,|

| |tap Done. |

| |4) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, |

| |Fapiao Capture verifies and |

| |extracts the fapiao information |

| |from the captured photo. |

|[pic] [pic] |Once the system has verified the |

| |fapiao, the information appears on|

| |the To Be Sent tab on the SAP |

| |Concur 发票助手 screen. |

| |5) On To Be Sent tab, tap on the |

| |desired verified fapiao. |

| |6) On the Detail screen: |

| |Fill in the fields (if any) and |

| |make the desired selections |

| |Tap Send to Concur (bottom of the |

| |screen) |

| |7) When done, tap Send to Concur |

| |to submit the verified fapiao to |

| |Concur Expense. |

Capture Multiple Fapiaos From Existing Photos - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To capture multiple fapiaos from |

| |existing photos on the Receipts |

| |screen: |

| |1) On the SAP Concur 发票助手 |

| |screen, tap [pic]. |

| |2) On the Recents screen, select |

| |the desired photos and then tap |

| |Done. |

|[pic] [pic] |3) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, |

| |Fapiao Capture verifies and |

| |extracts the fapiao information |

| |from the captured photo. |

| |Once the system has verified the |

| |multiple fapiao, the information |

| |then appears on the To Be Sent tab|

| |on the SAP Concur 发票助手 screen.|

| |4) On the To Be Sent tab, tap on |

| |the desired verified fapiao. |

|[pic] [pic] |5) On the Multiple Fapiao screen, |

| |you can: |

| |Tap the photo (top of the screen) |

| |to view the full screen of |

| |multiple verified fapiao photos |

| |Tap the desired verified fapiao to|

| |view/edit the fapiao details on |

| |the Detail screen |

| |Swipe the desired verified fapiao |

| |to the left to delete it |

|[pic] |6) When done, tap Send to Concur |

| |to submit the multiple verified |

| |fapiao information to Concur |

| |Expense. |

Scan a QR Code to Capture a VAT Fapiao - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To scan a QR code to capture a VAT|

| |fapiao: |

| |1) On the SAP Concur 发票助手 |

| |screen, tap [pic]. |

| |2) On the camera screen, you can |

| |do the following: |

| |Scan the VAT fapiao QR code |

| |Tap [pic] to go to the Recents |

| |screen |

| |Tap [pic]to go back to the SAP |

| |Concur 发票助手 screen |

| |NOTE: The QR code scan option is |

| |not available for non-VAT fapiaos.|

|[pic] [pic] |3) Once the VAT fapiao QR Code has|

| |been scanned, tap [pic] to go to |

| |the Recents screen. |

| |4) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, |

| |Fapiao Capture verifies and |

| |extracts the fapiao information |

| |from the captured photo. |

|[pic] [pic] |Once the system has finished |

| |verifying the fapiao, the verified|

| |fapiao appears on the To be Sent |

| |tab on the SAP Concur发票助手 |

| |screen. |

| |For VAT fapiaos, the【验】stamp |

| |implies that a validation has been|

| |performed against the State |

| |Taxation Administration of the |

| |People's Republic of China. |

| |5) On the To Be Sent tab, tap on |

| |the desired verified fapiao. |

| |On the Detail screen: |

| |Fill in the fields (if any) and |

| |make the desired selections |

| |Tap Send to Concur (bottom of the |

| |screen) |

| |6) When done, tap Send to Concur |

| |to submit the verified fapiao to |

| |Concur Expense. |

Capture a VAT Fapiao From the WeChat™ Wallet - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To capture a VAT fapiao via the |

| |WeChat™ Wallet: |

| |1) On the SAP Concur 发票助手 |

| |screen, tap [pic] (lower-right |

| |corner). |

| |2) On the SAP Concur 发票助手 |

| |Apply window, tap Allow to obtain |

| |your electronic fapiao from the |

| |WeChat™ Wallet. |

| |NOTE: The SAP Concur 发票助手 |

| |Apply window only appears the |

| |first time you capture a VAT |

| |fapiao via the WeChat™ Wallet. |

|[pic] [pic] |3) On the Receipts List screen, |

| |select the desired receipt. |

| |4) On the Receipts List screen, |

| |tap OK (lower-right corner). |

| |NOTE: The OK button displays the |

| |amount of selected receipts in |

| |parenthesis. |

|[pic] [pic] |5) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, |

| |Fapiao Capture verifies and |

| |extracts the fapiao information |

| |from the captured photo. |

| |Once the system has finished |

| |verifying the fapiao, the verified|

| |fapiao appears on the To be Sent |

| |tab on the SAP Concur发票助手 |

| |screen. |

| |For VAT fapiaos, the【验】stamp |

| |implies that a validation has been|

| |performed against the State |

| |Taxation Administration of the |

| |People's Republic of China. |

| |6) On the To Be Sent tab, tap on |

| |the desired verified fapiao. |

|[pic] |7) On the Detail screen: |

| |Fill in the fields (if any) and |

| |make the desired selections |

| |Tap Send to Concur (bottom of the |

| |screen) |

| |8) When done, tap Send to Concur |

| |to submit the verified fapiao to |

| |Concur Expense. |

Itemize

Add an Itemized Attachment to a Fapiao - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To add an itemized attachment to a|

| |fapiao: |

| |1) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, tap|

| |on the desired verified fapiao. |

| |2) On the Detail screen, tap [pic]|

| |(lower-right corner). |

| |3) On the window, you can either |

| |tap: |

| |Attachment |

| |-or- |

| |Delete Fapiao |

| |-or- |

| |Cancel |

| |NOTE: For this example, tap |

| |Attachment to attach a receipt to |

| |a fapiao transaction. |

| |4) On the window, tap Attachment. |

|[pic] [pic] |Fapiao Capture processes the |

| |receipt attachment. |

|[pic] |Once Fapiao Capture processes the |

| |receipt attachment, a message |

| |appears – on the Attachment screen|

| |- confirming the attachment was |

| |added. |

Delete

Delete a Verfied Fapiao - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To delete a verified fapiao: |

| |1) From the SAP Concur 发票助手, |

| |on the To Be Sent tab, swipe the |

| |desired verified fapiao to the |

| |left. |

| |2) Tap Delete. |

|[pic] |The verified fapiao no longer |

| |appears on the To Be Sent tab on |

| |the SAP Concur 发票助手 screen. |

| |NOTE: You can delete a verified |

| |fapiao – only before sending it |

| |to Concur Expense - in the SAP |

| |Concur Fapiao Capture mini app. |

Delete Multiple Verfied Fapiaos - iPhone

|Screen(s) |Description/Action |

|[pic] |To delete multiple fapiaos: |

| |1) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, |

| |tap on the desired multiple |

| |fapiao. |

| |2) On the Multiple Fapiao screen,|

| |tap Delete all Fapiao (lower-left|

| |corner). |

| |The multiple fapiao no longer |

| |appear on the To Be Sent tab on |

| |the SAP Concur 发票助手 screen. |

| |NOTE: You can delete multiple |

| |fapiaos – only before sending |

| |them to Concur Expense - in the |

| |SAP Concur Fapiao Capture mini |

| |app. |

Send

Send a Single Fapiao to Concur Expense - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To send a single fapiao to Concur |

| |Expense: |

| |1) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, |

| |swipe the desired verified fapiao |

| |to the left. |

| |2) Tap Send. |

| |3) On the Detail screen, tap Send |

| |to Concur. |

|[pic] [pic] |4) On the Send this Fapiao to |

| |Concur? window, tap Send. |

| |5) On the Overview of Fapiao Flow |

| |window, you can review the |

| |following fapiao capture process |

| |steps: |

| |Collect Fapiao |

| |Concur data / add attachment |

| |Send to Concur |

| |Manage expense report |

| |6) Once done with reviewing the |

| |fapiao capture process steps, tap |

| |OK. |

Send Multiple Fapiaos to Concur Expense - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To send multiple fapiaos to Concur|

| |Expense: |

| |1) From the SAP Concur 发票助手 |

| |screen, on the To Be Sent tab, tap|

| |the desired multiple fapiao. |

| |3) On the Multiple Fapiao screen, |

| |tap Send to Concur. |

| |4) On the Send multiple Fapiao to |

| |Concur? window, tap Send. |

|[pic] |5) On the Overview of Fapiao Flow |

| |window, select the applicable |

| |options and then tap OK. |

View Fapiaos Sent To Concur Expense - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To view fapiaos sent to Concur |

| |Expense: |

| |1) On the SAP Concur 发票助手 |

| |screen, tap Expenses. |

| |2) On the Expenses screen, tap the|

| |desired fapiao. |

| |NOTE: Once the fapiao is uploaded |

| |to Concur Expense, the fapiao |

| |appears in Available Expenses, |

| |Available Receipts, and in the |

| |expense list, like any other |

| |receipt. |

|[pic] |The Expense screen appears with |

| |the fapiao information displayed |

| |at the top of the screen. |

| |NOTE: You will need to sign into |

| |the SAP Concur mobile app to view |

| |the submitted fapiaos in Concur |

| |Expense within the mobile app. |

| |IMPORTANT: SAP cannot guarantee |

| |compliance of fapiao receipts if |

| |you are not using the SAP Concur |

| |Fapiao Capture mini app - embedded|

| |in the WeChat™ mobile app - to |

| |capture and upload receipts to |

| |Concur Expense. |

Configuration / Feature Activation

The change occurs automatically; there are no additional configuration or activation steps.

Android / iPhone / iPad – Multi-Leg Trips and Cash Advances Options Supported for Concur Request

With this release, Concur Request users can now create multi-leg trips within the air and rail segments of a travel request in the SAP Concur mobile app.

[pic]

Additionally, Concur Request users can now view and create cash advances in the mobile app.

[pic] [pic]

Business Purpose / Customer Benefit

This update provides Concur Request users with a more streamlined experience while creating a travel request within the mobile app.

Configuration / Feature Activation

The change occurs automatically; there are no additional configuration or activation steps.

**Ongoing** Android / iPhone / iPad – Retirement of Auto Sign-In Setting

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

Overview

|Information First Published |Information Last Modified |Feature Target Release Date |

|September 9, 2020 |February 2, 2021 |November - March |

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

With the November release, SAP Concur solutions retired the automatic sign-in setting in the SAP Concur mobile app. This change coincided with the redesign of the mobile sign-in page.

! IMPORTANT: Between the November release (9.86) and the March release (9.89), users can switch back to the old sign-in page design and, if the autologin property is enabled for their company, users can use the automatic sign-in setting in Concur mobile app Settings.

Between the November and March releases, admins should confirm that users are aware of this change.

Business Purpose / Customer Benefit

The retirement of this feature better supports secure authentication by removing the less secure automatic sign-in setting.

What the User Sees

Users see the redesigned sign-in page. The redesigned sign-in page does not support the automatic sign-in setting.

Between the November release (9.86) and the March release (9.89), users can switch back to the old sign-in page design and, if the autologin property is enabled for their company, the user will be able to use the automatic sign-in setting in Concur mobile app Settings.

N The following screenshots were taken from an iPhone. The experience is similar on other devices but might have a slightly different appearance.

Auto Sign-In Settings

[pic] [pic]

The option to switch between the old and new page designs will no longer be available beginning with the March (9.89) release and the auto sign-in setting will no longer be available.

The user no longer sees the Auto Sign In setting on the Security page in Concur mobile app Settings.

← For more information on the new mobile sign-in experience, refer to the **Ongoing** Android / iPhone / iPad – Redesign of the Sign In Page release note in the SAP Concur mobile app release notes.

Configuration / Feature Activation

This change occurred automatically; there are no additional configuration or activation steps.

← For more information, refer to the Mobile Authentication Update FAQ.

**Ongoing** Android / iPhone / iPad – Redesign of the Sign In Page

Overview

|Information First Published |Information Last Modified |Feature Target Release Date |

|October 2019 |February 2 2021 |November - March |

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

The Mobile Sign In page has been redesigned and improved. The enhancements improve the user experience, improve security, and simplify configuration. These changes also assist customers who use more than one Identity Provider (like OKTA or Azure) for Single Sign-On (SSO).

Users see the new sign-in pages and have an option to switch back to the old sign-in page design. The option to switch between the old and new page designs will no longer be available beginning with the March (9.89) release.

N The following screenshots were taken from an iPhone. The experience is similar on other devices but might have a slightly different appearance.

Old Sign-In Experience

[pic] [pic]

New Sign-In Experience

N The options on the screen that appear after a user enters their username, email address, or SSO code differ depending on their company’s configuration.

[pic] [pic]

Configuration / Feature Activation

The change occurred automatically; there are no additional configuration or activation steps.

← For more information, refer to the Mobile Authentication Update FAQ.

**Ongoing** Android / iPhone / iPad – Retirement of Mobile PIN

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

Overview

|Information First Published |Information Last Modified |Feature Target Release Date |

|October 2019 |February 2, 2021 |November - March |

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

With the November (9.86) Mobile release, SAP Concur solutions retired the Mobile PIN sign-in option in the SAP Concur mobile app.

This change coincided with the redesign of the mobile sign-in page which was implemented with the November release.

Users can switch back to the old sign-in page design and can use the Mobile PIN sign-in option on that page. The option to switch between the old and new page designs will no longer be available beginning with the March (9.89) release.

! IMPORANT: Between the November and March releases, admins should confirm that users are aware of this change and ensure that users can sign in using one of the supported methods listed in this release note.

With the retirement of the mobile PIN sign-in option, users can continue to sign into the mobile app through the following methods:

• Single Sign-On (SSO)

□ Mobile SSO

□ SAP Concur SAML v2 SSO (SAML v2)

• Username and password

• Verified email address and password

For companies that have Single Sign-On (SSO) enabled for the web version of SAP Concur solutions, we recommend that they enable SSO on the SAP Concur mobile app, ideally migrating to SAML v2.

← For information about migrating to SAML v2, refer to the SSO Service: Overview Guide and the Shared: SSO Management Setup Guide.

Business Purpose / Customer Benefit

The retirement of this feature better supports secure authentication by removing the less secure PIN option, simplifies the way users sign into the SAP Concur mobile app, and makes the mobile sign-in experience more consistent with the web sign-in experience.

What the User Sees

Users see the new sign-in screen, including the option to go back to the old sign in experience.

N The following screenshots were taken from an iPhone. The experience is similar on other devices but might have a slightly different appearance.

Old Sign-In Experience

[pic] [pic]

New Sign-In Experience

N The options on the screen that appears after a user enters their username, email address, or SSO code, differ depending on their company’s configuration.

[pic] [pic]

Forgotten Passwords

If a user installs or upgrades to version 9.86 (or later) of the mobile app and they enter their retired mobile PIN in the Password field on the redesigned sign-in page, they will receive a message that the password is invalid and will be prompted to reenter their password.

N Between the November (9.86) and March (9.89) releases, users can switch back to the old page design, and can use their PIN to sign in on that page. Users must have an alternate, supported sign-in method before installing the March (9.89) release.

If a user has forgotten their password, there are several ways they can reset it:

• Users can reset their password by tapping Forgot Password on the sign-in screen.

• Users can reset their password by going to Profile > Profile Settings > Change Password within the web version of SAP Concur solutions.

N In some SAP Concur configurations, the ability for users to reset their passwords is disabled. If password reset is disabled and you need to reset your password, contact your company’s designated resource (for example, a Company Administrator) to address this issue.

← For more information on the new mobile sign-in experience, refer to the **Ongoing** Android / iPhone / iPad – Redesign of the Sign In Page release note.

Configuration / Feature Activation

The change occurred automatically; there are no additional configuration or activation steps.

← For more information, refer to the Mobile Authentication Update FAQ.

**Ongoing** Android / iPhone / iPad – New Report Entry Experience

Overview

|Information First Published |Information Last Modified |Feature Target Release Date |

|August 20, 2020 |February 2, 2021 |August 2021 |

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

With the August (9.83) Mobile release, SAP Concur mobile app users gained access to the new report entry experience within the mobile app. The new user interface is available exclusively in "preview mode" in implementation environments.

Once SAP has received and addressed customer feedback, a migration of this experience - from implementation environments to production environments - will be scheduled. In the meantime, customers can escalate any detected issues to SAP Concur support.

[pic] [pic]

Enable / Disable Experience

This new experience can be enabled / disabled via a toggle on the Additional Features screen in the mobile settings. The toggle is titled Report Entry Experience for the Android mobile devices or Expense Report (New) / Expense Claim (New) [US / UK] for iOS mobile devices.

New Expense Details Screen Experience

The new expense details screen will not appear, if the user adds the following expense entries to an expense report:

• Personal Car Mileage, Company Car Mileage, Japan Public Transport expense types

• Expenses created via itineraries

Android

Enable / Disable the Report Entry Experience

|Screen(s) |Description/Action |

|[pic] [pic] |To enable / disable the Report |

| |Entry Experience: |

| |1) On the home screen, tap [pic] |

| |(upper-left corner). |

| |2) On the side-menu screen, tap |

| |Settings. |

| |3) On the Concur Settings screen,|

| |tap Additional Features. |

|[pic] |4) On the Additional Features |

| |screen, either swipe the Report |

| |Entry Experience toggle to the |

| |right or the left. |

(Spain) Receipt Digitization Android Users

With the January (9.87) Mobile release, Spain Receipt Digitization Android users will have access to the new UI in their production environments. This experience can be disabled anytime in the Mobile app settings.

← To enable / disable the new report entry experience, refer to the Enable / Disable Experience section of this release note.

iOS

With the January (9.87) Mobile release, iOS mobile users can now preview their receipts from the Expense screen. Additionally, users now have access to the newly redesigned menu - with allocation, attendee, and itemization options - on the Expense screen.

Access the Receipt Preview View While Creating an Expense in an Open Expense Report - iPhone

|Screen(s) |Description/Action |

|[pic] [pic] |To access the receipt preview |

| |view while creating an expense in|

| |an open expense report: |

| |1) On the home screen, tap |

| |Expense Reports. |

| |2) On the Reports screen, tap the|

| |desired expense report. |

| |3) On the report screen, tap |

| |[pic] (upper-right corner). |

| |4) On the New Expense screen, tap|

| |Add Receipt. |

| |5) On the menu, tap: |

| |Attach via Camera to use your |

| |device camera |

| |Attach via Photo Album to select |

| |an image in your device photos |

| |Receipt Store to select an image |

| |in your Concur Receipt Store |

| |NOTE: Turn the device |

| |horizontally or upside down to |

| |correctly adjust the camera |

| |screen. |

| |Once the desired receipt is |

| |uploaded to the Concur Receipt |

| |Store and attached to the |

| |expense, it will appear in the |

| |receipt preview view at top of |

| |the Expense screen. |

Access the Redesigned Allocation, Attendees, and Itemization Options From an Expense Created in an Open Expense Report - iPhone

|Screen(s) |Description/Action |

|[pic] |To access the redesigned |

| |allocation, attendees, and |

| |itemization options from an |

| |expense created in an open |

| |expense report: |

| |1) On the home screen, tap |

| |Expense Reports. |

| |2) On the Reports screen, tap the|

| |desired expense report. |

| |3) On the report screen, tap |

| |[pic] (upper-right corner). |

| |4) On the New Expense screen, tap|

| |[pic] (upper-right corner). |

| |5) On the menu, tap: |

| |View Itemizations to view |

| |itemizations and itemization |

| |View Attendees* to view the |

| |desired attendees |

| |Delete Expense to delete the |

| |expense from the report |

| |NOTE: Options will only appear in|

| |the menu that are applicable to |

| |the expense type the user has |

| |selected. |

N Customers can send feedback about their experience to SAP Concur support.

Configuration / Feature Activation

There are no additional configuration or activation steps.

**Ongoing** Android / iPhone / iPad – Direct Connect Content Access

|Information First Published |Information Last Modified |Feature Target Release Date |

|March 26, 2020 |October 1, 2020 |May 2020 |

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

! IMPORTANT: SAP is delaying the release of Mobile Parity, originally targeted for March 31st, due to an issue discovered in later rounds of validation. This issue specifically impacts the addition of a Direct Connect Hotel to an existing Air booking, which fails processing in TMC's back office procedures. Engineering teams are currently engaged.

Overview

On March 31, 2020, SAP Concur mobile app users will have the ability to shop, book, and cancel content from Hotel Service V2.

N Airbnb content remains unsupported in the SAP Concur mobile app.

[pic]

Example:

[pic]

User/Customer Benefit

Travelers expect to be able to book travel on any device. After March 31st, travelers will be able to search, book, and cancel Hotel Service V2-sourced hotels from within the SAP Concur mobile app.

Configuration / Feature Activation

The change is automatically enabled. There are no additional configuration or activation steps. These updates are enabled automatically for all sites with content that is available through Hotel Service V2 Direct Connect, with the exception of Airbnb.

Planned Changes

**Planned Changes** Android / iPhone / iPad – Travel Allowance Calendar Updated

Overview

|Information First Published |Information Last Modified |Feature Target Release Date |

|February 16, 2020 |-- |February 2021 |

Targeted for the February (9.88) Mobile release, the calendar - in the new Travel Allowance experience - will be updated in the SAP Concur mobile app.

N This update will only appear for mobile users with the new Travel Allowance experience – in the mobile app - on their mobile devices.

Business Purpose / Customer Benefit

This change will make the Travel Allowance calendar more accessible.

Android

Before

[pic]

After

[pic]

Configuration / Feature Activation

The change occurs automatically; there are no additional configuration or activation steps.

**Planned Changes** Android / iPhone / iPad – Simplified Manual Mileage Expense Creation

Overview

|Information First Published |Information Last Modified |Feature Target Release Date |

|February 1, 2021 |-- |February 2021 |

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

Targeted for the February (9.88) Mobile release, we will be simplifying the manual mileage expense creation for Drive users within the mobile app. Drive users – with the Variable Rates configuration enabled – who wish to create a manual Mileage expense will no longer see the Vehicle and Passengers fields on the Mileage screen. Additionally, these fields are not available to mileage expenses created automatically by Drive since the same configurations apply.

[pic]

N There will be no changes to these fields within the expense report and Drive users can edit them once the manual mileage expense is moved to a report.

Business Purpose / Customer Benefit

This update provides Drive users with a more streamlined experience while creating a manual mileage expense in the mobile app.

Configuration / Feature Activation

The change occurs automatically; there are no additional configuration or activation steps.

**Planned Changes** Android / iPhone / iPad – Expense Report Experience Updated for e-Bunsho Users

Overview

Targeted for the February (9.88) Mobile release, we will be updating the expense report user interface (UI) for e-Bunsho users within the SAP Concur mobile app.

In addition to a more modern, usable, and stable user interface, e-Bunsho users will now have access to features - only available in the new UI - including:

• Delete Report (all Timestamped Receipts are Retained in the Expense List/Receipt Store)

• Recall Report

• Cost Object Approval

• Sort and Filter Options When Approving Company Bill Statements

• Missing Receipt Declaration/Affidavit

• Support for Launching an External URL

• Metrics in Cognos Reports

Business Purpose / Customer Benefit

This update addresses the unique needs of e-Bunsho users, provides them with improved usability and stability, and introduces new features.

What the User Sees

Access Expense Reports List in the Mobile App via the e-Bunsho User View:

iPhone

|[pic] |To access an expense report in the mobile |

| |app: |

| |1) On the home screen, tap Expense Reports. |

| |2) On the Reports screen, tap the desired |

| |report. |

Android

|[pic] |To access an expense report in the mobile |

| |app: |

| |1) On the home screen, tap Expense Reports. |

| |2) On the Reports screen, tap the desired |

| |report. |

Access Expense Report Details in the Mobile App via the e-Bunsho User View:

iPhone

|[pic] |To access report details in the mobile app: |

| |1) On the Reports screen, tap the desired |

| |report. |

| |2) On the Report screen, tap the Details tab.|

| |The Details tab appears with report details. |

Android

|[pic] |To access report details in the mobile app: |

| |1) On the Reports screen, tap the desired |

| |report. |

| |2) On the Report screen, tap the Details tab.|

| |The Details tab appears with report details. |

Approve a Submitted Expense Report in the Mobile App via the e-Bunsho User View:

iPhone

|[pic] |To approve a submitted expense report in the |

| |mobile app: |

| |1) On the home screen, tap Approvals. |

| |2) On the Approvals screen, tap the desired |

| |report. |

| |3) On the Report Approval screen, either tap |

| |Send Back or Approve. |

Android

|[pic] |To approve a submitted expense report in the |

| |mobile app: |

| |1) On the home screen, tap Approvals. |

| |2) On the Approvals screen, tap the desired |

| |report. |

| |3) On the Report Approval screen, either tap |

| |Send Back or Approve. |

Configuration / Feature Activation

The change occurs automatically; there are no additional configuration or activation steps.

**Planned Changes** Android / iPhone / iPad – Mobile Deprecation Policy Update

Overview

|Information First Published |Information Last Modified |Feature Target Release Date |

|October 1, 2020 |-- |January 2021 |

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

Targeted for the January (9.87) Mobile release, SAP Concur solutions plans to reduce maintaining mobile app access and security for the current version and previous 6 versions (total of 7 versions) to the current version and 2 previous versions (total of three versions). This means that a user will be signed out automatically if they haven't updated the SAP Concur mobile app over the course of 3 updates (typically 3 months) and is using the fourth most recent version.

For example, users with the 9.84 version of the mobile app on their mobile devices - after the January (9.87) Mobile release - will automatically be logged out of the app. Once users have updated the mobile app on their mobile devices to version 9.85 or higher of the app, they will be able to sign back into the SAP Concur mobile app.

N Mobile app users - who are on the third most recent version - will be notified via a message in the Message Center and push notifications – that they should update the mobile app to the latest version. Once the user upgrades the app to the latest version, they will no longer receive these messages and notifications.

Business Purpose / Customer Benefit

The update to this policy provides greater resources for innovations and improves overall security.

Configuration / Feature Activation

The change occurs automatically; there are no additional configuration or activation steps.

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or 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’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or 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. 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.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download