SAP Integration Suite Licensing: BTP-Based iPaaS Costs Explained for 2026

SAP Integration Suite is SAP's cloud-based integration platform as a service (iPaaS), built on SAP Business Technology Platform. It consolidates what was previously sold as separate products — SAP Cloud Platform Integration (CPI), API Management, Event Mesh, Integration Advisor, and Open Connectors — into a single, capability-pack-based commercial offering. The consolidation sounds like simplification. The reality is a SAP Integration Suite licensing model that is genuinely complex: message-based pricing that scales unpredictably with transaction volume, multiple capability packs that must be licenced separately even for basic scenarios, and a relationship with BTP service units that most organisations never fully model before contract signature.

This guide provides a forensic breakdown of SAP Integration Suite licensing for 2026 — how the message-based pricing model works, which capability packs are mandatory versus optional, how Integration Suite interacts with BTP credits, and the practical steps that consistently reduce SAP Integration Suite cost during procurement and renewal cycles. If you are planning a greenfield Integration Suite deployment or approaching an existing contract renewal, the cost traps described here will save you from the most common commercial mistakes.

What This Guide Covers

1. What SAP Integration Suite Is and How It Evolved
2. How Message-Based Pricing Works
3. Capability Packs — What You Need vs What SAP Sells
4. Integration Suite and BTP
5. What RISE with SAP Includes
6. Hidden Cost Drivers and SAP's Commercial Playbook
7. How to Negotiate Your Integration Suite Contract
8. FAQ

What SAP Integration Suite Is and How It Evolved

SAP Integration Suite replaces a set of individually licenced integration products that SAP built and acquired over two decades: SAP Process Integration (PI), SAP Process Orchestration (PO), SAP Cloud Platform Integration (CPI), Mashery API management, and others. The commercial rationale for bundling these capabilities into a single "suite" was compelling — enterprise integration landscapes require multiple patterns (batch, real-time API, event-driven, B2B EDI), and managing separate contracts for each was administratively burdensome.

The commercial outcome for buyers was less compelling. SAP used the suite repackaging to introduce capability-pack-based pricing that is far more granular than the old per-connection or per-server model. The result is that organisations now need to actively govern which Integration Suite capabilities they have licenced, which they are consuming, and whether their consumption patterns are approaching the limits of their committed volumes.

The transition from on-premise SAP Process Orchestration (PO) to Integration Suite is a live project for thousands of SAP ECC and S/4HANA customers in 2026. SAP has announced end of mainstream maintenance for Process Orchestration in 2027, creating migration urgency that SAP's commercial team actively exploits. Organisations migrating from PO should conduct an independent SAP contract negotiation review before accepting any Integration Suite proposal that is framed as a "migration uplift" — the commercial terms in these proposals are almost never optimal for the buyer.

How Message-Based Pricing Works

The core pricing unit for SAP Integration Suite's Cloud Integration capability is the message. SAP defines a message as a single data packet processed through an integration flow — an API call, a batch data transfer, an event triggered by an S/4HANA business object, or an EDI document exchange with a trading partner. Each message consumes from the monthly message quota committed in your contract.

This sounds straightforward until you measure actual integration volumes. A typical SAP S/4HANA enterprise with 20–30 active integration scenarios — order management, financial postings, logistics, master data replication — generates hundreds of thousands to millions of messages per month. High-frequency scenarios, such as real-time inventory updates or financial settlement events, can consume message quotas 10–20x faster than architecture teams estimated during procurement.

SAP sells Integration Suite message volumes in annual tiers, with pricing per thousand messages decreasing as committed volume increases. The published pricing ranges from approximately $0.10–$0.80 per 1,000 messages depending on tier, geography, and contract vintage. Actual transacted prices are lower, but the consumption model means that underestimating integration volume at contract time creates immediate overage risk.

Capability Packs — What You Need vs What SAP Sells

SAP Integration Suite is structured as a base platform with optional capability packs. Each pack enables specific integration patterns and carries separate licence fees. Understanding which packs your integration architecture genuinely requires — versus which SAP has included in a bundled proposal — is one of the most impactful commercial analyses you can conduct before signing.

Cloud Integration (Mandatory Base Capability)

The core integration flow designer and runtime. All Integration Suite contracts include this capability. Message volume commitment applies here. This is the product that replaces SAP Cloud Platform Integration (CPI) and is the foundation for all other packs.

API Management

Provides API gateway, developer portal, API analytics, and lifecycle management capabilities. Licenced separately based on API call volume and number of managed API endpoints. Organisations that expose SAP S/4HANA data via APIs to internal or external consumers need API Management. Organisations using only point-to-point integration scenarios between known systems can often defer or avoid API Management entirely — SAP's commercial team frequently bundles it as standard without challenging whether the use case warrants it.

Integration Advisor

Supports B2B mapping standards (EDIFACT, ANSI X12, HL7) and industry-specific integration content. Relevant for retail, healthcare, and manufacturing enterprises with extensive EDI trading partner communities. If your integration landscape is primarily SAP-to-SAP or SAP-to-Salesforce, Integration Advisor adds cost without value.

Event Mesh

SAP's cloud-native event broker, enabling asynchronous event-driven architectures between SAP applications and external systems. Licenced separately on an event volume basis. Critical for RISE with SAP and S/4HANA Cloud deployments where the standard integration pattern is event-driven (business events published from S/4HANA, consumed by downstream systems). Organisations on ECC or traditional S/4HANA landscapes with synchronous integration requirements may not need Event Mesh for initial deployments.

Open Connectors

Pre-built connectors for over 170 third-party SaaS applications (Salesforce, ServiceNow, Workday, Marketo, etc.). Reduces custom integration development effort significantly for multi-cloud landscapes. Licenced per connector or as bundles. Relevant for organisations with diverse SaaS ecosystems; less relevant for SAP-centric or limited-SaaS environments.

Trading Partner Management

Manages B2B trading partner onboarding, agreement management, and compliance monitoring. Relevant for organisations with large EDI trading partner communities (retail, CPG, manufacturing, pharmaceuticals). Often bundled with Integration Advisor in commercial proposals for B2B-heavy industries.

The commercial insight: SAP's Integration Suite proposals routinely include all six capability packs in a "complete suite" commercial structure. Request itemised pack pricing for every capability, then evaluate each against your current integration architecture and a 12-month integration roadmap. Eliminate packs without a documented use case in the first contract year. You can always add packs in Year 2 once business cases are validated. Our SAP licence optimisation service includes this capability pack rationalisation analysis as a standard component of Integration Suite reviews.

Integration Suite and BTP

SAP Integration Suite is a BTP service. This creates a relationship between Integration Suite licence fees and BTP service unit (BTPSU) consumption that is important to understand before signing either contract. Our detailed SAP BTP licensing guide covers the BTPSU model comprehensively — the short version relevant to Integration Suite is this: some Integration Suite workloads consume BTPSUs from your BTP capacity pool, depending on how your contract is structured and which infrastructure resources are invoked.

In the current Integration Suite commercial model, most customers pay a subscription-based fee for the Integration Suite capability packs and message volumes, with BTP infrastructure costs either included in the Integration Suite subscription or separately metered from a BTPSU pool. SAP's contract language on this point is deliberately ambiguous, and the resolution matters: if Integration Suite workloads consume from your BTPSU pool, they reduce the capacity available for other BTP services (extension development, automation, Analytics Cloud, Datasphere). If Integration Suite has dedicated infrastructure included in its subscription, there is no BTPSU conflict.

Before finalising any Integration Suite contract, request explicit written confirmation from SAP about whether Integration Suite capability pack consumption draws from your BTP credit or service unit pool. If it does, the BTPSU consumption model needs to be incorporated into your total BTP capacity modelling.

What RISE with SAP Includes

RISE with SAP includes a baseline Integration Suite allocation as part of the standard package. The baseline typically covers Cloud Integration with a message volume allotment sized for SAP-to-SAP integrations within the RISE tenant. This allocation is deliberately minimal — sufficient to connect RISE infrastructure components to each other, but not sufficient for enterprise-grade integration landscapes with dozens of integration scenarios and multiple third-party systems.

SAP's RISE sales process routinely presents this baseline inclusion as "integration included," implying that Integration Suite costs are covered. In practice, organisations running more than 10–15 active integration scenarios, or integrating with more than 5–6 external systems, will exceed the RISE baseline within 6–12 months of deployment. The result is an incremental Integration Suite licence purchase that adds significant cost to the RISE total contract value — and that SAP's account team knew would be needed at contract signature but did not surface explicitly.

Our analysis of RISE with SAP hidden costs identifies Integration Suite capacity as one of the three most common sources of post-signature cost surprises. Before signing any RISE proposal, demand a documented Integration Suite sizing that maps your planned integration scenarios to message volumes and confirms whether additional Integration Suite capacity is required beyond the RISE baseline. See also our RISE with SAP advisory service for comprehensive pre-signature commercial review.

Hidden Cost Drivers and SAP's Commercial Playbook

SAP Integration Suite contracts contain several cost patterns that surface only after deployment is underway. These are not accidents — they are structural features of how SAP prices integration that favour SAP's revenue position over buyer cost predictability.

Migration from SAP Process Orchestration: The "Migration Discount" That Isn't

SAP offers "migration incentives" to customers transitioning from on-premise SAP PI/PO to cloud-based Integration Suite. These incentives are typically structured as multi-year discounts applied to the new Integration Suite contract, offset by the requirement to commit to substantially higher message volumes than your current on-premise integration landscape would suggest. The net effect: the "discount" is consumed by inflated volume commitments, and the customer pays more in Year 1 than a well-negotiated commercial conversion would deliver. Challenge every migration discount by modelling actual message volumes from your PO landscape before accepting the commercial terms.

Premium Edition vs Standard Edition

SAP offers Integration Suite in Standard and Premium editions, with the Premium edition adding disaster recovery, enhanced SLAs, and additional runtime capacity. SAP's sales team defaults to proposing Premium edition. For most integration workloads, Standard edition provides adequate performance and resilience. The Premium uplift is typically 25–40% above Standard pricing — a significant cost difference that warrants explicit evaluation. Unless your integration landscape includes mission-critical, zero-downtime scenarios where the Premium SLA translates directly to measurable business risk reduction, Standard edition is almost always sufficient.

Third-Party Connector Costs Outside Open Connectors

Integration Suite's Open Connectors capability covers 170+ pre-built SaaS connectors, but not all third-party integration needs are covered. Custom connector development, SAP partner-delivered connectors, and integration with legacy on-premise systems may require additional BTP resources (development accounts, build tools, pipeline capacity) that are not included in the Integration Suite subscription. These costs appear as BTP line items on invoices that procurement teams often struggle to attribute back to the Integration Suite programme.

Integration Content Hub Subscriptions

SAP provides pre-built integration content (iFlows) for common integration scenarios via the SAP Integration Content Hub. Access to this content is included in the Integration Suite subscription, but third-party content from SAP partners may carry additional fees. Organisations that purchase integration content from SAP's ecosystem partners should account for these costs separately from the core Integration Suite licence.

How to Negotiate Your Integration Suite Contract

SAP Integration Suite negotiations are structurally similar to other SAP cloud product negotiations, with one critical difference: message volume modelling is both the most important commercial variable and the one most organisations get wrong. Here is the negotiation framework that delivers results.

Step 1: Build a Message Volume Model from Production Data

If migrating from SAP Process Orchestration, extract 12 months of message processing data from your SAP PO landscape. Count messages by scenario, by month, and identify your three highest-volume months. If deploying greenfield, model message volumes by scenario type using the integration pattern volume tables in this guide as a reference. Never accept SAP's architecture team's volume estimate without independently validating it against your actual business transaction volumes.

Step 2: Challenge Capability Pack Bundling

Request itemised pricing for each capability pack. Evaluate each pack against your 12-month integration roadmap. Remove any pack without a committed use case from the initial contract scope. You can add capability packs at any renewal cycle — removing them from the base contract is far harder once initial commitments are made. Our SAP licence optimisation team runs this analysis for every Integration Suite client engagement.

Step 3: Introduce Competitive Alternatives

The enterprise iPaaS market is competitive. MuleSoft (Salesforce), Azure Integration Services, Google Cloud Apigee, Boomi, and Workato all compete for the integration scenarios that SAP Integration Suite serves — including SAP-native integration scenarios. Obtaining a commercial proposal from one of these alternatives creates direct negotiation pressure. SAP's commercial team has significant discount authority for Integration Suite in competitive situations — up to 40–60% of list price in some documented cases. Presenting a credible alternative is the single most effective lever available to Integration Suite buyers.

Step 4: Negotiate Standard Edition Unless Premium is Genuinely Justified

Request that SAP document the specific operational benefits of Premium edition that apply to your integration landscape. If the primary driver is disaster recovery, evaluate whether the Premium uptime SLA improvement from 99.5% to 99.9% translates to quantifiable business value that exceeds the Premium licence premium. In most enterprise integration landscapes, it does not.

Step 5: Secure RISE Integration Suite Sizing in Writing

If RISE is part of the commercial package, obtain written confirmation of exactly how many Integration Suite messages are included in your RISE subscription, which capability packs are included, and what the commercial terms are for additional Integration Suite capacity beyond the RISE baseline. This documentation should be an addendum to the RISE Order Form, not a verbal confirmation from the account team. The SAP contract negotiation experts at SAP Licensing Experts review this documentation as a standard pre-signature checklist item.

FAQ — SAP Integration Suite Licensing