UiPath’s SAP S/4HANA Migration Brought Automation to Finance — And Built Confidence in the Numbers

UiPath ran its SAP S/4HANA migration as a Customer Zero initiative, embedding automation and agentic AI directly into finance workflows during the implementation.

Hitesh Ramani, UiPath’s chief accounting officer and deputy chief financial office, says the most revealing part of the migration was not the technology itself. What stood out was how quickly finance work changed once routine processes were automated, he told SAPinsider.

“The first thing that changes is where people spend their time,” Ramani says. “Tasks that used to consume hours — reconciliations, invoice matching, routine journal entries — start moving through the system without someone manually shepherding every step.”

That shift was noticeable almost immediately. The first reaction inside finance was uncertainty about how roles would change. “If the system is doing what I used to do,” Ramani recalls hearing from teams, “what’s my role now?”

Automation Arrived With the SAP S/4HANA Migration

UiPath embedded automation directly into the SAP S/4HANA migration rather than waiting until after go-live to introduce it.

The program ran as a Customer Zero initiative under live finance operations, with SAP operating as the system of record while automation handled reconciliations, validations, and exception-heavy workflows across finance processes.

Finance teams naturally approached the shift with caution.

“Finance people are trained to own the numbers,” Ramani says. “Accuracy isn’t just part of the job — it’s part of the professional identity. When a system starts doing work you used to check line by line, the instinct is to ask whether you can trust it.”

Ramani brings an auditor’s perspective to that question. Before joining UiPath in 2021, he spent more than 16 years at Deloitte as an audit partner.

“People need to see it working in their own environment,” Ramani says. “Once they see that it’s catching exceptions, flagging mismatches, and creating a clear audit trail, the conversation changes.”

What Finance Teams Notice First: Speed

As finance teams begin working with the automated workflows, the operational impact becomes visible quickly. Processes that once required hours of verification start moving through automated workflows in minutes.

“Speed is the first thing people notice,” Ramani says. “Close activities, reconciliations, exception handling — work that used to stretch across days can move much faster once automation is orchestrating the process.”

That acceleration produces a second effect. As workflows execute automatically, discrepancies and anomalies surface earlier in the process, often before they cascade into larger reconciliation problems at the end of the reporting cycle.

“You start seeing mismatches sooner,” Ramani says. “The system flags them, creates an audit trail, and routes them to the right place for review.”

Over time, those improvements begin to change how finance teams interact with the numbers themselves. The role shifts from manually verifying each transaction toward understanding patterns, investigating anomalies, and interpreting results.

“The biggest change is confidence,” Ramani says. “The conversation shifts from ‘let me verify that figure’ to ‘here’s what the numbers are telling us.’”

That progression—from speed to accuracy to confidence—marks the point where automation stops feeling like a tool and starts reshaping how finance teams work.

When Confidence in the Numbers Begins to Change Finance Work

As that shift in confidence begins to take hold, finance’s role begins to expand.

Instead of spending most of their time verifying transactions and reconciling records, finance teams gain more time to interpret results and advise the business. The focus moves away from reconstructing what happened toward understanding what the numbers mean while decisions are still being made.

“For years finance has operated in a retrospective model,” Ramani says. “You close the books, you verify the numbers, and then you explain what happened.”

UiPath’s SAP S/4HANA migration provided the foundation for that change, keeping SAP as the system of record while automation handled intervention-heavy finance workflows.

“The real value shows up when finance can help leaders make decisions while the window to act is still open,” Ramani says. “Instead of explaining the past, you’re helping shape what happens next.”

In that sense, the S/4HANA migration did more than modernize UiPath’s finance systems. It created the conditions for automation that allows finance teams  to move from verifying transactions to interpreting what the numbers mean for the business.

The Hardest Part of Agentic Finance Is Still Ahead

UiPath’s experience suggests the impact of an SAP S/4HANA migration extends beyond system modernization. The Customer Zero initiative embedded automation directly into the migration, turning the implementation into a proving ground for how finance could run once automation and AI were part of the operating model.

But Ramani cautions that the operational gains visible during Customer Zero represent only part of the transformation. As organizations begin introducing agentic capabilities and expanding automation across finance processes, new challenges emerge around governance, data integration, and organizational change.

“When people talk about agentic AI, they often focus on the technology,” Ramani says. “In practice, the harder part is how the organization adapts to working with it.”

Those challenges—how teams govern, trust, and coordinate work with intelligent systems—are now becoming the next phase of finance transformation.

What This Means for SAPinsiders

Migrations are becoming automation design points. Embedding automation during migration changes how processes are designed. Organizations that treat SAP S/4HANA implementations as architectural foundations for automation can redefine work allocation between systems, agents, and people earlier in the transformation.

Automation shifts finance risk earlier in the reporting cycle. When reconciliation and exception detection occur continuously, operational risk surfaces sooner. This changes how finance teams manage controls, shifting effort from retrospective verification toward monitoring anomalies and resolving issues before reporting deadlines.

Confidence becomes the real automation milestone. Finance teams adopt automation only after trust in the numbers develops. Once systems consistently surface discrepancies, generate audit trails, and resolve exceptions, automation shifts from an efficiency tool to an operational foundation.