SAP SuccessFactors Time Tracking is one of the newer additions to the HXM Suite, and one of the modules that customers most often discover they have already paid for, or in a smaller subset of cases, paid for twice. Its licensing position sits awkwardly between Employee Central, the SAP Time Management offering for on-premise customers, and the broader HXM Time and Attendance category — and the awkwardness translates directly into commercial confusion.
This article walks through what Time Tracking is, how it is licensed within the HXM Suite, the patterns that produce double-counting and double-payment, and the audit and renewal exposures that follow.
What SuccessFactors Time Tracking actually replaces
SAP Time Tracking is positioned as the cloud-native successor to two distinct legacy paths. The first is SAP ERP Time Management — the CATS, PT, and related modules that on-premise customers have used for two decades. The second is Employee Central Time Off, the lighter cloud time-management capability that was bundled with EC for several years. Time Tracking is intended as a single, richer cloud time-and-attendance offering that supersedes both.
Customers migrating from ECC to S/4HANA or to RISE encounter the licensing question at the moment of HXM Suite expansion. Customers already running EC encounter it at the renewal when SAP positions Time Tracking as a separately metered module.
The licensing structure
Time Tracking is licensed per employee, on a subscription basis, within the HXM Suite. The metric is straightforward — total active employees in scope — and the per-employee rate is published in SAP's price list, though significantly negotiable in enterprise deals.
The complication arises in what counts as an active employee for Time Tracking purposes. The default scope is all employees in the EC system, but customers frequently want to scope Time Tracking to a subset — typically hourly or shift-based employees, with salaried employees on a simpler Time Off model. SAP's licensing model accommodates the scoping but requires explicit definition at contract.
The patterns that produce double-payment
The first double-payment pattern is the EC-plus-Time-Tracking overlap. Customers who licensed EC several years ago, with the Time Off capability bundled, who then later add Time Tracking, are sometimes invoiced for Time Tracking as if it were an entirely new capability when in fact some of its functionality is already covered by EC. The defence here is to read the original EC order form carefully and to push back where the Time Tracking scope overlaps with EC's existing entitlement.
The second double-payment pattern is the ECC overlap. Customers who are still operating ECC HR with CATS time entry, in parallel with EC and Time Tracking in a hybrid landscape, can find themselves licensed for both the on-premise time module and the cloud Time Tracking module for the same population. The defence here is to align the licence position with the operational reality — if Time Tracking is the system of record, the on-premise time module should be scoped down at the next renewal.
The third pattern is the contractor inclusion. Time Tracking, like the rest of the HXM Suite, is licensed per active employee, with specific rules about whether contractors and external workers count. The rules differ from the broader EC contractor rules and need to be read carefully at contract — getting this wrong can either over-licence the customer or expose them to a true-up.
The integration question
Time Tracking integrates with EC Payroll, with on-premise SAP Payroll, and with third-party payroll providers. The integration is typically straightforward but each integration touchpoint has implications for the licence position — particularly where time data is being passed to a payroll system that is itself counting users or employees for licensing purposes. The customer's integration architecture and the customer's licence position need to be designed together.
For broader context on the HXM Suite, see our SuccessFactors topic page and the SuccessFactors Licensing Handbook.
The audit angle
SuccessFactors audits are less frequent than ECC or S/4HANA audits but are increasing in frequency as the customer base matures and as SAP's cloud audit practice expands. Time Tracking is one of the modules that audit teams look at, primarily because the per-employee count is straightforward to verify against the customer's EC headcount and any discrepancy is a clear true-up trigger.
The defence in a SuccessFactors Time Tracking audit is essentially a defence of the scope — confirming that the contracted scope matches the deployed scope, that the deployed scope matches the actual users, and that any contractor or external worker inclusion has been handled per the contractual rules. Customers who have not maintained that documentation through the deployment phase are exposed.
What to negotiate at contract
Three elements of the Time Tracking contract deserve specific attention. The first is the scope definition — explicit listing of which employee populations are in scope, with whatever exclusions are needed for salaried, executive, or other non-hourly populations. The second is the true-up mechanism — how the per-employee count is verified, on what cadence, and with what trigger thresholds. SAP's standard mechanism is annual reconciliation; customers with rapidly fluctuating headcounts may benefit from a different cadence.
The third is the price-protection mechanism through the contract term. Standard SAP cloud contracts permit a price increase at renewal, and Time Tracking, as a newer module, is more exposed to renewal increases than some of the more established modules. A negotiated price cap or renewal rate is worth seeking. For renewal negotiation tactics, see our contract negotiation service, the global retailer case file, and the true-up triggers article.
The relationship to broader HCM strategy
Time Tracking is rarely the central element of a customer's HCM strategy, but it is one of the modules where commercial pain is most concentrated relative to functional impact. Customers tend to over-pay for it because it appears small in the suite context, and the audit and renewal teams know that. The right posture is to treat the Time Tracking line item with the same negotiating discipline as any other module — even where the absolute cost is lower, the percentage savings available are typically high. For more on the per-module discipline, see our HXM Suite tier comparison.