Skip to main content
🤖 ZoneReconcile customers: your first AI agents are here. See your cash position before it changes, model what's coming, and see what already happened — free for ZoneReconcile customers.
Join us October 15 for a live walkthrough and demo. Register for the Webinar.

How to Verify a ZoneReconcile Update and Choose the Right Update Window

Audience: External | ZoneReconcile Admins

 

Use this checklist to confirm a ZoneReconcile update installed correctly, resolve common post-update errors, and choose the safest time to update. Following it protects your bank reconciliation processes from disruption.

Post-update checklist

After a ZoneReconcile update, complete the following checks:

  • Verify data preservation: Check that record data is preserved and that scripts function as expected.
  • Monitor progress: Refresh the Installed Bundles page to track installation progress. A green checkmark appears under the Status column when the update is complete.
  • Validate end-to-end flows: Run regression tests in a Sandbox account for key use cases, such as importing bank statements and processing transactions.
  • Review the release notes: Read the ZoneReconcile Release Notes for new features, bug fixes, and any required actions.

Known symptoms after updates

The following issues can appear after an update:

  • Search column errors: The update can trigger SSS_INVALID_SRCH_COL errors when it introduces or changes internal IDs (for example, custrecordzab_c_system_batch_id) that existing scripts or saved searches reference.
  • Script failures: Client scripts (for example, customscript_ff_sc_sl_srchres_data_list) can fail to install.

Resolve a script installation failure

  1. Delete the specific script deployment manually in the target account.
  2. Retry the upgrade.

When to request an update versus wait

Request an update when

  • You completed testing in a Sandbox account and confirmed there are no issues.
  • Zone & Co released a hotfix for a critical issue that blocks your business processes (for example, bank reconciliation stops).
  • You are outside of critical financial periods.

Important: Avoid updating close to month-end.

Postpone an update when

  • Month-end close is approaching: Avoid updates during or immediately before month-end to prevent disruptions.
  • Known issues remain unresolved: If high-priority issues are open, wait until Zone & Co confirms a fix and you test it in Sandbox.
  • Your environment is processing a high volume of transactions: Pause the update or schedule it for a safe test window, such as a weekend. This prevents "straddling states," where transactions are caught mid-process.

💡 Tip: Always test an update in a Sandbox account before you request it for your Production account.

Related articles

Related to

Was this article helpful?