What is journal entry approval in NetSuite?

Journal entry approval in NetSuite is a control that requires a journal entry to be reviewed and approved before it posts to the general ledger. NetSuite supports this two ways: a native accounting preference called Require Approvals on Journal Entries, which relies on the Journal Approval permission, and workflow-based routing built with SuiteFlow or the SuiteApprovals SuiteApp for multi-step approval. The purpose is to keep unreviewed entries out of the ledger, enforce segregation of duties between the person who records an entry and the person who approves it, and create a documented review trail. Lightbridge ERP treats journal entry approval as a designed control rather than a default left untouched.

How do you enable journal entry approval in NetSuite?

The native control is enabled at Setup > Accounting > Accounting Preferences. On the General subtab, in the General Ledger section, check the Require Approvals on Journal Entries box. After that, a user with the Journal Approval permission at Edit level or higher must approve each journal entry before it posts to the general ledger. By default only administrators hold the Journal Approval permission, and an administrator can add it to a customized role so specific reviewers can approve. For routing beyond that single check, the Journal Entries setting on the Approval Routing subtab hands approval to a SuiteFlow or SuiteApprovals workflow. Lightbridge ERP configures the preference, permissions, and any workflow together so the control matches the close process.

What is the difference between native and custom (SuiteFlow) journal entry approval?

Native journal entry approval is the Require Approvals on Journal Entries preference. It is a single gate: any entry must be approved by someone holding the Journal Approval permission before it posts. It does not by itself route entries by amount, subsidiary, or approval tier, and a permission holder can approve their own entry unless restricted. Custom approval uses SuiteFlow or the SuiteApprovals SuiteApp to route an entry through structured logic. A SuiteFlow workflow can route to as many as three approvers, block self-approval by checking the Created By field against the logged-in user, and notify recipients on rejection. Workflow routing does not rely on the Journal Approval permission to decide who approves. Lightbridge ERP recommends the native check for simple needs and workflow routing when tiered or conditional approval is required.

How does journal entry approval support segregation of duties?

Segregation of duties is the principle that no single person should control an entire financial transaction end to end. For journal entries, that means the person who creates an entry should not also be the person who approves and posts it. Journal entry approval enforces this by inserting a second reviewer between recording and posting. The native NetSuite preference alone allows a permission holder to approve their own entry, so strong segregation usually depends on a workflow rule that compares the logged-in user to the entry Created By field and blocks self-approval. Paired with role-based permissions that separate who can create from who can approve, this gives auditors evidence that recording and authorization sit with different people. Lightbridge ERP designs these roles and rules so the control holds in practice, not just on paper.

Does journal entry approval support SOX compliance?

Journal entry approval is a control that supports, but does not by itself achieve, SOX compliance. Under the Sarbanes-Oxley Act, public and many pre-IPO companies must maintain internal control over financial reporting, and manual journal entries are a recognized area of risk because they can bypass routine transaction controls. Requiring approval before an entry posts, separating the creator from the approver, and retaining an audit trail through NetSuite System Notes and GL Audit Numbering are the kinds of controls that address that risk. Compliance is a matter of overall control design, testing, and management assertion, not a single setting, so journal entry approval is one supporting control among many. This is general information, not accounting, tax, or legal advice. Lightbridge ERP, whose team includes CPAs and controllers, helps map these controls to a reporting framework.

What audit trail does NetSuite keep for approved journal entries?

NetSuite records the history of each journal entry in System Notes on the record, capturing who made a change, what changed, and when, including approval actions. The journal entry also carries a System Information subtab that lists active and executed workflows against the record, so workflow-driven approvals are traceable. For entries that impact the general ledger, GL Audit Numbering assigns a sequential number to posting transactions, and GL impact locking generates copy and reversal transactions rather than silently altering a numbered entry, which preserves an unbroken record. Together these give accounting and external auditors a defensible history of how an entry was created, approved, and posted. Lightbridge ERP configures these features so the audit trail is complete before an auditor asks for it.

Can NetSuite route journal entry approvals by amount or subsidiary?

The native Require Approvals on Journal Entries preference is a single approval gate and does not route by amount, subsidiary, or approval tier on its own. Conditional routing of that kind is built with SuiteFlow or delivered through the SuiteApprovals SuiteApp. A workflow can branch on fields such as amount or subsidiary and direct an entry to the appropriate approver, and a SuiteFlow workflow can route through as many as three approvers before an entry is approved for posting. Because this logic is configured rather than switched on, the design should reflect the organization approval matrix and delegation of authority. Lightbridge ERP scopes and builds this routing under change control so each rule is documented and testable.

How does Lightbridge ERP help configure NetSuite journal entry approval?

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm that delivers NetSuite in-house. It configures journal entry approval end to end: enabling the native preference where a single gate is enough, and building SuiteFlow or SuiteApprovals routing where tiered, amount-based, or self-approval-blocking logic is required. Because the team includes CPAs and controllers, the configuration is shaped by how the control has to behave for the close and for auditors, not just by what the software can toggle. Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, so its platform advice is driven by fit rather than commission. This is general information, not accounting, tax, or legal advice; confirm control design with your auditor.

JH Written by Jully Hayasaka with Robert LabardeeNetSuite Advanced Accounting Lead and Founder and CEO

Last updated July 2026.

What is NetSuite journal entry approval?

Lightbridge ERP defines journal entry approval as the internal control that requires a second person to review and approve a journal entry before it posts to the general ledger. In NetSuite, this control enforces segregation of duties, so the person who records an entry is not the person who approves and posts it.

NetSuite controls advisory Talk to an ERP advisor

Journal entry approval is a control that reviews an entry before it posts to the general ledger.

A journal entry is a direct posting to the general ledger, which makes it one of the highest-risk actions in an accounting system: it can move balances without a customer, vendor, or transaction behind it. Journal entry approval is the control that requires a second person to review and approve an entry before it posts. The concept is platform-neutral, and NetSuite is used here as a concrete example of how the control is implemented.

The purpose is straightforward. Approval keeps unreviewed entries out of the ledger, it separates the person who records an entry from the person who authorizes it, and it produces a documented trail of who did what. For how those posted entries then roll up into financial statements and dashboards, see the Lightbridge ERP guide to NetSuite reporting.

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm that delivers NetSuite in-house. It treats journal entry approval as a designed control, tuned to the close process and the control environment, rather than a default setting left in place or ignored. This guide is general information, not accounting, tax, or legal advice.

NetSuite implements journal entry approval as a native check plus optional workflows.

NetSuite journal entry approval has two layers. A native accounting preference provides a single approval gate, and workflow tools add structured routing on top of it. Each layer has a distinct job, and choosing between them is the first design decision for any NetSuite controls project.

Native approval preference

NetSuite offers a built-in control called Require Approvals on Journal Entries. When enabled, an entry cannot post until a user with the Journal Approval permission approves it, so no journal reaches the general ledger unreviewed.

SuiteFlow custom routing

SuiteFlow, the NetSuite workflow engine, builds approval routing beyond the native check. A custom workflow can route a journal entry through as many as three approvers and email specific recipients when an entry is rejected.

SuiteApprovals SuiteApp

The SuiteApprovals SuiteApp packages configurable approval routing that includes journal entries. It supports approval logic without hand-building every workflow rule, a common path for teams that want structured multi-tier routing.

Audit trail and posting

Every approval action is captured in System Notes on the record. Combined with GL Audit Numbering, this gives accounts payable and accounting a defensible history of who created, approved, and posted each entry.

NetSuite journal entry approval splits into a native preference and workflow routing.

The native preference is fast to switch on but limited to a single gate. SuiteFlow and the SuiteApprovals SuiteApp add multi-step routing, self-approval blocking, and conditional logic. Distinguishing the two accurately matters, because they behave differently and rely on different mechanisms to decide who can approve.

Native: Require Approvals on Journal Entries

Set at Setup > Accounting > Accounting Preferences on the General subtab, in the General Ledger section. When checked, a user with the Journal Approval permission (Edit level or higher) must approve each entry before it posts. By default only administrators hold that permission, and it can be added to a custom role.

Native: what the permission does

The Journal Approval permission determines who may approve. A user who holds it can approve their own entry at the time of entry unless a workflow restricts it, so the native preference alone does not guarantee that the creator and approver are different people.

Custom: SuiteFlow approval routing

Enabled through the Journal Entries setting on the Approval Routing subtab of Accounting Preferences, a SuiteFlow workflow handles routing. It can route to as many as three approvers, block self-approval by comparing the logged-in user to the Created By field, and notify recipients on rejection.

Custom: SuiteApprovals SuiteApp

For teams that prefer a packaged approach, the SuiteApprovals SuiteApp provides workflow-based approval that includes journal entries. Workflow-driven routing does not use the Journal Approval permission to decide who approves, so approver authority is defined in the workflow itself.

NetSuite journal entry approval enforces segregation of duties between creator and approver.

Segregation of duties is the principle that no one person should control a financial transaction from start to finish. For journal entries, the line to hold is between recording an entry and authorizing it: the person who creates a journal should not be the person who approves and posts it. Journal entry approval is the mechanism that inserts a second reviewer at exactly that point.

There is a subtlety in NetSuite that a careful design has to address. The native Require Approvals on Journal Entries preference gates posting on the Journal Approval permission, but a user who holds that permission can approve an entry they created themselves unless a workflow prevents it. Robust segregation therefore usually pairs the native gate with a SuiteFlow rule that compares the logged-in user to the Created By field and blocks self-approval, alongside role permissions that separate who can create entries from who can approve them.

Segregation of duties also reaches beyond the single entry into how books, subsidiaries, and roles are structured. For groups running parallel accounting books where controls must hold across each book, see the Lightbridge ERP guide to NetSuite multi-book accounting. Lightbridge ERP designs the roles and workflow rules so the separation is real in the system, not merely stated in a policy document.

Journal entry approval is a control that supports SOX and ICFR, not a compliance guarantee.

For public companies, and for pre-IPO companies preparing for the requirement, the Sarbanes-Oxley Act calls for internal control over financial reporting, or ICFR. Manual journal entries are a recognized risk area within ICFR because they post directly to the ledger and can sidestep the routine controls that govern ordinary transactions. Requiring review and approval before an entry posts is a direct response to that risk, which is why journal entry approval features in most SOX control matrices.

It is important to be precise about scope. Journal entry approval is one supporting control, not compliance in itself. SOX compliance rests on the overall design of controls, on testing that they operate, and on management assertion, so a single NetSuite setting does not make an organization compliant. What NetSuite provides is the raw material: approval gating, role-based access, System Notes that record who changed what and when, and GL Audit Numbering that keeps posted entries in a sequential, tamper-evident record. See how those posted entries surface in the NetSuite reporting guide, and how revenue-related postings are governed under the applicable standard in the guide to ASC 606 revenue recognition. This is general information, not accounting, tax, or legal advice. Lightbridge ERP, whose team includes CPAs and controllers, helps map these controls to the relevant framework and to an auditor's expectations.

Lightbridge ERP configures NetSuite journal entry approval to the control environment.

Turning a preference on is quick. Designing an approval control that satisfies segregation of duties, matches the organization's delegation of authority, and stands up to an audit is the harder work. Lightbridge ERP delivers NetSuite in-house and configures the native preference, the Journal Approval permission and roles, and any SuiteFlow or SuiteApprovals routing as a single coherent control, then documents how it behaves.

Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its platform advice is driven by fit rather than commission. A structured ERP consulting engagement is the right starting point when journal entry approval is part of a wider push to strengthen financial controls in NetSuite.

NetSuite journal entry approval: frequently asked questions

What is journal entry approval in NetSuite?: Journal entry approval in NetSuite is a control that requires a journal entry to be reviewed and approved before it posts to the general ledger. NetSuite supports this two ways: a native accounting preference called Require Approvals on Journal Entries, which relies on the Journal Approval permission, and workflow-based routing built with SuiteFlow or the SuiteApprovals SuiteApp for multi-step approval. The purpose is to keep unreviewed entries out of the ledger, enforce segregation of duties between the person who records an entry and the person who approves it, and create a documented review trail. Lightbridge ERP treats journal entry approval as a designed control rather than a default left untouched.
How do you enable journal entry approval in NetSuite?: The native control is enabled at Setup > Accounting > Accounting Preferences. On the General subtab, in the General Ledger section, check the Require Approvals on Journal Entries box. After that, a user with the Journal Approval permission at Edit level or higher must approve each journal entry before it posts to the general ledger. By default only administrators hold the Journal Approval permission, and an administrator can add it to a customized role so specific reviewers can approve. For routing beyond that single check, the Journal Entries setting on the Approval Routing subtab hands approval to a SuiteFlow or SuiteApprovals workflow. Lightbridge ERP configures the preference, permissions, and any workflow together so the control matches the close process.
What is the difference between native and custom (SuiteFlow) journal entry approval?: Native journal entry approval is the Require Approvals on Journal Entries preference. It is a single gate: any entry must be approved by someone holding the Journal Approval permission before it posts. It does not by itself route entries by amount, subsidiary, or approval tier, and a permission holder can approve their own entry unless restricted. Custom approval uses SuiteFlow or the SuiteApprovals SuiteApp to route an entry through structured logic. A SuiteFlow workflow can route to as many as three approvers, block self-approval by checking the Created By field against the logged-in user, and notify recipients on rejection. Workflow routing does not rely on the Journal Approval permission to decide who approves. Lightbridge ERP recommends the native check for simple needs and workflow routing when tiered or conditional approval is required.
How does journal entry approval support segregation of duties?: Segregation of duties is the principle that no single person should control an entire financial transaction end to end. For journal entries, that means the person who creates an entry should not also be the person who approves and posts it. Journal entry approval enforces this by inserting a second reviewer between recording and posting. The native NetSuite preference alone allows a permission holder to approve their own entry, so strong segregation usually depends on a workflow rule that compares the logged-in user to the entry Created By field and blocks self-approval. Paired with role-based permissions that separate who can create from who can approve, this gives auditors evidence that recording and authorization sit with different people. Lightbridge ERP designs these roles and rules so the control holds in practice, not just on paper.
Does journal entry approval support SOX compliance?: Journal entry approval is a control that supports, but does not by itself achieve, SOX compliance. Under the Sarbanes-Oxley Act, public and many pre-IPO companies must maintain internal control over financial reporting, and manual journal entries are a recognized area of risk because they can bypass routine transaction controls. Requiring approval before an entry posts, separating the creator from the approver, and retaining an audit trail through NetSuite System Notes and GL Audit Numbering are the kinds of controls that address that risk. Compliance is a matter of overall control design, testing, and management assertion, not a single setting, so journal entry approval is one supporting control among many. This is general information, not accounting, tax, or legal advice. Lightbridge ERP, whose team includes CPAs and controllers, helps map these controls to a reporting framework.
What audit trail does NetSuite keep for approved journal entries?: NetSuite records the history of each journal entry in System Notes on the record, capturing who made a change, what changed, and when, including approval actions. The journal entry also carries a System Information subtab that lists active and executed workflows against the record, so workflow-driven approvals are traceable. For entries that impact the general ledger, GL Audit Numbering assigns a sequential number to posting transactions, and GL impact locking generates copy and reversal transactions rather than silently altering a numbered entry, which preserves an unbroken record. Together these give accounting and external auditors a defensible history of how an entry was created, approved, and posted. Lightbridge ERP configures these features so the audit trail is complete before an auditor asks for it.
Can NetSuite route journal entry approvals by amount or subsidiary?: The native Require Approvals on Journal Entries preference is a single approval gate and does not route by amount, subsidiary, or approval tier on its own. Conditional routing of that kind is built with SuiteFlow or delivered through the SuiteApprovals SuiteApp. A workflow can branch on fields such as amount or subsidiary and direct an entry to the appropriate approver, and a SuiteFlow workflow can route through as many as three approvers before an entry is approved for posting. Because this logic is configured rather than switched on, the design should reflect the organization approval matrix and delegation of authority. Lightbridge ERP scopes and builds this routing under change control so each rule is documented and testable.
How does Lightbridge ERP help configure NetSuite journal entry approval?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm that delivers NetSuite in-house. It configures journal entry approval end to end: enabling the native preference where a single gate is enough, and building SuiteFlow or SuiteApprovals routing where tiered, amount-based, or self-approval-blocking logic is required. Because the team includes CPAs and controllers, the configuration is shaped by how the control has to behave for the close and for auditors, not just by what the software can toggle. Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, so its platform advice is driven by fit rather than commission. This is general information, not accounting, tax, or legal advice; confirm control design with your auditor.

From a default setting to a control your auditors trust.

When journal entry approval has to enforce segregation of duties and support SOX controls, Lightbridge ERP designs the NetSuite configuration end to end, vendor-neutral by design and delivered in-house.

Talk to an ERP advisor Explore ERP consulting