Quick answer: Promenta’s SAP journal entry add-on runs inside SAP ECC, S/4HANA On-Premise and RISE with SAP S/4HANA Cloud, Private Edition. It installs through standard SAP transport, uses existing SAP roles and authorisations, and needs no external servers, middleware or data replication. SAP S/4HANA Cloud, Public Edition is not currently supported.
Finance and IT teams evaluating a journal entry tool need one question answered first: will it run inside the SAP landscape they already operate, or will it add infrastructure they have to buy, secure, and maintain?
Promenta’s SAP journal entry add-on is certified by SAP and runs inside the customer’s own SAP system. It supports SAP ECC, S/4HANA On-Premise, and RISE with SAP Private Edition, which makes compatibility with RISE with SAP a settled question rather than an open risk. No external server sits between the finance team and the ledger.
Key takeaways
Which SAP versions does the SAP journal entry add-on support?
| Deployment model |
Supported |
Notes |
| SAP ECC 6.0 |
Yes |
Runs inside the existing ECC system. |
| S/4HANA On-Premise |
Yes |
Runs inside S/4HANA On-Premise. |
| RISE with SAP (S/4HANA Cloud, Private Edition) |
Yes |
Runs inside the customer’s RISE Private Edition tenant. |
| SAP S/4HANA Cloud, Public Edition |
Not currently supported |
Public Edition’s architecture does not allow on-stack ABAP add-ons. See the section below. |
Because Promenta extends SAP as an SAP native journal entry workflow rather than operating alongside it, the supported-version question is really a question about the SAP system itself. Wherever a customer runs a supported SAP finance environment, the journal workflow runs in the same place, validating against the same live data and the same security model.
SAP ECC mainstream maintenance ends on 31 December 2027, with optional extended maintenance to the end of 2030, so an SAP ECC journal entry tool that also runs in S/4HANA matters for teams that want journal control in place now and carried through their eventual migration.
Does Promenta work with RISE with SAP S/4HANA Cloud, Private Edition?
Yes. Promenta is a supported RISE with SAP add-on for S/4HANA Cloud, Private Edition, and runs inside the customer’s own tenant.
RISE introduces a shared-responsibility model, and this is where IT buyers have genuine questions. Under RISE, SAP manages the underlying infrastructure and platform, while the customer retains the application layer: user roles, authorisations and segregation of duties. The journal workflow operates entirely within that customer-controlled application layer, which is why it fits a RISE landscape without compromising the governance the finance team is accountable for. For teams planning the move, our guide to SAP journal entry management in S/4HANA Private Cloud covers the migration view in detail.
Who manages what under RISE :
| Layer |
Managed by |
What it means for journal control |
| Infrastructure, hosting, database and technical upgrades |
SAP |
Promenta adds nothing to this layer. |
| User roles, authorisations and segregation of duties |
Customer |
Promenta uses these existing SAP controls. |
| Promenta journal workflow |
Customer-controlled application layer |
Validation, approvals and audit evidence stay under finance governance. |
Is SAP S/4HANA Cloud, Public Edition supported for add-ons?
Not currently. S/4HANA Cloud Public Edition is a standardised, multi-tenant SaaS environment, and its architecture does not permit the installation of classic ABAP add-ons on the SAP stack. Extensibility in Public Edition is confined to SAP’s clean-core model: key user extensibility, developer extensibility inside the SAP S/4HANA Cloud ABAP Environment using only released SAP objects and APIs, and side-by-side extensions built on SAP BTP. A certified add-on delivered through standard SAP transport, which is how Promenta is installed in ECC, S/4HANA On-Premise and RISE Private Edition, is an on-stack installation model that Public Edition does not accommodate.
This is a property of the Public Edition itself, not a Promenta-specific limitation. Any transport-installed finance add-on faces the same constraint in that environment. For organisations running Public Edition, or weighing it against Private Edition for finance workloads, the practical first step is a short technical conversation about where journal control should sit. Our guide to cloud-ready SAP journal entry management compares the deployment models.
Is SAP GUI required for end users?
Promenta gives finance users a web interface alongside the SAP-integrated Excel Add-in used to upload journal entries in SAP S/4HANA. Journal preparation and approval workflows run through Excel or the web interface, so SAP GUI is not the required entry point for day-to-day journal work. This matters as more organisations move finance users towards Fiori-led or browser-based access and reduce locally installed desktop components. The result is reduced reliance on SAP GUI for core journal processing, which keeps the workflow aligned with a modern S/4HANA access strategy.
Does the add-on need external servers, middleware or data replication?
No. Promenta is Built Natively on SAP, which means the journal process has nothing to install outside the SAP system. Journal data, approvals, and audit evidence stay inside the SAP security boundary throughout the lifecycle.
This has a direct consequence for IT and audit. There are fewer systems to govern, audit scope stays within a single environment, and there is no external integration to re-test every time SAP is upgraded.
How is the SAP journal entry add-on installed?
Promenta’s SAP Journal Entry Management solution is delivered as a certified SAP add-on and installed through standard SAP transport into the customer’s own system. It uses the existing SAP security model, so finance and IT work with the users, roles and authorisations already in place. No parallel user directory or separate security layer is introduced.
Deployment summary : one journal path in every supported SAP environment
Promenta’s SAP journal entry add-on supports SAP ECC, S/4HANA On-Premise and RISE with SAP Private Edition, running inside the customer’s SAP system in every case. The journal path is the same wherever it runs :
Prepare → Validate → Submit → Route → Review → Approve → Post → Audit
Three questions worth asking of any journal tool before you commit to it:
Frequently Asked Questions
