Training
Travel Incorporated Concur Support Desk
Navigational issues, or other Concur technical questions.
Phone: (877) 811-9898, #3
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-5858869 : US2 : Expense | Travel | Invoice | Analysis/Intelligence : Issue Resolved
1 May 2024 | 4:24 pm
In the US2 Data Center, expense report submissions, invoice submissions, accessing, running or viewing Analysis/Intelligence reports, and completing travel searches through the SAP Concur website and SAP Concur mobile app were below expected level. Users may have experienced latency or errors when attempting to complete tasks. The Incident Response Team (IRT) made a routing configuration change on a networking service tier to restore service. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will be conducted , and a root cause analysis report provided when that investigation is complete.
-
OPI-5858869 : US2 : Expense | Travel | Invoice | Analysis/Intelligence : Issue Status Update
1 May 2024 | 3:59 pm
In the US2 Data Center, expense report submissions, invoice submissions, accessing, running or viewing Analysis/Intelligence reports, and completing travel searches through the SAP Concur website and SAP Concur mobile app were below expected level. Users may have experienced latency or errors when attempting to complete tasks. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.