Concur Invoice Standard Edition Administration Help

February 2017 Invoice Standard Edition Admin Summary

QuickBooks Import Users Button Is Now Available

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

Business Purpose/Client Benefit: This functionality ensures admins can update user information for multiple users at one time.

**Coming Soon** Check for Missing Account Code Later in Workflow

Employees will be able to save, submit, and approve a payment request even if one or more account codes are missing for expenses in the payment request.

Currently, whenever an expense is saved, the system validates that an account code has been provided for the related expense type and adds that account code to the expense (a process not visible through the UI). If there is no account code associated with the expense, the expense cannot be saved.

With this update, the system will validate and add the account code to the expense after the final approval step.

After the final approval step, the payment request goes to the pre-payment processing step. If an account code does not exist for one of the expense types used in the payment request, the system will block the expense data from being extracted or posted to your financial system until your Concur company administrator provides an account code mapping for the expense type in Setup.

A new query, Financial Posting Failed, in the Processor view makes it easy to find any payment requests that cannot be extracted or posted to your financial system. Such payment requests will be flagged with an exception.

Business Purpose/Client Benefit: Employees are no longer prevented from completing their payment requests when an account code is missing in the expense type configuration. Account codes are now populated at a single, consistent point in the workflow.

**Coming Soon** Support for TLS v 1.0 Encryption Protocol Ends March 2017

Concur announces an End-of-Support 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.

Please Note New End Date Of Support Is March: We have moved the date support will end from 31 January to 31 March of 2017 in order to give our clients ample time to understand and make the required manual changes to their browser's security settings. These changes will be detailed in an upcoming service release.

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

For more information about any of these topics, refer to this month's release notes.