SuccessFactors is the SAP human experience management platform, and like most cloud HXM products it is licensed primarily on a per-employee subscription model. Mobile access — the iOS and Android SuccessFactors apps that field, retail, manufacturing, and frontline workforces typically rely on — is treated as part of the subscription for the categories of employees whose underlying seat is fully entitled. For the substantial population of employees who are not on a full SuccessFactors seat — most commonly hourly retail associates, shift-pattern manufacturing operators, contract field-service technicians, and seasonal staff — the mobile licensing position is materially different. This article walks through how it actually works and where audit findings consistently appear.
The four SuccessFactors employee categories
SuccessFactors contracts typically distinguish four employee categories with different licensing treatment. Mobile access intersects with each one differently.
Full-suite HXM employees
Employees on the full Human Experience Management subscription receive desktop and mobile access as part of the seat fee. There is no incremental cost for mobile use, but the seat itself carries the highest per-employee price on the SuccessFactors price list.
Core HR (Employee Central) employees
Employees licensed on Employee Central alone, without the broader talent modules (Performance, Goals, Learning, Recruiting, Compensation), receive desktop and mobile access for the Employee Central functionality. Mobile access to talent modules is not entitled at this tier — even if the employee’s manager has Employee Central plus Performance, the employee’s self-service mobile cannot access talent functionality without an additional licence.
Frontline / mobile-only employees
The category that produces the most audit findings. SuccessFactors offers a dedicated "Mobile Only" or "Frontline" seat at a substantially lower price point, designed for employees whose entire interaction with SuccessFactors is through the mobile app. The seat carries restrictions: read-only access to certain modules, no manager-level approval rights, and bounded talent-module functionality.
Contractors and contingent workers
Contractor licensing in SuccessFactors is complex enough to warrant its own article — see our contractor counts piece. The short version: contractors who access SuccessFactors mobile to record time, submit expenses, or view payroll information need a licensed seat under the relevant category, even where they are not on the customer’s payroll.
How the audit reconciliation actually works
SuccessFactors audit reconciliation is more straightforward than on-premise SAP audits because the platform produces native usage analytics that SAP can extract directly. The audit conversation typically starts with two reports: the licensed seat count by category, and the active user count by access channel (web, mobile, integration). Discrepancies between the active mobile user count and the entitled mobile seat count are the finding.
The reconciliation works in three steps. First, SAP produces an extract showing all employees with mobile-app activity during the audit period. Second, the customer’s seat allocation is mapped against the extract, identifying which mobile users sit under which entitlement category. Third, any active mobile users without a corresponding mobile-entitled seat are flagged as the finding population.
The three clauses to negotiate before deploying mobile
Procurement teams who are planning a mobile SuccessFactors rollout to a previously desktop-only workforce should negotiate three specific clauses into the contract before deployment begins.
1. The mobile-access definition
The contract should define what constitutes "mobile access" in measurement terms. Does single sign-on from a mobile browser count? Does notification receipt without app interaction count? Does API access from a mobile device management platform count? Each of these has been argued in audit defence; the contract definition determines the outcome.
2. The Frontline-tier ratio
The standard SuccessFactors contract offers Frontline tier seats at approximately 30% of the full EC price. The ratio is negotiable. Customers with large frontline populations have moved the ratio to 20-25%, particularly where the frontline functionality is genuinely bounded (no goals, no performance reviews, no learning).
3. The seasonal-population provision
Retail and hospitality customers see their workforce double or triple in seasonal peaks. A provision allowing the licensed seat count to be measured on annual average rather than peak — or alternatively, allowing a defined peak buffer above the entitled base — prevents the seasonal spike from triggering an over-deployment finding.
The Employee Central Service Center wrinkle
Where the customer deploys Employee Central Service Center (the SuccessFactors HR shared-service capability), the mobile licensing picture becomes more complicated. Employees raising tickets through the mobile app may be using a service-centre licence that has its own per-employee fee structure, separate from the underlying EC seat. Customers routinely deploy Service Center as a "self-service efficiency" play without modelling the licence implication.
The same issue applies to the Onboarding 2.0 module accessed via mobile. New hires using the mobile onboarding flow consume an Onboarding seat that is typically licensed separately from the EC base. See our companion piece on recruiting and onboarding bundles for the full structure.
What to do before the next true-up
Three actions, all of them mechanical, should precede every annual SuccessFactors true-up.
- Run the mobile access report from the SuccessFactors admin centre, filtered to the audit period, and reconcile it against the seat-category allocation. Identify the population of mobile-active users without mobile-entitled seats.
- Re-categorise the population — some users will need promotion to a full seat, some can be moved to Frontline, some are inactive accounts that should be deactivated before the true-up declaration.
- Document the seasonal profile if the workforce is variable. The seasonal averaging provision is much harder to negotiate retroactively than prospectively.
The S/4HANA integration consideration
Customers running SuccessFactors alongside SAP HCM on-premise or in conjunction with S/4HANA core HR face an additional licensing layer. Employees who interact with both SuccessFactors mobile and the S/4HANA backend through the mobile app may consume both a SuccessFactors seat and a named user license on the S/4HANA side. The double-count is contractual, not technical, and resolving it requires an explicit named-user exemption clause in the SuccessFactors contract.
For broader context, see our SAP SuccessFactors topic page and the SuccessFactors licensing guide white paper. The global retailer SuccessFactors rollout case file documents a $3.2M Frontline-tier saving achieved through pre-deployment seat right-sizing across 18,000 hourly associates.
The independent advisory question
SuccessFactors mobile licensing sits at the boundary of three procurement disciplines — HXM platform administration, mobile device management, and contract negotiation. The cases where independent advisory pays back fastest are first-time mobile deployments to large frontline populations, M&A integrations where two SuccessFactors estates are being merged, and audit defences where the mobile-user count exceeds the entitled mobile-seat count by more than 15%. For the broader SuccessFactors contract structure, see our SAP License Compliance Assessment service.