NetSuite Insights & Guides | CuriousRubik

NetSuite Month End Close Checklist and Review Controls

Written by CuriousRubik | May 21, 2018, 12:33:00 PM

Updated 6 October 2026.

A useful NetSuite month end close checklist links every task to an owner, a prerequisite and evidence of completion. It should tell a reviewer why the numbers are ready, as well as whether a system task has been marked complete. Begin with reliable cutoffs and reconciled subledgers, complete the applicable valuation and consolidation processes, then approve the period for closure.

NetSuite provides a Period Close Checklist, but the business still owns its accounting judgments and supporting workpapers. The sequence and available tasks depend on enabled features. Adapt this framework with your controller and test it against your own account before turning it into an operating procedure.

Establish the close before the month ends

Assign a preparer and reviewer to each balance-sheet reconciliation, major estimate and reporting output. Identify deadlines for receiving, billing, time entry, expenses and integration processing. Give operational teams a clear route for reporting items that missed the cutoff.

For each task, record the required input and the task it enables. Inventory valuation may depend on complete receipts and cost processing. Revenue review may depend on updated arrangements and plans. Consolidation depends on accepted entity results, rates and intercompany work. Making these dependencies visible prevents reviewers from approving reports that will change underneath them.

Agree an escalation threshold for unresolved issues. Financial materiality, fraud indicators, statutory impact and process failure deserve different responses. A low-value unexplained bank entry can still indicate a control problem and should not disappear solely because the amount is small.

Set up the accounting periods before close

Finance should approve the fiscal calendar and any adjustment period before setup. The operator needs at least Edit access to Manage Accounting Periods.

  1. Open Setup > Accounting > Manage G/L > Manage Accounting Periods and choose Set Up Full Year.
  2. Check the fiscal start month, year, period format, naming and any approved year-end adjustment period, then save. If Multiple Calendars is enabled, use the subsidiary-calendar procedure and verify the selected calendar.
  3. Inspect the resulting hierarchy and dates for complete coverage before posting or closing. Individual periods need correct parent rollups; do not create gaps or use accounting-period setup as a substitute for tax-period requirements.

The close checklist controls review and closure of the configured accounting periods.

Stage one is completeness and cutoff

Review interface queues and rejected imports. Confirm that source systems have supplied the expected population, not merely that their latest job says “successful.” Compare record counts and monetary control totals where available, and investigate missing batches.

Have operations confirm unbilled shipments, goods received without invoices, customer returns, unsettled payment batches and late employee expenses. Finance decides the appropriate accrual, deferral or correction based on evidence and accounting policy.

Capture a cutoff snapshot for the teams preparing reconciliations. If transactions subsequently change, identify the workpapers that need refreshing. A timestamped export is useful only when its scope, account, subsidiary and period are also recorded.

Stage two is subledger and account reconciliation

Reconcile bank accounts to statements and explain outstanding items. Reconcile receivables and payables to their control accounts, including unapplied cash, credits and unusual journals. Review inventory quantities and valuation against the relevant ledger accounts and investigate negative stock or incomplete costing.

Review fixed assets, accruals, prepayments, payroll clearing and tax balances appropriate to the business. The checklist should point to approved workpapers rather than repeat every reconciliation procedure. Require preparers to explain changes from the prior period and identify aged unresolved amounts.

A completed task should carry the report or workpaper reference, preparer, review date and open exceptions. Avoid treating a tick beside “review inventory” as proof that valuation agrees with the ledger.

Stage three is dependent accounting processes

Complete foreign-currency, revenue and intercompany work in the sequence supported by your configuration. Use approved exchange-rate sources and ensure late source changes are considered before the final run.

For Advanced Revenue Management, Oracle specifies recognition before deferred revenue reclassification and calls for saving the Deferred Revenue Waterfall report at the end. Include those dependencies where the feature is used.

Reconcile intercompany activity before elimination, then review consolidated outputs and any remaining exceptions. Confirm that the group report uses the intended subsidiary context and accounting book. A local trial balance approval does not by itself establish that consolidation is correct.

Understand locking and closing

A locked period limits posting according to permissions; closing prevents general-ledger posting into that period. Oracle documents both the ability of suitably authorised users to override locking restrictions and the need to reopen a closed period for GL-impacting changes. Build your internal approval controls around that distinction.

Define who may request an exception, who approves it and which reports must be regenerated. Do not distribute broad override permissions simply to reduce close-day support requests. Monitor exceptional access and remove temporary arrangements when their purpose ends.

Quick Close deserves particular care: Oracle warns that it marks tasks complete without running the closing processes. Use only an approved process in which the necessary work is independently established. A completed checklist state is not proof that valuation, recognition or reconciliation has run.

Hypothetical close dependency example

A fictional distributor plans to close September on its fifth working day. Its warehouse confirms receipts on day one, inventory accounting validates costing on day two, and the controller reviews gross margin on day three.

On day three, a missing September receipt is identified. The issue is assigned to operations, and finance determines the correct posting treatment. If September source data changes, the inventory reconciliation and margin review are invalidated and rerun. The close tracker preserves the first review and records the replacement evidence.

Without dependency tracking, all three tasks might remain marked complete while the underlying numbers changed. With it, the controller can explain the effect of the exception and decide whether the revised evidence supports closure. The dates in this example are illustrative, not a promised close timetable.

A reusable close row

For every significant task, include:

  • Task name and the account, entity or process covered
  • Preparer, reviewer and backup owner
  • Cutoff time and prerequisite tasks
  • Report parameters or workpaper reference
  • Difference or exception requiring attention
  • Corrective action, owner and due date
  • Review outcome and final evidence version
  • Conditions that require the task to be repeated

Use separate statuses for prepared, under review, blocked and accepted. A task awaiting an upstream correction should remain visibly blocked rather than being called complete with a footnote.

Finish with a reporting and release review

Compare the accepted trial balance with the management reporting pack. Review unusual movements, cash, working capital, revenue, margin and any significant estimates. Check whether report filters, exchange rates or layouts changed during the close.

Once the controller approves closure, preserve the final pack and communicate the late-transaction process. Run a short retrospective focused on recurring causes and missing evidence. Improve the originating process where possible instead of adding another manual reconciliation every month.

What should happen before a period is locked?

Confirm cutoffs, communicate restrictions and identify authorised adjustment routes. Locking is part of controlled processing; it should support the close sequence rather than substitute for reconciliations.

How should late transactions be handled?

Finance should determine the correct treatment and obtain the required approval. If reopening is necessary, assess downstream periods and repeat affected reconciliations and reports. Avoid changing dates simply to bypass a control.

Use your last completed close and its unresolved exceptions as the starting point for a close improvement discussion.

Related resources