Sage incident

Banking Service - Partial Outage

Sage is currently experiencing a minor incident affecting Banking Service and Sage 50 and 1 more component, which began 3d ago. The vendor's full update timeline is below.

Started
May 18, 2026, 08:17 AM UTC
Resolved
Ongoing
Duration
● 2d 14h
Detected by Pingoru
May 18, 2026, 08:17 AM UTC

Affected components

Banking ServiceSage 50Sage Intacct

Update timeline

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. identified May 19, 2026, 01:22 PM UTC

    We are continuing to work on a fix for this issue.

  6. 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.

  7. 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.