For a while, SAP Concur mobile app users have had the option to continue using the expense claims legacy user interface via disabling the Expense Claim (New) and Expense Claim (New) – Approver toggles on the Additional Features screen in the mobile app settings.

With this release, we have removed the Expense Claim (New) and Expense Claim (New) – Approver toggles from the Additional Features screen within the mobile app and mobile users now no longer have access to the expense claims legacy user interface.

Business Purpose / Client Benefit: This update offers a more streamlined experience to users, while they work with expense claims in the mobile app.

With this release, SAP adjusted the time allowance for two stop options within Concur Drive in the mobile app. The following stop options have been adjusted:

• The default option time went from 5 minutes to 7 minutes

• The traffic mode option time went from 10 minutes to 15 minutes

With this release, the Travel Allowance experience has been updated in the SAP Concur mobile app.

Updates are listed below:

• The New Travel Allowance screen was redesigned to better resemble the web version of the mobile app

• The manage itinerary screen now utilises swipe actions, which resembles the Claims screen

• Mobile users now have the option to switch between the simple and detailed itinerary editing mode (dependent on the allowance category)

• The error handling and presentation with visual clues have been improved to provide the user with a more simplified experience

• The defaulting of date and time input fields has been improved for a faster workflow

• After users save their itinerary, the Adjustments tab of the Travel Allowances screen automatically appears, displaying the saved itinerary details for the user

DETAILS MODE

Depending on which allowance category the user selects, they may have the option to choose between the simple or detailed itinerary mode. The detailed mode displays all fields, whereas the simple mode hides certain fields, which the system automatically populates with meaningful data.

After the user saves their itinerary, their saved itinerary details appear on the Adjustments tab of the Travel Allowances screen. The user can tap the Itinerary tab to view a summary of their itinerary.

The user can edit or delete an itinerary from the list in the Itineraries section on the Travel Allowances screen, by swiping the desired itinerary to the left and then tapping on Edit or Delete.

Users can also edit or delete an itinerary on the itinerary overview screen by tapping the more information icon (upper-right corner) and then tapping Edit Itinerary or Delete Travel Allowance on the menu that appears.

Depending on which allowance category the user has selected, additional fields for border crossing will appear. Similarly, if a user selects an allowance category with the German 3-month-rule configuration, the Arrival Location field will require the full address to be filled out. Without this configuration enabled, the user only needs to fill out the destination city field and the full address is not required. If the user configures multiple destinations, the individual destinations will appear on a header line for a better overview.

The user can also add more destinations by tapping Add Destination between the destinations.

If a user enables the Detailed Itinerary toggle - while in detailed mode - the user’s detailed changes will be lost. The system will then replace their information with defaulted values.

ERROR HANDLING

All required fields - denoted by an asterisk – need to be filled in by the user. If a required field is not filled in, the Alerts section appears at the top of the screen. Additionally, the Required Field red text will appear by the affected field. The user can tap Alerts to expand and access the list of error messages.

ADJUSTING DAILY ALLOWANCES

To view the daily allowances screen for a desired itinerary, the user can tap on the desired itinerary listed on the Travel Allowances screen. The screen with daily allowances appears, where the user can tap on individual daily allowances to further adjust the allowance.

REDESIGNED SUMMARY APPROVAL SCREEN

The redesigned summary screen provides the approver with a list of all the daily adjustments and excluded days of the itineraries. The approver can tap on the Itineraries tab to view a list of all the itineraries in the current expense claim.

With this release, we made changes to support Android version 10 (or above) where new location permission options were added to the operating system. To access and use Concur Drive within the mobile app, users - with mobile devices with Android version 10 (or above) – need to tap Allow all the time on the OS location permission window asking for location access for the SAP Concur mobile app.

With this release, Android users can now confirm a confirmation agreement while submitting a request within the mobile app.

With this release, the SAP Concur mobile app is now compatible - for mobile app users who have iOS mobile devices (iPhone / iPad) - with the iOS 14 operating system.

With the 9.83 release, SAP Concur mobile app users gained access to the new claim 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.

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

User / Customer Benefit: Travellers expect to be able to book travel on any device. After 31 March, travellers will be able to search, book and cancel Hotel Service V2-sourced hotels from within the SAP Concur mobile app.

Targeted for a future release, Travel Allowance users residing in Norway will see the new With Cooking Facility, Without Cooking Facility and None meal types on the Daily Allowance screen - in the Meal Type menu - within the SAP Concur mobile app.

Mobile app users will also see the new Overnight and None accommodation types on the Daily Allowance screen - in the Accommodation Type menu.

The Overnight and None accommodation types are provided to users as options, because the rates given by the tax authority and the tax-free rates are differentiated based on where the user stays for the night. Residents of Norway are required to provide this information for tax reporting purposes.

SAP Concur solutions updates the minimum operating system regularly in order to ensure the best possible experience for mobile users. Targeted for the October (9.85) Mobile release, SAP Concur solutions will be updating the minimum supported operating system to v7.0 (Nougat, API 24).

The September Mobile release (9.84) will be the final release for version v6.0 (Marshmallow, API 23) of the Android operating system.

Please ensure that the operating system on all user devices has been updated to at least v7.0 (Nougat, API 24).

Be aware that users will not be forced to upgrade their device’s operating system, but users who do not update older operating systems will not be able to install versions of the SAP Concur mobile app after the 9.85 October Mobile release.

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.

Business Purpose / Client Benefit: The update to this policy provides greater resources for innovations and improves overall security.

These changes are part of SAP's continued commitment to maintaining secure authentication.

Targeted for the November (9.86) Mobile release, SAP plans to retire the automatic sign-in setting in the SAP Concur mobile app. This change coincides with the redesign of the mobile sign-in page which will also be implemented with the November release.

Business Purpose / Client Benefit: The retirement of this feature better supports secure authentication by removing the less secure automatic sign-in setting.

For a while, SAP Concur mobile app users have had the option to continue using the expense claims legacy user interface via disabling the Expense Claim (New) and Expense Claim (New) – Approver toggles on the Additional Features screen in the mobile app settings.

Targeted for the October (9.85) Mobile release, SAP plans to remove the Expense Claim (New) and Expense Claim (New) – Approver toggles from the Additional Features screen and mobile users will no longer have access to the expense claims legacy user interface.

Business Purpose / Client Benefit: This update offers a more streamlined experience to users, while they work with expense claims in the mobile app.

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

Targeted for the November (9.86) Mobile release, SAP plans to retire the Mobile PIN sign-in option in the SAP Concur mobile app.

This change coincides with the redesign of the mobile sign-in page which will also be implemented with the November release.

Beginning with the November release, users will be able to switch back to the old sign-in page design and will be able to 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.

With the retirement of the mobile PIN sign-in option, users will continue to be able to sign into the mobile app via 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, 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 (English Only) and the Shared: SSO Management Setup Guide (English Only).

Business Purpose / Client 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.

Starting with the October release (9.85), when users sign in to the mobile app, they will see a message similar to the following message notifying them of the upcoming change.

Starting with the November release, users will see the new sign-in screen, including the option to go back to the old sign-in experience.

Targeted for the November (9.86) Mobile release, the Mobile Sign In page will be redesigned and improved. The enhancements will improve the user experience, improve security and simplify configuration. It will also assist customers who use more than one Identity Provider (like OKTA or Azure) for Single Sign-On (SSO).

Starting with the October release (9.85), when users sign in to the mobile app, they will see a message similar to the following message notifying them of the upcoming changes.

Starting with the November release, users will see the new sign-in pages and will 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.

For more information, refer to the Mobile Authentication Update FAQ (English Only).