SAP Concur Real Time Status

19 November 2025 | 1:02 pm

We have completed the post recovery stability monitoring period and confirmed that service is operating at a normal and stable level and will now resolve this incident. Please contact the Support Engineer assigned to your case for any questions about this incident. We are sorry for any inconvenience this may have caused. Thank you for your patience. In the US2 Data Center, completing Car and Hotel searches in the New Concur Travel experience was below expected levels. Affected users may have encountered the following errors: for Car searches, ‘No results found,’ and for Hotel searches, ‘No location found.’ A workaround for this issue was not available. The Incident Response Team (IRT) has rolled back a recent deployed change to restore service.

19 November 2025 | 12:47 pm

Service has been restored to a normal operating level, and we have started a mandatory post recovery monitoring period to ensure service performance stability prior to declaring the incident resolved. We will post the next incident communication at or before 8:15PMUTC on 19 November 2025. In the US2 Data Center, completing Car and Hotel searches in the New Concur Travel was below expected level. Affected users may have received the following error when attempting to search for travel: "No results found" A workaround for this issue is not available at this time Complete post recovery service performance stability monitoring and verification

19 November 2025 | 12:30 pm

We have identified a disruption affecting your service. We have provided details of the incident known at this time below, and are currently assessing and verifying the full extent of the user impact and assembling a specialized Incident Response Team (IRT) to investigate and resolve the issue. We will post the next incident communication at or before 7:15PM UTC on 19 November 2025.

19 November 2025 | 12:09 pm

We are working to determine the user impact and will provide information as it becomes available.

12 November 2025 | 9:12 am

Impact as Reported: Customers using the American Express GL1025 file for credit card transaction feeds may have experienced issues with incorrect transaction labeling for transactions posted on or before September 2. Affected users may see payment transactions displayed to employees either with no vendor name or with an "unknown" vendor, while certain fee types may be incorrectly classified as cash advances. Root cause: The credit card vendor for the impacted customers sent incorrect transaction data to SAP Concur. SAP Concur engineering worked with the vendor to identify the impacted data set and apply the necessary corrections. Please refer to your support case for any additional information on individual impact. If you continue to have issues please create a support case. Corrective Actions: Code was written to identify and fix the incorrect data. A tool was developed that can now be used to more readily fix data on request.