Solutions BlogSuccessFactors7 min readOctober 2026

SuccessFactors Employee Central to third-party payroll: getting delta replication right

Effective dating, future-dated changes and terminations break simple payroll interfaces. How to design a delta replication payroll teams can trust.

By the Klynexa integration team

Applies to
SAP SuccessFactors Employee Central, SAP Integration Suite
APIs
Compound Employee API, OData v2
Receiver
Third-party payroll providers

The problem

A payroll interface works in testing, then the first live cycle shows missing pay changes, duplicated employees and terminations that arrived too late. The cause is almost always the same: Employee Central data is effective-dated, and the interface treated it like a simple table.

What makes it hard

  • Effective dating: a record can be created today for a change that takes effect next month, or corrected for a past date.
  • Multiple records per period: one employee can have several job or compensation records in the same pay period.
  • Terminations and rehires: these change employment records, not just a status field.
  • Cutoff dates: payroll needs a stable snapshot, while HR keeps working.

The design

  • Use an interface built for replication, such as the Compound Employee API, or OData with change-based filtering, rather than full extracts.
  • Select by last modified time since the previous successful run, and request the full effective-dated history for changed employees, not just the current record.
  • Store the timestamp of the last successful run only after the payroll provider confirms receipt.
  • Map effective dates explicitly, so the provider applies each change to the correct period.
  • Send terminations, rehires and global assignments as clearly flagged events.

An OData request for job records changed since the last run, including their effective-dated history:

/odata/v2/EmpJob?$filter=lastModifiedDateTime ge datetimeoffset'2026-10-01T00:00:00Z'
    &fromDate=1900-01-01
    &$select=userId,startDate,endDate,company,payGroup,lastModifiedDateTime

Operate it safely

  • Reconcile headcount and changed-employee counts between Employee Central and payroll every run.
  • Freeze the extraction window at payroll cutoff, and route late changes to the next cycle with a report.
  • Protect personal data in logs: no payloads in traces in production.

Result

Payroll receives exactly the changes it needs, in the right period, every cycle, and HR and payroll teams can prove it with a reconciliation report.