Clean Core in practice: staying upgrade-ready
“Clean Core” is usually stated as a prohibition — don't modify the standard. In practice it is something more useful: a set of decisions about where and how you extend S/4HANA. For Finance, getting those decisions right is what keeps the system cheap to upgrade, easy to audit, and ready for SAP's cloud innovations.
What Clean Core actually means
It means keeping the digital core close to standard and pushing customisation outward through governed, released mechanisms: key-user extensibility for fields and simple logic, and side-by-side extensions on SAP BTP for anything heavier — all built on public APIs and released events, with data, integrations and processes kept inside governed boundaries.
Where Finance teams break it
- In-app modifications to standard objects that then block upgrades.
- Custom tables shadowing the Universal Journal, so reporting drifts from the single source of truth.
- Uncontrolled Z-developments with no owner, no documentation and no API.
A pragmatic Clean Core for Finance
Adopt SAP Best Practices first and treat the standard as the default answer. Use key-user tools for custom fields, validations and simple logic. Reserve BTP side-by-side for genuine differentiators and heavy integration. And govern it: a short extension catalogue that records what was built, why, and through which pattern is worth more than any policy slogan.
Key takeaways
- Clean Core is a spectrum of choices, not an on/off switch.
- Decide the extension pattern before the build, not during it.
- Every extension needs an owner, a reason and an API.
Done well, Clean Core is not a constraint on the business — it is what lets the business keep taking SAP's innovations without a re-implementation every few years.