Fit-to-Standard for Finance, without losing control
Fit-to-standard can feel like surrendering control to SAP's defaults. Done well, it is the opposite: you adopt the standard for the 80% of finance that is the same in every company, and spend your energy and budget on the 20% that is genuinely yours.
Why fit-to-standard wins
Standard processes are cheaper to build, faster to upgrade, better tested, and aligned with the SAP Best Practices content that S/4HANA is designed around. Every deviation has a lifetime cost — in build, in testing, and in every future release. Fit-to-standard is simply the discipline of making those costs explicit before you take them on.
Running workshops that work
- Show the standard live. Demonstrate the Best Practices process in a sandbox before discussing requirements, so the conversation starts from “why not this?”.
- Capture deltas, not preferences. Separate “the standard cannot do this” from “we have always done it differently”.
- Decide adopt / adapt / justify. Each delta gets a decision and an owner, recorded in the backlog.
Protecting what matters
Some deviations are non-negotiable: statutory and tax localisation, and the few processes that are a real competitive differentiator. Those justify extension. Legacy habit, undocumented and unowned, does not. The skill is telling them apart — and that takes someone who has seen the standard work at scale.
Key takeaways
- Default to the standard; make the business justify each deviation.
- Separate statutory must-haves from preference and habit.
- Document every decision — the backlog becomes your audit trail.
Control does not come from customising everything. It comes from knowing exactly which few things are worth customising, and why.