The open accounting period problem
Open accounting periods are a control risk that most NetSuite teams don't monitor. Here's how to find them and what to do about them.
An open accounting period in NetSuite is a period that hasn't been locked. Transactions can still be posted to it, modified in it, or deleted from it. For an accounting period that closed six months ago, that's a material control risk — your historical financial statements can be changed without any formal re-opening process.
The root cause is process, not system. NetSuite supports period locking — a feature that prevents posting to a closed period without explicit permission. But the feature requires someone to actively close periods, and closing periods requires reconciling the period first. When close is running late, periods get left open to avoid the formal reconciliation step.
The audit risk is straightforward: an open period from Q3 that should have been closed in October means that any journal entry can be backdated to Q3 by a user with the appropriate role. External auditors check for open periods. Regulators check for open periods. The finding — 'accounting periods left open beyond 30 days' — appears in more management letters than it should.
The fix requires two steps: close the backlog of open periods, and build a process that prevents it from happening again. Closing the backlog requires a formal reconciliation for each period, which is why it didn't happen the first time. Preventing recurrence requires automating the period-close reminder and assigning clear ownership to the close process.
NetSuite's period management allows locking at different levels — all transactions, or all except adjusting journals. The graduated approach — lock ordinary transactions promptly while leaving adjusting journals open for a further period — is a practical compromise that addresses the main risk without creating operational problems from premature locking.