General Information
Version 2.16.0 was released on the 29th of April and contains major enhancements and several bug fixes. Below you can find more information related to the changes introduced in the new version. We will update your live account automatically and the sandbox account can be updated from the customer's end at any given time.
Enhancements
SC-3873 Enhanced vendor matching using bank account number
Vendor matching logic has been enhanced to provide more accurate identification based on captured supplier bank account details.
In addition to existing IBAN-based matching, the captured Bank Account Number is now also compared against the following fields in the vendor’s Primary Bank Details:
- custrecord_2663_entity_acct_no
- custrecord_2663_entity_bban
With this enhancement, the vendor matching algorithm now fully leverages all available captured bank details—IBAN and/or Bank Account Number—to improve matching accuracy and reduce manual corrections.
SC-3906 3-Way Matching Enhancement – Option for Header-Level Matching based on total amount
ZoneCapture now offers an additional option to perform 3-way matching based on header-level totals, in addition to the standard line-level matching.
When header-level matching is enabled, then captured total amount from the invoice is compared against the purchase order's total billable amount (including tax):
- If the totals match, all PO lines will be marked as billed,
- If the totals do not match, none of the PO lines will be marked as billed.
Important: This feature requires configuration. By default, 3-way matching continues to operate on line-level data. To activate header-level matching, a new preference must be enabled in the setup.
This setup is particularly recommended in scenarios where the invoice lines from the vendor do not match the structure of the PO lines in NetSuite. For example, if the vendor provides a single summary line on the invoice, but your PO is broken down into multiple detailed lines, header-level matching allows you to validate the invoice based on the total amount rather than individual line comparisons.
The preference has been introduced on
- ZoneCapture Main Configuration (in case the same logic is expected for all vendors and all subsidiaries),
- ZoneCapture Subsidiary Setup (in case the same logic is expected for all vendors for the selected subsidiary only),
- Vendor record (in case different logic is expected for selected vendors).
Select "Total Header Matching" to apply newly introduced logic.
The feature is compatible with autoprocessing of PO-related vendor bills.
SC-3940 Respect closed/locked posting periods during autoprocessing of vendor bills/credits
ZoneCapture’s handling of vendor bills and credits during autoprocessing has been updated to better align with standard accounting controls. Previously, when the captured transaction date fell within a locked or closed accounting period, ZoneCapture would set the posting period as if the transaction were processed by an Administrator— who has rights to book transaction in locked periods.
With this update, posting periods are now determined as if the transaction were created by an AP Clerk, adhering to your NetSuite Accounting Preference:
“Default Posting Period When Transaction Date in Closed Period.”
Additionally, if your Accounting Preference “Allow Transaction Date Outside of Posting Period” is set to Disallow, ZoneCapture will honor this setting. In such cases, if the captured transaction date falls outside the allowed posting period, autoprocessing will fail, and manual intervention of the end user will be required in this particular use case.
SC-3957 3-Way Matching: Improved Handling of Bill Lines Without Quantity and Rate
Enhancements have been made to better support vendor bill lines that include only a description and amount, without specified quantity or rate. Previously, such cases required manual intervention during 3-Way Matching in ZoneCapture.
With this update, ZoneCapture will now automatically default missing values when they are not present on the PDF invoice:
- Quantity will default to 1
- Rate will default to the captured amount
This logic ensures that 3-Way Matching can proceed seamlessly, even when the invoice lacks full line-level detail.
SC-3983 Improvements on the backend logic responsible for data visible in the Incoming queue
The backend logic responsible for displaying data in the Incoming Transactions to be Processed queue has been rebuilt to optimize the scripts running in the background and to limit any unnecessary execution of the scripts.
SC-3992 Clickable PDF Now Supported on Line-Level Fields
The ZoneCapture split-screen view now supports clickable PDF functionality on line-level fields, enabling users to extract data directly from the PDF into line items. This enhancement applies to both expense and item lines, across purchase order-related bills and standalone bills.
The interaction remains consistent with the existing experience for header-level fields:
- Click on the desired line field.
- Click on the blue rectangle overlay on the PDF (or manually draw a rectangle if needed).
- Selected data will be copied into the corresponding field.
Note: This functionality does not support autolearning. Any manually drawn or selected rectangles are not retained for future bills.
SC-4094 Decrease the minimum of characters required to correctly parse captured document number
The minimum number of characters required to correctly populate the Document Number field on vendor bills has been reduced from 3 to 2. This change addresses scenarios where a valid captured document number contains only two characters, which previously resulted in the field not being populated—even when the number was accurately captured.
SC-4127 Enhanced subsidiary matching using legal name
Subsidiary matching logic has been enhanced to improve accuracy. In addition to comparing the captured subsidiary name against the "Name" field in NetSuite, the system now also checks the "Legal Name" field as a secondary matching layer. This complements the existing AI-based and tax registration number matching, providing a more robust and reliable subsidiary identification process.
Bug Fixes
SC-3924 Bill to process connected to rejected POs has Process button active in the Incoming queue
When the user preference is to disable the Process button when the Purchase Order is not ready for processing, POs in the status Rejected should follow this logic. In version 2.15.0 the Process button was available in this use case, what was incorrect. The issue has been fixed and Rejected POs do have Process button disabled.
SC-3990 Outbound E-invoices: item rate calculation when rate is empty on the invoice line
An issue has been resolved in the outbound e-invoicing process where the item rate was not correctly calculated when:
- The rate is missing on the invoice line, and
- The quantity is less than 1 (e.g., 0.25).
Since a rate is a mandatory field in the e-invoicing network, ZoneCapture calculates it based on the amount and quantity values from NetSuite when the rate is not explicitly provided. The previous logic failed to calculate the rate correctly for quantities less than 1, leading to e-invoice delivery failures.
This logic has now been fixed to accurately handle such cases, ensuring successful e-invoice generation and delivery.
SC-4000 Fix for TypeError: Cannot read property 'headerValues' of null in the script S&C FF Bill To Process UE
In certain scenarios the script S&C FF Bill To Process UE was logging error message Cannot read property 'headerValues' of null. The issue has been fixed so that the following error is handled correctly in the script, not causing error log anymore.
SC-4024 Incorrect Vendor Matching Reason = "Not Matched" when vendor is selected manually
The field Vendor Matching Reason introduced on the Bill to Process record in 2.15.0 was not reflecting correct information in the use case when PDF has been loaded manually via Instant Upload screen and the vendor has been selected manually by the end user. In this case the logic has been changed to set the field as "Selected Manually", what is more informative for users.
SC-4059 Incorrect PO status shown in the Incoming queue for POs with expense lines
In the scenario when purchase order with expense lines has been connected to Bill to Process record, ZoneCapture Incoming queue (column Purchase Order status) was incorrectly showing it as Fully Billed, despite PO not being billed yet. The issue has been fixed to reflect the correct status in the Incoming queue.
SC-4071 Adding standalone lines via 3-way matching pop up does not work
In version 2.15.0 adding standalone expense or item lines via 3-Way Matching pop up did not work. When the user was opening the 3-Way Matching pop up and clicking green plus icon to add either standalone expense or item line, after clicking Submit, lines were not added to the vendor bill. The issue has been fixed and submitted lines are now correctly reflected on the vendor bill.
SC-4085 Autoprocessing with 3-way matching enabled is failing in certain scenario
In certain scenario the autoprocessing of Purchase Order related vendor bills was failing. The following error message was visible in the logs: TypeError: Cannot read property 'dataAdjustmentSettings' of null. The issue has been related to applying 3-way matching thresholds in case there was no match between PO line and captured line. The rootcause of the issue has been fixed so that the autoprocessing can be executed correctly
SC-4130 Static subsidiary matching is not working for certain scenario
An issue was identified in the subsidiary matching process when using a single email plugin and working with multi-subsidiary vendors. In this scenario, the expected matching logic should first attempt to match the captured subsidiary name against NetSuite subsidiary master data. If no match is found, the system should then proceed to AI-based matching.
The issue was that the initial matching step against the master data was skipped, causing the process to rely solely on AI matching.
This has now been corrected. The subsidiary matching logic will properly evaluate NetSuite master data first before applying AI matching, ensuring more accurate and reliable results.