SAP Concur incident

Japan - e-Bunsho for Expense: P1

Resolved after 1 hour, affecting Japan - e-Bunsho for Expense, on November 21, 2025.

resolved Dec 09, 2025, 02:20 PM UTC

In the US2 Data Center, generating an e-Bunsho timestamp in expense reports was unavailable. Affected users may have encountered the following error when attempting to submit an expense report that has an e-Bunsho timestamp requested, "Not Digitally Compliant: Please make sure the receipt image is given an e-Bunsho timestamp." A background process executing the image extraction and archiving of an expense report counting more than 50.000 line items, along with an aggressive re-try mechanism and a bug causing dead-lettered messages to reappear on the original processing queue, have resulted in severe resource consumption, to the point where available resources were exhausted causing 2/3 of the Imaging application to fail and consequently preventing the e-bunsho time stamp service from operating. Corrective Actions: A limit to the number of line items allowed in a single Expense Report is being introduced. This will prevent creation of oversized report that could generate similar issues in the future. A reconciliation process between the Imaging and Expense service is going to be executed to identify existing oversized report and a plan will be developed for the handling of those exceptions in the event a full images extract would be needed at some point on the future.

Started
Nov 21, 2025, 12:35 PM UTC
Resolved
Nov 21, 2025, 01:35 PM UTC
Duration
1h
Detected by Pingoru
Nov 21, 2025, 12:35 PM UTC

Affected components

Japan - e-Bunsho for Expense

Update timeline

  1. resolved Nov 21, 2025, 03:07 PM UTC

    In the US2 Data Center, generating an e-Bunsho timestamp in expense reports was unavailable. Affected users may have encountered the following error when attempting to submit an expense report that has an e-Bunsho timestamp requested, "Not Digitally Compliant: Please make sure the receipt image is given an e-Bunsho timestamp." As the Incident Response Team (IRT) was being assembled, the service self restored. We have verified that service performance is stable and will now resolve this incident. A continued investigation into the root cause of this incident will be conducted, and a root cause analysis report provided when that investigation is complete.

  2. resolved Dec 09, 2025, 02:20 PM UTC

    In the US2 Data Center, generating an e-Bunsho timestamp in expense reports was unavailable. Affected users may have encountered the following error when attempting to submit an expense report that has an e-Bunsho timestamp requested, "Not Digitally Compliant: Please make sure the receipt image is given an e-Bunsho timestamp." A background process executing the image extraction and archiving of an expense report counting more than 50.000 line items, along with an aggressive re-try mechanism and a bug causing dead-lettered messages to reappear on the original processing queue, have resulted in severe resource consumption, to the point where available resources were exhausted causing 2/3 of the Imaging application to fail and consequently preventing the e-bunsho time stamp service from operating. Corrective Actions: A limit to the number of line items allowed in a single Expense Report is being introduced. This will prevent creation of oversized report that could generate similar issues in the future. A reconciliation process between the Imaging and Expense service is going to be executed to identify existing oversized report and a plan will be developed for the handling of those exceptions in the event a full images extract would be needed at some point on the future.

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 →