Oracle EBS Journal Entry Approval Workflow R12.1.3

The intent of this document is provide the reader with a fundamental understanding of Oracle’s Journal Entry Approval Workflow enriched with lessons learned from actual implementations.  Matt Makowsky is an Oracle Financial Applications Consultant with 17 years experience and a Senior Solutions Architect with Perficient.  Feel free to ask him any questions in the comments section below the blog.

Oracle’s Journal Entry Approval Workflow enables what in many companies may be a key SOX control:

  • prevent unauthorized journals from posting into your ledger
  • prevent unsubstantiated changes to financial statements

The control does this by ensuring journal entries are reviewed by supervisors to verify the journal is complete, accurate, and has supporting documentation.

Journal Approval works as follows in EBS:

  1. A journal is created in EBS (or uploaded via WebADI)
  2. The user clicks the “Approve” button on the journal form (note, if submitted via WebADI, the user must query the journal up in the core forms to submit for approval)
  3. The approver, typically the user’s supervisor as defined in Oracle HR, receives a notification with the ability to review the journal, and then approve, reject, or ask for more information.
  4. The workflow will move to the next supervisor if the value of the largest journal line is greater than the supervisors approval threshold.

Those are the basics, but under the hood there are a lot of mechanisms in motion to make it all work.

Oracle - Guide to Oracle Cloud: 5 Steps to Ensure a Successful Move to the Cloud
Guide to Oracle Cloud: 5 Steps to Ensure a Successful Move to the Cloud

Explore key considerations, integrating the cloud with legacy applications and challenges of current cloud implementations.

Get the Guide

Enabling Journal Approval: The basics

Journal Approvals can be enabled easily with the following basic setups:

  1. For a given ledger (primary or secondary), navigate to the setups and “Enable Journal Approval”
  2. Review your Journal Sources, and enable Journal Approval for a given source – turn it off where journal approval is not required (ie: subledger journals from Receivables, Assets, Payables, and so on)
  3. Add Approvers and “signing limits” into the system by ledger.
  4. Set profile options to enable/disable “preparer can approve own journal” – if enabled, the preparer can approve their own journal, providing they have the signing limit for the journal.

Best practice is to disable this capability, to prevent people from splitting journals for the purpose of self approval.

Points to remember:

  • Journal approval is conducted at the journal batch level. The highest journal line value across all journals within the batch will determine the supervisor.
  • Journal approval looks at amounts, not accounts.  To look at accounts, customization will be required.
  • Journals will always go up the supervisor hierarchy, although there are options to “go direct” or to move up through the hierarchy.  If going direct, the journal will skip anyone who would not have  signing authority, as determined in the signing limits definition.
  • Be sure managers have remote access to email and email is enabled for month end approvals.
  • Appoint a workflow administrator to reassign workflows in the event an approver is absent and has not set their vacation rules.
  • AME is not available for Journal Entry Approval as of 12.1.3. Customization must be done through workflow.

Pros and Cons of Implementing Journal Workflow


  1. Enables and simplifies a key sox control.
  2. Electronic signatures, governed by the system, are more easily audited.
  3. Prevents forgery of approved documents and loss of offline data.


  1. Month End process can be slowed if approvers are on vacation or out sick.
  2. Limited functionality in standard approval rules.

Implementation Recommendations and Considerations

  1. The size of your accounting department, the number of managers, the number of approvals needed
    • Avoid situations where multiple approvals are needed, especially at month end, enabling “unlimited” authority for most managers.
  2. Consider other controls to prevent over burdensome approvals
    • Mass Allocations and Recurring Journals- disable approvals for mass allocations, provided that the forumlas are “locked down” to select users (supervisors and managers)
    • Sub Ledgers – disable approvals.  The source of the activity has already been approved, or was otherwise generated with other system controls in place.
    • Freeze all subledger journals to prevent changes and out of balance control accounts.
    • Disable approval for automatic reversing journals (controlled by profile option)
  3. Create workflow reports
    • Monitor the status of unapproved journals
    • Audit Preparer vs. Approver to check on “system gaming” if preparers are allowed to approve own journals. See who is approving their own journals on a regular basis.
  4. Enable Auto Post and Schedule it Frequently (often at Month End)
    • Auto Post simplifies the record to report process, by posting journals automatically (as the name suggests) if the journal has an approved status or does not require approval.
    • Auto Post reduces redundancy in process.  Consider that once approved, a journal is expected to be posted. Let the system manage the process from Approval to Post.
  5. Customization
    • Avoid unnecessary customization, balancing business requirements against the technical complexities.
    • Be flexible and look for functional solutions, using reports or other controls before customizing the workflow.


In summary, Journal Approval Workflow can provide huge benefits to your enterprise: Control over and Insight into your process.  Prevent simple accounting errors, and streamline your month end process.  Combined with Auto Post, implementing approvals can fundamentally change the way your finance team does business.



About the Author

Matthew is the managing director of Perficient's Oracle ERP practice. He has 19 years of experience in Oracle Financial Applications which include 5 large-scale, global, full cycle implementations across multiple industries and multiple countries across Europe and Latin America, plus upgrades across many release of Oracle EBS.  Matthew has extensive application experience in General Ledger, Accounts Payable, Accounts Receivable, and Fixed Assets.  In addition he has managed implementations ranging from 2-3 people to as many as 100 people.  Matthew is personable, and has both excellent written and verbal communication skills.  Matthew has experience conducting workshops– both formal and informal and is charged with driving design sessions.   Matthew’s application experience extends into supply chain modules including purchasing, order management, and inventory, and with that he is able to guide our clients through month end and financial reporting, seamlessly, end to end.

More from this Author

Thoughts on “Oracle EBS Journal Entry Approval Workflow R12.1.3”

  1. Hi, Matt. Thank you for your thoughtful article. Unfortunately, I have not been able to find very much information on how to audit change management on the R12.1.1 Journal Workflow configuration itself. Ideally, we would like to run a report which shows when the Journal Batch approval workflow or the associated approver group was changed. Do you have any ideas on how this can be accomplished?

  2. Matt Makowsky Post author

    Thanks for reading the blog and your question. If Oracle GRC doesn’t do the job, I’m pretty sure there’s no standard report or mechansim to track those specific changes.

    If I had to respond to my client with a solution, I’d possibly recommend a trigger on the relevant tables to record the changes in the approvers and run a daily report off that table.

    Same type of thing you might do for suppliers bank accounts and other sensitive data.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to the Weekly Blog Digest:

Sign Up