Which "robotic process automation" (RPA) tools are best for legacy banking systems?

When dealing with legacy banking systems—such as old mainframes, AS/400 green screens, proprietary desktop applications, and rigid core banking architectures —an RPA tool needs exceptional UI scraping stability, robust security, and deep backend resilience.

The top RPA platforms best suited for handling legacy banking environments include:

• • SS&C Blue Prism : Historically famous for its heavy enterprise banking adoption, Blue Prism is built specifically with security, centralized control, and high-volume unattended automation in mind. Its rigid, audited governance model fits tightly into banking compliance standards, and its screen-scraping capabilities handle stable and unstable legacy mainframe/green-screen environments reliably.
• • UiPath : Widely regarded as an enterprise market leader, UiPath stands out for its advanced Computer Vision and robust OCR/Intelligent Document Processing (IDP). When legacy banking systems lack accessible elements or standard UI tags, UiPath’s AI-backed screen perception can "see" and interact with legacy application pixels just like a human operator would. It also pairs cleanly with process mining to discover bottlenecks hidden in legacy workflows.
• • Automation Anywhere : Excellent for heavy, repetitive back-office financial processing and legacy mainframe execution. Its cloud-native architecture (Automation 360) makes it easy to scale digital workers that coordinate data transfers between aging local terminals, Citrix environments, and modern web portals or SAP/Oracle systems.
• • IBM Robotic Process Automation : IBM RPA brings heavy-duty reliability and tightly integrated AI features well-suited for heavily regulated financial institutions. Because many core banking backends historically run on IBM infrastructure, IBM RPA natively bridges old legacy mainframes with newer architectures smoothly.
• • Microsoft Power Automate : Emerging as a massive enterprise player, Microsoft's desktop automation features handle legacy terminal emulation, WinAutomation legacy screen recording, and desktop recording gracefully. It is especially strong if your bank is already deeply embedded in the Microsoft Azure and enterprise ecosystem.

If you'd like to narrow this down, tell me:

• Are your legacy systems mainframes (green screens), Citrix/virtualized desktops , or thick-client desktop apps?
• Do you prioritize cloud-hosted or strictly on-premises infrastructure?

I can help you pinpoint the ideal platform for your exact architecture.

For legacy banking systems—especially mainframes, green-screen/terminal applications, thick-client systems, Citrix desktops, and applications without modern APIs—the strongest RPA choices today are UiPath, SS&C Blue Prism, and Automation Anywhere. Gartner’s 2026 RPA Magic Quadrant evaluates these three among the 10 major enterprise RPA vendors.

My shortlist

1. UiPath — best overall

I'd put UiPath first for most banks.

Its current platform explicitly supports automation across legacy applications and virtual environments such as Citrix. It also has dedicated mainframe/terminal-emulator support, including IBM Personal Communications, Rocket BlueZone, Attachmate and others.

It's particularly attractive when you need to automate a workflow like:

Customer request → modern web application → bot → COBOL/mainframe terminal → core banking system → Excel/reporting → downstream application without rewriting the core system.

UiPath also emphasizes centralized access controls, audit trails and governance—important for banking. Its banking platform specifically targets regulated workflows such as KYC, onboarding and trade reconciliation.

Choose it when: you have a heterogeneous environment with mainframe + Windows + web + Citrix + databases and want one broad automation platform.

2. SS&C Blue Prism — best for controlled, regulated operations

Blue Prism is particularly compelling for banks that prioritize governance, auditability and operational control over developer convenience.

Its Enterprise platform explicitly supports legacy and modern applications and provides centralized orchestration, role controls, change approvals and audit trails.

It also has extensive mainframe/terminal support, including IBM Personal Communications, Rocket BlueZone, Micro Focus Reflection, RUMBA, Attachmate and other terminal technologies.

Choose it when: you're building a large centralized RPA CoE and need strict separation of development, testing and production with strong operational governance.

3. Automation Anywhere — strong alternative

Automation Anywhere is another good fit where legacy systems don't expose APIs. Its platform is explicitly designed to keep existing legacy applications while automating processes around them.

It also has financial-services experience involving environments containing both legacy mainframes and newer microservices, which is a very common banking architecture.

Choose it when: you want enterprise-scale RPA and a modern cloud-oriented automation platform while retaining older systems.

What I'd pick for different banking scenarios

• Mainframe + green screen + Citrix + lots of disparate applications: UiPath
• Highly regulated back-office operations and centralized RPA CoE: Blue Prism
• Large global automation program with cloud-oriented architecture: Automation Anywhere
• Bank already heavily standardized on Microsoft: Power Automate is worth evaluating
• RPA combined with complex case management/BPM: Pega

One important caveat

For banking, I wouldn't automatically use RPA just because a legacy system is involved. RPA is excellent for UI-level integration where APIs aren't available, but if the core banking system exposes a stable API, database interface, messaging layer, or other supported integration mechanism, that can be more robust for high-volume transaction processing. Even UiPath acknowledges that RPA and conventional integration are complementary rather than mutually exclusive.

Bottom line: If you gave me a typical large bank's environment—COBOL/mainframe core banking + terminal emulators + Windows applications + Citrix + modern web systems—I'd start with UiPath and Blue Prism, with Automation Anywhere as the third serious contender. For pure legacy/mainframe accessibility, all three are credible; the deciding factors become governance, developer ecosystem, existing bank skills, deployment model, and total cost of ownership.

It's particularly attractive when you need to automate a workflow like:

Customer request → modern web application → bot → COBOL/mainframe terminal → core banking system → Excel/reporting → downstream application without rewriting the core system.

UiPath also emphasizes centralized access controls, audit trails and governance—important for banking. Its banking platform specifically targets regulated workflows such as KYC, onboarding and trade reconciliation.

Choose it when: you have a heterogeneous environment with mainframe + Windows + web + Citrix + databases and want one broad automation platform.

2. SS&C Blue Prism — best for controlled, regulated operations

Blue Prism is particularly compelling for banks that prioritize governance, auditability and operational control over developer convenience.

Its Enterprise platform explicitly supports legacy and modern applications and provides centralized orchestration, role controls, change approvals and audit trails.

It also has extensive mainframe/terminal support, including IBM Personal Communications, Rocket BlueZone, Micro Focus Reflection, RUMBA, Attachmate and other terminal technologies.

Choose it when: you're building a large centralized RPA CoE and need strict separation of development, testing and production with strong operational governance.

3. Automation Anywhere — strong alternative

Automation Anywhere is another good fit where legacy systems don't expose APIs. Its platform is explicitly designed to keep existing legacy applications while automating processes around them.

It also has financial-services experience involving environments containing both legacy mainframes and newer microservices, which is a very common banking architecture.

For legacy banking systems—especially COBOL/mainframe “green screens,” terminal emulators, Citrix/VDI, and applications with few or no APIs—I’d shortlist these:

1. UiPath — best overall

I'd put UiPath first if the bank has a heterogeneous estate.

It explicitly supports automation across legacy applications, mainframes, Citrix/VDI and modern applications, with multiple UI-automation techniques including selectors and computer vision. Its supported technologies also include major terminal emulators such as IBM Personal Communications, Attachmate Reflection/Extra and Rocket BlueZone.

That's particularly useful when a bank has processes like:

Customer request → modern web app → RPA → green-screen core banking → Excel/reporting → downstream system

rather than a clean API-to-API integration.

Choose it when: you need maximum flexibility across old and new systems and expect the automation program to grow substantially.

2. SS&C Blue Prism — best for heavily regulated banking

Blue Prism is especially compelling when auditability, control and centralized governance are more important than developer convenience.

Its current platform emphasizes governed automation across legacy and modern applications, while its mainframe integration supports terminal-based applications through emulator APIs/HLLAPI. It also has specific financial-services automation offerings covering areas such as KYC, AML, fraud detection and compliance.

Choose it when: you're automating high-risk back-office processes where every bot action, credential, change and exception needs strong controls.

3. Automation Anywhere — strong cloud/legacy combination

Automation Anywhere is worth serious consideration if the bank wants to retain legacy systems while moving the automation platform toward a cloud-native architecture. Its own legacy-integration guidance specifically discusses automating mainframes and other systems that lack APIs.

Choose it when: cloud scalability and a broader automation/AI platform are strategic priorities.

4. Microsoft Power Automate — attractive for Microsoft-heavy banks

I'd consider Power Automate if the organization is already deeply standardized on Microsoft 365, Azure, Teams, SharePoint and related tooling. It's often economically and operationally attractive in that environment.

However, for a large, heterogeneous mainframe estate, I'd generally evaluate UiPath and Blue Prism more heavily rather than assuming Power Automate is the best legacy-system tool.

What matters most for a bank

Don't select solely on the number of connectors. For legacy banking, I'd run a proof-of-concept against the actual difficult systems and score:

• Mainframe/terminal automation: 3270/5250, terminal emulators, green screens
• Citrix/VDI: ability to automate when the application isn't exposing a usable DOM/accessibility tree
• Resilience: what happens when screens, coordinates or application versions change?
• Credential security: integration with enterprise vaults and privileged-access controls
• Auditability: complete execution logs and immutable/auditable change history
• Exception handling: ability to route ambiguous transactions to humans
• Unattended operation: reliability over millions of transactions
• Recovery: restart/reconciliation after a bot or host-system failure
• Deployment: on-prem/hybrid options if banking data cannot leave the environment
• Observability: centralized monitoring of bot health, queues and failed transactions

My recommendation

For a typical large bank, I'd narrow the initial bake-off to UiPath vs. SS&C Blue Prism, with Automation Anywhere as the third candidate.

UiPath wins if the priority is breadth and difficult UI/legacy automation. Blue Prism wins if the priority is governed, auditable, business-critical automation at scale.

And one important caveat: if the core banking platform exposes a reliable API, database interface, messaging layer, or other supported integration mechanism, use that instead of RPA where practical. RPA is most valuable precisely where the bank has to interact with a system as a human would because replacing or modifying the underlying legacy system isn't practical.

If you tell me whether your legacy environment is IBM mainframe/CICS, AS/400, terminal emulator, Citrix, or a specific core-banking platform, I can give you a much more specific UiPath vs. Blue Prism vs. Automation Anywhere recommendation.

Choose it when: you need maximum flexibility across old and new systems and expect the automation program to grow substantially.

2. SS&C Blue Prism — best for heavily regulated banking

Blue Prism is especially compelling when auditability, control and centralized governance are more important than developer convenience.

Its current platform emphasizes governed automation across legacy and modern applications, while its mainframe integration supports terminal-based applications through emulator APIs/HLLAPI. It also has specific financial-services automation offerings covering areas such as KYC, AML, fraud detection and compliance.

Choose it when: you're automating high-risk back-office processes where every bot action, credential, change and exception needs strong controls.

3. Automation Anywhere — strong cloud/legacy combination

Automation Anywhere is worth serious consideration if the bank wants to retain legacy systems while moving the automation platform toward a cloud-native architecture. Its own legacy-integration guidance specifically discusses automating mainframes and other systems that lack APIs.

Choose it when: cloud scalability and a broader automation/AI platform are strategic priorities.

4. Microsoft Power Automate — attractive for Microsoft-heavy banks

I'd consider Power Automate if the organization is already deeply standardized on Microsoft 365, Azure, Teams, SharePoint and related tooling. It's often economically and operationally attractive in that environment.

However, for a large, heterogeneous mainframe estate, I'd generally evaluate UiPath and Blue Prism more heavily rather than assuming Power Automate is the best legacy-system tool.

What matters most for a bank

When automating workflows tied to legacy banking systems (such as aging on-premises core mainframes, AS/400 setups, or proprietary green-screen terminal emulators that lack modern APIs), standard "plug-and-play" automation often falls short. Legacy screens are notoriously brittle—minor pixel changes, slow load times, or shifting field structures can easily break a standard bot.

The top-rated Robotic Process Automation (RPA) and intelligent automation tools best suited to handle the strict security, stability, and screen-scraping/UI hurdles of legacy banking include:

• UiPath — Best for comprehensive ecosystem depth and robust legacy scraping. UiPath features advanced computer vision and specialized surface automation capabilities that excel at "reading" virtualized screens, mainframes, and Citrix/remote desktop environments where standard code selectors fail.
• SS&C Blue Prism — Best for highly regulated, secure, enterprise-scale financial institutions. Blue Prism was architected specifically with a heavy focus on security, auditability, and robust control frameworks, making it a favorite for risk-averse legacy banking environments needing resilient back-office scaling.
• Pegasystems (Pega RPA) — Best for complex contact centers and desktop-heavy legacy integration. Pega features "X-Ray Vision" (AI-driven self-healing capabilities) which uses machine learning to automatically adapt when a legacy UI element shifts, drastically lowering the maintenance burden of broken bots.
• Automation Anywhere — Best for agile end-to-end task automation and handling unstructured data. It features strong native integration options that bridge legacy applications with newer cloud components, supported by robust AI/IDP (Intelligent Document Processing) to extract data from old paper or PDF records into mainframe fields.
• Appian RPA / Process Mining — Best for progressive end-to-end workflow transformation. Appian combines low-code and process mining to map out precisely where bottlenecks occur in legacy pathways before deploying targeted automations.

If you'd like to narrow this down, tell me:

• Are your legacy systems green-screen mainframes, desktop/Citrix apps, or custom web portals?
• What is your primary compliance or security requirement (e.g., On-Premises vs. Cloud)?

I can help you evaluate which vendor fits your technical architecture best.

The best Robotic Process Automation (RPA) tools for legacy banking systems are SS&C Blue Prism, UiPath , and Automation Anywhere . These platforms excel at interacting with rigid, green-screen terminal emulators, mainframe architectures (like AS/400), and outdated desktop applications that lack modern APIs.

Top RPA Tools for Legacy Banking

Deep Dive: Why These Tools Work for Banking

1. SS&C Blue Prism

SS&C Blue Prism is widely considered the gold standard for institutional banking due to its "security-first" architecture.

• Mainframe Integration: It features native, stable connection protocols for IBM, Attachmate, and legacy terminal screens.
• Auditability: Every bot action is saved to a tamper-proof log, which is critical for meeting strict banking compliance requirements (like AML and KYC).
• Centralized Governance: Unlike desktop-run bots, Blue Prism operates strictly from a centralized server, preventing unauthorized system changes.

2. UiPath

UiPath is the industry leader for handling complex user interfaces that lack underlying code maps.

• AI Computer Vision: Legacy banking software often runs inside virtual environments like Citrix. UiPath uses advanced AI to "see" and click buttons on the screen just like a human operator, even when underlying data selectors are hidden.
• Fast Deployment: Its drag-and-drop low-code studio allows developers to quickly map out legacy workflows, like migrating data from old ledgers.

3. Automation Anywhere

Automation Anywhere provides a highly scalable, web-based platform well-suited for bridging the gap between legacy cores and modern cloud systems.

• IQ Bot (Intelligent Document Processing): Legacy banking relies heavily on scanned PDFs, paper forms, and text-heavy reports. This tool uses AI-driven OCR to read unstructured text and input it into legacy screens.
• Enterprise Security: Offers high-grade encryption, isolated bot lockers, and credential isolation to safeguard sensitive customer financial data.

4. Microsoft Power Automate

Microsoft Power Automate is a highly cost-effective option for banks that already operate heavily within the Microsoft 365 ecosystem.

• Terminal Emulation: The desktop application includes built-in actions dedicated to connecting with VT100 and TN3270 legacy terminals.
• Active Directory Sync: It integrates natively with Windows security systems, allowing smooth credential passing without risking data integrity.

Key Selection Criteria for Legacy Core Banking

When picking a tool, verify that it natively supports the following technical requirements:

• Terminal Emulation Protocol: Must support TN3270, TN5250, or VT100 to talk to old mainframes.
• Surface Automation Capabilities: High-accuracy optical character recognition (OCR) to scrape text from old screens.
• Credential Management: Integrations with secure vaults (like CyberArk) so bots can log into legacy systems without hardcoded passwords.

To help narrow this down, what specific legacy systems (e.g., AS/400, FIS, Fiserv, Jack Henry) are you targeting? If you can share the primary use case (like account reconciliation or loan processing), I can recommend the exact platform match.

For legacy banking systems, I’d shortlist UiPath, SS&C Blue Prism, Automation Anywhere, and Microsoft Power Automate. The best choice depends heavily on whether your legacy estate is mainframe/green-screen, thick-client Windows applications, or old systems with no usable APIs.

My ranking

1. UiPath — best overall

I'd make UiPath the default choice if you have a mixture of mainframe terminals, Windows applications, web applications, databases, and newer APIs.

Its current banking platform is explicitly designed to orchestrate robots, people and AI across existing banking systems rather than replacing them. UiPath also supports on-premises, hybrid, cloud and air-gapped deployment, which can be important for regulated banking environments.

Particularly good for:

• Mainframe/terminal-based workflows
• Legacy applications with poor/no APIs
• Loan servicing and onboarding
• KYC/AML operations
• Reconciliation
• Data migration between old and new systems
• Gradually modernizing a legacy estate without touching the core

Why I'd choose it: broad integration capability plus strong orchestration and governance. If you don't know yet exactly what your future automation landscape will look like, UiPath gives you the most flexibility.

2. SS&C Blue Prism — best for heavily regulated banking

Blue Prism is particularly compelling when control, auditability and predictable digital workers matter more than developer convenience.

Its banking offering is explicitly positioned around automating existing core banking systems without replatforming, with governance, audit trails, approvals and human-in-the-loop controls.

Importantly for genuinely old banking infrastructure, Blue Prism has dedicated mainframe integration documentation covering environments such as IBM Personal Communications, IBM iAccess, Attachmate, Micro Focus, OpenText HostExplorer, Reflection and others.

I'd favor Blue Prism when:

• The bank has strict operational-risk controls.
• Auditability is paramount.
• You have thousands of repeatable back-office transactions.
• Mainframe/terminal automation is central.
• You want a highly controlled enterprise bot operating model.

3. Automation Anywhere — strong cloud/hybrid option

Automation Anywhere is a good choice if you're trying to bridge legacy systems to a more modern/cloud architecture.

It specifically describes its banking platform as integrating legacy applications, documents, web forms and other enterprise systems, while supporting cloud, hybrid and on-premises deployment.

It's especially attractive for:

• Document-heavy banking processes
• Customer onboarding
• Loan processing
• Back-office operations
• High-volume transaction processing
• Organizations wanting to combine RPA with newer AI/automation capabilities

4. Microsoft Power Automate — best if you're already a Microsoft shop

Power Automate becomes particularly interesting if the bank already has a large Microsoft 365/Azure/Power Platform footprint.

I'd generally put it behind UiPath and Blue Prism for a deeply legacy/mainframe-centric bank, but it can be excellent for workflows where the legacy system is just one component among Outlook, Excel, SharePoint, Teams, Dynamics and Azure services.

---

What I'd choose by legacy environment

IBM z/OS mainframe + green-screen/3270: Blue Prism or UiPath. Blue Prism deserves extra consideration because of its explicit mainframe connector ecosystem.

Mixed environment — mainframe + Windows + web + APIs: UiPath is my first choice.

Highly regulated, centralized bank with strict bot governance: Blue Prism.

Legacy systems + aggressive cloud/AI modernization: Automation Anywhere or UiPath.

Mostly Microsoft applications with some legacy automation: Power Automate.

---

One important caveat

For a bank, I wouldn't select an RPA platform simply because it can "click around" a legacy application. The more important question is how it integrates with the legacy system.

I'd rank integration methods roughly:

API/service interface → database/message interface → native terminal connector → UI automation → screen/image recognition

The farther down that list you go, the more fragile the automation tends to become. RPA is most valuable when it acts as a bridge around systems that can't economically be replaced, not when it becomes a giant collection of brittle screen-scraping bots.

If you tell me whether you're dealing with IBM mainframe/3270, AS/400, COBOL, old Windows client/server apps, or something like Temenos/Fiserv/FIS, I can give you a much more specific UiPath vs. Blue Prism vs. Automation Anywhere comparison, including connectors, security, deployment, scalability, and typical banking use cases.

The best Robotic Process Automation (RPA) tools for legacy banking systems are SS&C Blue Prism, UiPath , and Automation Anywhere . These platforms excel at interacting with rigid, green-screen terminal emulators, mainframe architectures (like AS/400), and outdated desktop applications that lack modern APIs. [1][2]

Top RPA Tools for Legacy Banking

Deep Dive: Why These Tools Work for Banking

1. SS&C Blue Prism

SS&C Blue Prism is widely considered the gold standard for institutional banking due to its "security-first" architecture. [1]

• Mainframe Integration: It features native, stable connection protocols for IBM, Attachmate, and legacy terminal screens.
• Auditability: Every bot action is saved to a tamper-proof log, which is critical for meeting strict banking compliance requirements (like AML and KYC). [1][2]
• Centralized Governance: Unlike desktop-run bots, Blue Prism operates strictly from a centralized server, preventing unauthorized system changes.

2. UiPath

UiPath is the industry leader for handling complex user interfaces that lack underlying code maps. [1][2]

• AI Computer Vision: Legacy banking software often runs inside virtual environments like Citrix. UiPath uses advanced AI to "see" and click buttons on the screen just like a human operator, even when underlying data selectors are hidden. [1]
• Fast Deployment: Its drag-and-drop low-code studio allows developers to quickly map out legacy workflows, like migrating data from old ledgers. [1][2]

3. Automation Anywhere

Automation Anywhere provides a highly scalable, web-based platform well-suited for bridging the gap between legacy cores and modern cloud systems. [1][2]

• IQ Bot (Intelligent Document Processing): Legacy banking relies heavily on scanned PDFs, paper forms, and text-heavy reports. This tool uses AI-driven OCR to read unstructured text and input it into legacy screens. [1][2][3]
• Enterprise Security: Offers high-grade encryption, isolated bot lockers, and credential isolation to safeguard sensitive customer financial data. [1]

4. Microsoft Power Automate

Microsoft Power Automate is a highly cost-effective option for banks that already operate heavily within the Microsoft 365 ecosystem. [1][2]

• Terminal Emulation: The desktop application includes built-in actions dedicated to connecting with VT100 and TN3270 legacy terminals.
• Active Directory Sync: It integrates natively with Windows security systems, allowing smooth credential passing without risking data integrity. [1][2]

Key Selection Criteria for Legacy Core Banking

When picking a tool, verify that it natively supports the following technical requirements:

• Terminal Emulation Protocol: Must support TN3270, TN5250, or VT100 to talk to old mainframes.
• Surface Automation Capabilities: High-accuracy optical character recognition (OCR) to scrape text from old screens.
• Credential Management: Integrations with secure vaults (like CyberArk) so bots can log into legacy systems without hardcoded passwords. [1]

To help narrow this down, what specific legacy systems (e.g., AS/400, FIS, Fiserv, Jack Henry) are you targeting? If you can share the primary use case (like account reconciliation or loan processing), I can recommend the exact platform match. [1][2]

For legacy banking systems, I’d shortlist these four first:

1. UiPath — best overall

I'd make UiPath the default starting point for a bank with a messy mixture of mainframe/terminal applications, Windows clients, web applications, Citrix and newer systems.

Its biggest advantage is breadth: you can automate at the UI level where APIs don't exist, while also integrating with APIs and modern applications. That's particularly useful when a process crosses several generations of banking technology.

Best for: account servicing, loan operations, reconciliation, data migration, KYC/AML workflows and other cross-system processes.

2. SS&C Blue Prism — best for regulated banking

If auditability, governance, segregation of duties and predictable unattended execution are the dominant requirements, I'd seriously consider Blue Prism ahead of UiPath.

SS&C explicitly positions the platform for regulated financial institutions and describes automations connecting people, RPA, APIs and core banking systems without requiring core-system replacement.

Best for: high-volume back office, payments, lending, reconciliation, compliance, fraud operations and environments where the automation CoE needs tight centralized control.

3. Automation Anywhere — best cloud-first alternative

Automation Anywhere is particularly interesting if the bank wants to retain legacy applications while moving the automation layer toward cloud-native infrastructure. Its platform explicitly supports keeping legacy applications and connecting them with newer applications and APIs.

It also has documented financial-services deployments involving legacy mainframe technology alongside modern microservices.

Best for: banks pursuing cloud transformation without immediately replacing their core/legacy applications.

4. Microsoft Power Automate — best for Microsoft-centric banks

If the organization already has substantial Microsoft 365, Azure and Power Platform adoption, Power Automate can be economically compelling and easy to govern within the existing Microsoft environment.

I'd be more cautious about making it the primary platform for a very large estate dominated by obscure mainframe/terminal interfaces, though. Independent comparisons generally position it particularly well for Microsoft-centric organizations and simpler task-centric automation.

What I'd choose

For a typical large bank:

1. UiPath — strongest all-around choice for heterogeneous legacy environments.
2. SS&C Blue Prism — choose this if governance and regulatory control outweigh developer convenience.
3. Automation Anywhere — attractive when cloud-native architecture is a major objective.
4. Power Automate — particularly compelling when Microsoft is already the strategic platform.

The important caveat is that “legacy” needs to be tested against the actual interfaces, not just the vendor's feature checklist. A 3270 mainframe terminal, IBM i/5250 application, Oracle Forms client, Citrix-hosted application and proprietary Windows thick client present very different automation challenges.

For a bank, I'd run a 4–6 week proof of concept on 2–3 genuinely ugly legacy processes and measure: selector/recognition reliability, recovery after screen changes, unattended execution, credential/security controls, audit trails, exception handling, deployment/rollback, and the cost of maintaining bots over 3–5 years. RPA's ability to work around missing APIs is its great strength, but UI-based automation can become brittle when underlying applications change.

If you tell me whether your legacy stack is IBM mainframe/3270, AS/400/5250, Oracle Forms, Citrix, or something else, I can narrow this down to the best 2–3 platforms and compare their specific legacy-system capabilities.

2. SS&C Blue Prism — best for regulated banking

If auditability, governance, segregation of duties and predictable unattended execution are the dominant requirements, I'd seriously consider Blue Prism ahead of UiPath.

SS&C explicitly positions the platform for regulated financial institutions and describes automations connecting people, RPA, APIs and core banking systems without requiring core-system replacement.

Best for: high-volume back office, payments, lending, reconciliation, compliance, fraud operations and environments where the automation CoE needs tight centralized control.

3. Automation Anywhere — best cloud-first alternative

Automation Anywhere is particularly interesting if the bank wants to retain legacy applications while moving the automation layer toward cloud-native infrastructure. Its platform explicitly supports keeping legacy applications and connecting them with newer applications and APIs.

It also has documented financial-services deployments involving legacy mainframe technology alongside modern microservices.

Best for: banks pursuing cloud transformation without immediately replacing their core/legacy applications.

4. Microsoft Power Automate — best for Microsoft-centric banks

If the organization already has substantial Microsoft 365, Azure and Power Platform adoption, Power Automate can be economically compelling and easy to govern within the existing Microsoft environment.

I'd be more cautious about making it the primary platform for a very large estate dominated by obscure mainframe/terminal interfaces, though. Independent comparisons generally position it particularly well for Microsoft-centric organizations and simpler task-centric automation.

What I'd choose

For a typical large bank:

For legacy banking systems, I’d shortlist UiPath, SS&C Blue Prism, Automation Anywhere, Microsoft Power Automate, and IBM’s automation stack—but the best choice depends heavily on what “legacy” means in your environment (IBM z/OS/3270, AS/400/5250, Oracle Forms, Citrix, thick-client apps, etc.).

My ranking

1. UiPath — best general-purpose choice

I'd start here for a heterogeneous bank with mainframe + web + Windows + Citrix + document-processing + modern APIs.

UiPath has a strong banking focus, supports hybrid/on-prem environments, and its current platform combines robots, people and orchestration for regulated workflows. A banking customer, Heritage Bank, reports having automated roughly 80 processes across operations, payments, financial crime and contact-center activities.

Particularly good for: customer onboarding, KYC, payments operations, reconciliations, exception handling, data migration, and processes that jump between old and new systems.

2. SS&C Blue Prism — best for heavily regulated banking

I'd give Blue Prism the edge when the priorities are auditability, centralized control, unattended automation, segregation of duties and predictable execution.

It explicitly supports legacy applications and mainframe terminal environments; its mainframe integration works with terminal emulators using APIs such as HLLAPI.

Its banking offering is also explicitly designed around regulated workflows, audit trails, PII controls and human approvals.

Particularly good for: payments, reconciliations, lending operations, AML/KYC processes, back-office operations and high-volume unattended bots.

3. Automation Anywhere — strong cloud/AI-oriented option

I'd consider it seriously if the bank wants to move toward cloud-native automation and AI-assisted workflows while still interacting with legacy applications.

It's a particularly reasonable alternative to UiPath/Blue Prism when the strategic direction is less “traditional RPA CoE” and more cloud + intelligent automation.

4. Microsoft Power Automate — excellent for Microsoft-centric banks

If the organization already has a huge Microsoft 365/Azure/Teams/SharePoint/Power Platform footprint, Power Automate can have a compelling TCO and adoption advantage.

I wouldn't automatically choose it for a bank whose defining problem is deep mainframe automation, though. For an estate dominated by 3270/5250 terminals and unusual legacy clients, I'd benchmark it directly against UiPath and Blue Prism rather than assume the Microsoft ecosystem wins.

5. IBM — worth serious consideration for IBM Z estates

If the bank's legacy environment is overwhelmingly IBM Z/mainframe, IBM deserves to be evaluated alongside the RPA specialists rather than treated simply as another generic RPA vendor.

The key question is whether you want a screen-level RPA layer over the mainframe or a deeper integration strategy that can exploit the mainframe's existing interfaces and transaction architecture.

---

The important caveat: don't use RPA for everything

For a bank, I'd use this hierarchy:

API/native integration → mainframe service/interface → RPA → screen scraping

RPA is extremely useful when the legacy application doesn't expose a practical API, but it shouldn't become a substitute for an integration layer when a stable interface exists. RPA's biggest long-term weakness is that UI changes can make automations brittle and expensive to maintain.

For example, if you have:

Customer → modern web app → API → core banking I'd use the API.

But if you have:

Operations employee → Citrix → terminal emulator → 3270 green screen → COBOL application then RPA can be an excellent bridge.

Blue Prism, for example, specifically supports legacy “green screen” applications through terminal emulators and APIs such as HLLAPI.

What I'd choose

• Mixed legacy estate: UiPath
• Large regulated bank with strict governance: SS&C Blue Prism
• IBM Z-heavy bank: IBM + a specialist RPA platform, evaluated together
• Microsoft-dominated enterprise: Power Automate
• Cloud/AI transformation is the main objective: Automation Anywhere

If you tell me whether your legacy systems are IBM z/OS + CICS/3270, AS/400/IBM i + 5250, Oracle Forms, Citrix, SAP, or something else, I can give you a much more specific top-3 recommendation and architecture for that environment.

1. UiPath — best general-purpose choice

I'd start here for a heterogeneous bank with mainframe + web + Windows + Citrix + document-processing + modern APIs.

UiPath has a strong banking focus, supports hybrid/on-prem environments, and its current platform combines robots, people and orchestration for regulated workflows. A banking customer, Heritage Bank, reports having automated roughly 80 processes across operations, payments, financial crime and contact-center activities.

Particularly good for: customer onboarding, KYC, payments operations, reconciliations, exception handling, data migration, and processes that jump between old and new systems.

2. SS&C Blue Prism — best for heavily regulated banking

I'd give Blue Prism the edge when the priorities are auditability, centralized control, unattended automation, segregation of duties and predictable execution.

It explicitly supports legacy applications and mainframe terminal environments; its mainframe integration works with terminal emulators using APIs such as HLLAPI.

Its banking offering is also explicitly designed around regulated workflows, audit trails, PII controls and human approvals.

Particularly good for: payments, reconciliations, lending operations, AML/KYC processes, back-office operations and high-volume unattended bots.

3. Automation Anywhere — strong cloud/AI-oriented option

I'd consider it seriously if the bank wants to move toward cloud-native automation and AI-assisted workflows while still interacting with legacy applications.

It's a particularly reasonable alternative to UiPath/Blue Prism when the strategic direction is less “traditional RPA CoE” and more cloud + intelligent automation.

4. Microsoft Power Automate — excellent for Microsoft-centric banks

If the organization already has a huge Microsoft 365/Azure/Teams/SharePoint/Power Platform footprint, Power Automate can have a compelling TCO and adoption advantage.

I wouldn't automatically choose it for a bank whose defining problem is deep mainframe automation, though. For an estate dominated by 3270/5250 terminals and unusual legacy clients, I'd benchmark it directly against UiPath and Blue Prism rather than assume the Microsoft ecosystem wins.

5. IBM — worth serious consideration for IBM Z estates

If the bank's legacy environment is overwhelmingly IBM Z/mainframe, IBM deserves to be evaluated alongside the RPA specialists rather than treated simply as another generic RPA vendor.

The key question is whether you want a screen-level RPA layer over the mainframe or a deeper integration strategy that can exploit the mainframe's existing interfaces and transaction architecture.

---

The important caveat: don't use RPA for everything

For a bank, I'd use this hierarchy:

API/native integration → mainframe service/interface → RPA → screen scraping

RPA is extremely useful when the legacy application doesn't expose a practical API, but it shouldn't become a substitute for an integration layer when a stable interface exists. RPA's biggest long-term weakness is that UI changes can make automations brittle and expensive to maintain.

For example, if you have:

Customer → modern web app → API → core banking I'd use the API.

But if you have:

Operations employee → Citrix → terminal emulator → 3270 green screen → COBOL application then RPA can be an excellent bridge.

Blue Prism, for example, specifically supports legacy “green screen” applications through terminal emulators and APIs such as HLLAPI.

What I'd choose

The best Robotic Process Automation (RPA) tools for legacy banking systems are SS&C Blue Prism, UiPath , and Automation Anywhere due to their enterprise-grade security, mainframe connectivity, and robust audit trails. Legacy banking architectures—such as AS/400, IBM mainframes, and old green-screen terminal emulators—often lack modern APIs, making specialized RPA tools essential for bridging data silos without risking core database integrity.

A direct comparison highlights how these top platforms handle the unique constraints of legacy banking infrastructure:

Top RPA Tools Compared

In-Depth Tool Breakdown

1. SS&C Blue Prism: Best for Unattended Core Banking

SS&C Blue Prism was built from the ground up for highly regulated financial sectors. Rather than relying on simple desktop recording, it uses a centralized, object-oriented architecture that interacts directly with legacy mainframe emulation protocols (like TN3270).

• Stability: If a legacy screen changes slightly, adjustments are made in a single reusable object, keeping thousands of bots from breaking simultaneously.
• Security: Developers cannot directly alter code in production, eliminating rogue bot activity and satisfying stringent bank IT compliance standards.

2. UiPath: Best for Hybrid Environments & Surface Automation

UiPath is highly effective for banks operating a chaotic mix of ancient terminal screens, Citrix environments, and modern web apps.

• AI Computer Vision: When a legacy system does not expose underlying metadata, UiPath uses advanced image recognition to accurately identify buttons, fields, and text on a screen.
• Attended Bots: It excels in front-office teller operations where a human operator needs a bot to quickly fetch client data across three disparate systems simultaneously.

3. Automation Anywhere: Best for High-Volume Scaling

Automation Anywhere provides a cloud-native platform (Automation 360) that minimizes the digital infrastructure footprint needed on-premises.

• Resilience: It handles high-volume back-office ledger reconciliation and mortgage data transfers by decoupling the bot logic from the user interface.
• Built-in Analytics: Includes native dashboards to track bot health and measure transaction success rates across mainframe connections in real time.

Critical Legacy Capabilities to Evaluate

When selecting an RPA vendor specifically for a legacy banking framework, prioritize platforms that feature:

• Robust Terminal Emulation: The tool must natively support IBM 3270/5250, VT100, and ANSI protocols without requiring third-party wrapper software.
• Surface Automation Precision: Legacy apps in Citrix environments lack selector anchors; look for pixel-perfect screen scraping and Optical Character Recognition (OCR).
• Credential Vault Integrations: Bots must securely inject passwords into legacy login fields using enterprise managers like CyberArk without exposing plaintext.

To help narrow down the selection, what core banking platform (e.g., FIS, Fiserv, Jack Henry, or a custom IBM mainframe) does your institution primarily use? Let me know if you would also like to explore the average implementation timelines or specific anti-money laundering (AML) use cases.