Concur Invoice Standard Edition Administration Help

November 2016 Expense Standard Edition Admin Summary

QuickBooks

Import Users Button Hidden When Connected to QuickBooks

The Import Users button on the Users page of Setup is now hidden when Concur is connected to a QuickBooks company for customers using QuickBooks Online or using QuickBooks Desktop with the QuickBooks Web Connector.

Business Purpose / Client Benefit: This functionality helps prevent the creation of duplicate users in your Concur company.

User Import

Change Login ID Using "New Login ID" Field

With this release, admins using the User import who want to change the login ID value for an employee can now do so using a new field, New Login ID, in the User Import Excel template. This enhancement resolves a fix in the September release that prevents update of this value using the Login ID field. Prior to that fix, admins would incorrectly use the Login ID field and in the process corrupt user data.

Business Purpose / Client Benefit: This enhancement fixes an issue introduced in the September service release, and improves the overall ability to change a login ID using the User import template..

Expenses

Expanded Access to Payment Types

Users now have additional choices in the Payment Type list when creating an expense manually or via ExpenseIt. Users can select a payment type representing the card they used when incurring the expense. The cards available in the Payment Type list are configured by the company admin.

This enhancement does not affect corporate card charges from the credit card feed. Today corporate card charges have a fixed payment type, and this will not change.

Business Purpose / Client Benefit: This enhancement benefits companies with one or more credit card programs that are not tied to a corporate credit card feed.

Administration

Reminder: Support Ending for Deprecated APIs

As described in the Feb 2016 release notes, the effective date for the deprecation of the following Concur APIs was May 19, 2016. In two weeks, as of November 19, 2016, the APIs will be retired, and Concur will not address any new issues concerning them.

The Concur Platform deprecation policy is available here: https://developer.concur.com/tools-support/reference/deprecation-policy.html (English only)

Deprecated APIs and API Functions

API

API Function

Allocation

Create Allocation v3.0

Delete Allocation v3.0

Get Allocation Details v1.1

Get Allocation Info v1.1

Itemization

Get Itemization v3.0

Update Itemization v3.0

Delete Itemization v3.0

Post Expense Entry Itemization 1.1

List

Update List v3.0

Attendee/Attendee Type

Get Attendee v1.0

Delete Attendee v3.0

Create Attendee Type v3.0

Delete Attendee Type v3.0

Business Purpose / Client Benefit: This update removes outdated or unused APIs and API functions. Additional information is available on the Concur Developer Portal: https://developer.concur.com (English only).

Japan Public Transportation (JPT)

Jorudan Maintenance

The JPT database of stations and lines received routine maintenance changes such as additions, name changes, and removals.

Business Purpose / Client Benefit: Lists in Expense continue to reflect JPT's current stations and lines.

New Allocation Error Message

With this release, the Japan Public Transportation (JPT) feature will now alert the user whenever they attempt to add a route following the allocation of an existing route. In this scenario, the employee adds one or more routes, allocates them, and then attempts to add another route. The system detects this, and displays an error message notification that the existing allocation(s) will be removed from the expense report.

This change aligns the JPT feature with the behavior of Expense whenever an additional entry is added to an already allocated report. Under these conditions, the system always alerts the user and prevent the addition of another entry (or route).

Business Purpose / Client Benefit: This enhancement makes the Japan Public Transportation feature complement the behavior of other features within Expense and prevents the user from attempting to create an erroneous report.

**Coming Soon** Expense Assistant (Tentatively scheduled for January 2017 release)

Expense Assistant will soon be available for Expense. Expense Assistant has the following features:
  • The feature is enabled by default for the company, but can be turned off, if needed, at the company level to block access for all users. If the company allows access to Expense Assistant, each individual user will be allowed to opt in to use this feature.

  • If there are any expenses in the Available Expenses area, Expense Assistant will add them to an expense report.

  • Expense Assistant will not add expenses to a returned expense report. The exception is when a returned report includes a transaction that now matches an expense in the Available Expenses area.

    For example, if the returned report contains an ExpenseIt expense, and a credit card transaction that matches that expense is in the Available Expenses area, when the report is returned, Expense Assistant will combine the ExpenseIt transaction with the credit card transaction..

  • When the user opens an expense report, any transactions added by Expense Assistant since the user last viewed the report will be formatted in bold. The bolding will be removed when the user opens and views that expense.

  • Expense Assistant sends a summary email of all the activity that happened in the expense report to the user once a week.

Business Purpose / Client Benefit: This feature automates more of the expense reporting process, to provide an easier end user experience.

**Coming Soon** Support for TLS v 1.0 Encryption Protocol to End March of 2017

Concur announces an End of Support (March 2017) cycle for version 1.0 of the TLS encryption protocol, continuing support for the more secure 1.1 and 1.2 versions of TLS. As background, the TLS protocol allows secure back and forth communications between a phone or computer and a cloud-based service. Note that, since less than 1% of Concur users are logging in to Concur Solutions using browsers or phones limited to version 1.0, a very small number of users are affected by this support discontinuation.

Business Purpose / Client Benefit: Concur is taking this step after careful consideration of both the client’s security and ease of upgrade to the newer, more secure 1.1 and 1.2 versions of TLS. This end of life plan for TLS v 1.0 ensures our clients are communicating with Concur services in a safe and secure manner using TLS v. 1.1 and newer.