In this conversation
The context behind the clip.
Shahzad Naseem joins PayrollBADIes to discuss the reasoning behind SAP's SmartRecruiters acquisition and the relationship between recruiting capabilities, AI, and the wider HR landscape. The conversation also turns to the vision for autonomous payroll and reconciliation.
For: SAP payroll and HR teams following recruiting strategy, integration, and AI agents.
What we get into
- The discussion examines the applicant tracking capabilities behind the acquisition decision.
- Shahzad and the crew explore Joule, Winston, and questions about how HR applications could evolve.
- The closing sections cover the payroll-agent vision and questions about SuccessFactors Recruiting and onboarding.
Questions this conversation opens up
Why did SAP choose SmartRecruiters?
In this December 2025 conversation, Shahzad explains the acquisition through recruiting capability and the evaluation of applicant tracking systems. The discussion looks beyond an AI demonstration to the underlying recruiting product. It is an account of the decision at that time.
Try this with your team: Build your own evaluation around a real hiring journey. Ask a vendor to show how a candidate becomes a hire, where approvals happen, and how the resulting information reaches the systems your team relies on.
What should payroll ask about a recruiting system change?
The interview connects the acquisition with questions about SuccessFactors Recruiting and onboarding. That makes the handoff into the wider HR landscape a useful topic for payroll teams to bring into the conversation.
Try this with your team: Map the handoff from accepted offer to employee record. Assign an owner to each field and approval, then test a late change, a missing value, and a duplicate record. Use those scenarios to ask specific integration questions before selecting a solution.
What does autonomous payroll mean in this interview?
Shahzad describes a vision involving payroll agents, including reconciliation and alerts. These are roadmap discussions recorded in 2025, not a current availability list, a performance guarantee, or a commitment for a particular customer environment.
Try this with your team: Ask for a demonstration of one defined reconciliation task. Identify the records compared, how an exception is explained, who approves a correction, and what history is retained. Confirm current availability and prerequisites in official product documentation before making an implementation decision.
Bring it back to your team
This is an archive conversation published on YouTube in December 2025. Roadmap statements describe the discussion at that time. Use current official product information when making a migration, licensing, or implementation decision. Start by identifying the process you need to improve and the systems that will remain responsible for its data.
- Which recruiting problem is a new system expected to solve?
- What data must pass accurately from recruiting into core HR and payroll?
- What evidence would demonstrate that an agent improves reconciliation?
