NetSuite Release 2016.2

NetSuite Release 2016.2 is soon rolling out.

Here at JCurve we have gone through the pages of notes and found the items that are most likely to affect you as a JCurve customer.



Change to Merging Accounts

Prior to 2016.2, when merging bank or credit card accounts the merge process deleted the transaction history from the Merged From account. You could, however, manually preserve the transaction history in the Merged From account before performing the merge. To preserve the transaction history, you un-reconciled the reconciled transactions in the account register of the Merge From account. After the merge, you re-reconciled the transactions in the account register of the Merge To account. In 2016.2, when you merge bank or credit card accounts the merge process automatically un reconciles the reconciled transactions in the Merge From account. After the merge, you can re reconcile the transactions in the register of the Merge To account.


Quick Close Accounting Period

NetSuite 2016.2 introduces the Quick Close preference. This time-saving preference is useful when you have reopened one or more closed accounting periods to make a change. With Quick Close, NetSuite marks complete all tasks in all reopened accounting periods, eliminating the requirement to close them one-by-one. This is also useful when you prefer a one-click method for closing accounting periods. If your user role is granted both the Set Up Accounting and Period Closing Management permissions and you want to use Quick Close, you must enable the Allow Quick Close of Accounting Periods preference at Setup > Accounting > Accounting Preferences. On the General subtab under the General Ledger section, check the Allow Quick Close of Accounting Periods box and then save. This preference does not appear in user roles that do not have the Period Closing Management permission.


Legal Name in Chart of Accounts

If the Use Legal Name in Account accounting preference is enabled at Setup > Accounting > Accounting Preferences, the new Legal Name field appears on the account record. You can enter up to 400 characters in this field including special characters such as colon (:) and semicolon (;). You can also enter characters such as Éé,Çç, and 2 byte characters such as ######. This field is useful in countries where the legal name of an entity is required by law. The Legal Name field can be added to financial reports where account is an available component. It is also available in advanced searches, SuiteScript, and ODBC. System notes maintains an audit trail specific to the activity on the Legal Name field.


Five Administrative Permissions Separated from Administrator Role

Five permissions that formerly were part of the Administrator role, and were not available to be assigned to users with other roles, are being made available as new permissions as of 2016.2. These new permissions can be assigned to users other than account administrators. With these new permissions, you can limit the number of account administrators while assigning these administrative tasks to other users.

The five newly available Setup permissions are:

  • Enable Features
  • Set Up Company administrative tasks to other users.
  • Set Up Shipping
  • View Billing Information
  • Web Services Log

These new permissions can be found on the role record’s Permissions > Setup tab


New Notifications for Password Expiration and Password Change Important:

This feature is targeted for release in September 2016. As of 2016.2, NetSuite provides advance notice of the date that your NetSuite password will expire, eliminating uncertainty and the problems of having to change your password at an inconvenient time. Now all users, other than Customer Center users, receive a notification that their password is about to expire. The first notice is sent 14 days before the password expiration date. As soon as you update your NetSuite password, the notices stop. If the password has not been changed, the next notice arrives seven days before the password expires. If necessary, an additional notice is sent each day for the three days before the password expires. In addition, all users, other than Customer Center users, now receive a notification email when the password associated with their email address is changed. This notification enables you to be more aware and proactive in cases where there is a fraudulent attempt to change your password.


Change to Adding and Removing Payment Items to and from a Deposit

NetSuite 2016.2 changes the method by which you add all payment items to and remove selected payment items from a deposit. Prior to this release, to add all payment items to a deposit you clicked the Mark All button. To remove the selected payment items from a deposit you clicked the Unmark All button. Now, you check the box beneath the Customize button to add all payment items to a deposit. You clear the box to remove the selected items from a deposit.


Enhanced Reconciliation Detail Report

The Reconciliation Detail Report has been enhanced to permit you to customize the columns that appear in printed format. Removing columns is useful if your page orientation preference displays the report in a crowded format


Spam Protection for Support Case Email Messages

NetSuite 2016.2 introduces a SpamLock preference on support case email addresses. When enabled, messages sent using the support case reply-to email address are accepted only if they are sent from an email address entered for an employee, contact, or company record or on a case profile in NetSuite. Replies sent from an unrecognized source are discarded. The preference is applied to individual cases. Any user who can edit case records can click the Enable Spamlock button on an existing case record to enable this preference. Spamlock is turned off by default.


File Cabinet Folder Renamed

The Attachments to Send folder in the file cabinet has been renamed Attachments Sent. This standard folder is used to store files that are attached to email sent through NetSuite.


Bin Management by Location

In NetSuite 2016.2, you can use the existing Advanced Bin Management feature on a per location basis. Previously, if you used the Advanced Bin / Number Inventory Management feature, bins were enabled for every location. In addition, all locations had to use the associated Advanced Bin Management functionality or no locations could use it. With 2016.2, you can now set warehouse and store locations to use bins to track inventory and choose not to use the Advanced Bin Management functionality at your head office location. To use bins by location, you must have the Advanced Bin / Numbered Inventory Management and Multi-Location Inventory features enabled in your account. When these features are enabled, a Use Bins box appears on location records and a Location field appears on bin records.

Note: The Basic Bin Management feature remains unchanged. It must be enabled or disabled for all locations.


Commit Orders Scheduling

In NetSuite 2016.2, you can now schedule items to be automatically committed to specific orders at a defined interval. The new Commit Order Schedule page enables you to define when an automated commitment task runs and for which orders. Set the recurrence frequency and starting date and time for the tasks and then reference a saved search that defines the orders that should have items committed to them. For example, you create a saved search that defines all sales orders entered for a particular location. Then, you create an order commitment schedule to run one time every two weeks with a specified start date. NetSuite automatically commits items to those orders at the specified two-week interval.

Note: To use the new Commit Orders Scheduling enhancement, the Perform Item Commitment After Transaction Entry preference must be disabled.

You can still commit items manually using the Commit Orders page.


Replenish Location by Transfer Order

In NetSuite 2016.2, you can create transfer orders to distribute inventory across locations and allocate the right quantity for each retail store at the right time. This new capability enables distribution managers to review inventory across multiple locations and create transfer orders from one location to any locations where shortages are found. Previously, using the Replenish Location page was the only way to replenish inventory based on the set reorder point. Now, two pages are available:

  • Replenish Location by Inventory Transfer – Create an inventory transfer based on the set reorder point
  • Replenish Location by Transfer Order – Create a transfer order based on the set reorder point

Note: The Replenish Location page has been renamed Replenish Location by Inventory Transfer.

Merchandise planners can increase efficiency by reviewing current inventory levels at each location, then moving merchandise where you need it most. For example, during peak season for an item, you can transfer inventory out of warehouses and into retail locations to have stock where it is needed. Replenishing a location by transfer order enables you to quickly create a large number of transfer orders to distribute goods out of a source warehouse into multiple stores or warehouses.


Withdraw by Transfer Order

In NetSuite 2016.2, use the new Withdraw by Transfer Order form to withdraw inventory out of one or more locations and transfer it to another location. For example, keeping an item stocked at a retail location has a high holding cost compared to storing the item in a warehouse. At the end of the season to sell swimsuits, a retailer can withdraw swimsuit stock from the retail location to store them in a centralized warehouse, freeing up shelf space for product more appropriate to the season. Your merchandise planners can assess slow moving inventory and use the Transfer Order Withdrawal to optimize inventory distribution over locations. To use a Transfer Order Withdrawal, go to Transactions > Inventory > Withdraw Transfer Order.


Phantom BOM

In NetSuite 2016.2, users can now mark individual sub-assemblies in a BOM (bill of materials) as phantom assemblies. A phantom assembly is typically a non-stocked assembly that conveniently groups together material needed to produce a subassembly. For example, a specific type of wheel used on a mountain bike can be marked as a phantom as part of a build to order specification. The Phantom BOM option enables you to define the item source for the subassembly on a line-by-line basis. This means you can specify the subassembly to be phantom in one BOM but have it as a regular stock item in another. Previously, it was possible to only assign phantom items across all bills of material.


Additionally, when there is a manufacturing change to a component, it must be applied only to the BOM of the phantom item. Changes are automatically re-flowed to all related BOMs, which saves significant time and effort for material or manufacturing engineers. Phantom BOM is available on both assembly and work orders, when the Assembly Items feature is enabled. To mark a sub-assembly as a phantom, check the Mark Sub-Assemblies Phantom box on the record. The Mark Sub-Assemblies Phantom box replaces the existing Build Sub-Assemblies preference.


Transfer Order Enhancements

When using transfer orders with the Multi-Location Inventory feature, you can choose to enable the Use Item Cost as Transfer Cost preference. Now, in NetSuite 2016.2, when this preference is enabled, you can enter partial fulfilments and receipts for transfer orders and track item costs throughout the transfer process. Previously, when the Use Item Cost as Transfer Cost preference was enabled, you were required to enter the same quantity at each step for entering items, fulfilling, and receiving the transfer order. For example, if you entered a transfer order for ten widgets, you could not enter a partial fulfilment against the transfer order for only five widgets or an item receipt for only three widgets. Now, using NetSuite 2016.2, when the Use Item Cost as Transfer Cost preference is enabled, you can enter partial fulfilments and receipts for transfer orders. Costs can be tracked accurately for items when partial quantities are entered because when you receive the transferred items, you are required to match the receipt to the corresponding fulfilments.

For example: The item Deluxe Widget has a cost of $5.

You enter a transfer order for a quantity of 10 widgets. Then, you enter item fulfilments against the transfer order as shown below:

  • Item Fulfilment #1 for five widgets
  • Item Fulfilment #2 for two widgets
  • Item Fulfilment #3 for three widgets

Three individual fulfilments total a quantity of ten widgets fulfilled.

Next, you receive each transfer orders and match it to a fulfilment, as shown below:

  • Item Receipt #1 for five widgets (matches to Item Fulfilment #1)
  • Item Receipt #2 for three widgets (matches to Item Fulfilment #3)

Note: When the Use Item Cost as Transfer Cost preference is enabled at Setup > Accounting Preferences, you are now able to create intercompany transfer orders. For costing calculations, an intercompany transfer order uses the transfer cost instead of the item cost. Previously, you were not able to create intercompany transfer orders when the preference was enabled.


Matrix Items Name Template

In NetSuite 2016.2, you can now manage the naming convention for newly created matrix items. Specify the order in which matrix options appear in the item name field and apply custom separators and free text for exact formatting and specific encoding requirements. This can be done when creating new items using the Matrix Item Assistant (Step 3 — Choose Property Combinations) in the new Matrix Item Name Template field. By enabling users to define their own naming convention, NetSuite promotes more universal conformity across systems and easier mapping conditions when importing items from legacy systems.


Redesigned Reminders Portlet

For 2016.2, the Reminders portlet includes the following enhancements:

  • Headline Reminders
  • Highlighting of Reminders

Headline Reminders:

The Reminders portlet has been redesigned to include headline reminders. Headline reminders are displayed in the upper part of the portlet.

Headline reminders use a larger font for number values and a more prominent layout. To turn a reminder into a headline reminder, drag it to the upper part of the portlet. You can also turn a reminder into a headline reminder by editing it or using the portlet’s Set Up dialog box.

Highlighting of Reminders:

You can apply highlighting rules to any of your reminders. Each highlighting rule adds a colour indicator to the reminder whenever the specified threshold is reached.


Applying Item Custom Fields to Individual Items

As of 2016.2, you can specify that item custom fields be applied to individual items. The Applies To subtab on the Custom Item Field configuration page has new fields to support this feature.

The Select Individual Items box at the top of the right column controls the availability of the other fields on the subtab. If the Select Individual Items box is checked, the fields in the left column are unavailable, and the fields in the right column are available. If the Select Individual Items box is not checked, the fields in the left column are available, and the fields in the right column are unavailable.

Check the Select Individual Items box to specify where this custom item field is used. Then, in the Items list, press and hold the Ctrl key and click the items where this custom field is available.

An Include Child Items box has been added to the Applies To subtab of the Custom Item Field and of the Transaction Item Option configuration pages. When you are editing a parent record, you can check the Include Child Items box to apply these settings to this parent item and to all of its child items. The settings also apply to any child items added at a later date.

Note: If a field is used and then removed from an item, the value is still available on the record where it was used.


Show Hierarchy Option Added to Custom Fields

A new Show Hierarchy box is now available on the Display subtab of custom field pages in the following cases:

  • The custom field is of type list/record or multi-select.
  • The selection in the List/Record dropdown list is hierarchical, for example, a subsidiary, class, department, location, or hierarchical custom record.

To specify that the record hierarchy be shown in the field’s values, check the Show Hierarchy box, which is the default. To show the field name without the hierarchy, clear the Show Hierarchy box. For existing fields, the Show Hierarchy box is checked only for fields that already show the hierarchy.

When the hierarchy is shown, dropdown lists and multi-select fields show the record hierarchy.

In the case of accounts, when the Use Account Numbers preference is enabled, custom account fields now display account numbers together with account names.

The Show Hierarchy setting is also applied to field values shown in search results.


CSV Import Supported for Credit Card Transactions

As of 2016.2, you can import credit card charge and credit card refund transaction data into NetSuite from CSV files. Before you can import credit card transactions, you must add a credit card account. After the credit card account has been created, you can import credit card transaction data. In the Import Assistant, set the Import Type to Transactions and the Record Type to Credit Card Charge or Credit Card Refund.


CSV Import Supported for Inventory Adjustments

As of 2016.2, you can import inventory adjustment data from CSV files. Before you can import inventory adjustments, you must enable the Inventory feature.


New Character Encodings Supported in CSV Files

New encodings are now supported for CSV file data imported to NetSuite. The following options have been added to the Character Encoding dropdown list on the Scan & Upload CSV File page of the Import Assistant:

  • Chinese Simplified (GBK)
  • Traditional Chinese (Big5)
  • Korean (ISO-2022-KR)
  • Korean (EUC-KR)


End of Support for Internet Explorer 10

As of 2016.2, NetSuite no longer supports the Internet Explorer 10 browser. As of January 12, 2016, Microsoft stopped providing security updates and technical support for Internet Explorer 10 on Windows 7 and Windows 8.1. If you are using Internet Explorer 10, NetSuite strongly recommends that you upgrade to Internet Explorer 11 or switch to another supported browser. As of 2016.2, NetSuite no longer tests or addresses any issues related to Internet Explorer 10.

Note: This end of support for Internet Explorer 10 does not apply to web stores.


End of Support for Safari 6

As of 2016.2, NetSuite does not support the use of Safari 6. Any issues related to the use of Safari 6 are no longer addressed. If you are using Safari 6, NetSuite strongly recommends that you upgrade to a newer version of the Safari browser or switch to another supported browser.


End of Support for Google Chrome on Windows Vista and Mac OS X Versions 10.6, 10.7, and 10.8

As of April 2016, Google ended support for the Google Chrome browser on the following operating systems: • Windows Vista • Mac OS X Snow Leopard (v10.6), OS X Lion (v10.7), and OS X Mountain Lion (v10.8) As of April 2016, Google stopped providing security updates and technical support for Google Chrome on these operating systems. If you use Google Chrome on one of these platforms, NetSuite strongly recommends that you switch to another supported browser or upgrade your operating system. As of 2016.2, NetSuite no longer tests or addresses any issues related to Google Chrome running on these operating systems. Please note that Google Chrome continues to be supported on newer versions of Windows and Mac OS, including Windows 7, Windows 8, Windows 10, and OS X versions 10.9 and newer.


Electronic Payments Enhancements

Enhancements to the Electronic Payments SuiteApp will include the following:

Instant Bank File Creation:

 A new process will be introduced to generate payment files using existing bill or customer payment transactions. Unlike the current process where outstanding transactions are loaded for selection on the payment file generation page, the new process will use predefined saved searches for payment transactions. The use of saved searches will enable you to set the criteria that will filter payment transactions to be included in payment file generation. The preselected transactions from the saved search will be ready for processing as soon as they are loaded. Payment files will be generated from existing payment transactions that have been tagged through the new For Electronic Payment box. This box will be automatically checked on transactions for entities with any of the following preferences enabled in their record:


  • EFT Bill Payment – for vendors and partners
  • Direct Debit – for customers


Continuous File Creation:

You will have the ability to create payment files regardless of transactions with errors that are detected during processing. The list of failed transactions will be displayed on the Payment File Administration record. You will have the option to remove them from the record and process them in another payment batch.

Did this help? If not, try contacting us Submit a request