A global investment bank rebuilt its SAP HCM FTE engine measurement methodology, separated active payroll FTEs from non-payroll headcount and contingent workers, and reduced an $8.9M claim to $2.1M.
Every result on this site is anonymised at the client's request. Specific figures are real and verifiable through a confidentiality-protected reference call arranged on request.
The bank ran SAP HCM as the global payroll-and-personnel administration platform, with SuccessFactors EC layered on for talent management. The HCM FTE engine was licensed against a contracted tier of 95,000 full-time equivalents. The 2024 self-declaration produced a count of 112,000 FTEs, triggering an $8.9M overage claim on the 17,000-FTE excess.
The declared figure was generated by the standard HCM headcount report run against the global personnel administration table. The report counted every active personnel record across the global instance, regardless of administration status, payroll inclusion, or employment category. The internal HR-systems team had submitted the figure without further filtering on the assumption that headcount was a deterministic measure.
The 112,000 figure was approximately 23 percent above the bank's publicly reported employee count for the same year. The discrepancy was the trigger for re-examination. The publicly reported figure was 91,200 FTEs. The 21,000-person gap had to be in the HCM data set somewhere.
SAP's opening position rested on the 112,000 declared figure. The workpaper applied the contracted tier-overage rate to the 17,000 excess, producing the headline $8.9M claim. There was no further analysis of the FTE composition.
We obtained the full personnel administration table for the measurement year and applied the categorical breakdown that distinguishes payroll-active FTEs from the various non-payroll record categories. The breakdown produced six categories: 89,400 payroll-active FTEs, 8,200 contingent-worker records administered in HCM but paid externally, 7,100 inactive-or-suspended records retained for compliance purposes, 4,200 retiree-pension records, 1,900 board-and-non-executive director records, and 1,200 dual-employment records counted twice across regional instances.
Only the first category — 89,400 payroll-active FTEs — matched the contract definition of an HCM FTE subject to the engine metric. The remaining 22,600 records fell into categories that were either administered-but-not-paid, inactive, dual-counted, or otherwise excluded under the contract. The defended count was below the contracted 95,000 tier ceiling with no overage at all.
The defence ran on four workstreams. The first documented the categorical breakdown with personnel-administration evidence, employment-status filters, and per-category samples. The samples were submitted to SAP with employment-contract evidence for a representative sample of each category.
The second workstream addressed the contingent-worker category — the 8,200 records. The bank administered contingent workers in HCM for compliance reasons but paid them through external vendor-management systems. The HCM engine definition referenced "FTEs processed through SAP payroll," and the contingent workers were demonstrably not processed through SAP payroll. The contractual exclusion was uncontroversial once the payroll-processing flag was demonstrated.
The third workstream addressed the inactive-and-suspended records — the 7,100 records. Under banking-sector regulatory requirements, personnel records must be retained for several years after employment termination for compliance and audit purposes. The HCM engine definition referenced "active FTEs," and the retained records had a documented inactive status. The exclusion required citation of the employment-status field and a sample audit trail.
The fourth workstream addressed the dual-employment records — the 1,200 cases of regional double-counting. The bank's regional instances each maintained personnel records for cross-region assignments, with the same individual counted in multiple regions. The contractual engine should count distinct FTEs, not record-instances. The deduplication was demonstrated through the global personnel ID field. The counter-position offered the defended count of 89,400 payroll-active FTEs as the current measurement, with a $2.1M goodwill payment to close the historical period and a contract amendment refining the HCM engine definition to explicitly exclude the non-payroll categories.
Settlement closed at the proposed $2.1M figure with the proposed amendment. The current measurement was accepted at 89,400 FTEs, below the contracted tier ceiling. The amendment incorporated the categorical filtering protocol as a binding measurement methodology for future declarations. The reduction against opening was 76 percent.
The amendment was particularly valuable because the bank's contingent-worker population was growing as the firm shifted to a more flexible workforce model. Without the explicit exclusion, the next declaration cycle would have produced a similar over-count and a similar claim. With the exclusion in place, the contingent-worker growth was demonstrably outside the FTE engine entirely.
Total elapsed time from engagement to executed settlement was eighteen weeks. The reduction against opening was 76 percent. The HR-systems team adopted the categorical reporting as a quarterly licence-position review.
Further detail on the methodology behind the defence is set out in the Engine Metrics Reconciliation white paper. For the broader topic context, see the cluster pillar on Engine metrics, the cluster pillar and the deep dive on HR FTE engine metric explained. The topic landing at SuccessFactors provides the broader category context.
A pre-audit examination of named users, engine measurements, and indirect-access pathways. We surface the exposure before SAP does, and we quantify the remediation cost.
Read the brief →Reclassify users. Retire shelfware. Right-size engine metrics. The continuous reduction programme that runs between the audit cycles, year after year.
Read the brief →The cluster pillar covering measurement methodology, contractual definitions, and the standard defence patterns for the engine in question.
A global bank renegotiated its SuccessFactors EC and Compensation modules and removed $4.8M from a renewal forecast.
A multinational CPG group rebuilt its FI and SD engine measurements and removed $7.2M from a self-declaration claim.
It is the opening position of a negotiation. Speak with a specialist before responding. The first conversation is at no cost and under privilege.
Contact Us →Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.