SAP S/4HANA Archives

Journal Entry Approval Workflow in SAP S/4HANA: How It Works, How to Set It Up, and Where It Falls Short

Posted on August 25, 2026October 1, 2026 by by promenta

The journal entry approval workflow in SAP S/4HANA is managed through General Journal Entry Verification, a native SAP Fiori capability that routes general ledger entries to designated approvers before posting. Finance users submit the journal; the system evaluates configured conditions and assigns a processor; the approver reviews and either approves or rejects the entry. Once all required verification steps are complete, the journal progresses to posting.

Approving journal entries before they post is a vital financial control.

A journal entry approval workflow in SAP S/4HANA ensures that selected entries are reviewed and authorised before they are posted – using a native mechanism called General Journal Entry Verification, which allows journal entries to be submitted for review and routed to the appropriate approver.

For finance teams, however, approval is only one part of the journal process.

The wider control question is whether the journal has been prepared correctly, validated against SAP standards, supported with the required evidence, routed according to the organisation’s policy and retained with an end-to-end audit trail.

This article explains how the journal entry approval workflow in SAP S/4HANA operates, how the standard verification process is configured and where organisations may need additional journal management controls.

While this article focuses on SAP S/4HANA, the same approval principles and limitations apply to SAP ECC environments, where Promenta also operates natively.

What Is the Journal Entry Approval Workflow in SAP S/4HANA?

SAP S/4HANA uses General Journal Entry Verification – its native general ledger approval mechanism – to manage which journal entries require review before posting.

A finance user creates the journal and submits it for verification. An active workflow evaluates the conditions defined by the organisation and determines whether verification is required and who should receive the journal.

The designated person can then review the accounting information and take the appropriate action.

Where multiple verification steps are required, the journal progresses through the configured sequence before it can complete the process.

This is crucial, because the journal entry approval workflow in SAP S/4HANA is not simply the act of passing a journal from one person to another.

Its value as a financial control comes from ensuring that the required review takes place against a planned approval process, before the journal is allowed to progress through to posting.

It is also useful to distinguish journal upload from journal verification.

SAP provides standard functionality for uploading general journal entries from spreadsheet files. General Journal Entry Verification is the workflow capability used to control review and approval.

Though these are related activities, they are not the same process.

In SAP S/4HANA, General Journal Entry Verification is supported by three Fiori apps: the Verify General Journal Entries app for requesters (F2547), and two processor apps – the Inbox (F2728) and Outbox (F2729). The process is driven by standard Workflow Scenario WS02800046, which organisations configure and extend through the Manage Workflows for General Journal Entry Verification Fiori app.

SAP ECC mainstream support ends 2027. See how Promenta keeps journal control inside SAP through the transition.

Journal Entry Approval Workflow in SAP S/4HANA: Step by Step

The exact applications and options available can vary depending on the S/4HANA deployment and release, but the standard approval process broadly follows these stages.

1. Create the journal entry

Step 1: Create the Journal Entry. The requester prepares the journal, including relevant accounts, amounts, company code, and any required supporting information.

The journal contains the accounting information required for posting, including the relevant accounts, amounts, company code and other financial dimensions.

Supporting information may also need to be provided depending on the organisation’s control requirements.

2. Submit the journal for verification

Step 2: Submit for Verification. Once the entry is ready, the requester submits it into the verification process, creating a formal control point before approval or posting.

This creates a formal control point between journal preparation and the subsequent approval or posting activity.

The journal’s status also becomes visible within the workflow rather than relying on separate emails or manual follow-up.

3. SAP determines the approval route

Step 3: SAP Determines the Approval Route. The active workflow evaluates configured conditions and determines which verification process and approver should apply

Approval routing can reflect criteria relevant to the organisation’s financial-control model, such as:

So, different journals can follow different approval paths.

A routine lower-value entry may require a relatively simple process or no approval, while a higher-value or higher-risk journal usually requires additional verification.

4. The approver reviews the journal

Step 4: The Approver Reviews the Journal. The designated approver reviews the journal and the available information to make an informed decision.

The approver needs sufficient information to determine whether the journal is appropriate and the required financial controls have been followed.

Depending on the configured process, the approver may approve, reject, or suspend the journal.

5. The journal progresses towards posting

Step 5: The Journal Progresses Towards Posting. Once all required verification steps are complete, the journal continues through the configured process towards posting.

This connects approval to the journal lifecycle.

Where additional approval levels have been configured, each required step must be completed according to the workflow design.

6. Workflow status remains traceable

Step 6: Workflow Status Remains Traceable. The workflow provides full visibility into the journal’s progress status and the actions taken during verification.

Requesters and finance teams can see whether an entry is awaiting action, approved or rejected. They do not need to maintain a separate approval tracker.

This creates the basic SAP journal approval path:

The next consideration is how that routing is configured around the organisation’s own policies.

How to Configure Journal Entry Approval in SAP S/4HANA: General Journal Entry Verification

SAP journal entry workflow configuration for General Journal Entry Verification is managed through standard SAP workflow-management functionality.

At a high level, organisations define:

When verification should apply : Preconditions determine which journal entries enter a particular workflow.
The sequence of verification steps : The workflow defines whether one or multiple review stages are required.
Who should verify the journal : Responsibility can be determined according to the organisation’s defined approval structure.
How exceptions should be handled : Workflow behaviour can reflect different outcomes and processing requirements.
Which workflow is active : The required workflow must be configured and activated for the relevant scenario.

Thus, while SAP provides the framework for journal verification, the organisation still needs to translate its financial-control requirements into that framework i.e. design and build the workflow.

Approval thresholds, responsibilities, organisational structures and exceptions all need to reflect the way the finance function operates.

That becomes particularly relevant as entities, approval responsibilities or control policies change.

What Are the Limitations of SAP S/4HANA Journal Entry Approval?

General Journal Entry Verification provides an important approval control.

But approval is not the complete journal lifecycle.

Finance teams must also consider what happens before the approval starts and what evidence remains after the journal posts.

Excel preparation and SAP upload remain separate considerations

Excel remains widely used for journal preparation because it is practical for calculations, analysis, and complex financial data – a dynamic explored further in our guide to automated vs manual journal entries.

However, the manual entry process is not the biggest challenge here; it is how the spreadsheet connects to SAP.

SAP’s standard functionality for uploading general journal entriesallows journal information to be transferred from a spreadsheet into S/4HANA. This can remove some direct screen entry, but a file-based upload is different from having SAP functionality available inside Excel during preparation.

A deeper Excel-to-SAP process can provide controls while the journal is still being prepared, including:

The distinction is not simply whether SAP can receive an Excel file.

It is the degree of SAP control available before that file reaches the posting stage.

Approval does not replace early validation

Approval establishes whether the journal has been authorised.

Validation establishes whether the journal data itself is acceptable for posting.

A journal can be properly approved and still contain an account, cost object, period or other value that causes a posting problem later.

Therefore, the timing of validation matters.

If a material SAP error is discovered only after a journal has completed several approval stages, the entry may need to be corrected, resubmitted and approved again.

This creates unnecessary work during the close period, when finance teams are already under time pressure.

A better journal entry process offers more control and moves validation closer to preparation.

See Promenta's SAP Journal Workflow in Action

Built natively on SAP. No external servers, no duplicate financial data.

The aim is to identify avoidable posting problems before approvers spend time reviewing the journal.

Approval and validation serve different purposes.

A controlled process needs both.

Workflow administration can become a practical issue

Approval requirements rarely remain static.

People change roles. Organisations restructure. Approval thresholds are revised. Substitute approvers are needed during leave or close periods.

SAP provides configurable workflow capabilities, but organisations still need to consider how teams can easily maintain day-to-day approval structure.

If every routine change requires technical intervention, workflow administration can become another source of delay.

Finance teams therefore need to assess not only whether a workflow can be configured, but also how easily authorised users can maintain approval teams, thresholds, hierarchies and substitutes as operating requirements change.

High-volume journals need additional handling

Control requirements do not disappear when journal volumes increase.

Month-end and year-end can involve large journals, multiple requests and significant volumes of accounting adjustments moving through a limited close window.

Relevant standard SAP journal upload and verification scenarios can also encounter line-item constraints around large journal documents.

For finance teams processing entries beyond those limits, the process may need to divide the journal into multiple balanced SAP documents while maintaining the required validation and approval controls.

The same issue applies when several journals are prepared together.

Efficiency at close depends on being able to process volume without creating a separate manual control process for each journal.

Approval evidence needs to form part of the wider audit trail

Recording an approval action is useful.

However, for audit purposes, organisations may need to demonstrate substantially more than the final approval – a challenge explored in detail in our guide to SAP journal entry compliance.

That can include :

Who prepared the journal
What information supported it
What validation occurred
When it was submitted
Who reviewed and approved it
Whether it was rejected or amended
What supporting documentation was attached
When it was posted
Whether it was subsequently reversed

Thus, finance teams should also oversee whether the complete journal lifecycle can be reconstructed and reported from a connected control record.

How to Extend SAP Journal Entry Approval Beyond the Native Workflow

For organisations that require more than journal verification alone, Promenta brings Excel preparation, SAP validation, approval, posting and audit evidence into one controlled journal process.

It operates natively within S/4HANA (and ECC) instead of introducing a separate external platform into the core journal path.

SAP-integrated Excel preparation

Finance teams can continue working in Excel using the Promenta Excel Add-In , which connects directly to SAP during journal preparation.

Instead of preparing a disconnected spreadsheet and uploading it at the end, users can access SAP-connected functionality while the journal is being created.

This includes capabilities such as dynamic SAP picklists, add or remove journal fields, validation of all journal data prior to posting, as well as direct workflow submission from Excel ensuring strong compliance control.

Promenta also provides a Template Manager which supports multiple Excel journal templates e.g. GL, AP, AR, Recurring, Intercompany etc.

Even if Excel remains the preparation environment, the controls around it improve and journal risk is diminished.

Validation before approval

Promenta creates a fully validated virtual journal document and runs a full simulated SAP posting at the request stage.

This means the journal is tested against the SAP environment before it moves through approval.

Errors can be returned to the requester while the entry is still being prepared rather than after a multi-stage approval process.

That changes where rework occurs.

An issue corrected before submission creates far less disruption than the same issue discovered immediately before posting.

This capability is possible because Promenta runs natively inside S/4HANA, the system of record, unlike alternative external or cloud based solutions.

Journal-specific configurable workflow

Promenta provides an enterprise journal workflow designed specifically around documented financial approval rules and compliance requirements.

Routing can reflect any combination of fields available in the journal e.g. governed by company code, value, GL etc. and incorporates:

Multiple approval levels
Approval hierarchies
Approval teams
Substitute approvers
Segregation of duties
Self-approval prevention
Rejection and resubmission
Mandatory supporting information

The workflow is highly configurable without requiring every routine business change to become a coding exercise.

This allows the approval model to remain aligned with the organization as responsibilities and control requirements change.

Controlled posting and connected audit evidence

A journal does not progress simply because its spreadsheet has been uploaded.

Validation, approval and other required controls form part of the path towards posting.

The resulting journal history retains the preparation, supporting documentation, validation, approvals, rejections, amendments and posting activity as part of a reportable audit record.

This makes audit evidence a product of the process — finance teams do not need to reconstruct it after the close.

SAP-native architecture

Where the workflow operates is also a governance consideration.

Promenta runs within S/4HANA and SAP ECC, allowing the journal process to remain aligned with the organisation’s SAP users, authorisations, master data, finance configuration and security environment.

Sensitive journal information need not be moved to a separate external platform for the core workflow.

For organisations running SAP ECC as well as S/4HANA, the same journal entry approval principles and process limitations apply – Promenta’s solution addresses both environments natively.

This reduces the additional infrastructure, integrations and governance boundaries associated with managing the process across multiple non-SAP systems and environments.

Promenta has partnered with SAP for over 20 years and has been an SAP-certified partner since 2004, developing its Journal Management capabilities specifically for SAP finance environments.

SAP S/4HANA Native Journal Approval vs Promenta Journal Management: Feature Comparison

The table below shows how standard SAP S/4HANA journal approval compares with Promenta Journal Management across the wider journal process.

Area	Standard SAP S/4HANA	Promenta Journal Management
Journal upload	Standard spreadsheet-based upload capability	SAP-integrated Excel Add-In capable of deep SAP finance validation in the Excel context, add/remove journal fields, template manager, park, post, send-to-workflow
Excel preparation	Spreadsheet prepared for subsequent upload	Excel connected directly to SAP functionality during preparation
Templates	Standard upload structure	Template Manager supporting multiple journal templates
SAP validation from Excel	File-based upload process	Real-time SAP integration, deep transactional validation and dynamic picklists
Approval	General Journal Entry Verification configured for organisational requirements	Pre-built and proven journal-specific configurable workflow software
Pre-approval validation	Depends on the standard process and configuration used	Fully validated virtual journal with simulated posting before approval
Segregation of duties	Depends on workflow and SAP authorisation configuration	Journal-specific SoD controls and self-approval prevention
Workflow administration	Configured within the standard SAP workflow framework	Highly configurable journal workflow with no-code administration
High-volume processing	Standard upload and document constraints apply	Supports larger and multiple journals through the controlled process
Audit evidence	SAP journal and workflow records	Continuous, reportable preparation-to-posting journal audit trail and external support documentation storage against the SAP finance document

The standard SAP process may be suitable for organisations requiring a relatively straightforward journal verification model.

A broader journal management solution becomes more relevant when finance teams also need deeper Excel integration, earlier SAP validation, flexible journal-specific routing, high-volume processing and connected audit reporting.

Conclusion

For organisations evaluating a journal entry approval workflow in SAP S/4HANA, the native General Journal Entry Verification mechanism provides an important starting point.

As the journal volumes, entities and approval requirements increase in complexity, finance teams need to consider whether enhanced SAP partner tooling like Promenta is more appropriate to meet their process needs.

The process also needs to address how journals are prepared, when they are validated, how segregation of duties is enforced, how easily approval structures can adapt, and whether supporting evidence remains connected throughout the journal lifecycle.

Promenta extends the process beyond simple upload by connecting Excel preparation, live SAP validation, simulated posting, configurable workflow, controlled posting and audit evidence within SAP.

The result is a journal process designed to identify issues earlier, enforce the required controls before posting and maintain an end-to-end audit trail, supporting SAP finance teams to mitigate journal risk and pass audits.

If those questions are difficult to answer, the issue may lie less with journal preparation itself and more with the process surrounding it.

Frequently Asked Questions

How do you approve a journal entry in SAP S/4HANA?

In SAP S/4HANA, a journal entry that requires verification is created and submitted into the General Journal Entry Verification process.

The configured workflow determines which approver or processor should receive the entry. The approver reviews the journal and can take the appropriate action, such as approving or rejecting it.

Once all required verification steps have been completed, the journal can progress through the configured process towards posting.

What is General Journal Entry Verification in SAP S/4HANA?

General Journal Entry Verification is SAP S/4HANA functionality for controlling the review of general journal entries before they progress to the posting stage.

Organisations can configure workflow conditions, verification steps and responsibility according to their financial-control requirements.

Its purpose is to make journal review part of a structured SAP process.

What is the difference between a native SAP journal workflow and a non-native workflow?

Yes.

SAP S/4HANA provides General Journal Entry Verification functionality that can be configured to route relevant journal entries for approval.

However, journal approval is only one part of journal management.

Organisations may also need to consider Excel preparation, early SAP validation, segregation of duties, supporting documentation, high-volume processing and audit reporting when evaluating the wider process.

What is the difference between SAP journal entry upload and journal entry verification?

Journal entry upload moves prepared journal data into SAP.

Journal entry verification controls whether a journal requires review and approval before it moves to posting.

A complete journal management process goes further by connecting preparation, SAP validation, supporting evidence, approval, posting and audit reporting throughout the journal lifecycle.

Can finance teams prepare SAP journals in Excel and still use an approval workflow?

Yes.

Finance teams can continue using Excel as the preparation environment while applying a controlled approval process around the journal.

The level of integration depends on the solution used.

With Promenta’s SAP-integrated Excel Add-In, finance users can prepare journals in Excel while accessing SAP-connected picklists and validation, perform a simulated posting and submit the journal into the approval workflow without separating Excel preparation from the wider SAP control process.

What is SAP General Journal Entry Verification?

General Journal Entry Verification is the native SAP S/4HANA Fiori capability for controlling the review of general ledger journal entries before they are posted. It was introduced with SAP S/4HANA 1709 and is configured through the Manage Workflows for General Journal Entry Verification Fiori app. Organisations can define which entries require review, who should approve them, and how exceptions are handled. Its purpose is to make journal approval part of a structured, traceable SAP process.

For a broader view of how this capability fits into the wider journal management process, see our guide to the SAP journal entry approval workflow.

Can you set up a journal entry approval workflow in SAP ECC?

Yes. Journal entry approval workflow capabilities are available in both SAP S/4HANA and SAP ECC. In the SAP ECC environment, organisations can configure journal entry approval through workflow-based controls similar in principle to S/4HANA General Journal Entry Verification. Promenta’s journal management solution operates natively inside both SAP ECC and S/4HANA, providing the same pre-approval validation, configurable routing, segregation of duties, and audit trail capabilities across both environments.

How to Upload Journal Entries in SAP S/4HANA: Step-by-Step Guide and Best Practices

Posted on August 17, 2026October 1, 2026 by by promenta

Knowing how to upload journal entries in SAP S/4HANA correctly is more than a technical task – it is a significant point of control exposure in the financial close.

Accruals, provisions, recurring month-end postings and correction entries often arrive in volume and under time pressure. A single upload may move dozens or hundreds of line items into the general ledger in a single action.

The upload itself is only one part of the process. The more important questions concern what happens before and after it: how the journal is prepared, when it is validated, who approves it, and whether SAP journal entry controls – including segregation of duties and evidence retention – are enforced as a unified process rather than disconnected steps.

This distinction is important.

While Excel and other structured templates remain practical tools for journal preparation, the control weakness does not necessarily sit in the spreadsheet.

It develops when preparation, validation, approval, posting, and evidence are handled through disconnected steps that are difficult to govern as a unified process.

What is a controlled SAP journal entry upload?

A controlled SAP journal entry upload is a five-stage process – preparation, validation, approval, posting, and evidence retention – executed as a single governed sequence inside SAP.

It ensures only validated, independently approved journals reach the general ledger, with a complete and reportable audit trail attached to each document.

The SAP financial close journal entry process already operates within a limited window.

Journal preparation and posting are among the high-volume activities consuming that time. Where an upload must be reversed and reposted, the finance team spends time that the close window may not have.

This guide explains how to upload journal entries in SAP S/4HANA as a controlled process rather than simply a data-entry task. It covers the main upload approaches, the recommended sequence, the control questions that remain around the standard upload path, and the practices that help keep journals validated, approved, and audit-ready before they reach the ledger.

Why journal entry uploads require control at financial close

A journal entry upload can appear mechanical: populate a template, load the file, and progress to the close. The exposure lies in what the step commits to the ledger.

Manual journals often receive particular audit attention because they depend on judgement and may not originate from the same automated source controls as subledger transactions.

At period-end, volumes increase while the time available for review decreases. Accruals and provisions may depend on estimates.

Recurring entries repeat a familiar structure but require current-period values. Correction postings can surface late, after related balances have already changed.

Where an error reaches the ledger, the operational consequences may include :

Two considerations decide whether an upload is good to go :

The second is audit readiness: whether the record of preparation, review, approval, posting and supporting evidence is created as part of the process or assembled later from emails, files and system logs.

See Promenta's SAP Journal Workflow in Action

Built natively on SAP. No external servers, no duplicate financial data.

Two Common Ways to Upload Journal Entries in SAP S/4HANA

Generally, many finance teams handle journal entry creation in SAP S/4HANA in two ways.

Manual entry in SAP

Users can enter journals directly through the relevant SAP finance applications or transactions. This can be appropriate for a small number of straightforward entries.

However, it becomes less practical as volumes grow because line-by-line entry takes time and creates more opportunity for keying errors.

Manual entry is not inherently uncontrolled. The relevant question is whether authorisations, approval requirements and supporting documentation are applied consistently.

If the same person can prepare and post journals without an effective review step, the process may still create a segregation-of-duties risk.

Bulk upload from a structured template

In many scenarios, finance teams prepare accruals, provisions, and recurring month-end entries in a spreadsheet and perform a bulk upload of journal entries to SAP. SAP S/4HANA provides standard upload capability, and some organisations also use a free SAP journal posting Excel upload tool, free SAP journal posting Excel upload tool or specialist journal workflow solutions.

Though the spreadsheet remains useful for calculations, analysis and complex preparation, a static file does not by itself demonstrate that master data was valid when the journal was prepared, if the journal was independently approved, or if the supporting evidence remained connected throughout the process.

How to Upload Journal Entries in SAP S/4HANA: A Five-Step Controlled Sequence

1. Prepare the journal in a structured template

Complete the required header information, such as company code, posting date, document currency, and header text. Then populate the line items, including debit and credit values, G/L accounts, cost objects, etc.

Standardised templates can reduce avoidable rework, particularly for journal types that recur each period. The template should reflect the information needed for that journal rather than forcing every entry through a generic structure.

2. Validate the journal before posting

Ensure the journal is balanced and that accounts, cost objects, posting periods, and other SAP finance requirements are valid.

The timing of validation matters.

Errors identified during preparation are usually easier to correct than errors discovered when the journal is being posted under close pressure.

Depending on the standard SAP capability or solution in use, validation may occur after the file is uploaded into SAP, through a check or posting simulation, or earlier when the journal is still being prepared.

Finance teams should understand exactly which controls run at each stage.

3. Route the journal for approval

Segregation of duties in SAP journal entry processing requires the preparer and approver to remain structurally separated – not just by policy, but through system-enforced controls that prevent the same user from preparing, approving, and posting without an independent review step.

The approval path may depend on company code, journal value, G/L account, business area, or another relevant risk factor.

SAP S/4HANA supports a journal entry approval workflow journal entry approval workflow in applicable editions and releases when correctly configured – but coverage and approval conditions vary by system edition, release, and journal type. The control question is whether the workflow used covers the journal population in scope, applies the required approval conditions, and prevents unauthorized self-approval.

4. Post the approved journal in SAP

Only journals that have passed the required checks and approvals should enter the ledger. Posting creates the SAP accounting document and document number that confirm the transaction has been recorded.

5. Confirm the result and retain evidence

The final record – your SAP journal entry audit trail – should connect each journal to its preparer, reviewer, posting result, and supporting documentation, and be reportable across the complete journal population rather than reconstructed from separate files during an audit.

Together, these five steps form the control chain around the upload.

Where Does the Standard SAP Journal Entry Upload Path Leave Control Gaps?

SAP S/4HANA provides standard functions for uploading general journal entries, checking uploaded data and, in relevant configurations, routing journal entries for verification. It would therefore be wrong to describe the standard environment as having no validation or workflow capability.

The more useful assessment is whether the organisation’s configured process provides continuous control from preparation through posting and evidence.

Validation may remain disconnected from preparation

The standard upload can check journal data after it has been brought into SAP. However, where preparation takes place in a static spreadsheet, the preparer may not have live SAP-dependent validation or current pick lists during journal preparation.

This creates a timing issue. The journal can still be corrected before final posting, but errors may surface later in the close process, after preparation and review effort has already been spent.

Verification workflow may require separate configuration

Journal entry verification capability is available in SAP S/4HANA for supported scenarios, but it must be configured around the organisation’s requirements. Coverage can vary depending on the system edition, release, journal type and process design.

Finance and SAP teams should therefore confirm:

which uploaded journals enter verification
which conditions determine the approval route
whether self-approval is prevented where required
how rejected or corrected journals are handled
whether the approval history is easy to report alongside the posted document

The existence of workflow capability is not the same as a fully governed process – the configured outcome matters.

Preparation evidence can sit outside SAP governance

A generic spreadsheet may contain the journal data but not the complete control history. Review comments, approval emails and supporting files can remain in separate locations.

The posted document is visible in SAP, while the reasoning and evidence that preceded it may be fragmented.

This creates an auditability issue. The finance team may be able to prove that a journal was posted, but still need to assemble how it was prepared, reviewed, and approved.

Architecture can introduce an additional governance boundary

Some custom tools and external platforms process or stage journal data outside SAP before sending it back for posting. Depending on the architecture, this may introduce additional infrastructure, interfaces, security controls and data retention arrangements for IT, finance and internal audit to govern.

Although external architecture may be needed in certain scenarios, buyers should understand where financial data is held, which authorisation model applies at each step and how audit evidence remains connected across systems.

See how Promenta closes these control gaps inside SAP

Review how Promenta’s SAP-native workflow connects preparation, validation, approval, and audit evidence — with no external server required.

What Does a Governed SAP Journal Entry Upload Process Look Like?

A governed journal upload connects preparation, validation, approval, posting and evidence rather than treating the upload as an isolated event.

Promenta’s SAP Journal Entry Workflow does exactly that.

Preparation takes place in Excel through the Promenta Excel Add-in, which connects the spreadsheet to SAP in real time. This allows finance teams to continue using a familiar preparation environment while drawing on dynamic pick lists and SAP-dependent validation.

Duplication checks and SAP finance validations can be applied before submission, and a simulated posting can identify errors while the journal remains a request rather than a posted document.

Approval routing within the journal entry approval workflow SAP journal entry workflow is configured around relevant request data, such as company code, journal value, or G/L account. Segregation-of-duties rules can prevent a requester from approving their own journal, subject to the organisation’s agreed policy and any explicitly configured thresholds.

Because users submit journals through the controlled workflow, organisations may also be able to restrict direct access to powerful posting transactions for the relevant user population. This can help align system access with the intended approval process rather than relying on policy alone.

Posting takes place inside SAP.

Requests, approvals, posting results, and supporting evidence remain connected and reportable against the journal process. Attachments can be retained in SAP against the finance document, reducing the need to reconstruct the audit history from separate files and emails.

The architectural distinction supports the control model. Promenta runs natively inside SAP ECC or S/4HANA and is designed without an external server or replicated financial dataset in the journal path.

This may reduce the number of interfaces and infrastructure components that the organisation must govern.

Promenta has operated as an SAP partner product since 2002, supporting both on-premises and private cloud deployment options.

One architecture cannot apply to every organisation – each has unique needs. The relevant question is whether the solution fits the organisation’s SAP landscape, control requirements, security model and audit expectations.

Standard SAP capability and what a governed journal workflow adds

Area	Standard SAP S/4HANA capability	Promenta SAP Journal Entry Workflow
Templates	A single generic Excel upload template.	A template manager supporting multiple Excel templates, configured to the entry types a team actually posts.
Excel preparation	No SAP functionality inside the spreadsheet; the template is a static file until it is loaded.	An in-sheet Excel Add-in with real-time SAP integration: SAP validation, dynamic pick lists, duplication prevention, and journal risk mitigation during preparation.
Workflow & controls	No standard workflow; approval, segregation of duties, and the audit trail have to be designed and built by the customer.	Enterprise journal workflow with segregation of duties, compliance controls, and a reportable audit trail, highly configurable with no coding and native inside S/4HANA.
Audit Trail	May be stored separately	Commonly retained outside the journal record
Where data is held during the process	Inside SAP	May move through a custom or external tool
Audit trail	Audit trail relies on the SAP document record; supporting evidence and approval context are typically held in separate files, emails, or systems outside SAP.	Requests, approvals, posting results, and document attachments remain connected and reportable inside SAP against each journal document, without reconstruction.

Best practices for journal entry uploads in SAP S/4HANA

The decision to upload journal entries in SAP S/4HANA through a governed sequence – rather than as an isolated file transfer – depends on process design as much as technology.

The following practices apply whichever upload method an organisation uses.

Validate early

Run account, cost object, balance and SAP finance checks before final posting. Earlier validation reduces the likelihood that avoidable errors reach the final stages of the close.

Enforce segregation of duties through access and workflow

Approval should not depend only on an informal expectation that a colleague will review the journal.

Segregation of duties in SAP journal entry processing must be enforced through system access and workflow controls, not policy alone – ensuring the required separation between preparation, approval, and posting is structurally embedded in the process.

Keep evidence connected to the journal

Supporting calculations, explanations and approval history should remain easy to retrieve against the journal. Audit readiness is stronger when evidence is produced by the process rather than assembled afterwards.

Standardise recurring templates

Recurring journals often use the same structure each month even when the values change. Standardised templates can reduce preparation effort and inconsistency without removing the need for current-period validation and approval.

Review the complete configured process

Finance teams should assess the upload app, verification workflow, authorisations, supporting documentation and reporting together. A control may exist in SAP but still leave a gap if it is not configured for the relevant journal population.

Plan for S/4HANA transformation requirements

Where an organisation is moving from SAP ECC to S/4HANA, SAP journal entry workflow design – including templates, approval routing, and controls – should be part of the transformation plan, not retrofitted after go-live.

The objective should be to align governed journal processes with the standard S/4HANA environment rather than create unnecessary competition between them.

Preserve human judgement as automation develops

AI may support journal preparation by proposing recurring entries or suggesting accruals from prior patterns. That does not remove the need for professional finance judgement, current-period evidence and appropriate approval.

More automation does not automatically mean better control.

Conclusion

Uploading journal entries in SAP S/4HANA is only as controlled as the process around the upload. Standard SAP capabilities can support upload, checking and journal entry verification.

Organisations should focus heavily on whether the configured process connects preparation, validation, approval, posting and evidence for the journal population that matters.

A governed process should make it possible to answer the following questions clearly :

Are journals validated against relevant SAP rules early enough to avoid late rework?
Can the same person prepare, approve and post a journal, or is segregation of duties enforced?
Does the approval route reflect journal value, company code, G/L account or other relevant risk factors?
Are supporting documents and explanations retained with the journal?
Can finance and internal audit report the complete history without reconstructing it from separate systems?
Does journal data leave SAP, and if so, what additional governance does that architecture require?

Where the answers demonstrate connected control, the organisation is better placed to support an efficient close and audit-ready evidence.

Where the process depends on disconnected files, emails and late checks, finance teams continue to absorb the control and administrative work each period.

See a governed journal upload inside SAP

Review how preparation-side validation, approval, segregation of duties and continuous audit evidence can remain attached to the journal without introducing an external server into the process.

Frequently Asked Questions

What are the best practices for uploading journal entries in SAP S/4HANA?

The key best practices for a controlled SAP journal entry upload are:

1. Validate journals against SAP rules before final posting.

2. Enforce segregation of duties through system access and workflow, not policy alone.

3. Retain supporting documents and approval history connected to the journal inside SAP.

4. Standardise recurring templates to reduce preparation inconsistency each period.

5. Assess the entire configured process – upload app, verification workflow, authorisations, and reporting – together as a control chain rather than in isolation.

Does uploading journal entries work the same way in SAP ECC and S/4HANA?

The control principles are similar, but the standard tooling differs. SAP ECC environments commonly rely on manual entry, custom upload programs, or specialist tools for high-volume journal uploads.

SAP S/4HANA provides standard applications for uploading general journal entries and, in supported scenarios, journal entry verification workflows. The exact functions available depend on the edition, release, and configuration.

A governed workflow can provide a consistent control model across both environments by applying the relevant SAP rules and authorisations within each system.

Can journal entry uploads be scheduled for recurring month-end entries?

Recurring accruals and allocations are strong candidates for standardised templates and repeatable preparation. Scheduling can reduce manual effort, but it does not remove the need to validate current-period figures and apply the required approval.

The structure may repeat; the evidence and judgement still belong to the current period.

Is a spreadsheet-based upload sufficient for SOX and audit purposes?

A spreadsheet can be an appropriate preparation tool, but it does not offer complete control over the process by itself.

A spreadsheet-based upload alone is not sufficient for SOX or audit purposes without a governed process around it. SOX and audit requirements depend on the organisation’s control design, but finance teams will generally need to demonstrate validation, appropriate approval, segregation of duties, controlled changes, and retrievable evidence. A spreadsheet-based upload can support those requirements when it operates within a governed process that connects the file to the system of record and its approval history.

Does Promenta replace the standard S/4HANA upload template?

Not necessarily. Promenta is intended to add connected preparation, validation, approval, segregation of duties, and audit evidence around journal processing.

Some teams may continue to use standard SAP upload capability for suitable scenarios while applying a governed workflow where additional preparation-side control, routing, or evidence is required.

SAP Journal Entry Upload: Controlled Validation, Approval, and Audit Trail Inside SAP

Posted on August 11, 2026October 1, 2026 by by promenta

Manual journal entries are an essential part of financial reporting. They allow finance teams to record accruals, corrections, reclassifications, provisions and other transactions that may not originate from a standard source document.

However, this flexibility also makes manual journals a critical area of financial control.

Unlike a payment supported by an invoice or a goods receipt connected to a purchase order, a manual journal may begin with a finance user deciding the amount, account, cost object, posting period and accounting treatment.

This does not mean that every manual journal is inherently high risk. Nor does it mean that organisations should simply try to eliminate manual journals.

Rather, the focus lies in what happens around the journal.

How is the information validated? Who reviews and approves it? Can the preparer also post the entry? Is supporting documentation retained alongside the journal? Can the organisation demonstrate the complete history of the transaction during an audit?

The risk of manual journal entries in SAP therefore depends less on the number of journals being processed and more on where the controls are applied.

If controls operate only after a journal has posted, the organisation may be able to detect a problem. If the controls operate during preparation and approval, the organisation has a better opportunity to prevent the problem from reaching the ledger.

Why the Risk of Manual Journal Entries in SAP Requires Preventive Controls

Manual journals are a critical part of the financial close. They allow finance teams to record accruals, reclassifications, provisions, intercompany entries, corrections and other adjustments that require professional judgement.

The challenge is not the journal itself. It is the SAP journal entry upload process – how the journal moves from Excel preparation into the SAP general ledger, and what controls, validation, and approval exist along that path.

While many organisations use their own Excel upload process to post journals, in many SAP environments, finance teams still rely on one of two methods :

The problem is that neither of these methods necessarily provides a controlled process around preparation, validation, approval, supporting evidence, and auditability.

Promenta SAP Journal Entry Upload is designed to replace these approaches with a controlled, SAP-native process Finance users can continue preparing journals in Excel, while live SAP validation, posting simulation, approval routing, segregation of duties and audit evidence remain connected to the entry throughout its lifecycle.

Beyond enabling finance teams to upload journals more quickly, Promenta ensures each journal is validated, authorised and fully documented before it becomes a posted SAP financial document.

What Is SAP Journal Entry Upload?

SAP journal entry upload is the process of moving a manually prepared journal entry from Excel into the SAP general ledger. A controlled SAP Journal Posting, Excel Upload Tool includes live SAP validation, posting simulation, enforced approval, segregation of duties, and a continuous audit trail – all operating inside SAP ECC or S/4HANA without external servers or replicated financial data.

Why SAP Journal Entry Upload Requires Stronger Controls Than Manual Posting

The scale of manual journal posting in SAP remains significant across enterprise finance functions.

Research published in 2026 across finance shared-service teams found that only approximately 2% of organisations described their close as fully automated. This means manual journal preparation and posting are widely practised across enterprise finance functions.

Manual journal entries are also a specific area of auditor attention. Per PCAOB auditing standards, auditors are required to test journal entries and other adjustments because inappropriate or unauthorised journals are a proven pathway for misstated financial statements.

Finance teams may need to demonstrate:

Who prepared the journal
What information supported it
Which SAP validation rules were applied
Who reviewed and approved it
Whether segregation of duties was enforced
When each action occurred
Whether the journal was rejected or amended
How and when it was posted
Whether the complete process can be reconstructed during an audit

Promenta Journal Posting, Excel Upload Tool is designed to create this controlled path from Excel preparation through to posting and audit.

What a Controlled SAP Journal Entry Upload Replaces

Before evaluating a controlled upload process, it is important to understand the two methods it is intended to replace.

1. Manual Entry into Standard SAP Finance Screens

In SAP ECC, users may enter journals through standard posting or parking transactions such as FB50, FB01, or FV50.

In SAP S/4HANA, finance teams may use standard journal entry applications that post into the Universal Journal.

SAP validates the entry when it is submitted for posting. However, direct screen entry does not necessarily provide:

A structured journal preparation process
Validation before the user reaches the posting stage
An enforced approval workflow
Mandatory supporting documentation
A controlled separation between preparation and posting
A complete record of the decisions preceding the posting

The user entering the journal may also hold standing access to post it.

This creates an important segregation-of-duties issue. A user may be able to prepare and post the same journal without independent approval being enforced through the system.

An approval may still take place through email or another informal process. However, if the journal can be posted regardless of whether that approval occurred, the approval is not operating as a preventive control.

2. Custom or Generic Excel Upload Tools

Basic Excel upload tools make journal preparation easier by allowing finance users to structure entries in a spreadsheet and transfer them into SAP.

While these tools may confirm that the file is structurally complete, they do not confirm if the journal complies with the live finance rules SAP will apply when the document is posted.

Custom or generic tools may not provide:

An SAP-integrated Excel Add-In
Live SAP picklists
Real-time SAP finance validation
Full simulated posting before submission
SAP-native approval routing
Segregation-of-duties enforcement
Mandatory supporting evidence
A continuous SAP audit trail

Where approval exists, it may still be managed through email and retained separately from the journal.

The spreadsheet may improve preparation efficiency, but the controls surrounding the journal largely remain manual.

SAP ECC mainstream support ends 2027. See how Promenta keeps journal control inside SAP through the transition.

What Is the Difference Between a Format Check and Live SAP Validation?

Validation is one of the most important distinctions between a basic Excel upload and Promenta SAP Journal Entry Upload.

File and Format Validation

A format check determines whether the spreadsheet is structurally suitable for upload.

It may confirm that :

Though these checks are useful, a format check says nothing about whether the entry will actually post.

Even a correctly formatted journal may contain an invalid general ledger account, an incorrect cost object, an unavailable posting period, or another issue that causes it to fail when it reaches the SAP environment.

Validation Against Live SAP Rules

SAP journal entry validation examines the entry against the live SAP environment, including the master data, finance configuration, and posting rules that will govern the actual posting.

Depending on the organisation’s configuration, this may include:

General ledger account validation
Chart-of-accounts checks
Cost centre validation
Profit centre validation
Company code validation
Posting-period status
Tax determination
Tolerance rules
Document balancing
SAP substitutions
Configured finance validations, including GBB0

This is fundamentally different from merely validating the spreadsheet structure.

The journal is tested against the same live data and financial rules that will govern the eventual posting.

Why the Timing of Validation Matters

The challenge with manual entry into SAP and basic Excel upload tools is that in both, errors surface too late, usually close to posting.

By that stage:

The preparer may believe the journal is complete
Supporting information may already have been gathered
Informal approval may already have taken place
The journal may need to be corrected and resubmitted
Close activity may already be under significant time pressure

Promenta moves this validation earlier.

Promenta SAP Journal Entry Upload uses a fully validated virtual journal document and runs a full simulated posting at the request stage. So, the requester can see the errors SAP would raise before the journal is submitted for approval.

This allows structural, master-data and field-level issues to be corrected while the journal is still being prepared.

Thus, it allows finance teams to prevent avoidable errors from progressing to approval rather than discovering them at the final posting stage.

How an SAP-Integrated Excel Add-In Improves Journal Upload Control

Excel remains a practical and familiar preparation tool for finance teams.

It supports calculations, analysis, large datasets, and the preparation of complex journals. Replacing Excel is not always the most viable option.

An Excel journal upload to SAP is practical and familiar. The question is not whether to use Excel, but what connects it to SAP and whether that connection includes live validation, approval routing, and audit control. Organisations looking to move beyond manual screen entry can start with Promenta’s free SAP Excel upload tool as an entry point before adopting full workflow controls.

Promenta provides an SAP-integrated Excel Add-In that allows finance users to prepare journals using a familiar interface while accessing SAP-aware controls.

The Add-In supports:

Live SAP picklists
Validation against current SAP data
SAP finance-rule validation
Submission into the approval workflow
Supporting attachments
Status visibility
Controlled progression towards posting

The Add-In turns Excel into the controlled preparation point for an SAP journal request.

This connects the approval policy to the underlying SAP authorisation structure.

See Promenta's SAP Journal Workflow in Action

Built natively on SAP. No external servers, no duplicate financial data.

How SAP Journal Entry Upload Enforces Approval and Segregation of Duties

Validation establishes whether the journal data is acceptable; it does not establish whether the journal has been independently authorised.

That requires an approval workflow and segregation of duties.

With direct entry, the user preparing the journal may also have the standing SAP access required to post it.

With a basic Excel upload, the journal may be approved through email, but the approval remains detached from the SAP posting process.

Promenta moves the approval into the controlled SAP journal path.

The SAP journal entry approval workflow routes requests using meaningful financial fields, including :

The workflow can support :

Multiple approval levels
Approval hierarchies
Team inboxes
Substitute approvers
Rejection and resubmission
Mandatory documentation
Requester and approver separation
A complete approval record

A requester cannot approve their own journal.

Because the document posts only after the required approvals are complete, the organisation can also remove access to sensitive finance posting transactions from everyday users.

Segregation of duties becomes an enforced property of the workflow rather than a procedure dependent on individual behaviour.

Why SAP Journal Entry Upload Should Run Inside SAP

The location of the upload determines whether journal data, validation, approvals and audit evidence remain within SAP or must be managed across additional systems.

When preparation, validation, approval and posting remain connected to SAP, the process can use the organisation’s existing:

SAP users
Roles and authorisations
Segregation-of-duties framework
Master data
Finance configuration
Security controls
Operational support procedures
Audit environment

Sensitive financial information does not need to be replicated into an external platform for the core process.

By contrast, an external application may introduce:

A duplicate copy of journal data
Additional infrastructure
A separate user-administration model
Additional integrations
Another security boundary
Additional audit and compliance scope
Integration testing during SAP upgrades

Promenta operates inside SAP ECC and SAP S/4HANA without external servers, middleware or replicated financial data for the core journal process. Deployment can remain on-premises or within the organisation’s private-cloud SAP environment.

The journal is validated against the same finance rules and posted into the same ledger to which it belongs.

This helps preserve one connected control environment throughout the upload process.

How Promenta Replaces Both Existing Methods

A controlled SAP journal entry upload combines the familiar elements of Excel preparation and SAP posting within one governed process, keeping validation, approval, and audit evidence connected throughout.

A finance user continues to prepare the journal in Excel.

The difference is what happens around that preparation:

The Promenta Excel Add-In connects directly to SAP.
Live SAP picklists support more accurate preparation.
The journal is validated against current SAP data and finance rules.
A full posting is simulated before submission.
Supporting documentation is attached to the request.
The journal is submitted into an SAP-native workflow
Approvals are routed according to the organisation’s financial-control requirements.
Segregation of duties is enforced.
The document posts only when all required approvals are complete.
The full request, approval and posting history remains reportable inside SAP.

Promenta effectively replaces direct screen entry or custom Excel upload tools by providing an integrated Excel Add-In with live SAP validation, workflow and audit controls rather than relying on a file-format check.

A Comparative Mapping of the Three Approaches

Area	Direct Entry into SAP Screens	Custom or Generic Excel Upload	Promenta SAP Journal Entry Upload
Where the journal is prepared	Entered directly into the SAP posting screen	Prepared in a spreadsheet without a fully SAP-aware Add-In	Prepared in Excel through the SAP-integrated Promenta Add-In
When SAP validation occurs	At the point of posting	Usually limited to file and format checks before SAP posting	Against live SAP rules during preparation, with simulated posting before submission
Approval and segregation of duties	May rely on standing posting access and informal review	Approval commonly retained in email or another external process	Approval routed and enforced inside SAP
Supporting documentation	May be stored separately	Commonly retained outside the journal record	Attached to the controlled journal request
Where data is held during the process	Inside SAP	May move through a custom or external tool	Remains inside the SAP environment
Audit trail	May be divided between the ledger, emails and other evidence	May be divided between spreadsheets, emails and SAP	Continuous and reportable inside SAP
When errors are identified	At posting	Commonly at posting	Before submission and approval
SAP GUI dependency	Required for standard transactions	Depends on the tool	Promenta does not require SAP GUI
Primary objective	Enter and post the journal	Make spreadsheet upload more efficient	Control preparation, validation, approval, posting and audit

How SAP Journal Entry Upload Handles High-Volume and Month-End Activity

Control should not weaken when journal volumes increase.

Month-end and year-end close may involve large journals, recurring activity, and multiple journal requests that need to move through the process within a limited period.

The solution also supports complex, high-volume journal activity through the same controlled path used for individual entries.

Where a journal contains more than SAP’s standard 999 line-item limit, Promenta can automatically divide the entry into multiple balanced SAP documents. For example, a journal containing 3,000 line items can be split across the required balancing accounts and then posted through the same controlled process.

Finance teams can also prepare multiple journals within a single Excel sheet. Promenta identifies and processes each journal as a separate SAP document, allowing several journals to be validated, approved and posted together without requiring a separate upload process for each one.

How a Controlled SAP Journal Entry Upload Speeds Up the Financial Close

A faster financial close goes way beyond simply accelerating the spreadsheet upload.

It is the result of reducing the errors, rework, and uncertainties surrounding journal processing.

When journals are validated before submission:

When approvals are managed through one controlled workflow:

When the audit history is complete

The close becomes faster because there is less to correct, reconcile, and explain after the event.

What Audit Trail Does a Controlled SAP Journal Entry Upload Create?

The final difference is the SAP journal entry audit trail – the complete, continuous record of what was prepared, validated, approved, and posted, held inside SAP from start to finish.

Promenta SAP Journal Posting, Excel Upload Tool creates a continuous record inside SAP showing :

An auditor can review the lifecycle from one controlled record rather than reconciling a spreadsheet, an email chain, and the final SAP document. This is a direct outcome of running approvals inside the SAP journal entry workflow rather than outside it.

The Role of AI in Journal Preparation

AI has the potential to assist finance teams with journal preparation, classification and anomaly detection.

However, AI does not replace the controls required around a manual journal.

The data entered into the journal and the authority to approve it remain human responsibilities.

Validation, segregation of duties, approval evidence and accountability must therefore continue to operate through the organisation’s financial-control framework.

An SAP-native model keeps these responsibilities connected to the same authorisation and governance structure used by the wider finance function.

The bottom line – finance leaders evaluating their current process should consider:

Does the current method validate against live SAP finance rules before posting?
Does it provide a fully integrated Excel Add-In?
Can the requester post without independent approval?
Is segregation of duties enforced by the workflow?
Is supporting documentation mandatory?
Does the approval evidence remain inside SAP?
Are errors identified during preparation or only at posting?
Can the full journal history be demonstrated from one place?
Does sensitive financial data leave SAP during the process?

If these controls sit outside SAP or operate only after posting, the journal upload is not yet managing the full risk.

See Promenta SAP Journal Entry Upload Inside SAP

See how a manual journal moves from Excel preparation to a posted SAP document with live validation, controlled approval, segregation of duties, and a continuous audit trail attached to the entry.

Frequently Asked Questions

What Is Promenta SAP Journal Entry Upload?

Promenta SAP Journal Entry Upload is an SAP-native controlled process for moving manually prepared journal entries from Excel into the SAP general ledger, with live validation, enforced approval, segregation of duties, and a complete audit trail inside SAP ECC or S/4HANA.

Finance users prepare the journal through the Promenta Excel Add-In. The entry is then validated against live SAP data and finance rules, simulated before submission, routed for approval, and posted only after the required controls have been completed.

The complete preparation, approval, posting, and audit history remains inside SAP.

What Does Promenta SAP Journal Entry Upload Replace?

It is designed to replace:

● Manual journal data entry directly into standard SAP finance screens or SAP S/4HANA Universal Journal applications

● Custom or generic Excel upload tools that do not provide an SAP-integrated Excel Add-In, live SAP validation, enforced approvals, segregation of duties, and complete audit evidence

Promenta SAP Journal Entry Solution aims to retain the usability of Excel while creating a more controlled route into the SAP ledger.

Can Journal Entries Be Uploaded into SAP from Excel?

Yes. Excel is a preferred choice as the preparation tool for many finance teams.

With the Promenta Excel Add-In, finance users can access SAP picklists, validate the journal against live SAP rules, and submit it into the approval workflow directly from Excel.

This preserves the familiar preparation interface without separating validation, approval, or audit evidence from SAP.

Is a Custom Excel Upload Tool Sufficient for Journal Compliance?

It depends on what the tool validates and where the controls operate.

Many custom or generic tools confirm that a spreadsheet is correctly formatted but do not validate the journal against live SAP finance rules before submission.

Approval may also remain in email or another process outside SAP.

Key compliance and audit considerations include verifying whether:

● SAP validation occurs before posting

● Approval is enforced

● Segregation of duties is applied

● Supporting evidence is mandatory

● The complete audit record remains inside SAP

What Is the Difference Between a Format Check and Live SAP Validation?

A format check confirms that the spreadsheet structure is correct and required fields are populated.

Live SAP validation checks the journal against the organisation’s current SAP master data, finance configuration, substitutions, posting rules and validations.

A file can pass a format check and still fail when it reaches SAP.

Promenta performs live SAP validation and simulated posting before the journal is submitted for approval, which means errors surface during preparation rather than at the point of posting.

Does Promenta Require SAP GUI?

No. Promenta SAP Journal Entry Upload does not require SAP GUI for the end-user preparation and workflow process.

Finance users can prepare and submit journals through Excel while maintaining secure integration with SAP.

Why Should the Journal Upload Remain Inside SAP?

Keeping the process inside SAP allows the journal to remain connected to the organisation’s existing users, authorisations, master data, finance rules, security controls and audit environment.

It also avoids introducing an external server, replicated financial data, separate middleware or another application environment for the core journal process.

[/et_pb_text][/et_pb_column]
[/et_pb_row]
[/et_pb_section]