Go into an event with a problem you want to understand, and come home with evidence you can use. SAP lists Connect in Las Vegas for October 5 to 7, 2026, with virtual programming October 6 to 7. This is our question guide for payroll teams following the event in person or remotely.
Start with a payroll problem
Before opening the session catalog, name one process you want to improve. It might be an unclear handoff, an exception that takes too long to investigate, or a reconciliation step that depends on one person's memory. Use that problem to choose sessions and frame conversations.
A session can be interesting without answering your question. Write down what you learned and what still needs a follow-up. That distinction makes the recap more useful to the people who stayed home.
Ask what is available, and for whom
When a demonstration catches your attention, ask for the feature name, the relevant product documentation, and its status. Record whether the presenter is showing an available capability, a preview, or a longer-term direction. Check the environments, locations, and prerequisites that matter to your organization.
- Is this available now or part of a roadmap?
- What configuration, licensing, or integration does this require?
- Where can we read the current limitations?
Follow the data through the process
Payroll depends on what arrives from other systems and what happens after a result leaves it. Ask someone to walk through the whole example, including a missing or incorrect input. A useful answer should make the owner of each handoff understandable.
- Which system owns the relevant data?
- How are late changes and exceptions handled?
- What evidence is available for reconciliation and review?
Make an AI demonstration explain its boundaries
Ask what the assistant reads, what it recommends, and what it can actually change. Then ask for the point where a person approves the result. Look for an example of an unsuccessful attempt as well as the polished demonstration.
Bring the same questions to a remote session or a recorded demo. If the answer is not given, record it as a question for follow-up rather than filling the gap with an assumption.
- What happens when the input is incomplete or the answer is uncertain?
- Can the reviewer understand the source and reason for a proposed action?
- How can the team stop, reverse, or investigate an incorrect action?
Ask about the people who will operate it
A feature becomes part of somebody's working day. Ask who monitors it, who handles exceptions, and what the payroll team needs to learn. Discuss what changes for HR, finance, and support colleagues too.
For a customer example, look for the starting situation, the work required to implement it, and the measure used to judge success. Avoid treating a result from a different organization as a forecast for your own.
Bring home a decision, not a pile of slogans
For each promising idea, capture the source, the date, a concise answer, the unanswered question, and a sensible next step. Share a short recap organized around your team's problems. Link to the source so a colleague can check the details.
This guide is PayrollBADIes editorial preparation. It does not announce a speaking slot, an official partnership, or a confirmed crew appearance. Check SAP's current agenda and registration pages for event details.
Make it useful
Your working notes.
Use these prompts on your own or with your team. Notes stay on this page and are cleared when you leave or refresh. Save a copy before you go. Use task descriptions and test examples, not personal employee details.
No signup needed. Your notes are not submitted to PayrollBADIes.
