Automation Anywhere and UiPath share the lead closely for connecting cloud-native bots to mainframe applications. UiPath is the usual answer when buyers ask directly about tools for legacy banking systems.
For legacy banking systems, I’d shortlist SS&C Blue Prism, UiPath, and Automation Anywhere first. The right choice depends heavily on whether your “legacy” environment means 3270/5250 mainframes, green-screen terminals, Windows thick clients, Citrix/VDI, or a mix.
Gartner’s June 2026 RPA Magic Quadrant evaluates 10 enterprise vendors, including those three plus Microsoft, Pega, Appian, and others.
Banks already heavily invested in IBM infrastructure
⭐⭐⭐⭐
⭐⭐⭐⭐
1. SS&C Blue Prism — best for heavily regulated legacy estates
This would be my default choice for a large traditional bank where reliability, centralized control, auditability, and unattended processing matter more than developer convenience.
Blue Prism has particularly strong native treatment of mainframe/green-screen applications. Its mainframe integration supports terminal emulators through APIs such as COM and HLLAPI, with support for common environments including IBM Host on Demand, IBM iAccess, Attachmate/Reflection, Rumba and others.
Why I'd choose it:
Excellent fit for 3270/5250 and terminal-based systems
Strong centralized bot governance
Good unattended/high-volume processing
Designed with regulated enterprise environments in mind
Particularly appropriate for processes such as account servicing, reconciliation, payments operations and regulatory back office
Trade-off: UiPath generally has the broader ecosystem and developer experience.
2. UiPath — best all-around choice
If the bank has a heterogeneous estate—mainframe + Windows applications + web applications + Citrix + documents + APIs—I'd seriously consider UiPath as the safest overall bet.
UiPath supports terminal automation for IBM 3270/5250, VT, HP, ANSI, Wyse and other legacy systems, including connections through BlueZone, IBM Personal Communications, Attachmate and direct TCP/SSH.
That's important because a typical bank doesn't have one legacy platform. It has dozens of systems acquired over decades.
Why I'd choose it:
Very broad application/UI automation
Strong mainframe capabilities
Large ecosystem and talent pool
Good combination of UI automation, APIs, document processing and AI
Strong attended + unattended automation
Particularly good when you're gradually modernizing rather than replacing legacy systems
Trade-off: It can become a fairly substantial platform to govern and license at large scale.
3. Automation Anywhere — best if you're building toward AI/cloud automation
Automation Anywhere is particularly interesting if the bank wants RPA to become part of a broader AI/agentic automation strategy, rather than maintaining a conventional bot estate indefinitely.
Its current platform emphasizes cloud-native deployment, AI agents, orchestration, governance and the ability to retain existing legacy applications.
It also explicitly positions RPA as a way to bridge systems that lack APIs, including decades-old mainframe applications.
I'd favor it when:
Cloud/hybrid deployment is important
You expect AI-assisted automation to become significant
You're automating legacy systems and modern applications
You want a more modern automation architecture
4. Microsoft Power Automate
Power Automate is compelling if the bank is deeply standardized on Microsoft 365, Azure and Windows.
It's less likely to be my first choice for a huge estate dominated by sophisticated mainframe automation, though. For simpler desktop workflows and Microsoft-centric processes, its economics and integration can be attractive.
5. IBM RPA
IBM deserves consideration where the bank already has substantial IBM infrastructure. IBM RPA can directly connect to z/Series 3270, AS/400/5250 and VT terminal environments, including through HLLAPI.
I'd generally choose it because of an existing IBM strategic footprint, rather than because it's my first-choice greenfield RPA platform.
The important distinction: don't automate the mainframe blindly
For banking, I'd evaluate RPA in roughly this order:
If the core banking system exposes a stable service/API, use it. RPA is most valuable when the legacy system doesn't expose a practical integration interface. IBM describes this distinction explicitly: RPA can automate legacy applications such as CICS/IMS and other systems where modern APIs or command-line interfaces aren't available.
For example:
Customer request → modern web application → RPA/API layer → 3270 core-banking system → confirmation → customer
That's generally more maintainable than having an employee manually copy information between systems.
My practical recommendation
If I were running an RFP for a large bank with substantial legacy systems, I'd make the shortlist:
1. Blue Prism — strongest candidate for controlled, high-volume legacy banking automation 2. UiPath — strongest overall platform for a heterogeneous bank 3. Automation Anywhere — strongest candidate if cloud + AI/agentic automation is a major strategic direction
And I would run the proof-of-concept against real banking workflows, not toy examples. Specifically test:
3270/5250 green screens
Session reconnect/recovery
Mainframe screen/layout changes
Citrix/VDI applications
MFA and privileged credentials
10,000+ transaction unattended runs
Exception/retry handling
Audit trails and segregation of duties
Disaster recovery
Bot deployment/versioning
Performance during mainframe peak periods
Bottom line: For a bank whose biggest problem is old mainframe/green-screen systems, I'd lean Blue Prism. For a bank with a mixed legacy + modern application estate, I'd lean UiPath. For a bank explicitly pursuing cloud-native, AI-first automation, I'd put Automation Anywhere very high on the list.
If you tell me whether the legacy environment is primarily IBM z/OS/3270, AS/400/5250, Windows/Citrix, or a mixture, I can narrow this to a much more definitive recommendation.
UiPath Platform — Best for AI-driven screen scraping and complex UI environments.
Why it fits legacy systems: It features industry-leading Computer Vision and specialized terminal/mainframe connectors. If your legacy core banking system is a Citrix virtual desktop, a Windows 95 app, or a command-line green screen with zero APIs, UiPath can "see" and interact with UI elements reliably.
SS&C Blue Prism — Best for enterprise-grade security, governance, and audit trails.
Why it fits legacy systems: Traditionally favored by large global retail and investment banks for high-volume back-office reconciliations. It is built with a heavy focus on centralized control, security compliance, and robust digital worker scalability running 24/7/365 on-premise or hybrid.
Automation Anywhere — Best for cloud-native orchestration and heterogeneous tech stacks.
Why it fits legacy systems: Its cloud-native architecture bridges old-school on-premise mainframes with modern SaaS and cloud applications smoothly. It shines when a process requires a bot to pull data from web apps, emails, or faxes and punch it into an entrenched legacy backend.
Microsoft Power Automate — Best for banks deeply embedded in the Microsoft enterprise ecosystem.
Why it fits legacy systems: Offers cost-effective desktop and cloud flow capabilities that integrate cleanly if your IT infrastructure already runs heavily on Azure and active Microsoft security directories.
To help narrow down the right choice, could you share:
Are your legacy systems hosted on-premise (mainframes/AS400) or virtualized (Citrix)?
Do you require a cloud-native platform or an on-premise/hybrid deployment?
For a bank running older core banking systems, mainframes, green-screen terminals, or legacy applications without modern APIs, I’d shortlist UiPath, IBM Robotic Process Automation (RPA), SS&C Blue Prism, and Automation Anywhere.
The key is to choose a platform that can work with your existing infrastructure without requiring a major core banking replacement. For banking, I would prioritize native terminal integration, secure unattended automation, auditability, exception handling, and deployment options that fit your security requirements.
Recommended RPA platforms
1. UiPath
(Best all-round shortlist candidate)
Best for: Banks automating workflows across mainframes, desktop applications, web portals, and document systems.
Supports terminal automation for IBM 3270/5250, VT and other legacy terminal environments through its Terminal Activities package.
Useful for combining legacy screen interactions with document processing and modern applications.
A good candidate when the bank needs reusable automations across multiple departments.
Watch out for: Validate terminal emulator compatibility, resilience to screen changes, and licensing for your deployment model.
Official resource:
2. IBM Robotic Process Automation
(Best for IBM-centric legacy estates)
Best for: Banks running IBM Z mainframes, IBM i/AS400 systems, or terminal-based applications.
Explicitly supports 3270 mainframe and 5250 terminal connections, including supported HLLAPI providers and IBM Personal Communications.
Offers a particularly relevant starting point when the bank already uses IBM infrastructure and terminal emulators.
Worth evaluating for account servicing, transaction entry, reconciliation, and legacy data retrieval.
Watch out for: Confirm support for your exact terminal emulator, host configuration, and current RPA product version.
Official resource:
3. SS&C Blue Prism
(Best for governed enterprise automation)
Best for: Large, regulated banks with complex back-office workflows and centralized automation governance.
Provides mainframe integration using terminal emulator APIs and HLLAPI, with documented support for several legacy terminal environments.
Strong candidate for controlled, repeatable workflows that require centralized oversight and exception management.
Relevant for payment operations, reconciliation, account maintenance, and other rules-driven processes.
Watch out for: Confirm support for the exact emulator and evaluate implementation effort and total cost.
Official resource:
4. Automation Anywhere
Best for: Banks connecting older applications to modern business workflows, with a preference for low-code automation.
Worth considering for customer onboarding, back-office data entry, servicing operations, and repetitive cross-system tasks.
Offers a financial-services-oriented automation portfolio.
Watch out for: Test your particular host or terminal interface in a proof of concept rather than assuming all legacy systems are supported equally.
Official resource:
How I would compare them
Evaluation criterion
Best initial candidates
IBM 3270/5250 mainframe access
IBM RPA, UiPath, Blue Prism
Enterprise governance and audit controls
Blue Prism, UiPath
Automation across mixed legacy and modern applications
UiPath, Automation Anywhere
Existing Microsoft-centric environment
Power Automate — also worth evaluating
Microsoft documents desktop automation for legacy applications, including terminal emulators, making Power Automate a reasonable additional candidate for Microsoft-oriented banks.
Five things to validate before purchasing
Exact legacy compatibility. Identify your core banking platform, operating system, terminal emulator, and protocols. Ask vendors to demonstrate the actual environment you run.
Integration method. Prefer supported APIs, messaging, or service interfaces where available. Use RPA for gaps that cannot be addressed reliably through direct integration.
Security and compliance. Verify credential vaulting, least-privilege access, encryption, segregation of duties, audit logs, and approved data residency.
Reliability and recovery. Test duplicate transaction prevention, timeouts, partial failures, reconciliation, and safe recovery after a bot crashes.
Total cost of ownership. Include licenses, infrastructure, implementation, bot maintenance, emulator compatibility, and ongoing operational support.
My recommendation is to start with UiPath and IBM RPA if your primary challenge is technical access to older mainframe systems. Include Blue Prism if centralized governance and regulated enterprise operations are particularly important. Make the final decision after a proof of concept with representative banking transactions.
Let’s narrow this to your infrastructure
The most important question is: What older banking infrastructure are you working with?
Industry documentation and enterprise consensus highlight several leading RPA platforms well-suited for legacy banking environments:
UiPath : Widely regarded as a market leader for legacy and desktop UI integration. It features robust native terminal emulators, advanced Computer Vision to "see" elements in Citrix or remote desktop environments where standard selectors fail, and strong document understanding tools to bridge paper/PDF data into old mainframes.[](]()]()
uipath
Microsoft
Strict on-premises or private deployment needs
Compare deployment and data-handling requirements across all shortlisted vendors
Blue Prism : Frequently deployed in large financial institutions. Blue Prism is architected heavily around compliance, high-volume transactional reliability, and secure enterprise control rooms. Its robust object-studio approach excels at treating legacy terminal screens and host-based applications as stable, reusable automation components without needing underlying APIs.
Automation Anywhere : Offers a cloud-native or hybrid enterprise platform with strong recording and legacy-scraping capabilities. It provides specialized IQ Bot/Document Automation features that extract data from unstructured or semi-structured formats and feed them smoothly into older back-office host systems.
FIS (Digital One / Modern Banking Platform) : If your legacy infrastructure sits within a traditional core banking provider ecosystem like FIS, they offer specialized modernization tools, Code Connect APIs, and hybrid RPA/middleware options designed specifically to hook digital layers into existing core databases safely.
To help narrow down the best platform fit, could you share:
What specific legacy host or terminal types you are targeting (e.g., IBM AS/400, mainframes, thick-client Windows apps)?
Whether you prefer a cloud-managed or strictly on-premises deployment due to compliance?
