SAP SuccessFactors pricing in 2026. Per employee, per module, and what that costs you.

SuccessFactors is priced per employee, per active module, per month, on your whole HRIS population. Employee Central is the foundation, the other modules stack on top, and most 2026 contracts carry an inflation indexed escalator.

How is SuccessFactors priced in 2026?

SAP prices SuccessFactors per employee, per active module, per month, contracted for a fixed subscription term. Employee Central is the foundation, and Performance and Goals, Compensation, Recruiting, Learning and Onboarding stack on top, each with its own per employee rate.

Four things set the bill: the employee count you sign for, the modules you switch on, the bundle discount across them, and the annual escalator.

Which employees count toward the price?

The count is the eligible HRIS population, not the number of people who log in. In practice every active employee profile the system holds data for is billed, so a warehouse worker who never opens the app still costs the full rate for every module you license.

That makes the population rules in your order form and SAP's usage metric definitions worth reading line by line. Ask which records count: contingent workers, interns, inactive profiles, employees on long term leave, and people in countries where a given module was never rolled out.

How does the bundle discount work?

Bundle discounts apply when you take three or more modules together. They typically run 15 to 28 percent against standalone module pricing, and SAP presents them as a per employee rate that falls with each module you add.

The discount is calculated on the whole set. Once a module is inside the bundle, SAP treats its removal as a loss of discount on everything else, which makes the bundle cheap to enter and expensive to leave.

How is employee volume metered?

SAP sizes the employee count at signing. Growth above the signed scope triggers a true up on the excess, usually first billed in year two. Reductions do not flow back: SAP's general cloud terms state that the customer may not reduce usage metrics during the subscription term, so a smaller workforce keeps paying for the signed number.

What changed with escalators in 2026?

Typical SuccessFactors escalators run 3 to 5 percent a year, either fixed or tied to an inflation index, and the 2026 price book moved most contracts we see to the index. An open index clause has no ceiling in a high inflation year, so the cap you negotiate matters more than the starting percentage.

Which SuccessFactors modules drive the most spend?

Six modules carry most SuccessFactors spend, and use across them is uneven. Employee Central and Performance and Goals reach most of the workforce, while Learning and Onboarding are often billed on the full headcount and used by a fraction of it.

• Employee Central. SAP SuccessFactors Employee Central is the core HRIS: employee data, organization structure, position management and workflow. Every other module depends on it.
• Performance and Goals. Goal setting, performance reviews, calibration and continuous performance management. Enterprise HR teams use it heavily.
• Compensation. Compensation planning, merit cycles, equity and total rewards statements. It is often bought alongside Performance and Goals.
• Recruiting. Requisitions, candidate experience, interview scheduling and offer management. Companies whose adoption is led by talent acquisition often start here.
• Learning. Course catalog, learning paths, compliance training and skills tracking. It carries the highest shelfware risk in the bundle.
• Onboarding. Preboarding, day one and the first 90 days of orientation workflow. Most enterprises buy it with Recruiting.

Across the full bundle, usage rarely exceeds 65 percent. Every module is billed on the whole population, so each gap in the last column is money paid for people who never touch that module. For a side by side view of how Workday prices the same scope, see our SuccessFactors vs Workday comparison.

What does SuccessFactors cost for a 5,000 employee company?

On assumed rates of $24 per employee per month for all six modules and a 20 percent bundle discount, a 5,000 employee company pays $1,152,000 a year. SAP does not publish SuccessFactors enterprise rates, so the figures below are illustrative assumptions, not SAP prices.

Replace them with the rates on your own order form. The mechanics stay the same whatever the starting rate, and the 20 percent discount sits inside the usual range.

What does Learning cost per person who uses it?

Learning costs $192,000 a year here, or $38.40 per employee. At the 42 percent median usage we record for Learning, 2,100 people use it, which puts the real price at about $91 per active learner per year.

What happens if you drop Learning at renewal?

Five modules remain, so the set still qualifies for a bundle. At the same 20 percent discount the rate falls to $16 and the annual cost to $960,000, a saving of $192,000.

SAP will usually argue that the discount has to shrink. Even at 15 percent on the remaining five modules, the rate is $17 and the annual cost $1,020,000, still $132,000 below the full bundle. Before deciding, ask SAP to price Learning for a smaller population and compare that with the tool your learning team would otherwise use.

What does a headcount swing cost?

If headcount grows to 5,600 in year two, the 600 extra employees trigger a true up of 600 times $19.20 times 12, or $138,240 a year. If headcount falls to 4,400 instead, you still pay for 5,000, and the same $138,240 goes on records you no longer have.

Escalators compound on top of both. On the $1,152,000 first year, a 5 percent annual escalator totals $3,631,680 over three years. A 3 percent cap totals $3,560,717, which is $70,963 less.

What triggers a SuccessFactors true up, and how do you contain it?

Two events drive most true ups and repricing: SAP's annual employee count check and the usage review SAP runs before renewal. SAP's cloud terms also make you responsible for monitoring your own use and reporting any excess, and they allow SAP to monitor use to verify compliance.

Employee growth above the signed scope

SAP checks the employee count every year, and growth above the signed scope produces a back charge on the excess. Size the contract on today's headcount plus an agreed growth buffer. A forecast built for a board presentation is the wrong basis for a number you cannot reduce later.

The usage review before renewal

SAP runs a usage review in the 12 months before renewal, and its findings shape the renewal proposal. Where use is low, the account team prepares reasons to keep the module in the bundle. Where headcount is up, it prices the growth into the new base. Run your own review first so the proposal has to answer your numbers.

The full renewal sequence is covered in our guide to SuccessFactors renewal negotiation.

What have we seen in recent SuccessFactors renewals?

We ran roughly 20 to 28 SuccessFactors renewal engagements in 2024 and 2025, and the medians below come from 24 of them. After a properly prepared negotiation, the signed price came in 25 to 38 percent below SAP's first quote, a median reduction of 31 percent.

• Learning was the most frequent shelfware. Usage sat between 30 and 55 percent at most enterprises, with a median of 42 percent.
• Employee Central always led. It was the most used module in every account, and Performance and Goals came second.
• Headcount growth was expensive. Year two growth triggered a true up in about 1 in 3 deals, and careful sizing at signing avoided most of it.
• Half used modules were common. In roughly 7 out of 10 enterprise renewals we advised, the customer was paying for modules used by fewer than half of its employees.

Should you take the full suite because the per employee rate falls?

SAP account teams present the full SuccessFactors bundle as the best value because the per employee rate drops with each module added. We disagree. The rate is charged on every employee while use is not, which is why those 7 in 10 renewals carried modules below 50 percent usage.

Subscribe only to the modules that survive a usage audit. For everything else, hold add on rights at the original bundle rate so you can add a module later without reopening the discount, and reprice the contract on trailing 12 month employee counts. SAP will not frame the deal this way, so you have to.

SuccessFactors is priced on the employees you have, not on the employees who use the modules. Reconcile both before renewal.

How do you reduce SuccessFactors cost at renewal?

Three steps recur in well run SuccessFactors renewals, in this order. The first two produce the data, and the third turns it into a counterproposal, backed by the contract terms listed further down.

Audit module usage

Pull 12 months of module usage by employee and flag every module below 50 percent. SuccessFactors already holds the records you need:

• Employee Central. Headcount by employment status, country and worker type, from People Analytics reports in Report Center.
• Performance and Goals and Compensation. Form completion by cycle: how many employees had a review or a compensation worksheet in the last cycle.
• Recruiting and Onboarding. Requisitions opened and new hires processed, compared with total hires from Employee Central.
• Learning. Completion and assignment history from Learning administration, split between mandatory and voluntary content.
• Login activity. The User Login Data ad hoc report, which shows who has an active profile but never signs in.

Reconcile the employee count

Compare the contracted employee count with the trailing 12 months of actuals, month by month. Set the renewal baseline on actuals and remove records that should not count under your order form definitions, such as terminated profiles still marked active.

Unbundle the renewal

Reprice each module on actual use and drop the ones that are underused. Model both the full bundle and the reduced set, with a per module rate for each, so SAP's claim that the discount must fall can be tested against real totals.

What will the SAP account team say, and how should you answer?

The same few arguments come up in most SuccessFactors renewals. Prepare the answers before the first meeting.

Which contract terms should you ask for?

Ask for these in writing on the order form, since the general terms will not give them to you.

• Employee definition. State which worker types and profile statuses count, so contingent workers and inactive records stay out of the bill.
• Growth buffer. A headcount band above the signed number that triggers no true up, which keeps normal hiring from generating back charges.
• Annual true down. The right to reduce the employee count at each anniversary, because SAP's general terms bar reductions during the term.
• Add on rights. The right to add any dropped module later at the original bundle rate for the whole term.
• Escalator and renewal cap. Cap the annual escalator at 3 to 4 percent, reject open inflation indexed clauses, and apply the same ceiling to the renewal price so the index cannot reset your base.
• Term length. Three year terms with annual employee true downs are the workable position. Reject five year terms without a step down clause that allows reductions in modules or employees at set points.

Our SuccessFactors negotiation guide covers how to sequence these requests during the negotiation.

When should you start preparing a SuccessFactors renewal?

Start the module usage audit at least 270 days before renewal. The data shapes every later decision, and SAP's own review starts inside the final 12 months.

For how SuccessFactors fits into your wider SAP spend, see the SAP knowledge hub and the SAP pillar hub.

What to do next

1. Pull usage. Export 12 months of module usage by employee.
2. Reconcile the count. Compare the contracted employee count with actuals and set the baseline on actuals.
3. Flag low use. Identify every module under 50 percent usage.
4. Model the options. Build the unbundled renewal model next to the full bundle.
5. Fix the commercial terms. Negotiate the escalator cap and the term length.
6. Protect dropped modules. Hold add on rights at the bundle rate for everything you remove.
7. Price integration. Map the integration cost that sits outside the SuccessFactors contract.
8. Get independent support. Our independent SAP advisory team can run the analysis and the negotiation with you.

Frequently asked questions