Concur Support & User Guides

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