Issue with exchange rates of Feb 24 to Feb 27

We confirm after review and further observations that all impacts and root causes have now been addressed. We also implemented an extra monitoring as mitigation. Incident is now closed. Thank you for your patience !

The team corrected the last impacted expenses today, system is now clean from all impacts and recovered. We will perform some final integrity controls on ERP interfaces tomorrow before closing this incident.

We identified all the impacted foreign expenses. A handful of cases remains, and we'll keep working toward clean resolution and communication to impacted customers.

We are also aware of cases impacting ERP interfaces sent between Feb 25 and Mar 7, where exchange rate conversion was applied on the fly. The team made great progress today towards a proper identification of impacted interfaces and customers. We'll continue to communicate pro-actively alongside the investigation in the coming few business days.

In case of concern, do not hesitate to reach out to our Tech Support.

We just confirmed that all corrupted rates were properly identified and corrected in the system. Identification and resolution of impacted expense data in underways.

Only foreign expenses created for the below rates may be impacted.

• Default rates (XE.COM) of Feb 25, 26, 27
• Croatian rates of Feb 25, 26
• Czech rates of Feb 24, 25
• Slovakian rates of Feb 24, 25
• Albanian rates of Feb 25, 26, 27

A server issue caused some exchange rates of Feb 25, 26, and 27 to be corrupted. The root cause was identified and resolved, but we are still working on cleaning up the impacts. The error does not appear to be global, and should only affect expense from these dates. Most of the bad exchange rates were already cleaned from the system and restored. We'll complete this cleanup as soon as possible and identify all impacted expenses to fix or inform our customers.