Concur Release Notes
Invoice Standard
Month Audience
January 2017
Initial Post: Friday, January 20, 3:00 PM PT Client – FINAL
Contents
Release Notes ... 1
Invoice Management ... 1
PO-Based Invoices Now Have Approval Workflow Capabilities ... 1
Invoice Users Can Reassign Invoices Directly to Another User ... 2
Description Field of Payment Request Header Form Now Extractable ... 5
Processors Can Add Comments to Payment Requests in Paid Status ... 5
System Received Date Field When Concur Receives Invoices ... 6
QuickBooks Desktop and QuickBooks Online Now Generally Available ... 8
**Reminder** Change in the Monthly Release Schedule ... 9
**Coming Soon** Support for TLS v 1.0 Encryption Protocol Ends March 2017 ... 9
Supported Configurations ... 10
Monthly Browser Certifications ... 10
Additional Release Notes and Technical Documentation Standard Edition .... 11
Concur Support Portal ... 11
Online Help: Admins ... 11
Release Notes
This document contains the release notes for the Invoice functionality for Concur Standard edition. Clients with the Expense or Travel products should review the respective release notes, located on the Concur Support Portal.
Invoice Management
PO-Based Invoices Now Have Approval Workflow Capabilities
Overview
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.
What the Admin Sees
The admin will see the two following options in the Approval Routing step of Setup:
• Apply the same approval routing as regular payment request (what is selected above)
Configuration/Feature Activation
The admin configures this feature in the Approval Routing step of the Setup Wizard.
For more information, refer to the Invoice: Approval Routing Setup Guide for Concur Standard Edition.Invoice Users Can Reassign Invoices Directly to Another User
Overview
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 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.
What the User Sees
For non PO-based invoices
If the user wants to assign an unsubmitted invoice, they can do so from the My Request page by clicking the new Assign button.
For PO-based invoices generated within Concur
If the user wants to assign the unsubmitted PO-based invoice, where the PO is generated within Concur, they can do so from the My Request page.
For example, Chris Collins needs to reassign a PO-based invoice that was incorrectly assigned to him. He opens the payment request, and then clicks the new Assign button as is shown in the image.
The Assign Requests window appears, where Chris can see who the purchase request owner is (in this example, Terry Brown) and select him.
Once Chris has clicked Assign, the request will be assigned to the original purchase request owner, that is, Terry Brown.
For PO-based invoices created outside of Concur
In cases where the AP user needs to assign the externally created PO-based invoice, they can do so by clicking the new Assign button or the Select Request Owner link.
In the window that appears, the AP user can see by whom the purchase order was requested, and assign the PO-based invoice to that user.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
Description Field of Payment Request Header Form Now Extractable
Overview
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.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
Processors Can Add Comments to Payment Requests in Paid Status
Overview
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.
What the Processor Sees
The processor will be able to see a comment box in which they can enter
information. This comment box only appears when the payment request is in an extracted or paid state.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
For more information, refer to the Invoice Administration User Guide for Concur Standard Edition.System Received Date Field When Concur Receives Invoices
Overview
When clients create payment request manually, Invoice shows the full date stamp in the Created Date field. In this release, Invoice will now have a field that shows the full timestamp when Concur receives an invoice through Capture Processing. 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.
What the Processor Sees
The processor will see a new option, System Received Date, in the Column Label list of the Preferences window.
In addition, the processor will see the System Received Date option in the Query Builder window.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
For more information, refer to the Invoice Administration User Guide for Concur Standard Edition.QuickBooks Desktop and QuickBooks Online Now Generally Available
Overview
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 utilize 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.
For more information, refer to the QuickBooks Resource page(http://www.concurtraining.com/customers/tech_pubs/_Docs_CCC_QuickBoo ks.htm).
**Reminder** Change in the Monthly Release Schedule
Overview
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.
Release Calendar
The release calendar is available here:
http://www.concurtraining.com/customers/tech_pubs/ReleaseCalendar/_ReleaseCale ndar_client.htm
**Coming Soon** Support for TLS v 1.0 Encryption Protocol Ends March 2017
Overview
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.
Note that, since less than 1% of Concur users are logging in to Concur Solutions by using browsers or phones limited to version 1.0, a very small number of users are affected by this support discontinuation.
PLEASE NOTE NEW END DATE OF SUPPORT IS MARCH
We have moved the date support will end from January 31 to March 31 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.
What This Means: The Client Experience
For our clients, the use of an unsecured connection can expose confidential data, resulting in compromised sessions across any TLS channel of communication (for example, Concur services). For this reason, Concur is alerting the client now to
with Concur, client admins can begin assessment of compliance with newer versions of TLS at their companies.
WHAT DEVICES ARE AFFECTED BY THIS CHANGE?
In general, browsers and phones using TLS to establish inbound/outbound
communication channels with Concur services are affected. Each device may or may not be capable of upgrade to support TLS v 1.1 and later versions.
INFORMATIONAL BANNER TO DISPLAY
A banner will now display whenever a user attempts to log in using a browser that does not support TLS v 1.1 and later and thus cannot negotiate a connection. The intent is to alert the client to this upcoming change using an informational-only message.
TRANSITIONING TO THE NEW VERSION AT THE WORKPLACE
Transitioning to support for TLS v 1.1 and later may simply require updating your browser. In most instances, the company already has the support in place, and need only identify non-compliant browsers and upgrade these desktops to newer versions.
Phones incorporating operating systems without support for TLS v 1.1 and later may be dealt with on a case-by-case basis. That is, each phone may be made compliant by an update to the OS or otherwise. Older phones without support or any method to update may need to be retired.
Supported Configurations
Monthly browser certifications, both current and planned, are available on the Release Notes page.
Monthly Browser Certifications
Monthly browser certifications, both current and planned, are available with the other Concur monthly release notes.
For information about accessing the other release notes and the monthly browser certifications, refer to the Additional Release Notes and Technical Documentation Standard Edition section in this document.Additional Release Notes and Technical Documentation Standard Edition
Concur Support Portal
You can access release notes and other technical documentation on the Concur Support Portal.
If you have the proper permissions, the Contact Support option appears in the Help menu. Click Contact Support to access the Concur Support portal, and then click Resources.
Click Release/Tech Info - Standard for release notes, technical documents and so on.
Online Help: Admins
Users with an admin role can access Invoice release notes, technical documents, and other resources by using online help in Concur.
Click Help > Invoice Administration Help. The links are available on the page that appears.
NOTE: The Invoice Administration Help menu option appears every time an admin accesses Help, including before and during setup.
Concur Release Notes
Invoice Standard
Month Audience
February 2017
Initial Post: Friday, February 17, 11:00 AM PT Client – FINAL
Contents
Release Notes ... 1
Invoice Management ... 1
QuickBooks Import Users Button Is Now Available ... 1
**Coming Soon** Check for Missing Account Code Later in Workflow ... 2
**Coming Soon** Support for TLS v 1.0 Encryption Protocol Ends March 2017 ... 3
Supported Configurations ... 4
Monthly Browser Certifications ... 5
Additional Release Notes and Technical Documentation Standard Edition ... 6
Release Notes
This document contains the release notes for the Invoice functionality for Concur Standard edition. Clients with the Expense or Travel products should review the respective release notes, located on the Concur Support Portal.
Invoice Management
QuickBooks Import Users Button Is Now Available
Overview
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.
What the Admin Sees
BEFORE
Before this release, the Import Users button was not displayed on the Users page of Setup if your Concur company was connected to your QuickBooks company.
AFTER
With this release, the Import Users button is now displayed on the Users page of Setup regardless of whether your Concur company is connected to your QuickBooks company.
Configuration/Feature Activation
The Import Users button is automatically displayed for QuickBooks Online clients and QuickBooks Desktop clients that use the QuickBooks Web Connector to connect their QuickBooks companies to Concur; there are no configuration or activation steps.
Concur recommends that you download and use the latest version of the Concur Employee Import Template for any user updates to ensure you have the latest fields in your template.
**Coming Soon** Check for Missing Account Code Later in Workflow
Overview
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. When you open the payment request, the exception looks like this:
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.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
**Coming Soon** Support for TLS v 1.0 Encryption Protocol Ends March 2017
Overview
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.
Note that, since less than 1% of Concur users are logging in to Concur Solutions by using browsers or phones limited to version 1.0, a very small number of users are affected by this support discontinuation.
PLEASE NOTE NEW END DATE OF SUPPORT IS MARCH
We have moved the date support will end from January 31st to March 31st 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.
What This Means: The Client Experience
For our clients, the use of an unsecured connection can expose confidential data, resulting in compromised sessions across any TLS channel of communication (for example, Concur services). For this reason, Concur is alerting the client now to ensure they are fully prepared for the removal of support for this protocol. Working with Concur, client admins can begin assessment of compliance with newer versions of TLS at their companies.
WHAT DEVICES ARE AFFECTED BY THIS CHANGE?
In general, browsers and phones using TLS to establish inbound/outbound
communication channels with Concur services are affected. Each device may or may not be capable of upgrade to support TLS v 1.1 and later versions.
INFORMATIONAL BANNER TO DISPLAY
A banner will now display whenever a user attempts to log in using a browser that does not support TLS v 1.1 and later and thus cannot negotiate a connection. The intent is to alert the client to this upcoming change using an informational-only message.
TRANSITIONING TO THE NEW VERSION AT THE WORKPLACE
Transitioning to support for TLS v 1.1 and later may simply require updating your browser. In most instances, the company already has the support in place, and need only identify non-compliant browsers and upgrade these desktops to newer versions.
Phones incorporating operating systems without support for TLS v 1.1 and later may be dealt with on a case-by-case basis. That is, each phone may be made compliant by an update to the OS or otherwise. Older phones without support or any method to update may need to be retired.
Supported Configurations
Monthly browser certifications, both current and planned, are available on the Release Notes page.
Monthly Browser Certifications
Monthly browser certifications, both current and planned, are available with the other Concur monthly release notes.
For information about accessing the other release notes and the monthly browser certifications, refer to the Additional Release Notes and Technical Documentation Standard Edition section in this document.Additional Release Notes and Technical Documentation Standard Edition
You can access release notes and other technical documentation on the Concur Support Portal.
If you have the proper permissions, the Support menu is available to you in Concur.
Click Support, and then, in the Concur Support Portal, click Resources.
Click Release/Tech Info - Standard for release notes, technical documents etc.
Concur Release Notes
Invoice Standard
Month Audience
Release Date: March 18 2017
Update #3: Wednesday, April 5, 3:00 PM PT Client – FINAL
Contents
Release Notes ... 1
Invoice Management ... 1
Users Can Now See Their Purchase Orders ... 1
New Look for the How It Works Topics ... 2
Default Values for QuickBooks Account Name or Number Column ... 4
Menu Changes for Accessing the Setup Wizard ... 5
Change in the Monthly Release Schedule ... 6
Terminology Change – Korean ... 6
**Coming Soon** Terminology Changes – Spanish ... 7
**Coming Soon** Terminology Changes – Italian ... 7
**Coming Soon** Check for Missing Account Code Later in Workflow ... 8
**Coming Soon** Enhanced Fiscal Calendar ... 9
**Coming Soon** Microsoft IE v.10 Browser Support Ends August 18, 2017 ... 11
Supported Configurations ... 12
Monthly Browser Certifications ... 13
Support for TLS v 1.0 Encryption Protocol Ends March 2017 – MOVED FOR THE US DATACENTER ... 13
Additional Release Notes and Technical Documentation Standard Edition .... 15
Release Notes
This document contains the release notes for the Invoice functionality for Concur Standard edition. Clients with the Expense or Travel products should review the respective release notes, located on the Concur Support Portal.
Invoice Management
Users Can Now See Their Purchase Orders
Overview
With this release, purchase request users will be able to view the purchase orders resulting from their created purchase requests.
BUSINESS PURPOSE/CLIENT BENEFIT
This feature gives users greater visibility to the workflow of their purchase requests.
What the User Sees
The purchase request user will see a new menu option, My Purchase Orders, in the Purchase Request menu.
NOTE: If the user is both a purchase request user and a purchasing admin, who processes purchase orders, they will not see the My Purchase Orders menu option.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
For more information, refer to the Invoice: Purchase Request and Purchase Order User Guide.New Look for the How It Works Topics
Overview
The How It Works Help topics in Setup have a new format.
The How It Works Help topics open when the company administrator clicks the How it works link on one of the Setup pages. The topic provides information relevant to the Setup page you are working on.
BUSINESS PURPOSE/CLIENT BENEFIT
This change improves the readability of the Help content.
What the Admin Sees Before
The following is an example of the previous version of the How It Works Help topic for the Cost Tracking – Data to Track page.
After
The following is an example of the new version of the How It Works Help topic for the Cost Tracking – Data to Track page.
The format change includes a new format for the topic titles, renaming the Done button to Close, simplifying the format of the content in the Help topics, and making it easier to locate the link(s) to additional information in the Concur Administration Help.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
Default Values for QuickBooks Account Name or Number Column
Overview
For QuickBooks Desktop (QBD) and QuickBooks Online (QBO) clients that are not using the QuickBooks Web Connector, the default value for the QuickBooks
Account Name or Number column is now blank for expense types on the Invoice – Account Codes page in Setup.
BUSINESS PURPOSE/CLIENT BENEFIT
This enhancement makes it easier for clients to enter values.
What the Admin Sees
The QuickBooks Account Name or Number column is blank for each expense type until an account name or number value is entered for the expense type.
Configuration/Feature Activation
Concur automatically implemented this change for QuickBooks Desktop and
QuickBooks Online clients that do not use the QuickBooks Web Connector to connect their QuickBooks companies to Concur; there are no configuration or activation steps.
Menu Changes for Accessing the Setup Wizard
Overview
Concur has removed the Setup menu option and changed the name of the Expense menu option to Invoice Settings to access the Setup Wizard. To access the Setup Wizard, clients need to click Administration > Invoice Settings. If clients are using both Expense and Invoice, the menu option will say Expense & Invoice Settings.
BUSINESS PURPOSE/CLIENT BENEFIT
This enhancement gives clients a more precise name for what can be found in this menu option.
What the Admin Sees
The admin will see a new menu option name, Invoice Settings, to access the Setup Wizard.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
Change in the Monthly Release Schedule
Overview
As shown on the 2017 release calendar, Invoice releases will now occur on Saturday instead of Friday. For most users, there is no change; they will see the release- related changes on Monday like they always have. Be aware that any weekend users will likely not see the release-related changes until Sunday.
Release Calendar
The release calendar is available here:
http://www.concurtraining.com/customers/tech_pubs/ReleaseCalendar/_ReleaseCale ndar_client.htm
Terminology Change – Korean
Overview
Concur has changed the following Korean term.
English Term Previous Korean Term Updated Korean Term
cost object 원가 직접 대상 비용 오오오오
NOTE: Please make a note of this change as it may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
This change improves accuracy and consistency of the Korean version of the Concur user interface.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
**Coming Soon** Terminology Changes – Spanish
Overview
In April, Concur will update the following Latin American Spanish terms.
English Term Previous Spanish Term Updated Spanish Term
Allocation distribución asignación
Allocate distribuir asignar
NOTE: Please make a note of these changes as they may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Spanish version of the Concur user interface.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
**Coming Soon** Terminology Changes – Italian
Overview
In April, Concur will change the following Italian terms.
English Term Previous Italian Term Updated Italian Term
Segment segmento tratta
Workflow regola del flusso di lavoro workflow
NOTE: Please make a note of these changes as they may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Italian version of the Concur user interface.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
**Coming Soon** Check for Missing Account Code Later in Workflow
Overview
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, Requests 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. When you open the payment request, the exception looks like this:
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.
What the Processor Sees
The processor will see a new query, Requests Financial Posting Failed, on the Requests Ready for Processing page.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
**Coming Soon** Enhanced Fiscal Calendar
Overview
Concur will soon provide an enhanced fiscal calendar for Analysis/Intelligence that will be available for Invoice. A fiscal calendar allows organizations to define their accounting periods independent of the standard calendar year. Many organizations define their own calendars to model their financial reporting to reflect seasons in their business, to compare results with direct competitors, and to avoid the busy year-end season in January.
A fiscal calendar has one or more fiscal years, and fiscal years have one or more fiscal periods.
Fiscal years have a start date and an end date. Each year may have a different length to accommodate leap years and short years or long years. Organizations use short years and long years when they change the start date of their fiscal year. Fiscal years cannot overlap with prior fiscal years and no gaps can exist between fiscal years.
Fiscal periods can vary in length within a fiscal year; however, they typically represent months.
BUSINESS PURPOSE/CLIENT BENEFIT
This feature gives clients the flexibility to define their accounting periods
What the Admin Sees
The admin will see an enhanced fiscal calendar in the Reporting Configuration step of the Setup Wizard.
On the Reporting Configuration page, the tab, which was previously called Fiscal Calendar Set Up, is now called Fiscal Calendar.
The Fiscal Calendar has five buttons, which are described in the following table.
Button Description
New Enables the admin to create a new fiscal calendar.
Modify Enables the admin to modify an existing fiscal calendar.
Activate Enables the admin to activate a fiscal calendar.
Deactivate Enables the admin to deactivate a fiscal calendar.
Remove Enables the admin to remove a fiscal calendar.
Configuration/Feature Activation
The budget administrator needs to go to Reporting Configuration step of the Setup Wizard to configure the Fiscal Calendar feature.
To access the Fiscal Calendar:1. Click Administration > Setup > Expense.
2. Click the Reporting Configuration step of Setup. The Reporting Configuration page appears.
3. Click the Fiscal Calendar step.
For more information, refer to the release notes for Analysis/Intelligence.**Coming Soon** Microsoft IE v.10 Browser Support Ends August 18, 2017
Overview
Support for Microsoft Internet Explorer (IE) version 10 browsers under Concur products will end August 18, 2017. Concur strongly advises clients using IE v.10 to update to the latest IE browser version before that date, or to install and work with another supported browser.
!
IMPORTANT: In addition, this change is a result of deprecating TLS 1.0.Upgrading to Internet Explorer 11 will enable companies to use a supported Microsoft browser that – by default – supports TLS 1.2.
BACKGROUND
Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical support and security updates from Microsoft in accordance with their Product Lifecycle program (view at https://support.microsoft.com/en-us/gp/microsoft-internet-explorer).
For more information about supported browsers under Concur products, refer to the Browser Support section of the Concur: Travel & Expense Supported Configurations - Client Version document.New Users by Browser Report Lists a Company's Employee Browser Use A report, Users by Browser, is available to all admins working with the Expense, Request, Invoice, and/or Travel offerings in both the Professional and Standard product editions.
This report allows the admin to select a browser version and then generate a list report of employees who are using that browser. The report includes first, last, and login names, last login and login count, and email and IP addresses for identification.
To run the Browser Report:1. Click Administration > Company > Users by Browser.
2. On the Browser Report page, select a browser in the Web Browser list.
3. Click Submit.
The system returns a list of all users with information about the user, their login name and status, and additional data to help identify the user(s) working with the selected browser version.
Supported Configurations
Monthly browser certifications, both current and planned, are available on the Release Notes page.
Monthly Browser Certifications
Monthly browser certifications, both current and planned, are available with the other Concur monthly release notes.
For information about accessing the other release notes and the monthly browser certifications, refer to the Additional Release Notes and Technical Documentation Standard Edition section in this document.Support for TLS v 1.0 Encryption Protocol Ends March 2017 – MOVED FOR THE US DATACENTER
Update: Please note these dates:
• EU datacenter: Completed on Tuesday, April 4, 2017
• US datacenter: MOVED TO Wednesday, April 12, 2017
Overview
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.
Note that, since less than 1% of Concur users are logging in to Concur Solutions by using browsers or phones limited to version 1.0, a very small number of users are affected by this support discontinuation.
PLEASE NOTE NEW END DATE OF SUPPORT IS APRIL
We have moved the date 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.
What This Means: The Client Experience
For our clients, the use of an unsecured connection can expose confidential data, resulting in compromised sessions across any TLS channel of communication (for example, Concur services). For this reason, Concur is alerting the client now to ensure they are fully prepared for the removal of support for this protocol. Working with Concur, client admins can begin assessment of compliance with newer versions of TLS at their companies.
WHAT DEVICES ARE AFFECTED BY THIS CHANGE?
In general, browsers and phones using TLS to establish inbound/outbound
communication channels with Concur services are affected. Each device may or may not be capable of upgrade to support TLS v 1.1 and later versions.
INFORMATIONAL BANNER TO DISPLAY
A banner will now display whenever a user attempts to log in using a browser that does not support TLS v 1.1 and later and thus cannot negotiate a connection. The intent is to alert the client to this upcoming change using an informational-only message.
TRANSITIONING TO THE NEW VERSION AT THE WORKPLACE
Transitioning to support for TLS v 1.1 and later may simply require updating your browser. In most instances, the company already has the support in place, and need only identify non-compliant browsers and upgrade these desktops to newer versions.
Phones incorporating operating systems without support for TLS v 1.1 and later may be dealt with on a case-by-case basis. That is, each phone may be made compliant by an update to the OS or otherwise. Older phones without support or any method to update may need to be retired.
Additional Release Notes and Technical Documentation Standard Edition
You can access release notes and other technical documentation on the Concur Support Portal.
If you have the proper permissions, the Support menu is available to you in Concur.
Click Support, and then, in the Concur Support Portal, click Resources.
Click Release/Tech Info - Standard for release notes, technical documents etc.
Concur Release Notes
Invoice Standard
Month Audience
Release Date: April 22 2017
Update #1: Tuesday, April 25, 4:30 PM PT Client – FINAL
Contents
Release Notes ... 1
Purchase Requests and Purchase Orders ... 1PO Change Order Now Available ... 1 User Can Now Change Bill to Address on Purchase Request ... 5 Concur Receiving: Prevent Associated Receipts from Being Changed ... 6 Terminology ... 8 Terminology Changes – Spanish ... 8 Terminology Changes – Italian ... 8
**Coming Soon** Terminology Changes – Italian ... 9
**Coming Soon** Terminology Change – Swedish ... 9
**Coming Soon** Terminology Changes – Dutch ... 10
**Coming Soon** Terminology Change – Brazilian Portuguese ... 10 Invoice ... 11
**Coming Soon** Check for Missing Account Code Later in Workflow ... 11 Budget ... 13
**Coming Soon** New Budget Insight Feature in Early Adopter Program Targeted for June ... 13
**Coming Soon** Enhanced Fiscal Calendar for Analysis/Intelligence ... 20 Capture Processing ... 22 Automatically Match Invoice to the Assigned Vendor Owner ... 22 Supported Configurations ... 22
Support for TLS v 1.0 Encryption Protocol to End – DATE MOVED FOR THE US DATA CENTER ... 23 Microsoft Internet Explorer v.10 Deprecation – UI Banner ... 24
**Coming Soon** Microsoft IE v.10 Browser Support Ends August 18, 2017 ... 25
Client Notifications ... 27
Subprocessors ... 27Concur Non-Affiliated Subprocessors ... 27 Browser Certifications ... 27 Monthly Browser Certifications ... 27
Additional Release Notes and Technical Documentation Standard Edition .... 28
Release Notes
This document contains the release notes for the Invoice functionality for Concur Standard edition. Clients with the Expense or Travel products should review the respective release notes, located on the Concur Support Portal.
Purchase Requests and Purchase Orders
PO Change Order Now Available
Overview
Concur now offers the ability for users to change a transmitted purchase order and resend it through the same workflow.
The user initiates the PO change order process of a transmitted purchase order. The purchase request user can then add line items to the request and let the request go through the workflow again, including approval and processing. A new version of the purchase order is created, but with the same PO number.
BUSINESS PURPOSE/CLIENT BENEFIT
This feature gives clients more control and flexibility in working with purchase orders by giving them an option to request a change to a purchase order.
What the Purchase Request User Sees
The purchase request user will see a new option, Create Change Order, in the Action menu of a transmitted purchase order.
The purchase request user will also see an icon in the unsubmitted purchase requests indicating that the purchase request is in a PO Change Order mode.
In addition, the purchase request user will see a Discard button on the purchase request details page of a PO change order.
What the Approver Sees
The approver will see an icon next to the purchase request number indicating that the purchase request is in a PO Change Order mode.
What the Purchase Request Processor Sees
The purchase request processor will see an icon next to the purchase request number indicating that the purchase request is in a PO Change Order mode.
What the Purchase Order Processor Sees
When the purchase order is in PO Change Order mode, the PO processor will see an icon on the Purchase Orders Pending Transmission page and on the details page of the purchase order.
Once a PO change order has gone through the workflow, the PO processor will be able to open the Preview Purchase Order window and see revision information about the PO change order.
In addition, PO processors will see a new Change Order Revision section in the purchase order with information.
Configuration/Feature Activation
Concur internal staff needs to activate this feature in a Concur internal-only tool.
For more information, refer to the PO Change Order Client Fact Sheet, the Invoice: Purchase Request and Purchase Order Setup Guide for ConcurStandard Edition, and the Invoice: Purchase Request and Purchase Order User Guide for Concur Standard Edition.
User Can Now Change Bill to Address on Purchase Request
Overview
The purchase request user will now be able to change the bill-to address on purchase requests, so that they can send the vendor the correct address to which to bill the request. Users can switch to any bill-to address available for their company.
The default bill-to address that is used on policy level should be used for the purchase request. If the user changes the policy on the purchase request, the system does not change the bill-to address on the purchase request since the user might have changed this previously from the former policy default.
The Ship To Address and Bill To Address fields work in the same way, that is, a user can click in the respective fields and select the relevant address to use.
In addition to this new feature, Concur has made some user interface changes on the purchase request details page. These include changing the location of the Actions, Delete, and Submit buttons (to the right on the page), and the Ship To Address section (to just above the Bill To Address section).
BUSINESS PURPOSE/CLIENT BENEFIT
This enhancement improves client efficiency by enabling them to easily update an incorrect bill-to address.
What the User Sees
The user will see a new editable field, Bill To Address.
Once a user has selected a bill-to address, the address will show in the Bill To Address field.
In addition, the user will see moved locations of the Ship To Address section and the Actions, Delete, and Submit buttons.
Configuration/Feature Activation
The feature is automatically on provided you have purchase request capabilities in Invoice. There are no additional configuration or activation steps.
For more information, refer to the Invoice: Purchase Request and Purchase Order User Guide for Concur Standard Edition.Concur Receiving: Prevent Associated Receipts from Being Changed
Overview
If a receipt is associated with an invoice, a user will not be able to delete or make data changes to this receipt, as it will affect invoices that are part of three-way matching. If a user needs to make changes to an invoice, they need to first unassociate the receipt to the invoice.
NOTE: The user, in this case, can be an invoice owner, invoice processor, PO processor, or purchase request owner.
This example image shows the Purchase Order page.
However, if a receipt is associated with an invoice, the user can attach images to this receipt.
BUSINESS PURPOSE/CLIENT BENEFIT
This enhancement gives clients more control over invoices when working with associated receipts.
What the User Sees
The user will see the Edit and Delete buttons disabled when working with associated receipts.
This example image shows the Purchase Order page.
Configuration/Feature Activation
The feature is automatically on automatically; there are no additional configuration or activation steps.
For more information, refer to the Invoice: Purchase Request and Purchase Order User Guide for Concur Standard Edition.Terminology
Terminology Changes – Spanish
Overview
Concur has updated the following Latin American Spanish terms.
English Term Previous Spanish Term Updated Spanish Term
allocation distribución asignación
allocate distribuir asignar
NOTE: Please make a note of these changes as they may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Spanish version of all Concur solutions.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
Terminology Changes – Italian
Overview
Concur has changed the following Italian terms.
English Term Previous Italian Term Updated Italian Term
segment segmento tratta
workflow regola del flusso di lavoro workflow
NOTE: Please make a note of these changes as they may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Italian version of the Concur user interface.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
**Coming Soon** Terminology Changes – Italian
Overview
In the May release, Concur will change the following Italian terms.
English Term Previous Italian Term Updated Italian Term
cash advance anticipo di cassa anticipo
line item voce riga voce
NOTE: Please make a note of these changes as they may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Italian version of all Concur solutions.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
**Coming Soon** Terminology Change – Swedish
Overview
In the May release, Concur will change the following Swedish term.
English Term Previous Swedish Term Updated Swedish Term
line item radobjekt radpost
NOTE: Please make a note of this change as this may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Swedish version of all Concur solutions.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
**Coming Soon** Terminology Changes – Dutch
Overview
In the May release, Concur will change the following Dutch terms.
English Term Previous Dutch Terms Updated Dutch Term vendor leverancier/aanbieder/merchant/bedrijf leverancier
supplier leverancier/aanbieder/bedrijf leverancier
merchant leverancier/merchant handelaar
provider leverancier/aanbieder/verstrekker/provider
verlener/uitgever aanbieder
NOTE: Please make a note of these changes as they may influence your company’s internal documentation or training materials.
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Dutch version of all Concur solutions.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
**Coming Soon** Terminology Change – Brazilian Portuguese
Overview
In the May release, Concur will change the following Brazilian Portuguese terms.
English Term Previous Brazilian
Portuguese Terms Updated Brazilian Portuguese Terms
route rota trajeto
employee empregado funcionário
NOTE: Please make a note of these changes as they may influence your company’s
BUSINESS PURPOSE/CLIENT BENEFIT
These changes improve accuracy and consistency of the Brazilian Portuguese version of all Concur solutions.
Configuration/Feature Activation
Concur automatically implements terminology changes; there are no configuration or activation steps.
Invoice
**Coming Soon** Check for Missing Account Code Later in Workflow
Overview
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, Requests Failing Financial Posting, 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. When you open the payment request, the exception looks like this:
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.
What the Processor Sees
The processor will see a new query, Requests Failing Financial Posting, on the Requests Ready for Processing page.
Configuration/Feature Activation
The feature is automatically on; there are no additional configuration or activation steps.
Budget
**Coming Soon** New Budget Insight Feature in Early Adopter Program Targeted for June
Overview
The Budget Insight feature enables clients to set up all components of a budget; a fiscal year to determine the budget period, Budget Categories to group expense types for budget purposes and budgets, which are the actual annual budgets, and Budget Items, which define the budget including fiscal year, budget owner, budget name and description.
This feature makes budgets visible, actionable, and real-time for approvers and budget owners, leading to high-quality spending decisions for Invoice (payment requests and purchase requests).
NOTE: The Budget Insight feature is going through a launch process led by Global Marketing. Your Marketing representative will advise you when you can test and demonstrate this feature for your region and edition; until that time, it is not accessible. Contact Melissa Michelon with any questions.
NOTE: The new Budget Insight feature will be released in an Early Adopter Program targeted for June. This feature is new for Invoice and different from the legacy Budget Insight feature currently existing for Expense and Request.
NOTE: The enhanced Fiscal Calendar for Reporting and the Fiscal Calendar in the new Budget Insight feature share data between both calendars.
BUSINESS PURPOSE/CLIENT BENEFIT
This feature makes budgets visible, actionable, and real-time for approvers and budget owners, leading to high-quality spending decisions for Invoice (payment requests and purchase requests) clients.
USER PERMISSION ROLES
There are four user permission roles available for clients who work with the Budget Insight feature.
Role Description
Budget
Administrator Configures the Fiscal Calendar, Budget Categories, and Budget Items.
Budget Owner Owns the budget and can view budgets in the dashboards.
Budget Approver Approves payment requests/purchase requests and can view budgets in the dashboards.
Budget Viewer Views budgets in the dashboards. Can be one to many budget viewers.
A budget must have a budget owner and only one owner can be selected per budget.
A budget may have multiple budget approvers and viewers or none. The Budget Approver role enables the budget manager hierarchy. Submissions of payment requests or purchase requests by direct and indirect employees are matched to budgets based on the manager hierarchy. Budget viewers are users who can view someone else’s budget without the permission to approve payment
requests/purchase requests for that budget. A budget owner can always see its own budget and can have multiple budgets. A budget owner may not need or want budget approver permission.
FISCAL CALENDAR
A fiscal calendar allows organizations to define their accounting periods independent of the standard calendar year. Many organizations define their own calendars to model their financial reporting to reflect seasons in their business, to compare results with direct competitors, and to avoid the busy year-end season in January.
A fiscal calendar has one or more fiscal years, and fiscal years have one or more fiscal periods.
Fiscal years have a start date and an end date. Each year may have a different length to accommodate leap years and short years or long years. Organizations use short years and long years when they change the start date of their fiscal year. Fiscal years cannot overlap with prior fiscal years and no gaps can exist between fiscal years.
Fiscal periods can vary in length within a fiscal year; however, they typically represent a full year, quarters, or months.
NOTE: If a fiscal year or a fiscal period is not marked as active, then Invoice cannot match the payment requests to the fiscal period and the system will try to map them to the next available active fiscal period. If Invoice cannot map a payment request to an active fiscal period, then the payment request cannot be associated to a budget.
BUDGET CATEGORIES
Budget Categories are groupings of Invoice expense types for budgeting purposes. If a payment request line item has an expense type belonging to a budget category, then the payment request line item is associated to the budget having that budget category (if all other criteria are matched as well). Budget Categories are optional to use. If Budget Categories are not used, then Invoice can match items based on the budget approver hierarchy.
NOTE: An admin can only remove a budget category if it is not associated with a budget.
BUDGET ITEMS
Budget items define the budget including a fiscal year, a budget owner, a unique budget name per fiscal year, a description, and a way to associate a budget with a spending item, such as a purchase request item or a payment request item.
What the User Sees
The user will see a new menu option, Budget Dashboards, in the Reporting menu.
Once the user clicks the Budget Dashboard menu option, two tabs, Budgets and Budget Details appear.
The Budgets tab contains information about the user’s budget, such as budget year and budget period, budget size (Budget), how much of the budget that has been spent (Spend), how much of the budget remains (Available), and how much of the budget is pending approval (Pending). In addition, the user can see a budget breakdown in percentage of Spend, Pending, and Available. In addition, users can view other budgets if they have the permission to do so.
The Budget Details tab contains detailed information about a user’s budget. The user will be able to see the same information as on the Budgets tab. In addition to this, they will be able to view more details about spent and pending budget of payment requests and purchase requests, such as, request name, invoice number, employee name, submit date, invoice date, total invoice amount, budget amount, and percent of budget that is spent or pending.
What the Admin Sees
The admin will see a new step and sub-step, Budget > Budget Configuration, in Setup. The Budget Configuration step contains three steps: Fiscal Calendar, Budget Category, and Budget Items.
The admin will see the following four roles on the Users page in Setup:
• Is Budget Owner?
• Is Budget Viewer?
• Is Budget Approver?
• Is Budget Admin?
Configuration/Feature Activation
Concur needs to activate this features in a Concur internal-only tool.
Once Concur has activated Budget Insight, the Budget Administrator needs to configure the feature in the Budget > Budget Configuration step of the Setup Wizard.
**Coming Soon** Enhanced Fiscal Calendar for Analysis/Intelligence
Overview
Concur will soon provide an enhanced fiscal calendar for Analysis/Intelligence that will be available for Invoice. A fiscal calendar allows organizations to define their accounting periods independent of the standard calendar year. Many organizations define their own calendars to model their financial reporting to reflect seasons in their business, to compare results with direct competitors, and to avoid the busy year-end season in January.
A fiscal calendar has one or more fiscal years, and fiscal years have one or more fiscal periods.
Fiscal years have a start date and an end date. Each year may have a different length to accommodate leap years and short years or long years. Organizations use short years and long years when they change the start date of their fiscal year. Fiscal years cannot overlap with prior fiscal years and no gaps can exist between fiscal years.
Fiscal periods can vary in length within a fiscal year; however, they typically represent months.
NOTE: The enhanced Fiscal Calendar for Reporting and the Fiscal Calendar in the new Budget Insight feature share data between both calendars.
BUSINESS PURPOSE/CLIENT BENEFIT
This feature gives clients the flexibility to define their accounting periods independently of the standard calendar year.
What the Admin Sees
The admin will see an enhanced fiscal calendar in the Reporting Configuration step of the Setup Wizard.
On the Reporting Configuration page, the tab, which was previously called Fiscal Calendar Set Up, is now called Fiscal Calendar.
The Fiscal Calendar has five buttons, which are described in the following table.
Button Description
New Enables the admin to create a new fiscal calendar.
Modify Enables the admin to modify an existing fiscal calendar.
Activate Enables the admin to activate a fiscal calendar.
Deactivate Enables the admin to deactivate a fiscal calendar.
Remove Enables the admin to remove a fiscal calendar.
Configuration/Feature Activation
The administrator needs to go to Reporting Configuration step of the Setup Wizard to configure the Fiscal Calendar feature.
To access the Fiscal Calendar:1. Click Administration > Invoice Settings (or Expense & Invoice Settings).
2. Click the Reporting Configuration step of Setup. The Reporting Configuration page appears.
3. Click the Fiscal Calendar step.