Resolve bank statements that remain in Processing, To Process, or Currently processing status in ZoneReconcile. Identify the cause, apply the matching fix, and unlock the statement when needed.
Looking for credit card statements instead? See Credit Card Statements: How to Unlock Statements Stuck in Processing.
Overview
ZoneReconcile automatically decides whether to process a statement immediately or as a scheduled background job in NetSuite. The decision depends on the number of submitted lines that display Yes in the first column.
- The threshold for scheduled processing is approximately 40 statement lines. When ZoneReconcile schedules the job, a green message appears stating that the statement is currently processing.
- When NetSuite finishes processing all the data, the solution sends an email to the user and unlocks the statement.
- Occasionally, a statement stays in Processing, To Process, or Currently processing status because of script conflicts, empty statement files, or system errors during the auto-import chain.
Review the causes below and apply the matching resolution.
Common causes and resolutions
Script deployment conflicts
If the ZR Process Bank Statement Transaction MR script is still processing a previous batch, later auto-imports can fail to trigger the processing script. This leaves statements in To Process status. Starting one automation process before the previous one finishes causes data conflicts and stuck statements.
Resolution: Adjust the script schedule frequency so each run finishes before the next run begins.
Empty statements
In certain versions, ZoneReconcile imports files that contain no transactions but leaves them in processing indefinitely instead of marking them as processed.
Queue stalling
The auto-import queue can stall when it encounters unrecognized records, meaning records that are missing a bank account or a linked file. A stalled queue prevents valid statements from processing.
Resolution: Confirm that the imported statement has corresponding ACTIVE bank account configuration, account, and subsidiary records.
Large statement processing
When a statement contains many transactions, a regression in some versions can cause ZoneReconcile to re-process lines that are already complete. This creates a permanent Currently processing lock.
Resolution: Follow the steps in the Unlock a statement section of this article.
Script failures
- Open the Map/Reduce Script Status page.
- Confirm that the
ZR Process Bank Statement Transaction MRscript has completed. - Check the summarize phase of the script for errors.
Errors after saving a statement
If an error occurs immediately after you save a statement, the statement can lock indefinitely.
- Unlock the statement by following the steps in the Unlock a statement section of this article.
- If the error persists after unlocking, contact support for investigation.
Unlock a statement
Use this procedure to unlock a statement that remains in Currently processing status. By default, only system administrators can unlock statements.
Prerequisites
- Log in with the Administrator role.
- Confirm that at least 1 hour has passed since the statement was submitted.
- Confirm that no instance of the
ZR Process Bank Statement Transaction MRscript is running.
Important: Do not unlock a statement while it is still processing or while the ZR Process Bank Statement Transaction MR script is running. If a user resubmits a statement that is still processing, the system processes the data twice and creates duplicate transactions. For this reason, the unlock feature is restricted to administrators.
💡 Tip: In a busy environment, wait longer than 1 hour before unlocking a statement.
Steps
- Navigate to Transactions > ZoneReconcile > Unlock Statements. The page lists all bank statements in Currently processing status.
- Select the statement to unlock.
- Click Submit. A success message appears when the unlock completes.
- Navigate back to the affected statement. Confirm that the green information message no longer appears and that you can edit the statement.
Provide custom roles access
To grant custom roles access to the unlock feature, see the Roles and Permissions article.