SAP Concur Real Time Status

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.

19 December 2025 | 4:17 am

Impact as Reported: New Concur Travel customers may have experienced an error message when attempting to submit a travel booking. Additionally, some users may have experienced latency when attempting to complete a booking or perform tasks.  Root cause: The root cause of the incident has been identified to be a service disruption within our third party Global Distribution System (GDS). Corrective Actions: N/A

18 December 2025 | 2:21 pm

User impact since last communication has changed. It has been determined impact is not limited to the GL1025 file. Expense customers using American Express (AMEX) files for credit card transaction feeds may experience duplicate transactions being imported. Affected users may observe duplicate or triplicate AMEX transactions listed in Available Expenses. Workaround: Customers may try the following potential workarounds: 1.) Customers may be able to bypass the issue by hiding 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.) Customers can 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.) Some users may have the ability to identify transactions that were duplicated or triplicated. If these transactions can be identified, please include the matching debit and credit transactions together in a single report. If assistance is required, please request help via your Salesforce case, and your case owner will assist. The Incident Response Team (IRT) has scheduled a follow up meeting on December 19 with the AMEX response team to align on current status and corrective actions. Our next update will be at or before 9PM UTC on 19 December or sooner should a significant change occur.

18 December 2025 | 12:02 pm

Expense customers using American Express (AMEX) GL1025 file for credit card transaction feeds may experience duplicate transactions being imported. Affected users may observe duplicate or triplicate AMEX transactions listed in Available Expenses. Workaround: Customers may try the following potential workarounds: 1.) Customers may be able to bypass the issue by hiding duplicate and reversal transactions. Concur Administrators with the Expense Company Card Administrator role can perform this action. If your company requires help hiding all affected transactions, your case owner can work with the administrator to identify and hide impacted transactions. For more details, refer to the article found in Knowledge base - How can I hide duplicate charge? 2.) Customers can 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.) Some users may have the ability to identify transactions that were duplicated or triplicated. If these transactions can be identified, please include the matching debit and credit transactions together in a single report. If assistance is required, please request help via your Salesforce case, and your case owner will assist. The Incident Response Team (IRT) has concluded a meeting with American Express representatives. American Express confirmed that further impact to U.S. customer has been mitigated while their investigation into impact outside the U.S. is in progress. We will share an update on their investigation as soon as more information becomes available. Meanwhile, the IRT is continuing work to identify the most effective corrective actions and to support affected customers. Our next update will be in 12 hours or sooner should a significant change occur.

18 December 2025 | 6:31 am

Expense customers using American Express (AMEX) GL1025 file for credit card transaction feeds may experience duplicate transactions being imported. Affected users may observe duplicate or triplicate AMEX transactions listed in Available Expenses. Workaround: Customers may try the following potential workarounds: Customers may be able to bypass the issue by hiding 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? Customers can 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? The Incident Response Team (IRT) collaborated with AMEX to identify the issue and has confirmed that the required fix has been implemented. In addition, the IRT is actively working with internal teams to determine appropriate corrective actions. Further updates will be shared at the earliest opportunity. Our next scheduled update will be provided at or before 05:30 PM UTC on 18 December 2025.