Skip to main content
📢 Looking to add e-invoicing support for France? We've partnered with Ecosio to extend coverage there. This is an upgrade to your current e-invoicing subscription — contact your Account Manager to get started.

Release 2.17.0

General Information


Version 2.17.0 was released on the 8th of July 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-3186 Option to run PO re-matching for existing incoming transactions

The additional script called ZC Bill To Process PO Re-Matching MR has been added to ZoneCapture. The purpose of this script is to run purchase order matching for incoming (not yet processed) transactions. The use case for which the script has been created is when the PDF invoice is scanned before purchase order is created in NetSuite. If purchase order number is captured from the PDF invoice, but not match as PO did not exist during scanning, then you can use the new script to run re-matching process. The script is not scheduled by default. Please schedule it as per desired frequency if needed.

SC-3412 Auto-matching of items on standalone vendor bills

The new feature has been added to allow automatching of items for standalone vendor bills based on captured article number and description. The default matching algorithm compares captured data with the following fields on the item definition:  

  • vendorcode
  • vendorname
  • itemid
  • displayname

to find a unique exact match.

The logic works for OCR-related vendor bills and e-invoices. The new logic is compatible with autoprocessing.

In case the default logic does not work in your case, you can disable it by checking this box on ZoneCapture Main Configuration:

SC-3840 Transaction Line Default Rules > Add option to select Customer field

ZoneCapture Transaction Line Default Rules screen has been extended with a new field: Customer. In case you use NetSuite feature "Bill Costs to Customers" and you would like to create a rule that depending on the captured description will populate Customer/Job column on the lines, you can now create a rule and populate a value in newly added field.

SC-4001 3-Way Matching: When data is outside of threshold, give an option to retain captured data

Customers using 3-Way matching with thresholds on quantity or rate would like to have an option to decide what logic should be applied in case data is outside of threshold.

Currently in case a difference outside of thresholds is identified, the logic is setting values equal to purchase order data. The new preference has been added to allow to switch this logic and retain captured data while still have it highlighted as outside of thresholds.

Starting from this release if your preference is to retain captured data even if the difference between captured data and purchase order data is outside of threshold, use the following new settings:

The new preference is available on the ZC Main Configuration, ZC Subsidiary Setup, Vendor record and Item record.

The new preference is compatible with autoprocessing.

SC-4015 Split Last Received IBAN and Account No. fields on the vendor record

To further enhance vendor matching algorithm the existing autolearning field Last Received IBAN/ Account No. that was storing last captured bank details of the certain vendor has been split into two separate fields:

  • ZC Last Received IBAN
  • ZC Last Received Bank Account No

Following this change also a vendor matching algorithm has been improved to compare captured IBAN against ZC Last Received IBAN and captured bank account number against ZC Last Received Bank Account No.

SC-4030 Introduce 'ContractDocumentReference' tag for E-Invoices

Outbound E-invoices logic has been extended to support sending of the contract number. The new Transaction Body Field called ZC Contract Number for E-invoices has been included in the bundle. If you want to provide a contract number in outbound e-invoices, show the new field on your invoice form, populate it and send E-invoice. Value provided in this field will be included as 'ContractDocumentReference' in the actual e-invoice.

SC-4060 E-invoicing outbound: Option to source endpoint and Tax ID from custom fields

The new option has been added to support more flexible setup for outbound e-invoices. In case of sending e-invoices from a subsidiary that is using multiple different tax registration numbers, with the new setup you have an option to deviate the tax registration number that should be sent in the particular use case.

The default setup remains without changes, meaning the tax registration number is sourced from ZoneCapture Subsidiary Setup> E-Documents tab > Tax ID field.

If you would like to switch to the logic allowing customized sourcing of tax id, use the new option available on ZoneCapture Subsidiary Setup called Custom endpoint and tax registration number sourcing

There are two options available:

  • Source from default transaction fields
    After selecting this option, the following fields on the transaction record becomes mandatory and will be the source of tax details on every e-invoice in the selected subsidiary. Please note that fields are included in ZoneCapture bundle and they are locked therefore you cannot edit the definition of the fields.
    --> Custom Subsidiary Endpoint ID (custbody_zc_partyendpt_id)
    --> Custom Subsidiary Endpoint Scheme (custbody_zc_partyendpt_scheme)
    --> Custom Subsidiary Tax ID (custbody_zc_tax_id)
    --> Custom Subsidiary Tax Scheme (custbody_zc_tax_scheme)
  • Source from custom transaction fields
    After selecting this option your custom fields will be the source of of tax details on every e-invoice in the selected subsidiary. Choose this option only if you cannot use default fields provided by ZoneCapture. As the next step populate internal IDs of all four required fields highlighted on the print screen. Save your changes and make sure you always populate values for these fields on your transaction records that should be sent as e-invoice.

 

SC-4088 New preference is available on the vendor record: Use items or expenses

The new preference has been added on the vendor record: Use items or expenses. So far it was possible to configure this setting on the Main Configuration level and Subsidiary Configuration level. This option has been extended to provide it also on the vendor level to make the setup more flexible. In case the vendors within the same subsidiary should follow different default logic (some of them using items and some of them using expenses), use the new setting to differentiate the setup.

If the new field is not yet visible on the vendor record, please make the following entity field visible on the custom vendor forms: Default Bill Lines to Items/Expenses (field id = custentity_zc_default_to_item_or_exp).

Set the field value to either Items or Expenses. Leaving the field empty will result in inheriting the default value from the ZC Subsidiary Setup. 

SC-4109 Introduce a field on the vendor bill/credit indicating standalone vs purchase order related bill

The new Transaction Body Field has been included in the bundle called ZC Purchase Order Related Transaction (field is = custbody_zc_po_related_txn) to differentiate if the saved vendor bill is a standalone one or purchase order related. The field can be used further in ZoneApprovals in case you want to configure different approval matrix for PO-related bills vs standalone bills.

SC-4123 Visibility of number of trainings per vendor in OCR model

OCR Station record has been extended with additional information. The end users can now get insights which vendors have been so far trained in the OCR model to improve the recognition results for similar PDF layouts. To verify the list navigate to Setup > ZoneCapture Setup > ZoneCapture OCR Stations. View the Nanonets station and open Custom Settings tab to get the list of vendors with the number of trainings.

SC-4187 Populate rate based on captured unit price on standalone bills with items

For standalone vendor bills with items in case the request is to automatically populate captured unit price in the rate column on the vendor bills lines, a dedicated custom parser mapping needs to be created. With the enhancement coming in this release, after performing the following steps, you can expect a rate to be populated on the vendor bill lines.

Type in the general NetSuite search: Scan & Capture Parser Mapping and open the page.

Click blue button "New" and populate the following details. Save you changes. 

 

Bug Fixes

 

SC-3766 Enable Redwood Experience > Bill to Process page not aligned to NetSuite Center tabs

With Redwood Experience enabled and the split screen on the vendor bills turned on, ZoneCapture toolbar was slightly covering NetSuite menu bar. The UI view has been adjusted to make sure that toolbars are correctly aligned.

SC-3970 Ignore whitespaces during 3 way matching of items

For certain PDF layouts captured article number or item description might have double whitespaces captured causing 3-way matching logic to fail. The algorithm has been adjusted to ignore whitespaces when looking for the item match between captured data and purchase order data.

SC-4017 E-invoicing: adjust parsing of bank details based on bank details scheme

Bank details in received e-invoices have corresponding scheme assigned to it: IBAN or BBAN. The logic of interpreting bank details have been adjusted to differentiate these schemes and use it either as bank account or IBAN for further vendor matching purposes. 

SC-4026 Autoprocessing logic in case the invoice date is not captured

For the use case when OCR tool does not capture an invoice date, NetSuite defaults the transaction date to the current date, therefore autoprocessing of vendor bills was not failing due to missing mandatory information. The logic has been adjusted so that not captured invoice date will cause a failure of autoprocessing. Thanks to that end user can be notified about missing information and correct it manually.

SC-4050 "Edit" button is not disabled when using foreign language

The issue has been identified when using NetSuite in Dutch language and expecting that “Disable Process button when PO is not ready for processing” will show EDIT button instead of PROCESS button in the Incoming queue. As the logic was not working correctly after switching NetSuite language to Dutch, it has been adjusted now to be compatible with any language.

SC-4063 Allow adjusting Memo and PO fields on rejected Bill to Process records

Rejected (inactive) bill to process records were subject to changes only after activating them. The logic has been adjusted so that the end users can edit rejected bill to process records (e.g. populate Memo field or edit purchase order) in case that streamlines their way of working.

SC-4113 Data Recognition Error > "No PO Matched" Status Despite PO Being Linked

Bill to process records in Data Recognition Error status needs to be processed manually by the end user. After manual connection of purchase order(s) to such records the Incoming Transactions was not reflecting the status correctly. The issue has been fixed so that manual changes are reflected correctly in the Incoming queue.

SC-4124 Redwood Experience Enabled > Pagination is not available in the Incoming queue

Incoming transactions to be processed queue did not show pagination option when Redwood Experience was enabled preventing users from switching to another page. The issue has been fixed so that Redwood Experience can be used without affecting Incoming queue.

SC-4154 Uncaught error in console - Vendor bill page stuck loading expense lines

Users experienced an issue with loading vendor bills when opening multiple bill to process records at the same time. The vendor bill form stuck loading on expense lines with the timeout error. The logic of loading vendor bill forms has been enhanced preventing this error from happening.

SC-4160 SuiteTax enabled > Autoprocessing fails for standalone bills with items

The issue has been identified during autoprocessing of standalone bills with items on NetSuite accounts with SuiteTax enabled. In case the item definition has a tax assigned, the autoprocessing was failing with the error that transaction does not balance. The issue has been fixed so that autoprocessing can be executed if all standard criteria are met.

SC-4174 Customer Email Plug-Ins being Deactivated by setup assistant

When ZoneCapture configuration is being created by setup assistant for newly onboarded customers, the conflict has been identified between existing custom email plugins which got deactivated by setup assistant. The issue has been fixed so that the setup assistant does not affect any existing email plugins.

SC-4193 Adjust missing Spanish translations on bill to process record

Bill to Process record was missing Spanish translations. The fix has been applied so that the page is fully translated into Spanish.

SC-4253 Processed transactions not removed from incoming transactions without refresh

ZoneCapture Incoming Transactions list has a logic built-in to automatically refresh the view in order to keep end users with the up to date view. The intermittent issue has been identified that the view was not always refreshed with recently processed transactions. The fix has been applied to make sure that the Incoming queue is being automatically refreshed without any glitches.

Was this article helpful?