SAP Concur experienced a critical incident on January 13, 2026 affecting Expense and Invoice, lasting 6h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Jan 13, 2026, 04:11 PM UTC
A subset of Concur Expense and Concur Invoice customers are experiencing an access issue. Affected users may encounter the following error after signing in to their account, “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance.” A workaround for this issue is not available at this time. To check if your company is affected by this incident please log onto the Personalized Concur Open website. The Incident Response Team (IRT) is engaged, has identified root cause, and is working to determine best course of action to resolve the incident. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Jan 13, 2026, 04:55 PM UTC
A subset of Concur Expense and Concur Invoice customers are experiencing an access issue. Affected users may encounter the following error after signing in to their account, “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance.” A workaround for this issue is not available at this time. To check if your company is affected by this incident please log onto the Personalized Concur Open website. The Incident Response Team (IRT) has identified blocking on a core database server as root cause. The IRT is investigating to determine best course of action to remediate blocking and restore service. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Jan 13, 2026, 05:47 PM UTC
A subset of Concur Expense and Concur Invoice customers experienced an access issue. Affected users encountered the following error after signing in to their account, “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance.” A workaround for this issue was not available. To check if your company is affected by this incident please log onto the Personalized Concur Open website. 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.
- resolved Jan 13, 2026, 06:02 PM UTC
A subset of Concur Expense and Concur Invoice customers experienced an access issue. Affected users encountered the following error after signing in to their account, “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance.” A workaround for this issue was not available. To check if your company was affected by this incident please log onto the Personalized Concur Open website. The Incident Response Team made a configuration update to a core database server and flushed the cache of a business service tier 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 now be conducted, and a root cause analysis report provided when that investigation is complete.
- resolved Jan 29, 2026, 12:14 PM UTC
A subset of Concur Expense and Concur Invoice customers experienced an access issue. Affected users encountered the following error after signing in to their account, “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance.” A workaround for this issue was not available. To check if your company is affected by this incident please log onto the Personalized Concur Open website. Root cause: A routine database maintenance did not complete successfully resulting in some expense tenants being offline. Tenants on the target database are briefly set to inactive while the operation is executed and then re-enabled when the operation is completed - this is normally completely transparent to end users. An automation failure during the maintenance operation unexpectedly resulted in the tenants of the target database not to be reactivated. The Incident Response Team identified the impacted tenants and re-activated them to restore functionality to the impacted users. Corrective Actions: The following corrective and preventative actions were identified: Update the automation error handling to automatically roll back the tenants state in case of failures Add additional monitoring to the database maintenance process to validate tenants status Increase the retry wait times to mitigate the chance of failures Update the documentation for database maintenance to improve the troubleshooting process and reduce service restoration times.