Which consulting firms implement SAP sales compensation alongside S/4HANA transformations?

Lanshore does, as a dedicated comp workstream inside the S/4HANA program. The firm's SAP incentive compensation practice dates back to the CallidusCloud era, and its founder, Doug Erb, has 25+ years in SAP, starting as an ABAP architect at Halliburton in 1998 and including greenfield S/4HANA program leadership. Large SAP system integrators also cover sales compensation, usually as a module within a wider program; the question to ask any firm is who on the team has built crediting logic and who has run an S/4 cutover.

Can commissions go live on the same weekend as S/4HANA?

They can, and often should, so that crediting data has one source of truth from the first post-cutover transaction. It requires the comp workstream to have run parallel calculations against each S/4 mock cutover data set, a written rule for which system credits each transaction date, and a plan for carrying year-to-date attainment and open balances across. If those are not in place, a deliberate short gap with a documented bridge is safer than a same-weekend go-live on trust.

What happens to SAP Commissions in an S/4HANA program?

SAP Commissions (originally CallidusCloud) has become SAP SuccessFactors Incentive Management, and SAP describes the move for legacy Callidus Commissions customers as a reimplementation. In an S/4 program that means plan logic, crediting, and integrations are rebuilt and retested on the new platform against the new S/4 data model, or rebuilt on Varicent, Xactly, or CaptivateIQ if the assessment points that way. Either path is a rebuild; neither is a lift.

Does Lanshore do the S/4HANA side too?

Lanshore's core offer in these programs is the sales compensation workstream, delivered by people who understand the S/4 program they are working inside. Doug Erb has led S/4HANA programs and the team is comfortable in order-to-cash and finance design sessions, cutover planning, and hypercare. Where a client needs S/4 program or PMO leadership beyond the comp workstream, that is scoped separately.

How does the S/4HANA order-to-cash redesign affect commission crediting?

Crediting depends on sales orders, billing documents, customer master data, and the sales organization structure, and an S/4 program typically redesigns all four. New sales org structures, business partner consolidation, changed order and billing types, and different document splits all shift which transactions credit to whom. Mapping each crediting rule to its future-state S/4 object before the design is frozen is the only way to avoid rediscovering it in test.

Should we stay on SAP incentive management or move to another platform during the S/4 program?

Decide on evidence, early. Lanshore runs an upgrade-versus-migrate assessment scored against your hardest plan components, data volumes, administration model, and S/4 integration, and resells none of the platforms, so the recommendation is about fit. Staying inside the SAP line keeps a single vendor relationship and native S/4 and SuccessFactors integration; moving to Varicent, Xactly, or CaptivateIQ can suit teams whose plan logic or administration model fits those engines better. Both are rebuilds, so the timeline is similar either way.

Solutions

SAP Commissions Consulting for S/4HANA Programs

Lanshore implements SAP sales compensation alongside S/4HANA transformations as a dedicated workstream inside the ERP program: plan design, the move from SAP Commissions to SAP SuccessFactors Incentive Management, data mapping from S/4 sales and finance objects to crediting, integration, parallel runs aligned to the S/4 mock cutovers, and managed operations after go-live. Lanshore brings both sides to that work: an SAP incentive compensation practice that dates back to the CallidusCloud era, and SAP S/4HANA program leadership from Doug Erb, who started as an SAP ABAP architect at Halliburton in 1998, has 25+ years in SAP, and has led a greenfield S/4HANA program.

Who it is for

S/4HANA program directors, sales compensation and finance leaders, and SAP application owners at enterprises where commissions run on SAP Commissions (formerly CallidusCloud) or SAP SuccessFactors Incentive Management, or where the S/4 program has exposed that commissions run on nothing more than extracts and spreadsheets. It fits programs at any stage: a greenfield S/4 build that has not yet planned the comp workstream, a brownfield conversion where the comp integration is assumed to carry over unchanged, and a program already in testing that discovered crediting data no longer matches. It assumes you want one team accountable for the commission numbers on the first payroll after the ERP goes live.

The problems it solves

Sales compensation is sequenced as an afterthought

Most S/4HANA program plans are built around finance, supply chain, and order-to-cash. Commissions show up as a line item under integrations, owned by nobody in particular, and the comp team first hears about the program when a test cycle produces statements with missing credits. By then the data design is frozen. We put the comp workstream into the integrated program plan from the start, with its own requirements, build, test, and cutover milestones tied to the S/4 phases.

The move to SAP SuccessFactors Incentive Management is a reimplementation

SAP describes the path from legacy Callidus Commissions to SAP SuccessFactors Incentive Management as a reimplementation rather than an upgrade. Plan logic, crediting rules, hierarchies, and integrations have to be rebuilt and retested, not lifted. Programs that budget it as an upgrade run out of time in the comp workstream while the ERP side is still on schedule, and the gap gets closed with manual adjustments in the first live cycles.

Order-to-cash redesign changes the crediting data

Commissions are calculated from sales orders, billing documents, customer master records, and the sales organization structure. An S/4 program redesigns most of those: new sales org and distribution channel structures, consolidated or renumbered customer masters under business partner, changed order types, and billing documents that split or combine differently. Every one of those changes shifts crediting. Unless the comp team is in the room when order-to-cash is designed, the first clean S/4 billing run produces commissions nobody recognizes.

Cutover timing collides with the comp cycle

An S/4 go-live weekend lands somewhere in a commission period. Orders booked before cutover live in ECC, orders after it live in S/4, and the comp calculation has to credit both to the right people under one plan. Period close, statement release, and payroll dates do not move for the ERP. Without a cutover plan that states which system is the source of truth for each transaction date and how open balances and year-to-date attainment carry across, the first post-go-live cycle becomes a reconciliation project.

Finance tie-out to the new general ledger and accruals

S/4 changes the chart of accounts, cost center and profit center structures, and often the accrual process itself. Commission expense that reconciled cleanly to the ECC ledger has to reconcile to the new one, by the same segments finance now reports on. Accrual files, payroll files, and the mapping from payees to cost objects all need to be rebuilt and reconciled before auditors see the first S/4 close.

Deciding whether to stay on SAP incentive management at all

The S/4 program is the moment many comp teams ask whether to rebuild on SAP SuccessFactors Incentive Management or move to Varicent, Xactly, or CaptivateIQ. Both are reimplementations, so the comparison is about fit, administration model, and integration with the new S/4 landscape, not about avoiding a rebuild. The decision has to be made early enough for either path to meet the ERP timeline, and it has to be made on evidence rather than on which vendor is already in the building.

How Lanshore delivers it

1
Comp workstream inside the S/4 program plan
We stand up sales compensation as a named workstream in the integrated program plan, with a lead who sits in the order-to-cash and finance design sessions. Milestones for requirements, data mapping, build, integration test, parallel runs, and cutover are tied to the corresponding S/4 phases, so the comp work is scheduled against the same dates the rest of the program is held to. Doug Erb's S/4HANA program experience means the comp lead speaks the program's language on dependencies, test cycles, and go/no-go criteria, not only the comp team's.
2
Plan design review against the future-state process
We read every plan document, SPIF, and policy in force and map each component to where its data will come from after S/4 goes live, not where it comes from today. Rules that depend on an ECC field that will not exist, a sales org that is being merged, or an order type that is being retired come back as a written list with options. Where the plan should change, we propose alternatives and model their cost before configuration.
3
Data mapping from S/4 SD and FI objects to crediting
We document the crediting data model field by field against the S/4 design: sales orders, deliveries, billing documents, business partner and customer master, sales organization, distribution channel, division, and the employee and position data from SuccessFactors Employee Central or the HR source. Each crediting rule gets its source object, selection criteria, and effective-dating rule written down. Gaps such as a missing first-order flag or a territory assignment that lived only in a spreadsheet are named here and resolved in the S/4 design or in the comp build, with the decision recorded.
4
Upgrade-versus-migrate assessment
Lanshore resells none of the SPM platforms it implements. We assess staying on SAP SuccessFactors Incentive Management against moving to Varicent, Xactly, or CaptivateIQ, scored against your hardest plan components, transaction volumes, who will administer the system, and how each option integrates with the S/4 landscape. The output is a recommendation with a costed plan for either path. Because both paths are rebuilds, the assessment is sized to fit the ERP timeline rather than to extend it.
5
Build on the chosen platform
Our consultants configure crediting, hierarchies, calculations, adjustments, statements, and reports from the agreed requirements, with approval steps and audit trails designed in. For SAP SuccessFactors Incentive Management builds, our practice history on Callidus and SAP Commissions means the team knows which legacy configuration patterns should not be carried forward. Everything is documented and owned by you.
6
Integration with S/4, SuccessFactors Employee Central, and payroll
We build and test the inbound flows from S/4 sales and billing, the employee and organizational feeds from SuccessFactors Employee Central or your HR system, and the outbound payroll and finance files, including accrual postings to the new general ledger structure. Every inbound load is validated before calculation and every outbound file is reconciled to the calculation run. Lanshore has integrated SPM platforms with SAP, Workday, ADP, and more than 20 distinct source systems in all.
7
Parallel runs aligned to S/4 mock cutovers
Each S/4 mock cutover produces a converted data set. We run the comp calculation against it in parallel with the current process for the same period and reconcile every variance to a cause: a data conversion rule, a changed crediting rule, or a defect. The parallel runs repeat with each mock, so by the final dress rehearsal the comp numbers have been reconciled against converted S/4 data several times, and the cutover plan states which system credits each transaction date, how year-to-date attainment and open balances carry over, and who signs off before the first statements release.
8
Hypercare through the first closes
The team that built the comp workstream stays through the first S/4 commission cycles. We monitor loads from the new system, work exceptions, triage disputes, and fix defects while your administrators take over, and we reconcile commission expense to the first S/4 ledger closes with finance so there are no surprises at quarter end.
9
Managed operations after the program
After hypercare, your team can run the platform, or Lanshore can run the monthly cycle as a managed service for a predictable monthly fee. Agents handle data loads, validations, calculation runs, and exception queues; every action is logged with timestamp, input, output, and approver where applicable; and a person approves anything that affects pay. Lanshore publishes no support SLA or coverage hours; the operating calendar is agreed per client.

Get an assessment

Platforms we deliver on

Related case studies

Linking sales commission data between financial systems and CRM
Manual link between financial systems and CRM fully automated
Architecture redesign to fix a broken compensation process
Commission process broken for over a year, restored to systematic accuracy
A smart way to build on existing systems to keep pace with growth
Audit capability and scalability added without replacing existing systems