Banking Service - Operational

Incident Report for Sage

Resolved

We identified that on Friday the 29th of May a subset of customers globally using the products listed below experienced transaction synchronization failures that led to delays in getting their transactions and failures during transaction imports.

The incident is now resolved with transaction syncing working as expected. We apologise for any inconvenience this might cause.

The list of product/services affected:
SBC Accounting UKI
SBC Accounting ZA
Sage 50 Accounts UKI
Sage Sole Trader
Sage Intacct
Sage 50 Accounts ES
Sage 50 Accounts CA
Sage 200 Standard
Sage 200 (ES)
Sage 50 ZA
Sage 200 ES / Murano / Despachos
Sage 50 Accounts US
Sage 50 Cloud (US)
Sage Active
Sage 100 US Contractor
Sage 100 Contractor Cloud
Sage for Accountants Portugal
Sage Evolution (ZA)
Sage 100c US
Sage 100 CA Contractor
Sage 300
Sage 50 Accounts PT
Posted Jun 01, 2026 - 09:03 UTC
This incident affected: Asia Pacific (Banking Service, Sage Intacct), Middle East and Africa (Banking Service, Evolution: Sync Dash (ZA), Sage 300 Connected Services, Sage Business Cloud Accounting ZA, Sage Intacct), South America (Banking Service), North America (Banking Service, Sage 100 Contractor Cloud, Sage for Accountants, Sage Intacct), and Europe (Banking Service, Sage 200 (ES), Sage 200 Partner Cloud (ES), Sage 200 Professional SPC (UKI), Sage 200 Standard (UKI), Sage Active, Sage Business Cloud Accounting (UKI), Sage for Accountants, Sage Intacct).