One of the hardest questions we hear for SAP S/4HANA Functional Consultant (Finance) roles is: “Walk me through how you run a Fit-to-Standard workshop for Record-to-Report, and what you do when the business asks for a customization that conflicts with standard.” What interviewers listen for In SAP consulting interviews, this question often tests whether you can operate end-to-end, not just list configuration steps. Strong signals include: Structured delivery thinking: a clear sequence (prepare, run, decide, document, follow-up). Fit-to-standard mindset: you anchor on standard process first, then evaluate gaps. Requirement triage: how you classify requests (must-have vs nice-to-have, compliance vs preference). Stakeholder management: handling conflict, decision rights, and change control. Test strategy linkage: how decisions flow into WRICEF scope, testing, and cutover readiness. Risk and integration awareness: downstream impacts (CO, tax, treasury, reporting, interfaces). A strong answer structure (use this in 2 to 4 minutes) Context: scope (R2R sub-processes), workshop goal, who’s in the room. Pre-work: process maps, pain points, baseline data, demo script, decision log template. Facilitation: show standard in S/4HANA, confirm process variants, capture gaps as user stories. Decisioning and triage: assess regulatory need, value, complexity, integration impact, and timeline. Recommendation: default to standard, propose alternatives (process change, configuration, extension) with tradeoffs. Governance: align on approvers, document in a backlog, manage change requests, confirm next steps. Validation: map outcomes to test cases (SIT/UAT), controls evidence, and readiness criteria.
If you want feedback, post your answer in 6 to 10 sentences: include one example of a “customization request” and exactly how you guided it to a decision.
What would your decision criteria be when the request is framed as “the CFO insists we must do it this way”?