Admin

SAP Concur is transitioning to a new email infrastructure for outbound email from our services to SAP Concur users. Because of this, companies who filter inbound email based on the sending IP address must add new IP addresses to their Safe Sender list to ensure that their users receive email from SAP Concur.

Initially, the issue described here affected only companies that use Concur Expense. Starting in January, email from other SAP Concur services (such as Travel and Concur Pay) will move to the new email infrastructure.

We will continue to add other services. Please monitor the release notes for more information about the timing of the additional changes.

With this release, customers must access SAP Concur products and services via the following domains:

• *.concursolutions.com

• *.concurcdc.cn

SAP Concur recommends clients migrate to one of the domains at their earliest convenience, if they are not already using one of them.

Please contact appsec@sap.com for any questions regarding this change.

Business Purpose / Client Benefit: This change will allow customers to access SAP Concur services in a consistent, secure manner.

Company Cards

For customers who use the Amex TMKD feed format for Business Travel Accounts (BTA), SAP Concur has improved the usability of the merchant name displayed in Available Expenses.

Before this change, Available Expenses displayed the data from the Merchant Name field received in the feed. With this change, Available Expenses displays the data from the Do Business As field from the feed. If there is no data in the Do Business As field, the data from the Merchant Name field continues to display.

Business Purpose / Client Benefit: This change is especially helpful when managing hotel transactions and allowing a user to properly identify a hotel merchant name versus a travel agency processing the booking.

E-Receipts

Uber will be deprecating an older connection method to Concur Expense, called SMTP or Receipt Images via Email, on 24 July. Uber will begin emailing certain SAP Concur users, asking them to reconnect their Concur Expense account to their Uber account.

This is a result of Uber updating their integration to the more robust SAP Concur Receipts v4 API and subsequently deprecating the SMTP connection. SMTP is a non-App Centre connected / non-OAuth integration which forwards PDF images of receipts to the user’s Concur Expense account.

Specifically, SAP Concur users who can expect this email are those that set up a Business Profile within the Uber app, selected Concur as their Expense provider and verified an email address associated with their Concur Expense account. Connecting to SMTP was available until March 2019.

SAP Concur users who, when prompted by this email, reconnect their Concur Expense and Uber accounts will continue to receive e-receipts from Uber displayed in Concur Expense.

User / Customer Benefit: Uber will be deprecating their SMTP/Receipt Images via Email connection in favour of the more robust Receipts v4 integration in the SAP Concur App Centre. The SMTP connection did not provide many of the features offered by the Receipts v4 integration, including pre-populated expense fields and matching to corporate card transactions (if available).

Benefits of the new Receipts v4 integration available in the SAP Concur App Centre include:

Expense Pay - Global

Expense Pay – Global for Concur Expense now supports the following commercial credit card programme for the United States Dollar (USD $):

• Comerica – Mastercard – US

Business Purpose / Client Benefit: This additional option can expedite the processing of credit card expenses.

Expense Pay

SAP Concur’s Expense Pay (classic) products execute payments associated with processing expense claims. To ensure compliance with ever-changing regulatory requirements, tailored to geo-diverse markets, SAP Concur has engaged dedicated, experienced, third-party payment-processing partners and developed a next-generation pay product: Expense Pay – Global.

As previously announced in these release notes (September 2017), moving forward, SAP Concur will use one Expense Pay product to service your business anywhere in the world. SAP Concur’s Expense Pay – Global product will replace our existing legacy Expense Pay (classic) offerings (including NA Pay, EMEA Pay and next APA Pay.) For SAP Concur clients with an Expense Pay product, Expense Pay – Global will be our go-forward product. This notification begins our sunset process for all legacy Expense Pay (classic) products.

EXPENSE PAY – NORTH AMERICA SUNSET DATE: 1 SEPTEMBER 2019

Over 4000 customers have already migrated to Expense Pay – Global. Customers paying in USD and CAD must switch their subscription from the depreciating service, “Expense Pay – North America”, to “Expense Pay – Global” prior to the 1 September retirement date. Expense Pay – Global supports USD, CAD, GBP and EUR today. Customers using other currencies on classic Expense Pay are not required to migrate those currencies this year but are welcome to start the migration process. Contact paymigration@concur.com to discuss and schedule your migration.

EXPENSE PAY – NORTH AMERICA AND EXPENSE PAY – EMEA LIMITATIONS

SAP Concur does not support clients adding the following currencies with the classic product: United States Dollars, Canadian Dollars, Mexican Pesos, European Euro, Swiss Franc, Danish Krone, Swedish Krona or UK Pounds. If a client has already implemented and is using these currencies with the classic product, they can continue using these until they are migrated to the new platform or until the defined sunset date.

Please also be aware of the following release note in this document: Expense Pay | New Approval Process for Classic Funding Accounts.

Business Purpose / Client Benefit: The Expense Pay – Global offering maintains industry best practices for payment processing functionality within SAP Concur.

In preparation for the deprecation of classic Expense Pay, customers who want a new funding account in the following currencies are required to contact SAP Concur support to have their request reviewed:

• United States Dollar (USD)

• Canadian Dollar (CAD)

• Mexican Peso (MXN)

• European Euro (EUR)

• Swiss Franc (CHF)

• Danish Krone (DKK)

• Swedish Krona (SEK)

• UK Pound (GBP)

After the June 2019 release, new funding accounts created in the above currencies will default to On Hold status and will not be available to process payments until they are reviewed by SAP Concur support and the migration team and approved for use.

In this instance, on the Funding Accounts tab of the Configure Batches page, the On Hold column will display Yes for the newly created funding or pre-funding account.

Customers will see the following text when creating a new funding account in North America (NA), Europe, Middle East, or Africa (EMEA) currencies for direct-debit or pre-fund funding type accounts (after they click Save), directing them to contact SAP Concur support:

"Classic Expense Pay offerings are being deprecated and limited support is available for customers already using NA and EMEA currencies until a defined deprecation date. Please contact SAP Concur support to have your request for a new account reviewed."

Additionally, the following new text displays on the Funding Account page for all users of classic Expense Pay to remind users of the limitations:

"SAP Concur no longer supports customers adding new funding accounts for the following currencies: United States Dollar (USD), Canadian Dollar (CAD), Mexican Peso (MXN), Euro (EUR), Swiss Franc (CHF), Danish Krone (DKK), Swedish Krona (SEK) or UK Pound (GBP). New funding accounts in these limited currencies must be reviewed and approved by SAP Concur support. If a client is already implemented and is funding with an account in one of these currencies with the classic product, they can continue using these currencies until they are migrated to the new offering or until the deprecation date, which will be communicated separately by SAP Concur. Please contact paymigration@concur.com if you have questions about the migration process."

Business Purpose / Client Benefit: This additional text supports the migration of classic Expense Pay customers to the use of Expense Pay Global.

Integration

The SAP integration with Concur Solutions has been updated to support a Payment Confirmation workflow step for Concur Expense. This enhancement can replace the payment confirmation flat file import. The payment confirmation process in the integration differs from the flat file import in the following ways:

The Payment Confirmation enhancement is available to clients who use the SAP Integration with Concur Solutions with the following SAP systems:

• SAP ECC 6.0 SP12

• SAP S/4HANA SP09

Business Purpose / Client Benefit: This enhancement provides more accurate and timely information about the payment cycle for expense claims and replaces the flat file import.

Next Generation (NextGen) Expense

Update: In order to respond to and take advantage of feedback from customers, and to align with SAP Concur’s commitment to ensure a smooth and successful transition, we are working on a revised deployment strategy for Next Generation Expense.

SAP Concur is dedicated to the consistent improvement of our products, not only the features they provide, but also the experience of using those features. How users interact with technology changes over time, along with needs and expectations. We are constantly listening to our customers and soliciting feedback on how we can improve the user experience.

NextGen Expense is the continued evolution of the SAP Concur user experience. It was built from extensive user research and data analytics that include 680 1:1 conversations, 58 usability studies, 3,000+ survey responses and 1.3B monthly user actions.

Customers will have the ability to preview and then opt in to NextGen Expense before the mandatory cutover.

Business Purpose / Client Benefit: The result is the next generation of the Expense user interface designed to provide a modern, consistent and streamlined user experience. This technology not only provides an enhanced UI, but also allows SAP Concur to react more quickly to customer requests to meet changing needs as they happen.

Authentication

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

When a user signs in to SAP Concur, one of the validation processes includes checking for and adhering to any IP Restrictions (IPRs). IPRs are specific IPs or IP ranges that are defined by a company to restrict the IPs from which their users can sign in to SAP Concur. An IPR can be a string that contains a list of acceptable IP addresses and/or IP address patterns, for example: "170.242.6.43;170.243.70.42;170.243.70.43;171.159.*.*".

Currently, IPRs are set for each of a company's travel configurations, which creates maintenance issues for companies with many travel configurations and provides opportunities for errors. In addition, new travel configurations are not automatically included and can easily be forgotten.

Targeted for the August release, SAP Concur will change this setting from a configuration-level setting to a company-level setting. With the change, one set of IPRs will apply to the entire company.

Be aware that there are very few customers who will be affected by this change. In addition, all of the affected customers will be contacted individually – in advance – by SAP Concur to make any required settings changes.

Business Purpose / Client Benefit: Customers who use IPRs can be assured that the IPRs apply to the entire company.

(Release note updated: 8 June)

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

In a future release, the SAP Concur Sign In page will be updated, providing a new login experience for both direct SAP Concur username/password users and Single Sign-On (SSO) users. SSO users will be able to start the SP-initiated SSO login process at www.concursolutions.com. This feature is planned for 2019.

The new Sign In page will include a two-step login process that will provide enhanced security, meet current industry standards and provide a better login success rate. This feature is planned for 2019.

Business Purpose / Client Benefit: This feature provides better security and a faster, convenient experience for users logging in to SAP Concur products and services.

(Release note updated: 8 June)

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

Single Sign-On allows users to access multiple applications using one set of login credentials. Currently, SAP Concur has two methods for signing in: with a user name and password or using SSO with identity provider (IdP) credentials, such as a user's login credentials for their organisation.

SAP Concur is planning to add a Manage Single Sign-On (SSO) feature to SAP Concur products that provides clients with a self-service option for setting up SSO for their organisation. SSO is currently supported for Concur Expense, Invoice, Request and Travel.

The new Manage Single Sign-On (SSO) feature is a replacement tool for clients using existing SSO configuration and a new tool for clients that now want to implement SSO at their organisation. Existing SSO configuration and the new SSO Self-Service tool will both be available until everyone has migrated to the new SSO Self-Service tool.

Other SAP Concur products and services are outside the scope of this initial release.

This feature is targeted for Q3 2019.

Business Purpose / Client Benefit: This feature provides SAP Concur customers with a self-service option for setting up SSO and for existing SSO customers who must eventually migrate to the new SSO service to manage SSO for their users.

Budget Insight

Budget Insight is a budget management tool that is being retired on 31 December 2019. It is recommended that clients who want to use budget functionality purchase the new Budget product that SAP Concur released last year. The new Budget feature offers greater functionality, an improved UI and additional integrations with SAP Concur products. Most notably is the inclusion of additional expense data from Concur Expense, Concur Invoice, Concur Travel and Concur Request (previously only data from Concur Expense and Concur Request were available).

Business Purpose / Client Benefit: The retirement of Budget Insight will provide clients with the opportunity to purchase the new Budget product, which gives greater value to clients by making budgets visible, actionable and near real-time.

Business Purpose / Client Benefit: This enhancement makes it easier for clients to see what product they use.

Company Cards

SAP Concur will soon offer an American Express (Amex) business card connection. The Amex Business Card direct connect feature will allow customers to connect Amex business credit cards while in Concur Expense.

The Amex Business Card feature provides the following functionality:

• Provides an automatic daily refresh of transactions from Amex to SAP Concur (Concur Expense users do not need to sign into Amex to refresh transactions)

• Offers compatibility with SAP Concur Expense Assistant

• Allows the primary card holder to manage transactions without having to view all supplemental card transactions

• Supports Delegate and Proxy capabilities on transactions

• Provides transaction currency handling for foreign transactions

• Includes viewing available transactions

• Includes Concur Analytics for Standard reporting (including unsubmitted transactions)

Business Purpose / Client Benefit: This feature provides SAP Concur customers with a business card connector.

For customers using the JP Morgan Chase (JPMC) MasterCard card feed, SAP Concur has modified the handling of certain inbound transactions to allow them to display as regular expenses. Specifically, inbound transactions that have the following ARC type and description pairings:

Business Purpose / Client Benefit: This change will allow certain transactions to display (as intended by the issuer, JPMC) as regular expenses (rather than being hidden, as they currently can be, based on your configuration) so that users can include them on expense claims.

E-Receipts

As part of our ongoing commitment to e-receipts and the effortless expense claim, air e-receipts generated by SAP Concur based on ticket and coupon data from GDS and some TripLink transactions will be getting a new look. The new e-receipt format will be released in stages, targeting the July/August timeframe. User / Client Benefit: This change brings air e-receipts up to SAP Concur’s standard e-receipt format, providing users with a more consistent experience in Concur Expense. The format is also more convenient for users working in NextGen Expense. This change also eliminates a performance/stability issue for end users who would sometimes not see new air e-receipts as quickly as they should.

E-receipt technology is evolving quickly. Today, the receipt handling rules are hardcoded to accept e-receipts to meet image requirements. Moving forward, as e-receipts become more common, and legislation about them becomes more complex, this is not a valid assumption for all countries and circumstances.

Clients who want to maintain their current system behaviour, that is to continue to accept e-receipts to meet image requirements, will need to configure a custom receipt rule.

Business Purpose / Client Benefit: This change will allow clients who use e-receipts to continue to comply with regulatory and contractual requirements for documentation to substantiate an expense.

FTP Updates

Non-SFTP (Secure File Transfer Protocol) protocols and password authentication will eventually be deprecated.

NEW CUSTOMERS

New file transfer accounts must use SFTP with Secure Shell (SSH) Key Authentication.

EXISTING CUSTOMERS

Existing non-SFTP file transfer accounts need to switch to SFTP with SSH Key Authentication.

Business Purpose / Client Benefit: These changes provide greater security for file transfers.

SAP Concur will implement source Internet Protocol (IP) checking for all Europe, the Middle East and Africa (EMEA) file transfer accounts beginning on 15 July 2019.

NEW CUSTOMERS

The IP addresses for new customers will be added by SAP Concur during new customer implementation to the SAP Concur access control list (ACL).

EXISTING CUSTOMERS

Please contact SAP Concur support by 1 July 2019 to have your source IP addresses added to the SAP Concur access control list (ACL).

Business Purpose / Client Benefit: These changes provide greater security for file transfers.

Quick Expense

SAP Concur will be deprecating the Quick Expense v3 API in a future release. This API will be replaced by Quick Expense v4. Developers using Quick Expense v3 should transition to Quick Expense v4 when it is available.

Business Purpose / Client Benefit: The Quick Expense v3 API only supports the previous authentication method, and it provides access to some fields that are not necessary to expose. These issues are resolved with the new Quick Expense v4 API.

SAP Concur will be releasing Quick Expense v4 for partner and client use. Quick Expense v4 includes the following improvements over Quick Expense v3:

• Secure authentication: This API supports the current SAP Concur authentication method.

• Multi-part messages: A developer can post both the data & receipt image in a single call rather than separate calls required by v3.

• Supports digitisation status: Quick expense v4 POST API supports the eBunsho timestamp requirement, if the client is using this functionality and has completed the required configuration in Concur Expense.

• Global availability: Quick expense v4 POST API is supported in all SAP Concur data centres.

Quick Expense v4 removes some of the functionality available in v3:

• ReceiptImageID attribute will no longer be exposed: This attribute may contain personally identifiable information and therefore has been removed to increase data security.

• GET, PUT and DELETE endpoints will no longer be exposed: These endpoints are not provided in v4 as there is no known business need.

Business Purpose / Client Benefit: This new version of the Quick Expense API supports the latest SAP Concur API authentication method and provides several enhancements to the POST functionality.

Receipts

SAP Concur will soon allow the conversion of paper receipts into digital copies with legal value. Receipt Digitalisation will provide SAP Concur customers the ability to conform a paper receipt into a legal digital copy according to their country's regulatory or government authorities.

Once it is available for general release, this feature will be available to new customers and existing customers in France and those who have configurations in France. Additional countries will be included in future releases.

The initial release for France will include:

• Enabling the conversion of paper receipts into digital copies with legal value

• Viewing the “Certified” status of the receipt in NextGen Expense (planned enhancement)

• Ability to configure an audit rule that looks for expenses with certified receipts

The Receipt Digitalisation feature requires that users must be using the NextGen Expense UI. It is recommended that customers migrate to the NextGen Expense UI before activating this service.

To capture legal receipt images, clients must also be using the SAP Concur mobile app and can use ExpenseIt with the mobile app, though ExpenseIt is not required. The user will take a picture of the paper receipt with the mobile app. Once the picture is taken, the digitisation process will be applied to the image. Once the process is complete, a stamp will display on the receipt image in the mobile app confirming whether the receipt is certified or not.

Receipt images will display for users in NextGen Expense in Available Expenses, Available Receipts and in the expense list.

Approvers and processors will view the digital receipt status in the expense claim and expense list in the existing version of Concur Expense. An audit rule can be created that identifies certified receipts on the expense line item. A new icon will display for receipts that are certified.

Business Purpose / Client Benefit: This feature provides a paperless receipt option that adheres to local requirements and regulations for paper into digital tax receipt processing and compliance.