How Bots Are Now Running 45 SAP Processes At A Utilities Provider

A utility business serving more than seven million customers across six states has taken its SAP automation program from a single bot to a fleet of more than 10 bots running 45-plus business processes, according to a case study published by Resolve Tech Solutions. RTS reports $10 million in cost savings, more than 100,000 manual hours reclaimed, and a five-hour process reduced to 15 minutes.

Inside the SAP Automation

The bots work inside SAP rather than around it. RTS says its automations pull past-due financial reports, run billing reconciliation, generate and distribute exception reports for multiple SAP business units, execute rate-case compliance steps, and compare test scenarios during the utility’s SAP S/4HANA migration with exception reports sent automatically to reviewers. ASUG’s coverage of the same program identifies the SAP footprint touched by the bots as SAP Business Warehouse, SAP BusinessObjects, SAP CRM, and SAP S/4HANA.

RTS structures the work around a Center of Excellence. One to two staff per shift monitor bot health, and SLAs govern remediation when a bot breaks; the case study reports no major post-production incidents outside routine system refreshes and patching.

From RPA to S/4HANA Testing

That utility engagement now anchors a broader SAP practice that lists six service lines: assessment and advisory, transformation, S/4HANA migration, Business Technology Platform, application managed services, and S/4HANA managed testing. RTS positions RPA and AI as automation layers on top of S/4HANA, Fiori, and SAP Integration Suite.

For SAP practitioners weighing partners on S/4HANA testing and post-go-live automation, the program is the reference architecture RTS is selling: SAP-embedded bots, a CoE operating model, and reusable test automation carried into steady-state operations. The open questions are the reconciliation of savings figures across RTS’s own materials and how the model scales beyond utilities.

What This Means for SAPinsiders

• Automation becomes migration infrastructure. Using the same automation estate for testing and operations reduces handoff risk between transformation and steady state. That continuity can turn migration investment into a reusable control layer rather than a temporary project cost.
• Governance is the real scaling constraint. Bot counts matter less than ownership, monitoring, and remediation discipline once automations touch regulated financial and billing processes. The CoE therefore becomes an operational-risk function, not merely a development team.
• Savings claims need process-level evidence. Large aggregate benefits are persuasive, but buyers need savings traced to individual workflows, avoided labor, and exception rates. That evidence determines whether RTS has a repeatable model or one unusually favorable utility case.