New Feature: Create Transactions Suitelet Subsidiary Restrictions
Previously, the Create Transactions suitelet allowed selection of any Subscriptions, regardless of the user’s subsidiary access. The Create Transactions suitelet now only displays Subscriptions accessible to the user via their NetSuite Role.For backwards compatible behavior where users can view and selectanySubscription, regardless of their Role and Subsidiary access, the Role(s) in use must have the ‘Subsidiary Restriction’ set to ‘All’.For example, a user’s Subsidiary is ‘United States’, and that user is logged in with a Role with the ‘Subsidiary Restriction’ = ‘All’.
In this case, the user will continue to see Subscriptions from all Subsidiaries displayed on the suitelet.
If the Role’s ‘Subsidiary Restriction’ is changed to ‘User Subsidiary’, and the user navigates to the suitelet, they will now only see Subscriptions under the 'United States' subsidiary.
If the Role is changed to ‘Selected’ and ‘United States’ and ‘Canada’ are both selected, the user will then see Subscriptions related to either subsidiary on the suitelet.
The out-of-the-box ‘Zone Advanced Billing Administrator’ role uses the Subsidiary Restriction ‘All’; the ‘Zone Advanced Billing User’ role uses the Subsidiary Restriction 'User Subsidiary’. Thus, any users using the ‘Zone Advanced Billing User’ role will only see Subscriptions with the Subsidiary listed on their User record.This change only impacts which Subscriptions are displayed on the Create Transactions suitelet; no changes have been made to Create Transactions logic when leveraging ZAB Automations.
Enhancement to Revenue Order Processing for Kits
Previously, in niche scenarios involving extremely high data volume scenarios and a high number of Subscription Items utilizing Kits, the Update Revenue Details process encountered native NetSuite Map/Reduce limitations for Time and Script Execution. This enhancement optimizes these processes to eliminate errors preventing the processing of all data.
New ZAB Charge Field
A new field, ‘Transaction Line Unique Key’, has been added to the ZAB Charge record. This field is populated during the Create Transactions process, with additional functionality planned for a future update.
Enhancements to ZAB Revenue Order Processing
Enhancements to the Revenue Order Processing process within Update Revenue Details. This ensures that if a Subscription uses a Revenue Configuration with ‘Inherit from Subscription’ and a child Subscription Item has its Revenue Type removed after a Revenue Order and Revenue Detail are created, the Revenue Order field is nulled on the Subscription Item to prevent unnecessary future processing. No changes were made to existing logic for updating Revenue Details to inactive or pending delete status.
Non-Impacting Error in ZAB Renewals
Resolves a non-impacting error present in script logs when executing ZAB Renewals processes.
Release 2025.09.09.1
Resolve Non-Impacting Managed Display Error
Resolves a non-impacting error present in script logs when leveraging ZAB Managed Display functionality.
Non-Impacting Error in ZAB Minimum Commitments
Resolves a non-impacting error present in script logs when executing the ZAB Minimum Commitment process.
Enhancement to Optimize Revenue Processes
This enhancement optimizes the Update Revenue Details and Update Revenue Arrangements processes in extremely high data volume scenarios. Previously, in niche scenarios, scripts encountered native NetSuite Map/Reduce limitations for Time and Script Execution, resulting in error and preventing the processing of all data. This enhancement optimizes these processes, and if needed, returns a message in the ‘ZAB Revenue Management Plugin’ script logs alerting the user when the threshold is reached and that additional records are pending. This prompts the user to re-run the Update Revenue Arrangements process to successfully update the remaining data.
Display Issue on Approve Subscription Suitelet
Resolves an issue when viewing the ‘Approve Subscriptions’ Suitelet where, in some instances, the search results displayed incorrect amounts. This issue applied to the search results displayed on the suitelet only; this change did not impact any logic in the Approve Subscriptions process.
New ZAB Revenue Transaction Link Field
A new field, ‘Transaction Line Unique Key’, has been added to the ZAB Transaction Link record. This release does not include logic to populate the field; that functionality will be introduced in a future update.
Issue in Create Transactions Subprocessing
Resolves an issue, introduced in 2025.06.19.3, in the Create Transactions process when billing an extremely high volume of Charges and Subprocessing was invoked. In niche scenarios, data was not passed appropriately between Subprocesses, resulting in an error blocking Transaction creation.
Release 2025.06.19.3
Standardizing Data
This new release brings all ZoneBilling customers onto a common version, enhancing speed and quality of support. Plus, it allows Zone support to see basic transaction volumes and feature usage for all ZoneBilling customers. All data is handled in full compliance with applicable privacy regulations.
New 'ZAB Date Billed' Field
A new field, 'ZAB Date Billed’, has been added to the ZAB Charge record for reporting purposes. This represents the date the Charge was billed and the related Transaction generated, which may or may not align to the date on the Transaction.
Release 2025.06.19.2
Non-Impacting Error in ZAB Process UE
Resolves a non-impacting error present in script logs when executing a ZAB Automation.
Issue Using Create Revenue Events Suitelet
Resolves an error, introduced in 2025.04.24.1, occurring when using the ZAB Create Revenue Events Suitelet.
Release 2025.06.19.1
Enhancement to ZAB API to Return Record Links
Enhancement to the ZAB API to allow users to optionally include a parameter to include a link to the record in the response file. To include the link, add the parameter include_links = True to a GET request.
Ability to Lock ZAB Billing Profile Record
A new feature to lock the ZAB Billing Profile record has been introduced to add controls and auditability for administrators. It is recommended that all Billing Profiles be locked once testing phases have concluded, before they are utilized on Subscriptions in Production. Unlocking and editing Billing Profile records once they are actively in use may result in unintended impacts to future Transactions.For System Administrators as well as any users listed as ZAB Administrators on the ZAB Preferences record, a new ‘Lock’ button will appear at the top of the Billing Profile.When pressed, the entire record will be locked so that no edits may be made, including adding, changing, or deleting Billing Profile Combine or Separate Groups.In order to proceed with making changes to the Billing Profile, a user with the appropriate permissions must first ‘Unlock’ on the record and click through a warning pop-up. Any changes to the lock status can be audited via the field called ‘Is Locked’ in the System Notes.
Enhancement to Optimize Contract Pricing
Enhancement to optimize the Execute Rating process specifically in scenarios when a Subscription Item leveraged a Contract Pricing record which included an extremely high number of Contract Pricing Details.
Enhancement to Approve Revenue Orders Suitelet
Resolves an extraneous search executed when loading the Approve Revenue Orders suitelet to improve efficiency. This was non-impacting and therefore removed.
Enhancement to Accommodate NetSuite Change to Script Deployment Audiences
Enhancement to accommodate NetSuite’s update to Script Deployment records, which now separates Audiences by ‘Internal Roles’ and ‘External Roles’. This ensures scripts previously set to ‘All Roles’ continue to function as expected, with no change to existing functionality.
Enhancement to Create Transactions Search
Enhancement to the search used in the Create Transactions process to optimize the retrieval of Charges and their related fields to source data to generate the Transaction. No change to billing logic was made as part of this update.
Enhancement to Charge Consolidation Backup File Functionality
Previously, when leveraging the Charge Consolidation feature, the ‘backup’ file of projected Charges only included Charges in periods in which consolidation occurred. If a particular period did not have any Charges to consolidate, no file was generated. This enhancement will ensure that a Consolidated Charge File is generated in all periods if Charge Consolidation is in use on the corresponding Rate Plan.
Issue Filtering Approve Subscription Suitelet
Resolves an error occurring when leveraging the ‘Approve Subscriptions’ feature and filtering by ‘Subscription’. This ensures that all filters and results are displayed appropriately.
Issue Leveraging Ad Hoc Rate Plan and Charge Schedule with 'Days' Interval
Resolves an issue occurring when leveraging a Subscription Item with an Ad Hoc Rate Plan and a Charge Schedule with a ‘Days’ interval. Previously, Charges were generated with the Charge Period Start and End Dates incorrectly set to the Ad Hoc Data date instead of using the Charge Schedule's settings.
Issue Leveraging Handlebars zab_round Function
Previously, when certain company and user number format preference combinations were used in conjunction with the handlebars zab_round function, the rounded number displayed incorrectly when periods and commas were not evaluated appropriately. This has been resolved so that all number formats are compatible with handlebars rounding functionality.