SAP Integration Suite (formerly CPI, Cloud Platform Integration) is central to modern SAP deployments, but its message-based pricing model and layered add-ons create significant cost surprises. Understanding the licensing tiers, API Management implications, and RISE entitlements is essential for controlling expenses and negotiating effectively.
SAP Integration Suite is SAP's unified cloud platform for middleware and integration services. It consolidates previously separate products — Cloud Platform Integration (CPI), Cloud Integration for Data Services, API Management, Integration Advisor, and Event Mesh — into a single commercial offering. Integration Suite is designed to support modern iPaaS (integration Platform-as-a-Service) integration patterns for SAP and non-SAP applications, cloud-to-cloud connectivity, and API-first integration architectures.
Integration Suite sits on top of SAP BTP (Business Technology Platform) and operates as a distinct licensing entity from BTP itself, though the two are technically and commercially linked. For organisations on S/4HANA or RISE, Integration Suite is not optional: it is the prescribed platform for system-to-system integration without modifying core SAP applications. Typical use cases include connecting S/4HANA to third-party applications, managing B2B partner integrations via EDI or other protocols, exposing enterprise APIs to external consumers, and event-driven real-time data synchronisation.
This guide is part of our comprehensive SAP license negotiation guide. For Integration Suite in the context of RISE, see our RISE with SAP review. For BTP context and credit mechanics, see our SAP BTP licensing guide.
SAP Integration Suite operates on a hybrid licensing model combining two core commercial mechanisms: message-based pricing for core integration functions, and capability-based add-on licensing for specialised features. The default model is message-based, where you purchase a certain volume of processed messages within a defined time period (typically one year). A "message" is a unit of data processed by the Integration Suite (typically a transaction, API call, or EDI document). Beyond the contracted message volume, overages are charged at rates typically 3–5x the contracted per-message rate.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
This message-based model differs from named-user licensing common in other SAP applications, creating complexity in sizing, cost forecasting, and commercial negotiation. Unlike named users (where you count how many people access the system), message volumes are consumption-based and require careful estimation against your integration roadmap.
Message-based pricing is theoretically flexible but operationally dangerous. Buyers commonly underestimate message volume by 40–60%, resulting in major overage charges mid-contract. Forward-looking sizing based on integration roadmaps is critical.
SAP Integration Suite is sold in four primary tiers, each with different capability inclusions and pricing:
Entry-level tier focused on synchronous integration patterns. Includes basic Cloud Integration (CPI) for REST, SOAP, and file-based integrations. Limited to synchronous flows and basic event handling. Pre-built content library for common SAP applications. Typical use case: departmental integrations, proof-of-concept deployments, simple cloud connector scenarios. Pricing is lower per message but limited feature scope.
Mid-tier offering adding asynchronous integration support, including queuing and pub/sub patterns via Event Mesh (often sold as separate add-on but included in this tier). Integration Advisor for B2B and EDI message mapping. Larger pre-built content library. No additional licensing required for basic API Management. Typical use case: medium-scale enterprise integrations, B2B partner networks, asynchronous order-to-cash integrations. Per-message cost is higher than Standard but features are broader.
Advanced tier adding comprehensive API Management (Portal, Developer Communities, Rate Limiting, OAuth), complete B2B/EDI functionality, Integration Advisor without limits, advanced monitoring and alerting, and higher transaction throughput for integration iFlows. No per-transaction cost for API calls in certain management scenarios. Suitable for large-scale integration platforms with significant external API exposure. Per-message cost is high but feature richness justifies cost for enterprise-scale deployments.
Highest tier adding advanced security (mTLS, certificate management), extended API rate limiting and quota management, dedicated integration runtime options, priority support, and custom service level agreements. Advanced compliance and audit logging. Suitable for highly distributed, complex integration platforms with strict security and SLA requirements. Used by enterprises with mission-critical integration workloads and significant external partner networks. Highest per-message cost but includes service guarantees and advanced features.
The tier structure is not granular by feature — you cannot cherry-pick individual capabilities from different tiers. Once you select a tier, you get all included features for that tier and above. This creates a "cliff edge" problem: adding a single required feature (e.g., Event Mesh without it being included) can force you to upgrade to a higher tier, increasing costs significantly.
Integration Suite operates on SAP BTP and consumes BTP credits for underlying compute and storage resources. This creates a two-layer cost structure: Integration Suite message-based licensing covers the application functionality (integration flows, API management), while BTP credits cover the runtime infrastructure. Both costs apply simultaneously and must be managed independently.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
The relationship between Integration Suite messages and BTP credit consumption is complex. A single Integration Suite message can consume variable BTP credits depending on payload size, transformation complexity, and message destination. A large file transfer integration consuming 100 Integration Suite messages might consume 500–1,000 BTP credits; a lightweight REST API call consuming 1 Integration Suite message might consume only 5–10 BTP credits. SAP does not publish a standard conversion formula, making cost forecasting difficult.
RISE customers typically receive included BTP credits as part of the base entitlement (commonly 5,000–10,000 credits per month), plus included Integration Suite message allocation (often 5–10 million messages annually). Both entitlements are typically undersized for complex deployments, creating a dual cost overrun risk. Independent SAP licensing specialists can help model the relationship and forecast both streams simultaneously.
API Management is a core capability of Integration Suite but carries separate licensing complexity. SAP Integration Suite Professional and Premium tiers include comprehensive API Management. Standard tier includes basic API publishing but not advanced management features (rate limiting, quota management, developer portal, OAuth). Standard Plus tier sits in the middle with intermediate API capabilities.
The distinction matters because many organisations initially deploy Integration Suite in Standard tier for synchronous integrations but later discover they need API Management capabilities (exposing internal services as external APIs, partner integrations, public API programmes). The only path forward is to upgrade to Professional or Premium tier, triggering a retroactive licensing cost increase that applies to historical message volumes as well as forward periods.
When selecting your Integration Suite tier, honestly assess your current and 12-month forward API management needs. If you have any external API exposure, any partner integrations, or any plan to move towards an API-first architecture, Professional tier is a safer baseline than Standard. The per-message cost difference is often overstated — the real cost comes from undersizing and forced tier upgrades.
| Feature | Standard | Standard Plus | Professional | Premium |
|---|---|---|---|---|
| Synchronous Integrations | Yes | Yes | Yes | Yes |
| Asynchronous / Event Mesh | Add-on | Included | Included | Included |
| API Management (Basic) | Limited | Limited | Full | Full |
| API Developer Portal | No | No | Yes | Yes |
| Integration Advisor (B2B/EDI) | Add-on | Included | Included | Included |
| Advanced Security | No | No | Yes | Full |
| Rate Limiting / Quota | No | No | Yes | Yes |
Beyond the base tier, several specialised capabilities are available as add-on licensing items, each with separate per-message or transaction pricing. Understanding these add-ons is critical because they are often discovered mid-project after integration scope expansion.
Integration Advisor is SAP's B2B and EDI message mapping tool, designed to simplify complex data transformations between EDI standards, EANCOM, Odette, ORDERS, INVOIC, and other document types. In Standard tier, Integration Advisor is not included and must be licensed as an add-on. Standard Plus tier and above include it. When negotiating Integration Suite, clarify whether your B2B / EDI usage is covered by your tier or requires separate add-on licensing. This is often a £100,000–£300,000 annual add-on for mid-market organisations with significant EDI partnerships.
Event Mesh is SAP's asynchronous event broker, enabling event-driven architecture and real-time data synchronisation across applications. Standard tier requires Event Mesh to be licensed as a separate add-on (typically priced as an annual subscription with tiered throughput). Standard Plus tier and above include Event Mesh. If your integration roadmap involves real-time order updates, inventory synchronisation, or event streaming from S/4HANA, Event Mesh is likely necessary. Negotiating this upfront as part of your Integration Suite tier selection is more cost-effective than adding it mid-contract.
Open Connectors are pre-built integration components for third-party SaaS applications (Salesforce, Netsuite, Workday, Slack, etc.). They accelerate integration development by providing standardised API mappings and authentication patterns. Open Connectors are licensed separately as a consumption-based add-on (per connector instance per month, typically £200–£1,000 depending on connector). For organisations with significant SaaS integration scope, Open Connectors can represent a major cost line item. Request that commonly used connectors be bundled into your Integration Suite tier agreement to avoid per-connector charges.
If you deploy Integration Suite in Standard or Standard Plus tier but later require advanced API Management features (advanced rate limiting, quota management, developer communities, OAuth with custom claim mapping), these can be licensed as separate add-ons rather than forcing an immediate tier upgrade. Pricing is typically £50,000–£200,000 annually depending on throughput and feature scope. Negotiation opportunity: include these advanced API features in your base tier pricing rather than paying premium add-on rates.
Customers purchasing RISE with SAP receive Integration Suite as a base entitlement, but the included allocation is typically minimal and undersized. A standard RISE contract for a mid-market organisation might include:
In practice, the 5–10 million included messages often covers only 30–50% of actual integration demand in complex deployments. Additional messages beyond the RISE entitlement are purchased as a separate line item (Integration Suite Message Top-Up) priced as a standalone subscription. The key negotiation point is ensuring that all Integration Suite components — tiers, add-ons, and message volumes — are explicitly modelled and negotiated as part of the RISE agreement, not left as defaults.
Many RISE customers discover 12–18 months into deployment that their actual Integration Suite usage exceeds the RISE entitlement by 200–300%. The only remediation is retroactive licensing true-up (backcharges for prior periods) plus prospective overage costs for the remainder of the contract. This is avoidable through detailed scoping and sizing before RISE signature.
Most common cost driver. Buyers estimate integration scope in the discovery phase based on SAP modules going into S/4HANA (Finance, Procurement, Sales), estimate ~1–2 million messages per year, and purchase Integration Suite at that level. Post-go-live, actual integration demand balloons to 5–10 million messages annually due to unplanned integrations, data synchronisation cycles, master data distribution, and ad-hoc reporting integrations. The cost multiplier from underestimation can exceed £500,000 annually for large organisations.
Initial deployment uses Integration Suite for backend system integrations (Standard tier, no API management). Six months later, business stakeholders request external API exposure for partner integrations or mobile applications. Upgrade to Professional tier is required, triggering tier upgrade costs that apply retroactively to all prior-period messages as well as forward periods. Total cost: £150,000–£400,000 unexpected bill.
Integration roadmap focuses on S/4HANA to cloud application connectivity. Partner and EDI integrations are discovered or prioritised post-go-live. Integration Advisor and B2B-specific capabilities were not included in the initial tier selection. Adding them mid-contract as an add-on or tier upgrade incurs premium pricing and potentially retroactive true-up costs.
Async integrations and event-driven patterns are significantly more message-intensive than initial estimates. Real-time inventory or order status updates generate one message per transaction, multiplied by transaction frequency across your business. Event Mesh throughput limits are exceeded mid-year, forcing additional Event Mesh subscription purchases at premium rates.
Integration flows are built without message consumption visibility. Flows include unnecessary transformations, fanout patterns that multiply message count, or polling intervals that are too aggressive (e.g., checking for changes every 1 minute instead of 5 minutes). A 10x difference in message consumption is achievable through flow redesign. By that point in the contract, cost remediation is not available — the only benefit is reduced overages in future years.
Accurate Integration Suite sizing requires a structured approach mapping business processes to message volumes. Follow this methodology:
Document all planned integration scenarios, including: S/4HANA to cloud (ERP to CRM, HR, Procurement, Finance), B2B partner integrations (EDI, REST APIs), data synchronisation (master data, transactional data), reporting integrations, and real-time event streams. For each scenario, estimate annual transaction volume (orders, invoices, employees, materials, etc.).
One business transaction may generate multiple messages. A single purchase order going into S/4HANA might trigger: 1 inbound message (PO receipt), 1 transformation in Integration Suite (CPI), 1 outbound message to Procurement Cloud, 1 outbound message to a supplier portal. Total: 4 Integration Suite messages per PO. If you have 1 million POs annually, that is 4 million messages per year.
If you deploy event-driven architectures (real-time inventory updates, order status notifications), multiply message count by event frequency. Real-time inventory sync generating updates 10 times per day across 100,000 SKUs is 365 million annual messages — vastly different from batch daily inventory sync (365 million ÷ 10 = 36.5 million).
Add 30–50% buffer to your calculated message volume to cover scope expansion, new integrations, and inaccuracies in estimation. If calculated demand is 8 million messages, purchase 10–12 million messages annually. Negotiated overage rate caps ensure that minor overshoots (< 5% beyond contracted) incur only marginal additional cost.
Engage an independent SAP licensing specialist to build a detailed Integration Suite sizing model before signature. The cost of specialist engagement (typically £15,000–£40,000) is recovered many times over by avoiding undersized licensing and mid-contract upgrade surprises.
Negotiate the Integration Suite tier based on your 12–18 month forward integration roadmap, not just your go-live scope. If API Management will be needed within 12 months, negotiate Professional tier pricing now rather than paying for a Standard tier upgrade later. Professional tier pricing locked in at signature is typically 20–30% cheaper than the cost to upgrade from Standard tier mid-contract.
Negotiate Event Mesh, Integration Advisor, and advanced API Management capabilities as bundled inclusions in your Integration Suite tier agreement, rather than paying per-unit add-on pricing. Bundled pricing typically saves 25–40% compared to standalone add-on costs. Example: Integration Advisor as an add-on might be £200,000 annually; negotiating it as part of tier might cost an additional £50,000–£80,000 annually.
Negotiate a cap on overage rates for messages exceeding your contracted allocation. Rather than paying 5x the contracted rate for overages, negotiate a cap of 150% of your contracted per-message rate. For a contract with 10 million messages at £0.10 per message (£1 million total), a 10% overage (1 million messages) would normally cost £500,000 at 5x rates but only £150,000 at 150% capping. Overage rate capping is standard ask and often granted.
Negotiate a clause allowing unused messages from one contract period to carry over to the next (typically 10–20% of annual allocation). This provides buffer against seasonal variation in message volume. Additionally, negotiate a true-up period (typically 90 days into the contract) where you can adjust your message allocation upward if initial usage is trending higher than expected, applying any increase retroactively. True-up periods eliminate the mid-year surprise of discovering undersizing.
Ensure that Integration Suite message volumes and BTP credit allocation are modelled together and negotiated as a coherent package. Don't accept separate negotiations for Integration Suite messages and BTP credits without explicit correlation. Request SAP to provide a BTP credit consumption model for your estimated Integration Suite usage, and negotiate sufficient BTP credits to cover your integration roadmap without running out mid-year. Coordinate true-up clauses for both Integration Suite messages and BTP credits to trigger simultaneously.
Integration Suite pricing is heavily discounted from list rates for large commitments and strategic accounts. Request benchmarking data showing typical per-message costs for organisations of your size and integration complexity. Use that benchmarking in negotiations to validate pricing. If you are being quoted 2x the benchmark rate, escalate to SAP account executive for pricing review. Competitive pressure (cloud integration alternatives like MuleSoft, Boomi, Azure Integration Services) can support better pricing if SAP perceives risk of alternative platform selection.
Don't sign a RISE or Integration Suite agreement without independent sizing and commercial review. The gap between estimated and actual integration demand is often measured in millions of messages and hundreds of thousands in cost.