ZoneLiquidity enables finance teams to generate AI-powered forecasts of future bank balances, giving proactive visibility into expected cash positions beyond what historical reconciliation alone provides.
Note: Clicking on the images within this guide will enlarge them for better viewing.
Overview
ZoneLiquidity sits within ZoneReconcile and is accessed via the ZoneLiquidity menu in NetSuite. Before generating a forecast, an admin user must complete a one-time configuration through the ZoneLiquidity Setup assistant. Once setup is complete, forecasts are created from the Forecasting section using the New Forecast button.
In the current version, ZoneLiquidity supports bank balance forecasting only.
Important: Custom transaction types are not supported in this version of ZoneLiquidity. Only the standard transaction types listed in the New Forecast Setup wizard are available for selection.
Prerequisites
Your organisation must have an active ZoneReconcile license with Treasury enabled.
ZoneLiquidity must be installed and deployed to your NetSuite account.
At least 1 subsidiary with associated bank accounts must be configured in NetSuite.
Historical transaction data must exist in the system for the subsidiaries and bank accounts you intend to forecast. The system looks back 365 days from the forecast creation date to train the AI model. For best results, aim for at least 6–12 months of reasonably complete transaction (payments) history before running a forecast.
Setup permissions
To complete the Treasury Setup assistant, a user must be logged in to NetSuite with one of the following roles:
The Administrator role in NetSuite, or
The custom role ZoneReconcile - Treasury Intelligence Role which has the minimum permissions required to execute the Forecast action.
Important: Without Administrator or ZoneReconcile - Treasury Intelligence Role, users will not be able to complete the Treasury Setup assistant. Contact your NetSuite Administrator to request the required permissions before proceeding.
Step 1: Open Treasury Setup
Navigate to Setup > ZoneLiquidity > ZoneLiquidity Setup to access the setup assistant. Complete the setup assistant before attempting to create a forecast.
This opens the New Forecast Setup wizard, which guides you through 5 configuration steps.
Step 2: Run the Setup Wizard
Step 2a: API Secret
The first step of the wizard configures the secure connection to the ZoneLiquidity backend. This is a one-time administrative setup — once an API Secret is saved, all subsequent forecast definitions reuse it automatically.
If an API Secret is already configured, the wizard displays a success state showing the stored Secret ID. No further action is required unless credentials need to be rotated. If no API Secret exists, enter the API credentials provided by your ZoneReconcile administrator and save the secret.
Step 2b: General preferences
General preferences define the basic scope of the forecast.
| Field | Description |
|---|---|
| Forecast Horizon | Select the forecast period length: 30, 60, or 90 days. Longer horizons provide a broader view but may be less precise. Align the horizon with your organisation's reporting cadence. |
Important: Custom forecast naming is not yet available. Forecasts are currently identified by their internal system ID. To distinguish between forecasts, note the creation date and configuration details in the ZR Forecast Definition record.
Select subsidiaries
Select 1 or more subsidiaries from the Subsidiary pick-list. The system does not currently support a Select All option, so select each subsidiary individually.
Tip: For cleaner forecast results, start with a single subsidiary. Combining multiple subsidiaries is supported, but all cash forecast amounts will be consolidated into the headquarter subsidiary's currency.
Select bank accounts
Once a subsidiary is selected, the Bank and Credit card Accounts pick-list automatically filters to show only accounts associated with the chosen subsidiary. Select 1 or more bank and credit card accounts to include in the forecast.
You do not need to include every bank (or credit card) account in a subsidiary. If a particular account has very low transaction volume and you do not wish to forecast it, leave it unselected. Exclude test or legacy accounts where possible to avoid noise in the forecast results.
Set the forecast period
Select a pre-defined period (such as Q3 2026) from the Forecast Period pick-list, or enter a custom end date manually. The forecast period determines the date range over which the system will project bank balances.
Select transaction types
Select the transaction types to include in the forecast.
The following transaction types are supported:
- Vendor bills
- Vendor credits
- Expense reports
- Customer invoices
- Credit memos
- Bill payments
- Customer payments
- Cash sales
- Customer deposit
- Customer refund
- Checks
Important: Only the transaction types listed above are supported in this version. Please note the following limitations: custom transactions are not supported, payments posted to the Undeposited GL account will not be considered, and transactions with a 'Pending Approval' status are excluded.
Step 2c: Configure destination rules
Destination rules define financial thresholds that are overlaid on the forecast chart to help users interpret results in the context of their cash management objectives.
| Rule | Description |
|---|---|
| Liquidity floor | The minimum bank balance the organisation must maintain. Use this to represent a legal minimum balance requirement or to account for known recurring expenses such as payroll or rent that the account must always be able to cover. |
| Cash milestone target | The target cash balance the organisation aims to reach by the end of the forecast period. This functions as a KPI or OKR benchmark within the forecast chart. |
Important: Destination rule amounts are always displayed in the headquarter subsidiary's currency. To verify which currency applies, navigate to Setup > Company > Subsidiaries and check the Currency field for the relevant subsidiary.
Step 2d: Review and execute
The Review and Execute screen displays a summary of all selections made in the previous steps. Review the configuration, then click Save and Execute to initiate the forecast.
At this stage, the system performs 2 actions simultaneously:
Creates a ZR Forecast Definition custom record to log the forecast configuration and track execution status.
Sends the selected transactions from the past 365 days to Zone's AI model via the ZR Treasury Transaction Sync MR script.
Important: The historical look-back period is fixed at 365 days and cannot be changed. The AI model uses this payment transaction history to generate the forecast.
Step 3: Monitor execution and confirm completion
After clicking Save and Execute, the system begins processing. Execution time varies depending on the number of transactions being sent. You do not need to remain on the page while the system processes.
When execution is complete, you will receive a NetSuite notification confirming that the forecast is ready.
You can also confirm completion by checking the ZR Forecast Definition record directly:
Type ZR Forecast Definition in the global search.
Locate the most recent record. Confirm the Status field reads Completed.
Note the Sync Count field, which shows the number of transactions sent to the AI model
Please note, the ZR Forecast Definition record is only accessible through the Administrator role .
Tip: To speed up the forecast submission times, you can use more processors on the ZR Treasury Transaction Sync MR script. Simply alter the deployment and increase the number of processors under Concurrency limit. Please contact and consult with your Administrator before executing this action.
Tip: The ZR Forecast Definition record also displays a full snapshot of the forecast configuration, including the subsidiary, bank accounts, forecast date range, and transaction types submitted. Use this record for troubleshooting if the forecast does not produce expected results.
Validating forecast results
Once the forecast status is Completed, validate the output before sharing it with your finance team. Navigate to Setup > ZoneLiquidity > Forecasting and check the following:
Inflows and outflows patterns look reasonable for the selected subsidiary and period.
The Liquidity Floor and Cash Milestone Target reference lines appear on the forecast chart as intended.
Troubleshooting
If forecast results look incorrect or unexpected, check the following:
Source criteria and bank account mapping — confirm the correct transaction types and bank accounts are selected and that no relevant cash activity is excluded (for this purpose, reach the ZR Forecast Definition record).
Historical data — check whether transaction history is complete for the look-back period. Missing or misclassified transactions will affect the AI model's output (for this purpose, reach the Transactions sublist of the Forecast itself).
Navigate to Setup > ZoneLiquidity > Forecasting to view your results. See the related articles below for guidance on interpreting the Liquidity page, the Cash Forecast chart, Working Capital Insights, and Scenario Planning Agent.