SAP Concur Real Time Status

21 January 2026 | 3:37 pm

A system outage caused a delay in posting incident communications. The issue has since been resolved, and communications for incidents that occurred during the outage are now being published. Most New Concur Travel customers were unable to perform successful travel searches for 50 minutes. Our internal monitoring tools measuring successful travel submissions detected a 95% drop in travel submissions during the incident. Further investigation confirmed successful travel submissions were impacted by an error, "Sorry something went wrong" after entering your desired search parameters and clicking the Search button when performing air, car, and hotel searches.. If you experienced impact, you may have been able to successfully perform a search by trying again. The Incident Response Team (IRT) quickly took action to revert a recent change to restore service. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

9 January 2026 | 4:45 pm

New Concur Travel users experienced an issue completing travel bookings. Our internal observability tools detected a 100% drop in travel bookings for approximately 17 minutes. Affected users may have encountered the following error when attempting to complete their travel booking from the Review and Book page, "Sorry, something went wrong." There was no workaround identified during service disruption. As the Incident Response Team (IRT) was gathering, services self-recovered. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

6 January 2026 | 2:25 pm

Expense customers using American Express (AMEX) files for credit card transaction feeds experienced duplicate transactions being imported. Affected users observed duplicate or triplicate AMEX transactions listed in Available Expenses. A duplicate credit card transaction issue was identified and resolved by American Express on 16 December 2025. Since then, American Express has issued reversal credit transactions for all duplicate transactions via customer file feeds. Additionally, the Incident Response Team (IRT) has provided three corrective actions customers are advised to take to clean-up and process all duplicate, triplicate, and reversal credit transactions. We have completed an extended post-recovery corrective measure monitoring period and will now resolve this incident.

23 December 2025 | 3:05 pm

Expense customers using American Express (AMEX) files for credit card transaction feeds experienced duplicate transactions being imported. Affected users observed duplicate or triplicate AMEX transactions listed in Available Expenses. Customers may try the following potential workarounds to action and clean-up duplicate transactions: 1.) Hide duplicate transactions. Concur Administrators with the Expense Company Card Administrator role can perform this action. For more details, refer to the article found in Knowledge base - How can I hide duplicate charge? 2.) Enable an audit rule to notify users not to submit expense reports containing potential duplicate transactions. For guidance, refer to the article found in Knowledge base - Can the system detect duplicate entries on a report? 3.) Include duplicate and credit transactions together. If users are able to easily identify and match duplicate or triplicate transactions to the imported credits, then users are advised to include the matching debit and credit transactions together in a single expense report. If assistance is required, please request help via your support case, and your case owner will assist. Post-recovery corrective actions are in progress. American Express has issued reversal credit transactions for all duplicate transactions via customer file feeds. The Incident Response Team (IRT) advises customers to proceed with one of the provided clean-up options and process all duplicate, triplicate, and credit transactions. Customers may update their support case requesting assistance from the case owner to perform necessary clean-up actions. Our next update will be at 9:00 PM UTC on 6 January 2026, or sooner should a significant change occur.

19 December 2025 | 2:53 pm

Expense customers using American Express (AMEX) files for credit card transaction feeds experienced duplicate transactions being imported. Affected users observed duplicate or triplicate AMEX transactions listed in Available Expenses. Customers may try the following potential workarounds to action and clean-up duplicate transactions: 1.) Hide duplicate transactions. Concur Administrators with the Expense Company Card Administrator role can perform this action. For more details, refer to the article found in Knowledge base - How can I hide duplicate charge?
 2.) Enable an audit rule to notify users not to submit expense reports containing potential duplicate transactions. For guidance, refer to the article found in Knowledge base - Can the system detect duplicate entries on a report?
 3.) Include duplicate and credit transactions together. If users are able to easily identify and match duplicate or triplicate transactions to the imported credits, then users are advised to include the matching debit and credit transactions together in a single expense report. If assistance is required, please request help via your support case, and your case owner will assist. The Incident Response Team (IRT) has confirmed with American Express that the issue resulting in duplicate or triplicate transactions is resolved for all affected customers. Additionally, American Express has advised that corresponding credit transactions have been sent all affected customers via file feeds. The IRT advises customers to attempt using one of the three workarounds to clean-up and process all duplicate, triplicate, and credit transactions. If any of the provided workarounds are not viable, customers are advised to update their support case requesting assistance from the case owner to perform necessary clean-up actions. Our next scheduled update will be at 9:00 PM UTC on 23 December 2025, or sooner should a significant change occur.