Support
Travel Incorporated Concur Support Desk
Navigational issues, password reset, or other Concur technical questions.
Phone: 866-738-6444
Forgot Password?
Submit a request to Concur for a password reset. Your username is your current institutional email address.
New User Registration
Concur registration for new users. Registration is limited to employees. The use of a university e-mail address is required for user name.
Additional Support
Overview of Concur Homepage (Video)
Homepage Tip Sheet (PDF)
How to find the lowest fares in Concur
Contact your institution’s travel manager for additional support questions.
Personalized SAP Concur Open Updates
Personalized up-to-the-minute service availability and performance information
-
OPI-5264438 : US | EMEA | PUBLIC_SECTOR : Travel | Compleat (TMC Services) : Root Cause Analysis
14 June 2021 | 5:09 pm
In the North America, EMEA, and Concur Cloud for Public Sector Data Centers, travel searches using the Sabre GDS service were 20% below expected level. Affected users may have experienced an error message “We encountered an issue which prevented us from completing your request” after clicking the Search button. Additionally, Compleat users in the North America Data Center were also impacted by the Sabre GDS outage. Customer PNRs were not being processed which includes, but not limited to, QC, FIle Finishing, Ticketing and email communications with the traveler. The Vendor removed a failed storage device from their environment to restore the service. The incident was caused by a hardware failure in the vendor's storage environment. Corrective measures include: - The impacted storage device has been isolated, and the environment is performing as expected.
-
OPI-5227938 : US : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence | Locate : Root Cause Analysis
10 June 2021 | 8:52 am
In the North America Data Center, logging in to the SAP Concur website and SAP Concur mobile app was unavailable. Impacted users may have received an error message when attempting to log in. Users already logged in were unable to use our services. As the Incident Response Team was being assembled, our services automatically self-recovered. The root cause of the incident is the failure of client network sessions to re-establish during a maintenance activity on a core network component. Corrective measures include: - We will remove the necessity for client network sessions to be re-established during future maintenance activities. - We will ensure that future upgrades on the core network component will be conducted during a scheduled maintenance window.