Closing a month end in NetSuite means working through the platform's built-in Period Close Checklist in order: locking subledgers, resolving mismatches, revaluing foreign currency, eliminating intercompany transactions where applicable, recognizing revenue, and finally locking the period so no further postings are allowed. This guide walks through the exact sequence, what to check at each step, and where teams typically get stuck.
What Does "Closing a Period" Mean in NetSuite?
In NetSuite, a "period" is an accounting period defined in Manage Accounting Periods, usually a calendar month, though some companies use a 4-4-5 or other fiscal calendar. Closing that period is the process of confirming every transaction that belongs in it has been recorded, reviewed, and reconciled, then locking the subledgers and the general ledger so nothing can be posted, backdated, or edited into that period afterward without deliberately reopening it.
NetSuite tracks this through the Period Close Checklist, a task list attached to each accounting period. Each task on the checklist (locking A/P, locking A/R, revaluing currency, and so on) has its own status, and the period itself cannot be fully closed until every task on the checklist is marked complete. This is different from simply changing a period's status manually. NetSuite expects the checklist tasks to be worked through in sequence, and skipping ahead can leave the ledger in an inconsistent state, for example if intercompany elimination runs before final journal entries are posted.
For companies on NetSuite OneWorld, the same checklist logic applies per subsidiary, with additional steps for consolidation, intercompany elimination, and consolidated exchange rates layered on top.
What Do You Need to Do Before You Start the NetSuite Month-End Close?
Before opening the checklist for the current month, a few prerequisites need to be confirmed. Skipping these is one of the most common reasons a close stalls halfway through.
- Go to Setup > Accounting > Manage Accounting Periods. This is the control panel for all fiscal periods and where the checklist for each month lives. Menu wording can shift slightly between NetSuite releases, so if this exact path doesn't match what you see, look under Setup > Accounting for a "Manage Accounting Periods" or "Accounting Periods" record.
- Confirm all prior periods are fully closed. NetSuite generally expects periods to close in order. If last month is still open, or partially closed with unfinished checklist items, that needs to be resolved first since it will affect balances carried into the current period.
- Open the checklist icon next to the target month. On the Manage Accounting Periods page, each period row has a checklist icon that opens the Period Close Checklist for that specific month. This is where you will work through every step below.
- Confirm all subsidiaries are ready (OneWorld only). If you run multiple subsidiaries, check that transactions have been posted and reviewed in each one before starting elimination and consolidation steps.
- Notify AP/AR and operational teams of the cutoff. Late invoices, unposted expense reports, and pending vendor bills are a frequent source of reopened periods, so a clear internal cutoff communication reduces rework.
How to Complete the NetSuite Period Close Checklist (Step by Step)
The Period Close Checklist presents tasks in a recommended order. The steps below follow that order and reflect the tasks most companies will see, though the exact list on your instance depends on which NetSuite modules and features are enabled (Multi-Book Accounting, Advanced Revenue Management, OneWorld, and so on).
Step 1: Lock A/R, Lock A/P, and Lock All in NetSuite
Locking a subledger prevents new transactions from posting to it for the period being closed, while still allowing later periods to remain open for ongoing work. Lock A/R stops new customer invoices, credit memos, and payments from posting into the closing period. Lock A/P does the same for vendor bills, bill credits, and payments. Lock All extends this to every subledger, including inventory and payroll where applicable.
What to check: confirm with AR and AP teams that all invoices and bills for the period are entered before locking, since a locked subledger will reject new transactions dated into that period (you would need Override Period Restrictions permission to force one through, which should be an exception, not routine practice). Locking early in the checklist is intentional: it stops the transaction volume from moving while the rest of the close proceeds.
Step 2: Resolve Date and Period Mismatches
This step catches transactions where the transaction date and the posting period don't line up, for example an invoice dated in the new month but still assigned to the closing period, or the reverse. NetSuite's checklist typically surfaces these through saved searches or the built-in reconciliation tools rather than a single button.
What to check: run a search for transactions with a transaction date outside the current period's start and end dates but still posted into that period. Correct the period assignment on each one before moving forward, since these mismatches distort both the closing period's numbers and the following period's opening balances.
Step 3: Review Inventory and Cost Accounting Adjustments
If your NetSuite instance uses inventory management, this step covers negative inventory situations, standard cost or average cost revaluations, and any inventory valuation adjustments that need to post before the period locks. This step is not applicable to service-only businesses.
What to check: look for items with negative on-hand quantities, confirm any landed cost or cost roll-up batches have processed, and review inventory valuation reports against the general ledger inventory asset account for discrepancies.
Step 4: Revalue Open Foreign Currency Balances
For companies transacting in multiple currencies, open balances in foreign-currency-denominated accounts (AR, AP, bank accounts) need to be revalued to reflect current exchange rates as of period end. NetSuite runs this through a currency revaluation process that calculates unrealized gains or losses and posts them to the appropriate GL accounts.
What to check: confirm exchange rates are current in the exchange rate table before running revaluation, and review the resulting unrealized gain/loss journal entry for reasonableness rather than accepting it automatically, particularly for currencies with recent volatility.
Step 5: Calculate Consolidated Exchange Rates
This step applies to multi-currency and OneWorld environments consolidating subsidiaries that report in different base currencies. NetSuite's Consolidated Exchange Rates feature translates subsidiary-level financials into the parent's reporting currency for consolidated statements, using rate types (current, average, historical) appropriate to each account type.
What to check: confirm the correct rate type is applied for balance sheet versus income statement accounts, and check that rates have been entered or synced for the current period before generating consolidated financial statements.
Step 6: Eliminate Intercompany Transactions
For OneWorld customers with intercompany activity, this step removes intercompany transactions (intercompany invoices, intercompany journal entries, intercompany loans) from the consolidated financials so they don't overstate revenue, expenses, or balances at the group level. NetSuite's intercompany elimination functionality automates much of this if intercompany transactions are tagged correctly at the point of entry.
What to check: verify intercompany transactions are correctly flagged with matching elimination accounts on both sides, and review the elimination journal entries the system generates for any unmatched or partially eliminated pairs, which are a common source of consolidation errors. This is where mismatched intercompany entries most often surface, and manually tracing them across subsidiaries in spreadsheets is one of the slower parts of a OneWorld close.
Step 7: Recognize and Reclassify Revenue
Companies using Advanced Revenue Management run this step to recognize revenue according to defined recognition rules and schedules (relevant for subscription, multi-element, or milestone-based revenue arrangements) and to reclassify amounts between deferred and recognized revenue accounts as performance obligations are satisfied.
What to check: confirm revenue recognition plans have been created for all applicable transactions and that the recognition journal entries for the period have run before moving on, since a missed recognition run will misstate both revenue and deferred revenue balances.
Step 8: Create Period-End Journals and GL Audit Numbering
The final checklist step covers any remaining manual period-end journal entries (accruals, allocations, adjusting entries) and GL Audit Numbering, which NetSuite uses to assign sequential, gapless numbers to GL transactions for audit trail purposes, if the feature is enabled on your account.
What to check: confirm all manual adjusting entries are posted and approved, and that GL audit numbering has processed without gaps or errors before proceeding to the final close and lock.
How to Complete the Final Close and Lock the Period in NetSuite
Once every task on the Period Close Checklist shows as complete, the final step is to review each item one more time and click Close on the last checklist item to lock the period entirely. This is distinct from the individual A/R, A/P, and All locks applied in Step 1: those lock subledgers, while this final close locks the accounting period itself so no further postings, of any kind, can be made into it without reopening.
- Review the checklist status for every task and confirm none are marked incomplete or skipped.
- Pull a trial balance and compare it against expectations before locking, since this is the last easy checkpoint before the period is sealed.
- Click Close on the final checklist item (wording may read as "Close Period" depending on your NetSuite version) to lock the period.
- Confirm the period status on Manage Accounting Periods now shows as closed.
How to Reopen a Closed Period in NetSuite
Occasionally a closed period needs to be reopened, typically to correct an error discovered after lock. NetSuite allows this from Setup > Accounting > Manage Accounting Periods by selecting the period and choosing the option to reopen it (this reverses the lock status but does not undo the checklist task completions, which need to be reviewed again if the underlying transactions change).
- Confirm reopening is genuinely necessary rather than posting the correction into the current open period, since reopening a closed period can affect previously issued financial statements or filings.
- Have the correction ready before reopening, so the period is reopened, corrected, and reclosed in one controlled pass rather than left open indefinitely.
- Document why the period was reopened and who approved it, since this is a common audit and SOX control point.
- Reclose the period through the checklist once the correction is posted, rather than assuming the prior lock still applies.
What Are the Most Common NetSuite Month-End Close Errors and Blockers?
Most delays in a NetSuite month-end close trace back to a handful of recurring issues:
- Unposted or late transactions. Vendor bills, expense reports, or invoices entered after the subledger lock force a choice between using Override Period Restrictions (an exception, not a routine step) or delaying the close.
- Unmatched intercompany transactions. One side of an intercompany entry posted without its counterpart, which blocks clean elimination and consolidation.
- Stale or missing exchange rates. Currency revaluation and consolidated exchange rate calculations depend on rates being current; missing rates for a given date will either block the process or produce incorrect revaluation entries.
- Revenue recognition plans not created or not run. Transactions without a recognition schedule, or a recognition batch that wasn't executed, leave deferred revenue misstated.
- Reconciliation mismatches discovered late. Bank, AR, or AP reconciliation differences found after subledgers are locked require either reopening the lock or carrying the discrepancy to the next period, neither of which is ideal.
- Manual spreadsheet tracking for OneWorld consolidation. Teams running elimination checks or FX true-ups in spreadsheets alongside NetSuite often lose time reconciling the spreadsheet back to what NetSuite actually posted.
How to Automate and Speed Up Your NetSuite Month-End Close
NetSuite's native Quick Close feature can shorten the close for periods with limited exceptions, by allowing the system to summarize AR and AP rather than lock every subledger task individually. This works well for a simple, low-transaction period, but most enterprise and OneWorld environments need more than a faster path through native functionality.
Common ways teams speed up the close beyond Quick Close:
- Standardizing a NetSuite period close checklist as a shared internal document (beyond what NetSuite tracks natively) so every close owner knows what's expected of them and by when.
- Automating recurring adjusting journal entries and accruals rather than rebuilding them manually each month.
- Pre-validating intercompany transactions at the point of entry so elimination doesn't surface mismatches for the first time at close.
- Running reconciliations continuously through the month rather than only at close, so period-end review is confirmation rather than discovery.
- Using saved searches or dashboards to flag date/period mismatches and unposted transactions before the checklist forces the issue.
These practices reduce close time, but for enterprise finance teams running multiple subsidiaries and high transaction volume, manual checklist discipline alone tends to hit a ceiling. This is where a dedicated continuous close layer on top of NetSuite becomes relevant.
How Bluecopa Extends NetSuite's Native Close Checklist for Enterprise and GCC Teams
NetSuite's Period Close Checklist is built to guide a close through the right sequence of steps, but it doesn't automate the underlying reconciliation, matching, or exception resolution work behind each step. For enterprise and Global Capability Center (GCC) finance teams running multi-subsidiary, multi-currency OneWorld instances, that gap tends to show up in three places: high-volume transaction matching, intercompany reconciliation, and FX revaluation checks, all of which are typically still done manually or in spreadsheets before the checklist tasks can be marked complete.
Bluecopa, an AI-native finance operations platform powered by SamyxAI, is designed to sit on top of NetSuite as an automation and extension layer rather than a replacement for NetSuite's own controls or checklist. In practice, that looks like:
- Automating matching and mismatch resolution for high-volume AR and AP transactions before subledgers are locked, so exceptions are surfaced and cleared earlier in the month instead of discovered at Step 1 of the checklist.
- Automating intercompany reconciliation across subsidiaries, flagging unmatched or partial intercompany entries before the elimination step runs in NetSuite, which reduces the manual spreadsheet tracing that typically slows down Step 6.
- Running FX revaluation checks ahead of lock, so currency exposure and open foreign balances are reviewed continuously rather than only at the point NetSuite's revaluation task appears on the checklist.
For GCCs managing close activities across regions or entities on behalf of a parent organization, this kind of pre-lock automation matters particularly because the volume of intercompany and multi-currency activity scales with each additional subsidiary NetSuite OneWorld consolidates. Bluecopa's role here is to make the inputs going into NetSuite's checklist cleaner and faster to validate, working alongside record to report processes rather than sitting outside them. NetSuite remains the system of record and the system that enforces the actual period lock; Bluecopa's job is to reduce the manual effort required to get each checklist step ready to close.
FAQ
1. What is the NetSuite period close checklist?
It's a built-in task list attached to each accounting period in NetSuite, covering steps like locking subledgers, resolving date mismatches, revaluing foreign currency, eliminating intercompany transactions, recognizing revenue, and posting final journals, in a recommended sequence, before the period can be fully closed.
2. How do I close an accounting period in NetSuite?
Go to Setup > Accounting > Manage Accounting Periods, open the checklist icon for the target period, and work through each checklist task (locking A/R, A/P, resolving mismatches, revaluation, elimination, revenue recognition, and final journals) in order, then click Close on the final checklist item to lock the period.
3. How do I reopen a closed period in NetSuite?
From Manage Accounting Periods, select the closed period and choose the option to reopen it. This removes the lock but doesn't automatically undo completed checklist tasks, so any correction should be posted and the period reclosed through the checklist again once the fix is made.
4. What does Lock A/R, Lock A/P, and Lock All mean in NetSuite?
These are checklist tasks that stop new transactions from posting into a period for accounts receivable, accounts payable, and all subledgers respectively, without preventing later periods from staying open for ongoing work.
5. What is NetSuite Quick Close?
Quick Close is a NetSuite feature that lets a period close faster by summarizing AR and AP activity instead of requiring every subledger task to be worked individually. It's best suited to periods with limited exceptions rather than complex multi-subsidiary closes.
6. Can I automate the NetSuite month-end close?
NetSuite provides native tools like Quick Close and the Period Close Checklist to streamline the process, and enterprise teams often add a layer on top, such as Bluecopa, to automate transaction matching, intercompany reconciliation, and FX checks before the native checklist steps are run, particularly for high-volume, multi-subsidiary NetSuite OneWorld environments.
