SAP SuccessFactors is sold as a per-employee-per-month subscription. The user-count licence is what most procurement teams see, negotiate, and budget for. There is a secondary cost surface that most customers under-attend — integration centre charges, platform-data minutes, data-transfer volumes, and inter-module integration fees — that on mid-sized HXM deployments can add ten to twenty per cent to total cost. The secondary cost is rarely visible at the original deal and frequently appears as a surprise at the first renewal.
This article walks the secondary cost surface, where each fee comes from, and the contractual language that materially contains the cost at renewal.
What integration centre actually charges for
Integration centre is the SuccessFactors tool for building and running integrations between SuccessFactors modules and external systems — payroll providers, time and attendance systems, identity providers, expense systems. The tool is included in the SuccessFactors platform licence in most order forms. What is not always included is the run-time cost of executing integrations at scale.
Integration centre runs are typically metered on a combination of "integration runs per month" and "data records processed per run." A customer with twenty active integrations running daily is processing roughly six hundred runs per month; if each run touches ten thousand records, the customer is processing six million records per month against the integration centre meter. The default tier in most order forms is well below this volume.
Platform-data minutes — the cost that nobody budgets
Some SuccessFactors order forms include a meter called "platform-data minutes" — a measure of the compute time consumed by integration runs, report generation, and ad hoc analytics queries. The meter is most common on order forms negotiated between 2022 and 2025, and is frequently a tier-based price ladder rather than a unit price.
Platform-data minutes are particularly expensive in two patterns: heavy use of People Analytics queries (each analytics query consumes substantial compute), and large daily integrations to legacy systems (each integration run consumes compute proportional to the data volume). Customers with extensive People Analytics deployments and legacy-integration estates can find platform-data minutes adding fifteen per cent to total cost.
Inter-module integration fees
SuccessFactors modules integrate with each other through standard connectors. Most inter-module integrations are included in the base SuccessFactors platform fee — Employee Central to Performance, Performance to Compensation, Recruiting to Onboarding. A meaningful minority of inter-module integrations are separately priced as "premium connectors," typically the integrations to Employee Central Payroll, Workforce Planning, and the Workforce Analytics module.
The premium-connector fees are usually small individually but they accumulate. A customer with a full HXM deployment that includes Employee Central, Employee Central Payroll, Recruiting, Onboarding, Performance, Compensation, Learning, Succession, and Workforce Analytics may be paying premium-connector fees on five or six of the integrations. The cumulative cost is meaningful.
The data-transfer dimension
For customers running SuccessFactors integrations to non-SAP systems — especially payroll providers like ADP, Ceridian, or NGA — the data-transfer dimension can be a separate cost. SuccessFactors meters outbound data transfer in some order forms, particularly for large-volume daily files. The meter is occasionally a flat fee per file and occasionally a volume-based fee on the underlying data.
The customer-side defence on data-transfer fees is contractual: the original licence should include the data-transfer volume as part of the platform fee for any integration to a documented partner system. The clause is often missing in original order forms and is reasonable to ask for at renewal.
How the secondary cost surface scales with the deployment
The secondary cost surface scales non-linearly with the deployment. A small HXM deployment (5,000 employees, basic Employee Central plus Performance) typically has secondary costs at two to three per cent of total. A medium deployment (15,000 employees, full talent bundle) has secondary costs at six to ten per cent. A large deployment (50,000+ employees, full HXM plus People Analytics plus extensive integrations) can have secondary costs at fifteen to twenty per cent.
The non-linearity is driven principally by analytics adoption and integration depth, not by employee count alone. Customers planning a People Analytics rollout should budget for the platform-data-minutes consequence; customers planning an Employee Central Payroll integration should budget for the premium-connector fee. See Employee Central Payroll licensing for the integration-specific detail.
The renewal-time contract clauses to negotiate
1. The integration-volume inclusion clause
The cleanest preventive clause includes a defined volume of integration centre runs and data records in the base platform fee, with a flexibility band before tier transition. The clause prevents the most common renewal-time surprise.
2. The premium-connector consolidation
Where the customer has three or more premium-connector relationships, the optimal commercial position is to negotiate a single "integrated HXM" rate that covers all premium connectors at a flat rate. SAP will negotiate this for customers with broad HXM footprints, but the customer has to ask.
3. The platform-data-minutes ladder
If platform-data minutes are on the customer's order form, the price ladder is negotiable. The customer should request the ladder be tied to a documented growth assumption (e.g., ten per cent annual growth in compute consumption is included in the platform fee) rather than to an absolute tier that can be triggered by ordinary usage growth.
The operational disciplines that contain secondary cost
Three operational disciplines materially reduce the secondary cost surface. First, an annual integration-centre audit that identifies dormant or redundant integrations for retirement. Second, a People Analytics dashboard governance process that limits query-heavy dashboards to a defined population. Third, an integration architecture review that consolidates multiple point-to-point integrations into fewer, higher-volume integrations through a hub pattern.
The disciplines are not technically complex but they require explicit ownership. The most common failure mode is that the integration estate grows organically over years without a periodic prune, and the platform-data-minutes meter inflates with it. See the broader operational framework in our license optimization service, the related discussion in Workforce Analytics licensing, and the SuccessFactors Licensing Guide for the full framework.
The audit-finding pattern on secondary cost
SuccessFactors audits, separate from contract-renewal exercises, increasingly include findings on the secondary cost surface. The most common findings are platform-data-minutes consumption above tier, integration centre runs above tier, and undeclared premium-connector usage (where an integration has been built but the connector fee has not been activated on the order form).
Customer-side defences on these findings rest on three principles: the contractual definitions of the meters, the documented historical consumption pattern (which often shows that recent inflation is anomalous), and the customer's right to negotiate tier adjustments rather than accept back-charges. See the audit defence service for the engagement model, and the closely related discussion in audit letter tone for the dispute approach.
What good looks like
A well-managed SuccessFactors secondary cost position has explicit integration-volume language in the contract, consolidated premium-connector pricing, a documented platform-data-minutes ladder, an annual integration audit, and a People Analytics governance process. Customers who hit this standard typically run their HXM deployments at the user-count licence cost plus five to seven per cent secondary, rather than the fifteen to twenty per cent the deployment would otherwise produce. See the broader SuccessFactors topic page for the full deployment context.