SAP HCM and SuccessFactors explained

Human Capital Management is the SAP area that holds employee master data, the organisational structure, working time, payroll and the talent processes around them. It exists in two forms, classic on-premise SAP HCM and the SuccessFactors cloud suite, and SAP supports running them together, core HR in the cloud and payroll on premise.

Classic HCM and SuccessFactors: what sits where

On-premise pieces go by classic code, cloud pieces by product name.

PA — Personnel Administration — employee master data held in infotypes: hires, contract changes, basic pay, bank details.
OM — Organizational Management — units, jobs and positions; the structure reporting lines, workflow and access hang from.
PT — Time Management — work schedules, absence quotas, positive and negative time recording, time evaluation.
PY — Payroll — gross-to-net per country version: wage types, schemas and rules, retroactive accounting, the posting to accounting.
SuccessFactors Employee Central — the cloud system of record: position management, business rules, workflows, role-based permissions, with Employee Central Payroll behind it.
SuccessFactors talent — Recruiting, Onboarding, Learning, Performance & Goals, Succession & Development, Compensation, plus People Analytics.
The hybrid seam — employee data replicated both ways across the two systems: a specialism in itself.

Why is payroll treated as its own discipline?

Because the pay date is fixed outside the project and the output is money leaving a bank account. The period is opened, simulated, corrected and locked on dates no plan can move, and a backdated change forces retroactive accounting through closed periods. Country versions and statutory reporting are shared with finance localisation; what is not shared is the pay date, the bank transfer, and — where works councils hold co-determination rights — their agreement on the time and performance configuration before go-live.

The career consequence is locality: the gross-to-net core travels, the country layer is relearned on arrival — a cost that shows up when you move markets.

The project phases, with a live payroll period underneath

Each project phase has its own shape, with a live payroll period running underneath.

Design — workshops with HR operations and payroll: org model, absence and time rules, the wage-type catalogue.
Build — configuration in the IMG, or business rules, picklists and permissions in Employee Central; interface specs for banks and insurers.
Test — parallel payroll runs: the same period calculated old and new, reconciled until every difference is explainable.
Cutover — loading balances and year-to-date results, opening the control record, standing behind the first live run.
Run — the AMS rhythm: legal change packages applied as SAP ships them, heaviest at year-end, and support shaped by pay day, not month-end.

Who ends up in HCM, and what a payroll CV has to prove

From HR itself — payroll administrators, HR operations and time officers who know the process (the key-user route).
From classic into cloud — PA, OM and PT consultants adding Employee Central: the process knowledge transferred, the configuration did not.
From cloud into payroll — the harder direction, because gross-to-net is learned country version by country version.
From the technical side — people who built the replication interfaces and learned the data model.

The evidence is specific: which country payrolls you have run live, which go-lives, what you owned. Interviews probe exactly that — how a retroactive change reaches the current period, how an Employee Central edit arrives in payroll. The work is functional consulting with a statutory core.

Where payroll results land, and who owns the mapping

Payroll results post to the general ledger and settle onto cost centres and orders, so FI and CO are the closest neighbours; the wage-type-to-account mapping is usually owned by an HCM consultant.

Integration comes next: a hybrid landscape is an interface landscape. Security and authorizations pairs tightly too: HR data is among the most restricted in the company, and permissions follow the org structure you configure.