Expense: P1

Update timeline

1. resolved Jun 22, 2026, 05:37 PM UTC

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

2. resolved Jun 22, 2026, 06:29 PM UTC

   All Go.gov customers in the Concur Cloud for Public Sector Data Center are currently experiencing a functional disruption impacting the Verify and Audit process. Since approximately 9:00 PM UTC on June 21, 2026, submitted expense reports are not progressing to the Verify queue for audit. As a result, expenses cannot be approved, processed, or paid. Affected users will see their expense reports remain in a “Pending Audit Review” status. Expense reports submitted prior to 9:00 PM UTC on June 21, 2026 are not impacted and have continued through the normal verification, approval, and processing workflow. Workaround: A workaround for this issue is not available at this time. The Incident Response Team is engaged and currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Jun 22, 2026, 06:52 PM UTC

   All Go.gov customers in the Concur Cloud for Public Sector Data Center experienced a functional disruption impacting the Verify and Audit process. Since approximately 9:00 PM UTC on June 21, 2026, submitted expense reports were not progressing to the Verify queue for audit. As a result, expenses could not be approved, processed, or paid. Affected users saw their expense reports remain in a “Pending Audit Review” status. Expense reports submitted prior to 9:00 PM UTC on June 21, 2026 were not impacted and continued through the normal verification, approval, and processing workflow. 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 Jun 22, 2026, 07:11 PM UTC

   All Go.gov customers in the Concur Cloud for Public Sector Data Center experienced a functional disruption impacting the Verify and Audit process. Since approximately 9:00 PM UTC on June 21, 2026, submitted expense reports were not progressing to the Verify queue for audit. As a result, expenses could not be approved, processed, or paid. Affected users saw their expense reports remain in a “Pending Audit Review” status. Expense reports submitted prior to 9:00 PM UTC on June 21, 2026 were not impacted and continued through the normal verification, approval, and processing workflow. Workaround: A workaround for this issue was not available during service impact. The Incident Response Team has implemented a configuration change within a business server tier and identified several unhealthy servers, which have since been taken offline. 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.

5. resolved Aug 03, 2026, 04:48 PM UTC

   Impact as Reported: All Go.gov customers in the Concur Cloud for Public Sector Data Center experienced a functional disruption impacting the Verify and Audit process. Since approximately 9:00 PM UTC on June 21, 2026, submitted expense reports were not progressing to the Verify queue for audit. As a result, expenses could not be approved, processed, or paid. Affected users saw their expense reports remain in a “Pending Audit Review” status until the incident was resolved. Expense reports submitted prior to 9:00 PM UTC on June 21, 2026 were not impacted and have continued through the normal verification, approval, and processing workflow Root cause: An issue impacted expense report processing, causing some reports to remain in a Pending Audit Review status. The audit and verification process could not complete because a dependent Receipt Recognition service in the CCPS environment was unavailable. The root cause was the deprecation of an IAM user account that the Receipt Recognition service relied on for access in the CCPS environment. While other environments had already been migrated to role-based access, CCPS continued to use a legacy IAM user configuration. When the IAM user was deprecated, the service could no longer access the required resources, resulting in audit processing failures. Service was restored by re-creating the required IAM user in CCPS, which re-established access for the Receipt Recognition service and allowed expense report processing to resume. The legacy configuration exception had not been identified during the service ownership transition and was therefore missed during the IAM user deprecation process. Corrective Actions: The following corrective and preventative actions were identiifed: Re-created the IAM user in CCPS to restore service. Migrate the Receipt Recognition service in CCPS from IAM user-based authentication to IAM role-based authentication, aligning it with the configuration used in other environments. Review and enhance monitoring, alerting, and operational playbooks for the Receipt Recognition service to ensure critical dependencies are properly tracked and monitored. Implement business validation and synthetic testing for receipt-processing workflows in CCPS to enable earlier detection of service degradation or failures. Improve operational readiness and dependency management processes to ensure environment-specific configuration exceptions are identified and addressed during future infrastructure or access changes. * Update synthetic test monitoring to validate the service for runtime issues