January 2017 Invoice Standard Edition Admin Summary
PO-Based Invoices Now Have Approval Workflow Capabilities
Previously, purchase order based invoices went from employee submission to processor. With this release, clients can actively select whether they want to use this option or use the same options that are used for regular payment requests.
Business Purpose / Client Benefit: This feature gives clients more control over the workflow process by having manager approval options.
Invoice Users Can Assign Incorrectly Assigned Invoice to Correct User
Invoice users can now assign an invoice to another user if, for example, the invoice was incorrectly assigned to them. The user does not need to unassign the invoice first, but can now directly reassign the invoice.
If there is a purchase order/purchase request associated with an invoice that needs to be assigned, the corresponding Purchase Order Owner/Purchase Request Owner appears as one of the options for the user who assigns the invoice.
Business Purpose / Client Benefit: This feature makes it easier for clients to assign incorrectly assigned invoices.
Description Field of Payment Request Header Form Now Extractable
Clients can now extract the Description field of the Payment Request Header form in the Custom GL Extract for Invoice Standard.
This is applicable to both payment requests and purchase order based payment requests.
Business Purpose / Client Benefit: This feature gives clients more information about the payment requests that are extracted.
Processors Can Add Comments to Payment Requests in Paid Status
In the April 2016 release, clients were able to add comments on a payment request after it had been extracted. With this release, clients will also be able to add comments to a payment request in a paid status.
Business Purpose / Client Benefit: This feature is beneficial for clients who want to research a discrepancy between Concur and their ERP system.
System Received Date Field for When Concur Receives Invoices
Invoice will now have a field that shows the full timestamp when Concur receives an invoice. This field, System Received Date, is carried over from client-managed Capture Processing to Invoice and will be a read-only field.
Business Purpose / Client Benefit: This feature gives clients a clear view of when Concur receives invoices.
QuickBooks Desktop and QuickBooks Online Now Generally Available
Concur and Intuit have partnered to make accounting for expenses in QuickBooks easier. Concur Invoice Standard Edition lets clients import QuickBooks accounting data into their Concur configuration. This data allows clients to utilise their unique accounting data when entering payment requests. When clients choose to send the data to QuickBooks, Concur sends the expense data as payment request data.
Business Purpose / Client Benefit: These features gives clients more flexibility when working with their accounting data.
**Reminder** Change in the Monthly Release Schedule
As shown on the 2017 release calendar, starting in March, Invoice releases will occur on Saturday instead of Friday. For most users, there is no change; they see the release-related changes on Monday, which they always have done. Be aware that, starting in March, any weekend users will likely not see the release-related changes until Sunday.
**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.
