Sage experienced a minor incident on May 18, 2026 affecting Banking Service and Sage 50 and 1 more component, lasting 4d 8h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 18, 2026, 08:17 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
- investigating May 18, 2026, 08:44 AM UTC
We have identified that customers in South Africa are experiencing severe slowness and failures when trying to use the product. The issue started at approximately 07:00 UTC on the 18th of May. We are currently investigating.
- investigating May 18, 2026, 08:54 AM UTC
We have identified an issue in South Africa where customers using FNB bank are experiencing re-authentication errors when trying to onboard new customers and syncing the latest transactions. Customers are presented with “authorization code not accepted when clients enter the authorisation code” error message. The product/service impacted: SBC Accounting ZA Sage 50 ZA Sage 200 Evolution Sage Intacct We are currently investigating.
- identified May 18, 2026, 03:37 PM UTC
Third-Party FNB has acknowledged the issue and are working on resolving it as a top priority. We appreciate your patience as we work to resolve this issue.
- identified May 19, 2026, 01:22 PM UTC
We are continuing to work on a fix for this issue.
- identified May 19, 2026, 04:10 PM UTC
The third-party provider, FNB is continuing to investigate the issue. We appreciate your patience as we work to resolve this issue.
- identified May 20, 2026, 12:13 PM UTC
Third-party provider, FNB is working on a fix. Thank you for your patience as we work to resolve this issue.
- identified May 21, 2026, 09:10 AM UTC
Third-Party FNB has applied a fix to the issue. Please note that while customers are able to complete an onboard there will be a delay in the new transactions coming through and therefore transactions will be pulled throughout today, 21st of May and back to normal tomorrow on the 22nd of May.
- resolved May 22, 2026, 05:09 PM UTC
The issue is resolved and the service is available and performing as expected.