assess.one – AI-powered business operations platform

Workflow Template

Journal Entry Approval Workflow

Captures a preparer's journal entry submission, routes it through review and correction cycles, applies threshold-based approval (financial controller for amounts over $50,000, finance manager otherwise), and notifies the preparer at each terminal outcome (rejected, returned, or ready to post).

This workflow is designed for finance teams that need a consistent way to capture, review and approve journal entries before posting. It automates the path from preparer submission through reviewer checks, correction cycles, and threshold-based approval by the financial controller or finance manager, notifying the preparer automatically at each terminal outcome. The result is a record-level audit trail of every submission's status, review comments and approval decision, without manual chasing or spreadsheet tracking.

Business Outcomes

  • Reduces manual follow-up by automatically notifying preparers at each terminal outcome
  • Supports consistent application of the $50,000 approval threshold across all journal entries
  • Makes it easier to track review and correction cycles through a single record timeline
  • Helps shorten the time between submission and posting-ready status
  • Improves visibility into pending reviews and approvals across the finance team

Workflow Steps

Steps

  1. 1
    Create Journal Entry Recordcreate record

    Registers the submitted journal entry as a record.

  2. 2
    Set Status: Submittedupdate record

    Sets the journal status to Submitted.

  3. 3
    Email Acknowledgement to Preparersend email

    Sends the preparer an acknowledgement email with their reference number.

  4. 4
    Set Status: In Reviewupdate record

    Sets the journal status to In Review.

  5. 5
    Reviewer: Review Journal Entrycreate task

    Assigns a reviewer (who must not be the preparer) to check the journal entry and record the result.

  6. 6
    Save Review Resultupdate record

    Persists the reviewer's result and comments to the record.

  7. 7
    Route on Review Result

    Branches based on whether the reviewer found the journal correct or needing correction.

    review_result: "Correct"→Route on Total Amount Threshold
    review_result: "Needs correction"→Set Status: Returned
    Default→End
  8. 8
    Set Status: Returnedupdate record

    Sets the journal status to Returned because it needs correction.

  9. 9
    Request Corrected Entry from Preparerrequest external input

    Emails the preparer the reviewer's comments and asks for the corrected entry, waiting for their reply.

  10. 10
    Save Corrected Entryupdate record

    Persists the preparer's corrected entry to the record.

  11. 11
    Return to Reviewrestart from step

    Restarts the workflow at the In Review stage so the reviewer can re-check the corrected entry, up to 3 times.

  12. 12
    Route on Total Amount Threshold

    Routes to the financial controller for amounts over $50,000, otherwise to the finance manager.

    total_amount: "50000"→Financial Controller Approval
    Default→Finance Manager Approval
  13. 13
    Financial Controller Approvalrequest approvalrequires approval

    Requests approval from the financial controller for journals over $50,000.

  14. 14
    Route on Controller Decision

    Branches based on the financial controller's approval decision.

    approval_status: "approved"→Set Status: Ready to Post
    approval_status: "rejected"→Set Status: Rejected
    Default→End
  15. 15
    Finance Manager Approvalrequest approvalrequires approval

    Requests approval from the finance manager for journals of $50,000 or less.

  16. 16
    Route on Manager Decision

    Branches based on the finance manager's approval decision.

    approval_status: "approved"→Set Status: Ready to Post
    approval_status: "rejected"→Set Status: Rejected
    Default→End
  17. 17
    Set Status: Rejectedupdate record

    Sets the journal status to Rejected.

  18. 18
    Email Preparer: Rejectedsend email

    Notifies the preparer that the journal entry was not approved.

  19. 19
    Set Status: Ready to Postupdate record

    Sets the journal status to Ready to Post.

  20. 20
    Email Preparer: Ready to Postsend email

    Notifies the preparer that the journal entry is approved and ready to post.

Fields

Show all 12 fields

FormJournal Entry Submission

  • Preparer Name*· Text
  • Preparer Email*· Email
  • Journal Type*· Choice
  • Period*· Text
  • Accounts and Amounts*· Long text
  • Total Amount*· Number
  • Business Reason*· Long text
  • Supporting Evidence*· File upload

TaskReviewer: Review Journal Entry

  • Review Result*· Choice
  • Review Comments· Long text

Other fields

  • Journal Status· Choice
  • Corrected Entry*· Long text
  • Preparer Name*
  • Preparer Email*
  • Journal Type*
  • Period*
  • Accounts and Amounts*
  • Total Amount*

Forms

Journal Entry Submission

8 fields

Data Views

Journal Entries

journal_type, period, total_amount, journal_status

Dashboard Widgets

Journals by Status

Recommended integrations

Setup the following integrations to extend workflow capability.

  • Send email in the workflow

    AWS SES logoAWS SES
journal entry approvalgeneral ledgeraccounting approvalmanual journalfinancial control

Similar Workflows

Similar Categories

FAQs

Why should we automate journal entry approval instead of managing it by email and spreadsheets?

Manual journal approval tracking relies on preparers and reviewers remembering to follow up, which makes it easy for entries to stall or for correction cycles to lose their history. This workflow captures each submission as a record with a reference number and status, so the current state of every journal entry is visible without chasing emails. It also applies the approval threshold routing automatically, reducing the chance of an entry reaching the wrong approver.

What is the ROI of using this workflow for journal entry review and approval?

The workflow removes the administrative overhead of manually assigning reviewers, tracking correction rounds, and routing approvals based on amount, freeing finance staff to focus on the substance of each entry. Because acknowledgement and outcome emails are sent automatically, preparers spend less time asking for status updates. Table views and dashboards showing records by status also make it easier to spot entries waiting on review or approval without a separate tracking spreadsheet.

How does this compare to handling journal entry approvals manually?

Manual handling typically depends on individual staff members to notice new submissions, remember the approval threshold, and forward corrections to the right reviewer. This workflow instead moves each journal entry through Submitted, In Review, Returned, Rejected and Ready to Post statuses automatically, with the record timeline showing what happened and when. The threshold-based routing to the financial controller or finance manager also happens without anyone needing to check the total amount manually.

Who is responsible for reviewing a submitted journal entry?

A reviewer, who must not be the preparer, is assigned to check the journal entry and record whether it is correct or needs correction, along with comments. The workflow waits for this review result before proceeding, and the result and comments are saved to the record. This separation between preparer and reviewer supports a basic segregation of duties in the review step.

What happens if the reviewer finds the journal entry needs correction?

The status is set to Returned, and the preparer is emailed the reviewer's comments with a request for the corrected entry. Once the preparer replies, the corrected entry is saved to the record and the workflow returns to the In Review stage for the reviewer to re-check it. This correction cycle can repeat up to three times before the entry proceeds through the standard routing.

How does the $50,000 threshold decide who approves a journal entry?

After a journal entry passes review, the workflow checks the Total Amount field: entries over $50,000 are routed to the financial controller for approval, while entries of $50,000 or less go to the finance manager. Each approver's decision is then routed to either a Rejected or Ready to Post outcome, with the preparer notified by email accordingly. This keeps the threshold rule applied consistently without a staff member needing to check it manually each time.

What does the preparer see and receive during the process?

The preparer submits the initial journal entry through the request form, providing details such as journal type, period, accounts and amounts, total amount, business reason and supporting evidence. They receive an acknowledgement email with their reference number after submission, and may be emailed again if corrections are needed. At the end of the process they receive an email confirming whether the journal entry was rejected or is ready to post.

Can this workflow be adjusted to match our organisation's approval thresholds or steps?

Yes, the workflow can be changed by describing the change in plain English or by editing its steps directly in the workflow editor, and earlier versions are kept. This means the $50,000 threshold, the number of correction cycles, or the wording of preparer notifications can be adjusted to fit an organisation's own policies. Changes take effect for future runs without requiring a separate development project.

How is journal entry status information tracked and reported?

Each journal entry is a record with a reference number, a current status, and a timeline showing what happened at each step, including review results, corrections and approval decisions. Table views and dashboards display records grouped by status, such as In Review, Returned, Rejected or Ready to Post. Businesses should confirm how this record-keeping aligns with their own internal control and audit requirements.

Do reviewers, approvers or preparers need a login to take part?

Reviewers and approvers work as workspace members completing assigned tasks within the platform. Preparers take part through the public request form for submission and through emailed forms for acknowledgements, correction requests, and outcome notifications, without needing an account of their own.

Ready to use this workflow?

Create a free account and customise this workflow for your business.

Journal Entry Approval Workflow | assess.one