Model Changes

With this release, there is a new source-related field for Expense.

Description: The Is Mobile Number Entered field allows users to report on whether employees have a mobile phone number entered in their user profiles. This field can help companies identify which employees need to enter a mobile phone number to ensure they can be contacted in case of an emergency or incident.

The new employee-related field for Expense is located in the following folder:

• Expense > Lists > Employee Information

With this release, there are new first approved date-related fields for Invoice.

Description: These fields are used for calculations of approved days for Invoice.

The new first approved date-related fields for Invoice are located in the following folder:

• Invoice > Payment Request Dates and Statuses > First Approved Date Attributes

Localisation Changes

With the June release, the localisation project for Analysis/Intelligence reports, model and archive was completed except for a handful of reports that were still being localised. With the July release, all but one of the remaining reports were localised.

With the August release, the following report in the Intelligence – Standard Reports folder is now available in Bulgarian, Brazilian Portuguese, Croatian, Czech, Danish, Finnish, French Canadian, Hungarian, Norwegian, Polish, Romanian, Russian, Slovak, Spanish and Turkish:

• Persona Dashboards > Department Manager Overview > Dashboard - Department Manager Overview

With the localisation of the Dashboard - Department Manager Overview report, the Standard Reports localisation project is now complete.

MORE INFORMATION

For more information about language settings in Cognos, refer to the Localisation for Analysis/Intelligence fact sheet (English only).

Report Changes

Concur TripLink captures data from flights, hotels and ground transportation – no matter where travel is booked. This report provides access to that data – giving companies of all sizes insight into travel expenditures before they occur and a more complete picture of spend outside the corporate travel system.

Invisible spend will go down over time as clients get visibility into travel spend before travel occurs through TripLink. In addition, the information can also be used to meet "duty of care" requirements as well as track spend with specific suppliers, giving companies the information they need for better negotiations.

The report also shows quarterly trends so the Travel Manager can see if invisible spend is increasing or decreasing over time. The report shows the current quarter and the previous 4 quarters based on the Sent for Payment Date.

REQUIRED SPEND CATEGORIES

The client has the option to set up spend categories and then map expense types to those categories, in this case, to "group" data for reporting reasons. The new Invisible Spend Trend Analysis report filters on spend categories. If the client has not mapped the expense types to the spend categories, no data is returned for this report.

This report uses these spend categories:

• Airfare
• Car Rental
• Accommodation – Track Room Rate Spending
• Train

For more information about spend categories, refer to the Expense: Expense Types Setup Guide (English only).

REPORT OUTPUT

This report includes these columns:

• Quarter and Year
• Spend Amount
• % of Total

LOCATION OF THE REPORT

The report is located here:

• Analysis - Standard Reports > TripLink
• Intelligence - Standard Reports ‎> TripLink

Analysis and Intelligence clients can use the new Invisible Spend Details report to track invisible spend at employee level. Invisible spend represents the expensed amounts that are not matched to a trip, with one exception — any charges from TMC direct bookings are considered visible spend and will be excluded from this report.

Like the Invisible Spend Trend Analysis report, this report filters on spend categories. If the client has not mapped the expense types to the spend categories, no data is returned for this report.

This report uses these spend categories:

• Airfare
• Car Rental
• Accommodation – Track Room Rate Spending
• Train

REPORT OUTPUT

This report includes these columns:

• Employee
• Employee ID
• Claim Name
• Claim ID
• Sent for Payment Date
• Transaction Date
• Spend Category
• Expense Type
• Payment Type
• Supplier
• City/Location
• Country
• Default Approver
• Invisible Spend Amount

LOCATION OF THE REPORT

The report is located here:

• Analysis - Standard Reports > TripLink
• Intelligence - Standard Reports ‎> TripLink

Analysis and Intelligence clients can use the new Purchase Order to Invoice Matching Exceptions report to identify discrepancies between purchase orders and the invoices associated with the purchase orders. This report can help accounts payable employees determine which invoices require investigation. The report can also help accounts payable managers identify potential issues in the accounts payable workflow, such as seeing exceptions for the same supplier — possibly indicating an issue with the supplier, or seeing the same exception appearing numerous times, regardless of supplier, which may indicate an issue with the purchase orders being created by their organisation.

REPORT OUTPUT

This report includes these columns:

• Supplier Code
• Supplier Name
• Exception Code
• Exception Text
• Purchase Order Number
• Purchase Order Name
• PO Requested By
• Invoice Number
• Request ID
• Request Name
• Invoice Date
• # of Days Until Payment Due
• Total Approved Amount (rpt)
• Reporting Currency

LOCATION OF THE REPORT

The report is located here:

• Analysis - Standard Reports > Invoice > PO Matching Exceptions
• Intelligence - Standard Reports ‎> Invoice > PO Matching Exceptions

Concur TripLink itineraries are now excluded from the following reports:

• Adoption (Air, Car, Hotel)
• Air Adoption by Month
• Air Analysis: Concur Travel vs. Agency Summary

These three reports already exclude TripIt itineraries. Excluding both TripIt and TripLink itineraries from the reports ensures these reports provide an accurate Concur Travel online booking engine adoption rate based on itineraries initially created online using Concur Travel versus itineraries created offline using a TMC/travel agency.

LOCATION OF THE REPORTS

The reports are located here:

• Analysis - Standard Reports > Compliance
• Intelligence - Standard Reports ‎> Compliance

Other Changes

Administrators and BI Managers can now suppress alerting for up to 30 merchant category codes from the Credit Card Transactions alert.

The Credit Card Transactions alert is sent to BI Managers when a credit card transaction is equal to or greater than a defined amount, or the transaction is associated with one or more of the merchant category codes in Concur's pre-defined list of flagged merchant category codes.

When Concur encounters a suppressed merchant category code for a credit card transaction, the transaction that references the merchant category code will not appear in the Credit Card Merchant Code Alert list on Credit Card Transactions alert.

Suppressing merchant category codes can help prevent unnecessary alerts for credit card transactions associated with merchant category codes that your organisation does not want to be notified about.

Business Purpose / Client Benefit: This feature provides clients with the ability to customise alerting for flagged merchant category codes.

WHAT THE ADMIN SEES

There is a new section for suppressing merchant category codes for the Credit Card Transactions alert on the Actionable Analytics Set Up tab on the Reporting Configuration page.

Administrators can enter up to 30 merchant category codes from Concur's pre-defined list of flagged merchant category codes in the field. The merchant category codes entered on the Actionable Analytics Set Up tab will be suppressed from the Credit Card Transactions alert for all BI Managers.

To suppress alerting for merchant category codes from the Reporting Configuration page:

1. On the Reporting Configuration page, click the Actionable Analytics Set Up tab.

2. In the merchant category code suppression field, enter the merchant category codes you want to suppress.

   The merchant category codes must be one of the codes in Concur's pre-defined list of flagged merchant category codes.

3. To see the full list of codes, click the here link in Click here to see the list of available flagged merchant category codes., located above the merchant category code suppression field.

   Clicking the link opens the Flagged Merchant Category Codes page.

   To see Concur's pre-defined list of flagged merchant category codes and their descriptions, refer to the Appendix: MCC Code List section in the Analysis/Intelligence: Actionable Analytics User Guide (English only).

   The codes you enter in the field must be separated by a comma.

   For example: 4814,5131,7011

4. Click Save.

WHAT THE BI MANAGER SEES

There is a new section for suppressing merchant category codes for the Credit Card Transactions alert on the Notification Settings page.

BI Managers can enter up to 30 merchant category codes from Concur's pre-defined list of flagged merchant category codes in the field. The merchant category codes entered by a BI Manager on the Notification Settings page will be suppressed from the Credit Card Transactions alert for the BI Manager.

In addition, any merchant category codes entered by the admin on the Actionable Analytics Set Up tab on the Reporting Configuration page will also be suppressed from the Credit Card Transactions alert for the BI Manager.

For example:

The admin entered the following merchant category codes on the Actionable Analytics Set Up tab on the Reporting Configuration page: 4814, 5039, 8044

The BI Manager entered the following merchant category codes on the Notification Settings page: 5039, 7234

The following merchant category codes will be suppressed from the Credit Card Transactions alert for the BI Manager: 4814, 5039, 7234, 8044

To suppress alerting for merchant category codes from the Notification Settings page:

1. Open the Notification Settings page (Profile > Profile Settings > Notification Settings).

2. In the merchant category code suppression field, enter the merchant category codes you want to suppress.

   The merchant category codes must be one of the codes in Concur's pre-defined list of flagged merchant category codes.

3. To see the full list of codes, click the here link in Click here to see the list of available flagged merchant category codes., located above the merchant category code suppression field.

   Clicking the link opens the Flagged Merchant Category Codes page.

   To see Concur's pre-defined list of flagged merchant category codes and their descriptions, refer to the Appendix: MCC Code List section in the Analysis/Intelligence: Actionable Analytics User Guide (English only).

   The codes you enter in the field must be separated by a comma.

   For example: 4814,5131,7011

4. Click Save.

MORE INFORMATION

For more information about Actionable Analytics, refer to the Analysis/Intelligence: Actionable Analytics User Guide (English Only).

SAP Concur is in the process of enhancing the Standard Reports by Folder guide (English only). We are adding definitions of the report prompts and fields, and adding the expressions associated with the report fields for each report.

This is an ongoing project. Clients will see these guide updates as they become available.

EXAMPLES

Example of the new report prompt definition for the Itinerary Details report:

Record Locator: Used to search by the record locator assigned to the trip(s)

Example of the new field information for the Itinerary Details report:

Planned Changes

The items in this section are targeted for future releases. Concur reserves the right to postpone implementation of – or completely remove – any enhancement/change mentioned here.

SAP Concur plans to retire our Insight Premium product on 31 December 2018.

Insight Premium is a reporting product that was offered briefly, but has not been offered or updated for several years. Concur Intelligence contains the functionality originally offered with Insight Premium.

Business Purpose / Client Benefit: This retirement allows Concur to focus development resources on further enhancements to our Intelligence product whose functionality, innovation and value now exceeds that of our legacy product.

Concur Open is the SAP Concur service status dashboard, which displays known and widespread outages and incidents for select SAP Concur services and all data centres. Concur Open displays the current service status as well as incident history for the past 20 days.

In a future release, there will be new functionality added to Concur Open. Users can continue to access Concur Open and view Concur service availability; no functionality will be removed. However, with the release, SAP Concur users will be able to log in to Concur Open and:

• View service status for the services and the data centre that are specific to their company
• Access subscription options for updates about the incidents that affect the services specific to their company
• View service history for the past two years as well as detailed root cause analysis information and the actions taken by SAP Concur for specific incidents

Business Purpose / Client Benefit: Customers use Concur Open to monitor their SAP Concur services outages, status and availability. Adding this new functionality will provide customers with a personalised view of their service status and availability. SAP Concur's goal is to provide a more accurate and transparent view of incidents/outages.

Client Notifications

The list of non-affiliated subprocessors is available here: SAP Concur list of Subprocessors (English Only)

Monthly browser certifications, both current and planned, are available with the other Concur monthly release notes, accessible from What's New - Professional Edition