Handling Closed & Locked Accounting Periods in ZoneReconcile

ZoneReconcile respects NetSuite's accounting period controls — understanding how closed and locked periods affect reconciliation processing helps accountants anticipate system behavior, resolve errors, and configure roles correctly.

System behaviors and error symptoms

Attempting to process or approve transactions within a locked or closed period triggers the following guardrails to protect General Ledger (GL) integrity:

• Posting errors: The system generates errors such as LOCKED_PERIOD_ERROR, or warns that the selected transaction date falls outside an active, open accounting period.
• Automatic period shifting: Based on your accounting configuration (Setup > Accounting > Accounting Preferences), the system may automatically reassign the transaction's Posting Period to either First Open Period or Current Period, while preserving the original transaction date.
• GL impact restrictions: High-impact transaction types — such as inventory transactions — are completely blocked from approval when costing calculations cannot be executed inside a closed period.
• Reconciliation halts: When a matched transaction resides in a locked accounting period, ZoneReconcile respects the permissions of the user who triggered processing and books the transaction according to NetSuite logic.

Period posting modes

Accountants configure backdated transaction behavior using 2 core posting modes in Accounting Preferences:

• Current Period: Posts backdated transactions directly to the active open period.
• First Open Period: Automatically posts backdated entries to the next open period immediately following the closed one.

Role-based access controls

• Administrators: Typically configured with Override Period Restrictions set to TRUE, allowing them to post transactions into locked (but not fully closed) periods.
• Custom roles: Generally set to Override Period Restrictions = FALSE, which blocks posting attempts to locked periods.

Scripting and automation considerations

Important: Background automated tasks — such as Map/Reduce scripts — frequently run under Administrator privileges. If period restrictions are not explicitly enforced in the script logic, these routines may inadvertently process transactions against locked periods. Review your script configurations to confirm period controls are applied as intended.

Manual processing by custom roles inherently enforces period restrictions. Automated background tasks do not unless explicitly restricted within the script logic.

Reconciliation of open transactions (transaction is created)

This scenario applies to transactions that impact Accounts Receivable (AR) or Accounts Payable (AP), where ZoneReconcile creates the transaction (for example: Invoice, Vendor Bill, Credit Memo, Journal Entry).

• When the date of the created transaction falls within a locked period, the system respects the Override Period Restrictions setting of the user who triggered the processing — whether processed via Suitelet or Map/Reduce script.
• The ZR Process Bank Statement Transaction MR script — triggered automatically during auto-processing via ZR Auto Import MR — is controlled by the role set at Setup > Company > General Preferences > Custom Preferences > Global Processing Role.

Reconciliation of closed transactions (transaction is linked)

This scenario applies to transactions that already impact bank accounts and only need to be linked and updated to match the bank statement (for example: Payments, Deposits, Journal Entries).

Important: When the transaction date falls within a locked period and the date must be changed, the system throws an error and does not proceed with linking — even if the user has permission to override period restrictions. This behavior applies during both manual and auto-processing, regardless of the Global Processing Role setting.

Transaction types by accounting task

NetSuite controls transaction booking based on the following accounting task categories: