SAP Intelligent RPA Licensing Guide

Executive Summary

SAP Intelligent RPA (iRPA) was officially discontinued on January 31, 2023, marking the end of a significant era in SAP's automation portfolio. All active iRPA licenses entered a sunset period, and SAP consolidated its automation capabilities into a single, more powerful platform: SAP Build Process Automation.

For enterprises still operating iRPA workloads or considering migration to SAP's cloud strategy (RISE with SAP or S/4HANA Cloud), understanding the licensing implications is critical. The transition from iRPA to Build Process Automation introduces a fundamentally different cost model—one based on consumption of Business Technology Platform (BTP) Credits rather than concurrent sessions. This shift has caught many organizations off-guard during migration planning, resulting in unexpected cost overruns when automation workloads consume credits at rates that exceed RISE starter allocations.

This guide provides a complete overview of iRPA licensing history, the Build Process Automation alternative, BTP credit mechanics, and strategic recommendations for enterprises navigating this transition.

What Was SAP Intelligent RPA?

SAP Intelligent RPA was a cloud-native robotic process automation (RPA) platform acquired by SAP and integrated into its portfolio around 2018–2019. It enabled enterprises to automate repetitive, rule-based business processes across SAP and non-SAP systems without requiring code modifications.

Key features included:

• Visual bot design with drag-and-drop automation builder
• Desktop and web application automation
• Cloud-based execution on SAP's infrastructure
• Integration with SAP ERP, SuccessFactors, Concur, Ariba, and third-party systems
• Process mining and analytics capabilities
• Enterprise governance and bot lifecycle management

iRPA was popular with enterprises seeking to reduce manual effort in order-to-cash, procure-to-pay, and hire-to-retire processes. It filled a gap between simple workflow automation and complex ERP customization, and offered an alternative to competing RPA platforms like UiPath and Automation Anywhere.

The Discontinuation: Why SAP Retired iRPA

SAP's decision to discontinue iRPA was driven by strategic consolidation. The company recognized that maintaining two separate automation platforms—iRPA and Workflow Management—was redundant. Rather than compete with best-of-breed RPA vendors, SAP chose to:

• Merge Workflow Management and iRPA capabilities into a single platform
• Add generative AI and process intelligence features
• Align automation pricing with BTP credit consumption model (enabling better cost transparency)
• Simplify the enterprise automation story for cloud-native deployments

The result: SAP Build Process Automation, which launched in 2022 and became the primary automation offering.

SAP iRPA Pricing Structure (Historical)

To understand the transition, it's important to know how iRPA was priced:

• Concurrent Session Licensing: ~$592/month per concurrent session. A concurrent session represented one bot actively executing automation at any given time. Enterprises purchased sessions based on peak parallel automation demand.
• Subscription vs. CPEA vs. RISE Credits: Customers could purchase iRPA via annual cloud subscription, SAP Cloud Platform Enterprise Agreement (CPEA), or included in RISE with SAP cloud credits.
• Professional Services: Onboarding, bot development, and integration work were typically billed separately.

Example: A company running 5 concurrent bots would license 5 sessions at ~$592/month each = ~$3,550/month (or ~$42,600/year).

This model was straightforward but became complex during migrations because session count didn't scale efficiently with process complexity or execution frequency. A single bot running 1,000 iterations per day still counted as one concurrent session.

Introducing SAP Build Process Automation

SAP Build Process Automation (BPA) consolidates three capabilities:

• Robotic Process Automation (bot execution, desktop automation)
• Workflow Management (human approval workflows, process orchestration)
• AI Capabilities (process mining, intelligent document processing)

BPA runs on SAP Business Technology Platform (BTP) and is available in two primary deployment contexts:

1. Cloud Deployments (RISE with SAP, S/4HANA Cloud, SuccessFactors): Included or available as an add-on with BTP credit consumption
2. SAP Business ByDesign: RPA automation now included in standard subscription at no additional cost

Build Process Automation Pricing Model

Unlike iRPA's session-based model, BPA pricing is consumption-based and measured in BTP Credits.

• Credit Exchange Rate: €1 = 1 BTP Credit (fixed, globally)
• Consumption per Automation: Depends on bot runtime, action complexity, and integration calls. Typical automation workloads consume 500–5,000 credits per month depending on process complexity and execution frequency.
• Procurement Models:
  • Direct BTP Credit purchase (for non-RISE customers)
  • Included in RISE with SAP starter allocation (4,000–16,000 credits per deal)
  • Bundled in SuccessFactors, Concur, or other cloud solution subscriptions

The consumption-based model offers flexibility but introduces cost variability that many enterprises underestimate during planning.

The Hidden Cost Issue: RISE Starter Credits and Overage

This is where migration complexity peaks. When SAP migrated customers from iRPA to Build Process Automation, many discovered their automation workloads consumed BTP Credits at rates that significantly exceeded their RISE starter allocation. SAP's transition messaging emphasized the feature improvements—not the consumption-based cost model that kicks in once starter credits are exhausted.

This scenario is not unique. Enterprises typically fall into one of two categories:

1. Under-provisioned RISE Deals: Teams negotiate RISE contracts without detailed automation consumption modeling. Starter credits get exhausted, and overages follow.
2. Over-licensed Legacy iRPA: Old session counts were inflated for safety. When migrated 1:1 to BPA, the automation footprint is larger than necessary, consuming more credits than expected.

The clear position: Any company with iRPA workloads migrating to S/4HANA or RISE must independently model BTP credit consumption for Build Process Automation BEFORE signing—the savings from sunsetting iRPA can be more than offset by BTP overages.

Understanding BTP Credit Consumption

To forecast Build Process Automation costs, enterprises must understand what drives credit consumption:

• Bot Runtime: The longer a bot executes, the more credits it consumes. A 10-minute automation costs more than a 1-minute automation.
• Action Complexity: Simple UI clicks cost fewer credits than API calls, database operations, or document processing.
• Frequency: Scheduling matters. 100 bots running daily will consume far more credits than 100 bots running monthly.
• Parallel Execution: Multiple bots running simultaneously increase credit burn.
• Third-Party Integrations: Calls to external APIs, SAP analytics cloud, or data warehouse systems incur additional costs.

SAP publishes rough consumption guidelines, but real-world rates vary significantly. A typical enterprise automation portfolio consumes 500–5,000 credits per month, depending on complexity and scale.

RISE with SAP: BTP Credit Allocation and Exhaustion Risk

RISE with SAP includes a starter allocation of BTP Credits—typically 4,000–16,000 credits per deal, based on SAP's standard model. This allocation covers:

• Build Process Automation (RPA + Workflow)
• SAP Analytics Cloud (limited)
• Data Intelligence (limited)
• Other BTP services (limited)

For enterprises with modest automation needs, the starter allocation is sufficient. However, for organizations with mature RPA programs or complex integration scenarios, the starter allocation exhausts quickly. Additional BTP Credits cost approximately €0.20–0.30 per credit when purchased at scale, depending on negotiated volume discounts.

The critical issue: RISE sales teams rarely challenge automation consumption forecasts during deal negotiation. If a customer claims they need "enough credits for automation," sales accepts the baseline. If actual consumption exceeds forecast, the customer pays overage at full published rates.

Migration Path: iRPA to Build Process Automation

SAP provided sunset support for existing iRPA customers, but migration is now mandatory. The recommended approach:

1. Audit Existing iRPA Workloads: Document all active bots, execution frequency, and runtime. Identify which automations still deliver ROI and which can be retired.
2. Model BTP Consumption: Use SAP's Build Process Automation calculator or engage SAP commercial advisory specialists to forecast credit consumption for the migrated bot portfolio.
3. Rationalize Workloads: Consolidate redundant bots, retire low-value automations, and optimize remaining bots for BPA (which may require code changes).
4. Plan RISE Credits: If purchasing or renegotiating RISE, build credit consumption into the contract. Request credits beyond starter allocation if needed, and negotiate volume discounts.
5. Migrate and Monitor: Execute migration in phases. Monitor actual credit consumption against forecast and adjust as needed.

Build Process Automation for SAP Business ByDesign

If you're operating SAP Business ByDesign (rather than S/4HANA or other SAP Cloud solutions), the RPA story is different. Build Process Automation is now included in the standard ByDesign subscription at no additional cost. This eliminates the BTP credit consumption concern and makes automation significantly more cost-effective.

For ByDesign customers, the decision is simpler: migrate from iRPA to the included Build Process Automation to reduce licensing costs and simplify contract administration.

Clean Core Strategy and BTP Deployment

SAP's Clean Core strategy emphasizes minimal customization of core ERP. Automations running in Build Process Automation on BTP (rather than built into ABAP code) qualify as side-by-side extensions—a compliant way to extend functionality without bloating the core system.

This architectural approach is favorable for compliance, maintenance, and upgrade cycles. However, it reinforces reliance on BTP Credits for ongoing operation. Enterprises should factor BPA operating costs into their multi-year Clean Core financial models.

Third-Party Support and Cost Optimization

SAP's support for Build Process Automation is included in cloud subscriptions, but implementation and optimization support often comes from SAP or partner professional services teams. Enterprises can realize cost savings of up to 50% by leveraging third-party advisory specialists to:

• Review existing automation workloads for consolidation opportunities
• Optimize bot designs to reduce BTP credit consumption
• Forecast and negotiate BTP credit allocations during RISE or S/4HANA Cloud contract renewal
• Identify opportunities to shift low-value automations to native workflow or other low-cost alternatives

Strategic Recommendations

Based on licensing and operational realities, here are best practices:

1. Audit Your iRPA Portfolio Now: If you still operate SAP Intelligent RPA, consolidate all bot metadata (runtime, frequency, creator, owner, business case). Identify decommissioning candidates.
2. Model BPA Costs Before Cloud Migration: Never sign a RISE or S/4HANA Cloud contract without detailed BTP credit consumption forecasts. Engage commercial advisory specialists to validate SAP's estimates.
3. Rationalize Before Migrating: Reduce iRPA workloads by 20–30% before migration to Build Process Automation. Retire low-ROI automations to reduce downstream BTP costs.
4. Negotiate BTP Credits at Deal Time: Request additional starter credits if your consumption forecast exceeds the standard allocation. Volume discounts are available at scale.
5. Monitor Consumption Post-Go-Live: Set up cost controls and dashboards to track BTP credit burn. Alert business owners when consumption deviates from forecast.
6. Plan for Maintenance Cycles: Remember that EHP 6-8 maintenance ends December 31, 2027. Budget upgrade and automation modernization efforts accordingly.

Conclusion

The transition from SAP Intelligent RPA to Build Process Automation represents both an opportunity and a risk. Opportunity, because Build Process Automation offers superior capabilities, including workflow orchestration and AI features, in a single platform. Risk, because the consumption-based pricing model can exceed budget if not carefully managed during migration planning.

Any organization with legacy iRPA workloads or planning automation as part of a cloud migration must treat BTP credit consumption as a primary cost driver—equal in importance to ERP licensing, cloud infrastructure, and professional services. Treat this transition strategically, not as a technology checklist, and you'll avoid the cost surprises that have caught competitors off-guard.