NetSuite approvals

Journal entry approval: a simple, auditable process

A lean journal approval policy that satisfies auditors without slowing the close.

6 min read · Updated 1 November 2026

On this page

Why journals need approval

Manual journals are one of the most common routes for errors and for management override of controls. Auditors almost always test them. A short, consistent approval rule protects the close.

A lean policy

  1. The preparer never approves their own journal.
  2. Manual journals above an amount need a second person — a controller or finance manager.
  3. Sensitive accounts always need approval, whatever the amount: cash, revenue, intercompany, equity, suspense.
  4. Recurring and system-generated journals (depreciation, amortisation schedules) are reviewed as a batch, not one by one.

What the approver checks

  • Supporting document attached and consistent with the entry.
  • Accounts, period, subsidiary and currency correct.
  • Reversal date set for accruals.
  • Explanation clear enough for someone who wasn't there.

Evidence that holds up

Approver, date and time on the journal record itself, plus the comment and any question asked before approving. Keep the approval inside NetSuite so the evidence sits next to the entry.

Don't let journals block the close

At month-end, approvers are busy and journals pile up. Sending each journal to the approver in Teams or Slack with the lines, amounts and attachment — and a one-click decision written back to NetSuite — removes the "I didn't see it" delay.

See Axiera Approvals on your own NetSuite records