Version 5.29.1 has been released on 29th of October 2026 and contains AU bank feed enhancements and ZoneReconcile bug fixes. Below you can find more information related to these. We will update your Production account automatically and the Sandbox account can be updated from your (the customer's) end at any given time.
Enhancements
BR-4042 & BR-3977 | Basiq Bank Feed: Automated Refresh, Rolling Lookback, and Resilient Sync
Reliability, failure recovery, and synchronization logic have been significantly improved for bank connections powered by Basiq.
Automated refresh verification: The sync process now directly triggers a connection refresh and verifies that all transaction retrieval steps complete successfully before fetching transaction data, rather than relying solely on cached data.
Retry and failure alerts: If an upstream bank or job step returns a temporary failure, the sync automatically retries with backoff. If a connection experiences repeated failures over a 24-hour period, an alert is raised to improve issue visibility.
Rolling lookback window: Each scheduled run now evaluates a configurable rolling lookback window (defaulting to 7 days), ensuring transactions delayed by bank outages, weekends, or bank holidays are automatically captured as soon as connectivity resumes.
Transaction deduplication: Transactions are deduplicated against existing bank statements using their unique Basiq transaction ID, preventing duplicate lines when delayed or backfilled transactions are imported across consecutive syncs.
Timezone-aware scheduling: Sync schedules now observe the configured IANA timezone of the financial institution (e.g., handling daylight saving transitions automatically).
Bug Fixes
BR-2148 | Run Match: Invalid Record Type Error Resolved for Accounts Without Electronic Payments
Bank statement matching now completes smoothly in environments where NetSuite's native Electronic Payments bundle is not installed.
Previously, triggering Run Match in accounts where Use other matching types was disabled could fail with an unexpected error (
The record type [CUSTOMRECORD_2663_FILE_ADMIN] is Invalid) if parameter-based matching of closed transactions was enabled.The matching logic has been corrected so it no longer attempts to query nonexistent EFT batch records when Electronic Payments is not in use.
BR-2166 | Matching Performance: Saved Search for Closed Transactions by Amount Restricted to Enabled Rules
An unnecessary background query executed during statement import and matching runs has been resolved.
Previously, the saved search used for matching closed transactions by amount was triggered whenever parameter-based matching was active, even when matching by amount was turned off.
The condition has been updated so this saved search executes only when amount-based matching of closed transactions is explicitly enabled, reducing processing overhead and loading times.
BR-2729 | Auto Import: Unrecognized Bank Statements to Process Excluded from the Queue
Automated bank statement generation now bypasses unassigned files to keep processing queues clear.
When automated integrations deliver files that are not linked to any bank account or configuration, the resulting Bank Statements to Process (BSTP) records previously occupied slots in the automated processing queue. In high-volume setups, this could delay legitimate bank statements from being generated.
The query for
ZR Auto Import Bank Statements MRnow explicitly excludes unrecognized records (where both Bank Account and File are unassigned), ensuring valid bank statements process without delay.
BR-3986 | Statement Processing: Resolved Concurrency Collision and Indefinite Locking During EFT Batch Processing
Bank statements processing EFT batches can now leverage multiple processors without concurrency conflicts.
Previously, when
ZR Process Bank Statement Transaction MRran with multiple processors, a conflict between statement header status updates and concurrent line saves could trigger an unexpected error. Affected transaction lines failed to mark their processing checkboxes, leaving the bank statement locked indefinitely and lines omitted from subsequent EFT processing scripts.Execution handling has been updated to prevent redundant statement rewrites during Map/Reduce runs and to commit line-level processing flags before setting the header lock, ensuring EFT lines process reliably under high concurrency.
BR-4079 | Instant Upload: Resolved External Module Loading Error
Users can now perform Instant Uploads without encountering missing module errors.
Previously, certain sandbox environments failed during Instant Upload with a
MODULE_DOES_NOT_EXIST: .../moment.jserror due to an incomplete external dependency reference.External library loading paths have been updated to ensure Instant Upload works consistently across both standard NetSuite and Zone Control Center (ZCC) interfaces.