SuccessFactors is sold per employee per month, and the definition of an "employee" is the load-bearing line in every SuccessFactors contract. Contractor populations sit awkwardly inside that definition: they appear in the HRIS for organisational and reporting purposes, they consume SuccessFactors functionality through self-service modules, and they are counted in the headcount measurement that drives the subscription fee. Customers with material contractor populations and ambiguous contract language routinely pay 8 to 18 per cent more than they need to on their SuccessFactors stack.
This article addresses the contractor-counting question across Employee Central, Performance Management, Goal Management, Compensation, Recruiting, Onboarding, and Learning, with a contractual frame that closes the recurring overcount.
How SuccessFactors counts employees
The SuccessFactors per-employee-per-month metric is measured at the platform level by counting active employee records — with "active" defined either as records carrying an active employment status code, records with a current employment record (HRIS-EE-INFORMATION effective-dated entries), or records that have been touched in the measurement period, depending on the contract version.
Contractor records can fit any of these definitions depending on how the customer's HRIS is configured. In an Employee Central deployment that includes contractors as employment records (often the case where HR uses EC for org-chart and time-off purposes for all workforce types), contractors land in the active count by default. In an EC deployment that segregates contractors to a separate person type or external workforce module, contractors are not counted.
Where the contract language matters
The contractual frame that drives whether contractors count is one or more of:
- The "employee" definition in the SuccessFactors order form. Some order forms define employee as "active employment record"; some define it as "individual person with access to the SuccessFactors platform"; some leave the definition to the price-list reference. The definition is the first place to look.
- The named-user or PEPM cap definition. Some contracts cap the licensed population at a contracted ceiling regardless of actual headcount; some scale dynamically.
- The exclusion list. Some contracts carry an exclusion list — "the licensed headcount excludes contingent workers, interns, and former employees retained for benefits administration." This is the customer-favourable language.
- The audit measurement methodology. Some contracts specify the dataset and the query that defines the measurement; many do not, which leaves the auditor with measurement discretion.
Customers approaching renewal should map the current contract against these four elements and propose targeted amendments to close the ambiguity. For the renewal negotiating frame, see our contract negotiation service and the EC vs PM/GM bundles article.
Module-by-module contractor implications
Employee Central
EC counts contractors by default if they have an active employment record. The decision to use the External Workforce module, or to deploy contractors as a separate person type, is an implementation choice that should be made at deployment time, not retrofitted. Customers retrofitting after deployment face a 6 to 14 month operational project to restructure the data model.
Performance Management
PM is functionally relevant only to populations that go through formal performance reviews. Most contractor populations do not have performance reviews because the engagement model is project-based or time-and-materials. Counting contractors against the PM PEPM is therefore a structural overpay. Where the contract permits, scope PM to the population that actually uses it (typically through a target population definition).
Goal Management
GM is similar to PM but with a slightly broader use case — contractors on longer engagements sometimes do receive goal-setting workflows. The decision to include or exclude contractors from GM should be made on the basis of business workflow, not on the contractual default.
Compensation
Compensation is the module where contractor exclusion is most clearly defensible. Contractors are paid through accounts payable, not through the compensation cycle that the SuccessFactors Compensation module manages. Including contractors in the Compensation PEPM count is a straight overpay.
Recruiting and Onboarding
Recruiting and Onboarding can be more complex. Some organisations use Recruiting to source contractor talent (in which case contractors interact with the Recruiting module before they become contractors). Onboarding is sometimes used for contractors and sometimes not. The contractual position should match the operational workflow.
Learning
Learning is the most universal of the modules — many organisations require contractors to complete compliance training and other learning modules. Including contractors in Learning is therefore often a legitimate licensing position, even when they are excluded from other modules. The price-list flexibility to differentiate Learning headcount from EC headcount is sometimes available and rarely exercised.
The measurement evidence
The audit measurement evidence chain for SuccessFactors contractor counting is mechanical:
- Active employment record extract from the EC HRIS-EE-INFORMATION table.
- Person-type classification (permanent employee, intern, contractor, contingent worker, former employee, etc.).
- Module-use attribution — which person types have access to which SuccessFactors modules.
- Contractual definition mapping — what does the contract count, in plain language.
- Reconciled count by module — the defensible measurement.
The evidence chain produces a clean defensible position in roughly 6 to 10 weeks of work, and reduces the recurring overcount by 60 to 75 per cent in our experience. The first build is heaviest; subsequent measurement cycles are operationally light.
The true-up trigger
SuccessFactors contracts typically include a true-up clause that allows SAP to bill for headcount growth above the contracted baseline. The true-up clause has an asymmetry: headcount growth triggers a true-up bill; headcount reduction rarely triggers a true-down credit. This asymmetry means contractor inclusions that survive into the headcount baseline at renewal then drive true-up exposure for the remainder of the contract.
The defence is to scrub the contractor population from the headcount baseline at renewal — both for the immediate subscription fee and for the future true-up exposure. For deeper coverage of the true-up mechanics, see our true-up triggers article.
The migration moment
The cleanest single moment to reset the contractor count is the migration from ECC HCM to Employee Central. At migration, the headcount baseline is recalculated, the contractual definitions are re-negotiated, and the External Workforce module can be deployed at the same time as the core EC implementation. Customers who carry their ECC HCM contractor count into EC without reset will carry it for the entire EC subscription term.
For the integrated migration treatment, see our S/4HANA migration compliance service and the global services firm SuccessFactors rebaseline case file. The migration window is short and the consequences are long.
What this looks like at the contract renewal
An EC customer with 22,000 active employment records, 3,800 of which are contractors, currently pays PEPM on all 22,000 records across EC, PM, GM, and Compensation. The contractor population uses EC (for time-off and org-chart) and Learning (for compliance training), but not PM, GM, or Compensation. The renewal opportunity:
- EC: Add an External Workforce subscription for the 3,800 contractors at a lower PEPM rate, reducing EC headcount to 18,200. Net saving roughly $190K per year.
- PM: Scope to the 18,200 permanent population. Saving roughly $130K per year.
- GM: Same as PM. Saving roughly $110K per year.
- Compensation: Same as PM. Saving roughly $160K per year.
- Learning: Maintain at 22,000 to cover the compliance training requirement.
Aggregate three-year saving roughly $1.8M on a base contract value of approximately $5.4M, with no functional reduction. The work that produces the saving is the contract amendment work at renewal, supported by the workforce-data evidence that demonstrates the workflow segregation. For the broader treatment, see the SuccessFactors Licensing Survival Guide and the SuccessFactors topic page.