SAP Concur incident

Expense: P1

Resolved after 1 hour 26 minutes, affecting Expense, on October 8, 2025.

resolved Oct 22, 2025, 06:27 AM UTC

Impact as Reported: In the Concur Cloud for Public Sector Data Center expense report creation were unavailable for Concur Travel and Expense users. Affected users were able to successfully click "Create New Report" , complete the Travel Allowance screen, and click "Next". However, when attempting click "Finish" on the following screen, users encountered an error, "Sorry Something went wrong“ Root cause: Due to a preceding change freeze in place to ensure stability during the month of September altering the normal code deployment schedule, and to a gap in the code release process, an update to a spend service component was rolled out before a pre-requisite code change had been applied to a separate spend module. Consequently the updated component couldn't function normally due to failed dependencies, resulting in disruption for the end users. The code update was rolled back to restore service. Corrective Actions: The engineering team is revising the deployment process to add a pre-release staging step validating that version dependencies are met ahead of production roll out. This will prevent a component mismatch from causing disruptions.

Started
Oct 08, 2025, 08:32 PM UTC
Resolved
Oct 08, 2025, 09:58 PM UTC
Duration
1h 26m
Detected by Pingoru
Oct 08, 2025, 08:32 PM UTC

Affected components

Expense

Update timeline

  1. resolved Oct 08, 2025, 09:39 PM UTC

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

  2. resolved Oct 08, 2025, 11:38 PM UTC

    In the Concur Cloud for Public Sector Data Center expense report creation is currently unavailable for Concur Travel and Expense users. Affected users are able to successfully click "Create New Report" , complete the Travel Allowance screen, and click "Next". However, when attempting click "Finish" on the following screen, users are encountering an error, "Sorry Something went wrong“. There is no known workaround at this time. The Incident Response Team (IRT) is currently investigating. Our next update will be in one hour or sooner should a significant change occur.

  3. resolved Oct 08, 2025, 11:39 PM UTC

    In the Concur Cloud for Public Sector Data Center expense report creation were unavailable for Concur Travel and Expense users. Affected users were able to successfully click "Create New Report" , complete the Travel Allowance screen, and click "Next". However, when attempting click "Finish" on the following screen, users encountered an error, "Sorry Something went wrong“. There was no workaround identified. 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.

  4. resolved Oct 08, 2025, 11:40 PM UTC

    In the Concur Cloud for Public Sector Data Center expense report creation were unavailable for Concur Travel and Expense users. Affected users were able to successfully click "Create New Report" , complete the Travel Allowance screen, and click "Next". However, when attempting click "Finish" on the following screen, users encountered an error, "Sorry Something went wrong“. There was no workaround identified. The Incident Response Team (IRT) rolled back a recent change 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.

  5. resolved Oct 22, 2025, 06:27 AM UTC

    Impact as Reported: In the Concur Cloud for Public Sector Data Center expense report creation were unavailable for Concur Travel and Expense users. Affected users were able to successfully click "Create New Report" , complete the Travel Allowance screen, and click "Next". However, when attempting click "Finish" on the following screen, users encountered an error, "Sorry Something went wrong“ Root cause: Due to a preceding change freeze in place to ensure stability during the month of September altering the normal code deployment schedule, and to a gap in the code release process, an update to a spend service component was rolled out before a pre-requisite code change had been applied to a separate spend module. Consequently the updated component couldn't function normally due to failed dependencies, resulting in disruption for the end users. The code update was rolled back to restore service. Corrective Actions: The engineering team is revising the deployment process to add a pre-release staging step validating that version dependencies are met ahead of production roll out. This will prevent a component mismatch from causing disruptions.

Your product runs on more than SAP Concur

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →