On this page
Summarize and analyze this article with
Process Runner and GLSU pricing is not publicly listed, so there is no reliable public figure for a typical licence or journal-workflow deployment. The final SAP Process Runner cost depends on the products, licence units, users, systems, workflow requirements and services included in the customer’s quotation.
For finance teams, the key distinction is between purchasing Excel-to-SAP journal-posting capability and implementing a complete controlled journal process. GLSU addresses journal preparation and posting, while approval workflow may require Easy Workflow, which uses a SQL Server database and has its own licensing and administration considerations.
Promenta packages the requirement differently. Its SAP Journal Entry Management Workflow brings preparation, live SAP validation, approval routing, segregation of duties, posting and audit evidence together under an annual enterprise-wide subscription, with the workflow operating fully inside the customer’s SAP environment.
This article explains the publicly documented Process Runner SAP license model, the additional costs buyers should investigate and how to compare the two approaches over a three-to-five-year period.
Key takeaways
- Process Runner and GLSU do not have a publicly available rate card. Process Runner GLSU pricing is supplied by quotation.
- Process Runner is a modular product family rather than a single package containing every capability.
- GLSU is the finance-focused product for journal preparation and SAP posting; Easy Workflow adds workflow and approval capability.
- Easy Workflow uses a SQL Server database. Depending on existing Microsoft licensing and infrastructure, that can introduce additional operating costs.
- General InsightSoftware legal terms describe several licensing approaches, but the Process Runner SAP licensing model and licensed units applying to a particular proposal are defined in the purchase documentation.
- The most useful comparison is a three-to-five-year SAP journal tool total cost of ownership assessment covering software, implementation, infrastructure and administration, not an unsupported online price estimate.
Is Process Runner pricing publicly available?
No. At the time of publication, InsightSoftware does not provide a public Process Runner or GLSU rate card. Prospective customers are directed to request pricing, while major software-review platforms also describe pricing as available on request or do not display a figure.
There is consequently no defensible public benchmark for :
- one Process Runner or GLSU user;
- a typical finance-team deployment;
- Easy Workflow;
- a particular number of SAP systems or clients; or
- a complete journal-management configuration .
Customer reviews may describe the software as inexpensive or expensive, but they do not reveal the products, users, systems, contract term, services or negotiated discounts included in a particular agreement. Process Runner G2 reviews and pricing discussions, for example, should not be used as evidence of what a specific organisation will pay. The same applies to any Process Runner Capterra cost references that do not disclose the underlying commercial scope.
The practical question is not simply, “How much does SAP Process Runner cost?”
It is: Which products, users, systems, workflows, deployment rights and services are required for the intended journal process?
What needs to be licensed for a journal process?
Process Runner is sold as a modular product family. The products relevant to a finance evaluation can include :
- Process Runner Core: SAP transaction automation across multiple modules;
- Process Runner GLSU: Excel-based preparation and posting of SAP financial transactions;
- Process Runner DB: connectivity between external databases and SAP; and
- Easy Workflow: workflow and approval capability that can be used with journal processes.
For an organisation requiring journal preparation and posting, GLSU is the directly relevant product. Where the intended process also includes controlled submission, approval routing and workflow governance, Easy Workflow may become part of the proposed configuration.
This is why GLSU pricing vs Process Runner pricing cannot be treated as a simple like-for-like comparison without first defining which modules and workflow capabilities are included.
Buyers should therefore document the complete requirement before requesting or comparing quotations:
Excel preparation → SAP validation → submission → approval → posting → supporting evidence → audit reporting
An upload-and-posting requirement and an end-to-end controlled journal process are not the same commercial scope.
The principal Process Runner cost drivers
Insightsoftware does not publish a formula showing how a Process Runner quotation is calculated. The following areas should nevertheless be established during commercial evaluation.
1. Products and functional scope
Confirm which Process Runner products are included and which are separately chargeable. In particular, finance teams should establish whether the proposal covers only GLSU or also includes Easy Workflow and any other required modules.
2. Users and applicable licence units
Insightsoftware’s published terms describe a range of licensing models across its software portfolio. The structure applying specifically to Process Runner, GLSU and Easy Workflow must be confirmed in the customer’s order form.
For organisations comparing Process Runner per-user vs enterprise licence structures, ask the vendor to identify :
- the applicable licence type;
- the number and categories of licensed users;
- whether preparers, approvers and administrators require different rights;
- restrictions on transferring or reassigning access;
- limits applying to workflows, sites, systems or clients; and
- any server, desktop or deployment-specific rights.
3. SAP landscape
A production environment may also involve development, test and quality systems and multiple SAP clients. The quotation should state which systems and clients are covered and how future landscape changes affect the commercial agreement.
4. Implementation and configuration
Journal workflows may need to reflect approval responsibilities, financial-control policies, SAP authorisations, workflow rules and audit requirements. Confirm whether configuration and deployment assistance are included, charged as professional services or expected to be completed internally.
The Process Runner implementation cost for SAP should therefore be assessed separately from the software licence itself.
5. Training, support and upgrades
Request a clear breakdown covering:
- administrator, preparer and approver training;
- user onboarding;
- support and maintenance;
- future configuration changes;
- product upgrades; and
- regression testing after SAP or product changes.
Where applicable, organisations should also clarify whether a Process Runner annual maintenance fee for SAP forms part of the proposal or renewal structure.
6. Expansion and renewal
Ask how pricing changes when the organisation adds users, workflows, sites, SAP systems or Process Runner products. Initial pricing should not be assumed to represent the cost of the eventual enterprise deployment.
Easy Workflow and SQL Server costs
Easy Workflow uses a SQL Server database. Insightsoftware’s documentation states that its licence is associated with the configured SQL Server instance and database and can define limits for users and workflows. See Request Easy Workflow License and About License Management.
Depending on the customer’s existing Microsoft licensing and infrastructure, a workflow-enabled configuration may therefore introduce costs for :
- SQL Server licensing or consumption;
- database hosting and administration;
- security and access management;
- monitoring, backup and disaster recovery;
- patching and upgrade management; and
- audit and governance of a separate database tier.
These costs should not be presented as unavoidable new expenditure for every customer. An organisation may already have suitable SQL Server capacity and licensing. The key consideration for SAP journal tool total cost of ownership is what incremental infrastructure and administrative cost the proposed Easy Workflow configuration creates in that customer’s environment.
How to calculate three-to-five-year TCO and ROI
A useful financial model begins with the current process rather than an assumed software price.
Measure the current annual cost
Calculate the internal time spent on:
- preparing journal data;
- re-keying information into SAP;
- correcting validation and posting errors;
- managing large journal uploads;
- chasing approvals;
- reprocessing rejected journals;
- maintaining supporting evidence; and
- supporting the process during period close.
Convert the hours into a fully loaded employment cost and add any existing infrastructure, administration and quantifiable error or rework costs.
Calculate the proposed annualised cost
Include:
- software subscriptions and licences;
- implementation and configuration, annualised over the evaluation period;
- incremental database and infrastructure costs;
- training;
- support and administration; and
- upgrade and regression-testing costs.
The model can then use:
Estimated annual benefit = current annual operating cost − proposed annualised operating cost
Payback period = one-off implementation and transition cost ÷ estimated annual operating benefit
This provides a more useful basis for assessing SAP journal automation ROI than comparing licence quotations in isolation.
The platform supports SAP ECC and S/4HANA environments and operates as a broader finance automation platform integrated with SAP. Organisations considering Redwood are therefore making a wider automation decision than simply replacing an Excel upload tool.
Treat customer examples as directional evidence
Vendor-published case studies can show the types of processes that may generate savings, but they are not guaranteed ROI benchmarks. Differences in journal volumes, process design, staffing and implementation scope can materially change the outcome.
Finance teams should use case studies to identify measurable activities, then apply their own volumes, time savings and cost base.
Process Runner and Promenta: commercial and architectural comparison
The products cannot be compared reliably through public list prices because Process Runner does not publish a rate card and Promenta proposals depend on the customer’s scope. A more useful comparison considers what must be licensed, implemented and operated to deliver the intended journal process.
This is the practical way to evaluate what companies pay for the Process Runner SAP journal tool: not as a single public price, but as the combined cost of the required products, users, infrastructure, implementation and administration.
Promenta uses an annual enterprise-wide subscription for its SAP Journal Entry Management Workflow rather than licensing individual journal preparers and approvers separately. The precise systems, entities and contractual scope are defined in the customer agreement.
The workflow runs within the customer’s SAP ECC or SAP S/4HANA environment. Core journal preparation, submission and approval are delivered through a web-based interface served from SAP, without requiring a separate external application or workflow server. SAP authorisations and security remain in place.
| Evaluation area | Process Runner GLSU / Easy Workflow | Promenta |
|---|---|---|
| Journal preparation and SAP posting | GLSU | Included – Promenta Journal Management |
| Approval workflow | Easy Workflow is required for the compared workflow configuration | Included – Promenta Journal Management |
| Commercial structure | Modular, quote-based configuration | Annual enterprise-wide journal-management subscription per SAP Landscape |
| Excel preparation | Included with GLSU | SAP-integrated Excel add-in part of Promenta Journal Management |
| SAP validation | Pre-verification and SAP-connected validation capabilities | Live SAP master-data and configured finance validation |
| Pre-posting testing | Confirm the scope of test and functions in the proposed configuration | Validated virtual journal with SAP posting simulation before approval |
| Workflow infrastructure | Easy Workflow uses a SQL Server database | Workflow operates within SAP without a separate workflow database |
| SAP GUI | Required for relevant GLSU client functions | Not required by Promenta Journal Management |
| Approval controls | Determined by the selected Easy Workflow configuration | SAP native routing and segregation-of-duties controls by Promenta Journal Management |
| Audit evidence | Determined by the selected products and configuration | Supporting evidence and audit trail within Promenta Journal Management |
| Published list price | Not published | Not published |
| Quotation basis | Confirm products, users, systems, workflows and deployment rights | Confirm SAP Landscapes in scope and implementation services |
Questions to ask before comparing quotations
- Which products and modules are included?
- Which capabilities require an additional product or licence?
- How are preparers, approvers and administrators licensed?
- Which SAP systems, clients, sites and entities are covered?
- What infrastructure and database software are required?
- Are implementation, configuration and training included?
- What support, maintenance and upgrade services are included?
- How will expansion and renewal affect the price?
- What measurable process savings support the SAP journal automation ROI case?
- What costs should be included across the full evaluation period?
Conclusion
There is no published Process Runner or GLSU price that finance teams can use as a reliable benchmark. What is publicly clear is that Process Runner is modular, GLSU is the finance-focused journal product, and Easy Workflow supplies additional workflow capability using a SQL Server database.
Thus, for teams asking how much SAP Process Runner costs, the answer depends on the specific configuration rather than a standard public price.
Buyers should define the complete journal process before requesting a quote. The evaluation should cover products, users, SAP systems, workflow requirements, implementation, infrastructure, administration and future expansion across a three-to-five-year period.
So, if you are looking for an end-to-end controlled journal process, Promenta provides preparation, live SAP validation, approval routing, segregation of duties, posting and connected audit evidence through an annual enterprise-wide subscription. Its workflow operates within SAP without a separate external workflow database.
Frequently Asked Questions
Is Process Runner pricing publicly listed?
No public Process Runner or GLSU rate card is currently available. Process Runner GLSU pricing is supplied by quotation and depends on the products, licensed units, deployment and services included.
Does GLSU include workflow and approval?
GLSU provides finance-focused Excel-to-SAP preparation and posting capabilities. Easy Workflow is the additional Process Runner product used for the workflow configuration described in this comparison. Customers should confirm the precise product combination required for their process.
Does Easy Workflow require SQL Server?
Easy Workflow uses a SQL Server database. The incremental cost depends on the customer’s existing Microsoft licensing, hosting capacity and administrative model.
What costs should be included in a Process Runner TCO model?
A SAP journal tool total cost of ownership model should include the required products and licensed units, implementation, configuration, training, support, incremental infrastructure, database administration, expansion and upgrade-related testing.
How does Process Runner’s commercial structure compare with Promenta?
Process Runner uses a modular, quote-based configuration. Promenta uses an annual enterprise-wide subscription per SAP Landscape for its journal-management workflow. The exact contractual scope and implementation services should be confirmed in each vendor’s proposal.
Does Promenta publish a list price?
No public list price is used for this comparison. Promenta provides a quotation based on the SAP landscape scope, which is enterprise wide for unlimited users and transactions, avoiding separate per-preparer and per-approver licensing for journal management.