The JCurve ERP edition of NetSuite is an exclusive small business edition available to JCurve Solutions customers. As such, not all NetSuite enhancements and features will be released to the JCurve ERP edition.
We’ve made it easy for our customers to see the applicable features and enhancements in the following 2018.2 release summary.
Important: Changes To How Users Access Release Preview
As of 2018.1, the URL for access to Release Preview has changed for customers in North American (NA) data centers. Previously, users logged in to https://system.beta.netsuite.com to access a Release Preview account.
With 2018.1, users log in to Release Preview via their production account on the NetSuite domain at https://system.netsuite.com and choose their Release Preview role from the Choose Role page or Change Roles list. For more information, see the following articles:
Note: We suggest you change the colour theme of your Release Preview account. This will make it easy to tell when you are logged into your release preview account.
1) Two-Factor Authentication (2FA) Required for Administrator Role
NetSuite 2018.1 requires two-factor authentication (2FA) for the initial login of all Administrator and Full Access roles in newly provisioned accounts. This requirement enhances security for these accounts. Newly provisioned account types can include production, sandbox, development, Release Preview, test drive, demo, and student accounts.
Important: The 2FA required feature applies only to newly provisioned accounts in 2018.1. The 2FA required for the Administrator and Full Access roles feature will be enforced for all existing accounts in 2018.2.
The free 2FA solution available in NetSuite offers both online and offline methods for receiving verification codes. See the help topic 2FA by Phone or Authenticator App for more information. A link to a video, 2FA Your Way for Administrators, is also available in that topic. With this 2FA solution, the Administrator and Full Access roles are designated as 2FA authentication required by default. The requirement that designates 2FA for these roles cannot be removed. The first verification code is sent by email. The first time they log in, users with Administrator and Full Access roles are prompted to set up their preferred and backup methods for receiving verification codes. For more information, see the help topic Logging in with 2FA by Phone or Authenticator App. A link to a video, 2FA Your Way for Users, is also available in that topic.
Certain administrator permissions mandate that a role be 2FA required by default. Any standard or customized roles that include these permissions are indicated in the new Mandatory 2FA column on the Two-Factor Authentication Roles page. For more information, see the following topics:
- Permissions Requiring Two-Factor Authentication (2FA)
- Designating Two-Factor Authentication Roles
Users can choose to have their login device trusted by NetSuite for the length of time specified by an administrator in the Duration of Trusted Device column for a role. Per session is the default setting for trusted devices. Administrators can change the trusted device setting to a longer duration. For more information, see the help topic Designating Two-Factor Authentication Roles. For general information for Administrators about 2FA in NetSuite, see the help topic 2FA by Phone or Authenticator App. For general information for all users, see the help topic Using 2FA by Phone or Authenticator App.
Important: In your integrations, you might need to use certain functions that require an Administrator role. As previously mentioned, the feature requiring 2FA for Administrator and Full Access roles will be enforced for all existing accounts in 2018.2. In past releases, you could not use Token-based Authentication (TBA) tokens for integrations that required an Administrator role. This release introduces support for TBA for Administrators. Using an Administrator role with a TBA token ensures your integrations will continue to work after the upgrade to 2018.2. We recommend you begin now to transition integrations that require an Administrator role to use TBA rather than user credentials. For more information, see the help topic Token-based Authentication. See also Integration Management
2) Changes to Email Preferences Domain Keys Subtab
Note: For assistance with setting up DKIM on your account please speak with your IT contact or domain provider. They will be able to provide you with the necessary details to complete the DKIM setup within NetSuite.
Two fields related to DMARC compliance have been removed from the Domain Keys subtab of the Email Preferences page. The two fields are Compose DMARC-compliant Email Messages Using SPF and Forward Email Replies in DMARC-compliant Format.
These fields are no longer necessary due to the capability, introduced in 2017.2, to configure multiple DKIM (DomainKeys Identified Mail) keys with different domain selectors. The configuration of multiple DKIM keys ensures that the proper domain keys are signed on all email sent from NetSuite. The signing of proper domain keys to each email message ensures compliance with DMARC in relaxed alignment mode, and maintains full email bounce processing.
Before your account is upgraded to 2018.1, ensure that you have multiple domain keys with different domain selectors configured in NetSuite. Set up a DKIM key for each domain you control from which you send email. For more information, see the help topic DomainKeys Identified Mail (DKIM).
Also, verify you are following the Five Golden Rules for Outbound Email as outlined in Email Best Practices.
Important: If you do not set up domain keys in NetSuite, or if you are using a free email domain on email sent from NetSuite, the email’s From header is rewritten. The original email address is moved to the display string. The SMTP-related email address in the From header refers to netsuite.com. For example, if domain keys have not been set up in NetSuite, the email’s FROM header would be firstname.lastname@example.org <email@example.com>.
Changes to Bank Statement Imports
Note: For customers who are using the Fast Four bank reconciliation add-on, these changes will not impact your current bank processes. The changes mentioned below relate to the standard NetSuite banking functionality.
In NetSuite 2018.1, the following enhancements have been made to bank statement imports:
- You can now import a bank or credit card statement file in CSV format with UTF-8 encoding. This CSV file must adhere to the provided CSV template and constraints. Download the CSV template from Transactions > Bank > Import Online Banking Data. For details, see the help topic Preparing CSV Files for Import.
- In the Account list on the Account Statement Reconciliation page, there are now visual indicators to show which accounts require reconciliation. The indicators only appear immediately after import.
Delete Reconciled Statements
In NetSuite 2018.1, you can now delete reconciled statements. You may want to delete a reconciled statement and start over if you receive more transactions that you must include for a closed statement period. When you delete a statement, the transactions become unreconciled but remain matched. You also can no longer generate the associated reconciliation reports for the deleted statement.
You can delete only the last statement.
To delete the last reconciled statement, go to Transactions > Bank > Reconcile Account Statement > List and then click Delete.
For details, see the help topic Deleting Reconciled Statements.
Change to Account Reconciliation Fields and Buttons
In NetSuite 2018.1, the Statement End Date and Ending Statement Balance fields are now automatically populated with data from the imported statement, if available.
The memos that appear in the GL Transactions list are the Memo field values from the Journal Entry or Check headers, not the transaction line-level memos.
Go to Transactions > Bank > Reconcile Account Statement. For details, see the help topic Matching Transactions.
Also, in the Reconciled Statements page, Make Changes is now Edit. You can also click Delete next to the last reconciled statement.
To edit or delete a reconciled statement, go to Transactions > Bank > Reconcile Account Statement > List.
For details, see the help topics Reopening Reconciled Statements and Deleting Reconciled Statements.
To view and select accounts on the Reconcile Account Statement page, your user role must have the Accounts permission with an access level of View. For details, see the help topic Setting Reconciliation Permissions
New Account Reconciliation Portlet
In NetSuite 2018.1, an Account Reconciliation Summary portlet is now available on your dashboard. This portlet lists your bank and credit card accounts and displays key data for matching and reconciliation activities. The columns in the portlet include:
- Account Name
- GL Account Balance
- Last Reconciled Balance
- Last Reconciled Date
- Bank Statement Balance
- Bank Statement Date
- Item to Match
Click the name of an account in the portlet to view the Bank Register Report for that account.
If your role has the permission to view the Reconcile Account Statement page, this portlet is on your dashboard by default and does not require setup. If you remove it, you can add it again in the Personalize Dashboard panel.
For more information, see the help topic Portlet Types Table.
Improvements to Intelligent Transaction Matching
In NetSuite 2018.1, the following enhancements have been made to Intelligent Transaction Matching:
- New Transaction Types Available for Custom Rules
- Inactivate Transaction Matching Rules
- Automatic Correction to Matches when Transactions are Deleted
New Transaction Types Available for Custom Rules
When you specify rule conditions for custom matching rules, there are now more options available from the Transaction Types lists.
For NetSuite general ledger transactions, the following transaction subtypes are now available for selection:
- Credit Card Refunds
- Credit Card Charges
For the imported statement transactions, the following transaction types are now available for selection:
For details, see the help topic Transaction Types in Matching Rules.
Inactivate Transaction Matching Rules
In NetSuite 2018.1, instead of deleting transaction matching rules, you can temporarily make them inactive. You may want to inactivate certain default rules because you cannot delete default rules.
NetSuite stops running inactivated rules for subsequent imports, but the rule stays in the list on the page. To inactivate a rule, go to Transactions > Bank > Reconciliation Matching Rules. Under the new Active column, you can clear or check the box in the row for a rule. For details, see the help topic Inactivating Transaction Matching Rules.
Automatic Correction to Matches when Transactions are Deleted
Previously, when a transaction was deleted you had to find and undo any transaction matches manually. NetSuite now reverts the match and removes the cleared status if you delete an unreconciled transaction or void a general ledger transaction.
To match the transactions again, see the help topic Matching Transactions.
Include Accounts for Custom Transaction Matching Rules
For NetSuite 2018.1, you can now specify the accounts on which a custom rule should run. NetSuite only runs the custom rule against transactions from the selected accounts.
Previously, custom rules ran on all accounts. Any custom rules from 2017.2 automatically include all accounts, although you can see only those accounts for which you have permissions.
To choose the accounts a custom rule runs for, go to Transactions > Bank > Reconciliation Matching Rules, and click New Rule. In the Custom Matching Rule window, the Accounts subtab is open by default. To switch from a list of all accounts to only the currently included accounts, click Show Included Only. To filter the list of accounts further, select a type from the Account Type list, or use the search field. For details, see the help topic Creating Custom Transaction Matching Rules.
The list displays only the accounts your role has access to. Your user role must also have the Accounts permission with an access level of View. For details, see the help topic Setting Reconciliation Permissions.
4) Inventory Status
Note: This feature requires you to be using Multi Location Inventory and Advanced bins. If you are interested in using this functionality please contact your account manager to discuss further.
The Inventory Status feature enables you to associate attributes to items for detailed tracking of inventory and to drive internal processes. By creating inventory status records, you can assign a status to quantities of an item and track that item’s available inventory by status. For example, you can create an Inspection status for items that are pending quality control inspection.
You can also control the sale of specific inventory by choosing whether to make inventory associated with each status available to be allocated to orders. For example, you can create a Damaged status to associate with items that should not be sold. Clear the Make Inventory Available box on the Damaged inventory status record to prevent items with that status from being sold.
Important: The Make Inventory Available setting does not apply to items on drop shipments and special order purchases. Items with an unavailable status can be allocated to sales orders marked as drop shipments or special orders. You can also receive unavailable items on the associated purchase order created from a drop shipment or special order sales order. For more information on drop shipments and special orders, see Drop Shipments and Special Order Purchases.
To enable the Inventory Status feature, go to Setup > Company > Enable Features and click the Items & Inventory tab. You must first enable the Advanced Bin/Numbered Inventory Management and MultiLocation Inventory features on the same page.
For more information, see the help topic Inventory Status.
5) Landed Cost Added to Inbound Shipment Management
Customers who use the inbound shipment management feature can now associate landed costs at the shipment level. Previously, to calculate shipment level landed costs you had to calculate these values outside of NetSuite and manually update individual item receipts. ISM landed costs completely automates this task.
- Support for multiple-currency landed cost entries
- Allocation of landed cost to a specific item or to all items on a shipment
- Greater visibility of expected landed costs prior to receipt of goods
- Supports Suitescript, allowing provision of custom calculations and rules
To assign a landed cost to an item on an inbound shipment record, go to the new Landed Costs subtab.
Lists, Records, & Fields Submenu Reorganization
NetSuite 2018.1 includes a reorganization of some of the Lists, Records, & Fields submenu items, and of the subtabs on form customization pages have been reorganized.
The changes to the Lists, Records, & Fields submenu include the following.
- The Custom Segments menu item has been moved up to be below the Record Types menu item. This menu item is available when the Custom Segments feature is enabled.
- The Transaction Column Fields menu item has been renamed to Transaction Line Fields.
- The Other Custom Fields menu item has been renamed to Other Record Fields.
- A new Other Sublist Fields submenu has been added below the Other Record Fields submenu. The Other Sublist fields submenu is available when the Advanced Bill of Materials feature is enabled.
Form Customization Subtab Reorganization
The following changes have been made on entry form and transaction form customization pages:
- The Lists subtab is now Sublists.
- A new Sublist Fields subtab is available beside Sublists. The Sublist Fields subtab lists the column fields of sublists that can be configured.
- The Columns subtab has been removed from the Screen Fields subtab of the Custom Transaction Form page. The functionality on the Columns subtab can now be found on the Sublist Fields subtab.
Configuration Added for Mandatory Sublist Entry
Administrators or users with the Custom PDF Layouts permission can now specify that a sublist of any record type must contain at least one row.
On the Customize Form page, you can specify that an entry is required in a sublist by checking the Never Empty box for that sublist.
7) Sandbox Changes
Note: Sandbox accounts are available to all JCurve ERP and NetSuite customers. If you are interested in purchasing a sandbox account please get in touch with your account manager to discuss further.
An upgrade to sandbox architecture is now available to all sandbox accounts for customers in North American data centers. As part of the first refresh of the account after January 11th, 2018, each sandbox account on the sandbox domain is upgraded to the new architecture. The refresh shifts the sandbox to be on the NetSuite domain, instead of the sandbox domain. After a sandbox account transitions to the NetSuite domain, it is easier for users to switch between roles in production and sandbox accounts.
This change affects how users access their sandbox account. Before the transition, users log in to https://system.sandbox.netsuite.com to access a sandbox account on the sandbox domain (previously referred to as NA sandbox). After the sandbox transition, users log in to the sandbox account on the NetSuite domain at https://system.netsuite.com (previously referred to as EU sandbox). Users can choose between their production and sandbox roles on the Choose Role page or Change Roles list. Note that attempts to log in using the old sandbox URL no longer work after the transition.
In addition, when a primary sandbox transitions to the NetSuite domain, its account ID changes. Prior to the transition, a primary sandbox account has the same account ID as the related production account. After the transition, the sandbox account’s ID is appended with _SB1. Customers that have integrations to these sandbox accounts must update these integrations to point to the right account ID, to ensure that integration requests continue to work after the transition.
For more information about these sandbox changes, see the help topic Sandbox Pre-transition Checklist.
Zero Downtime When Refreshing Sandbox Accounts on the NetSuite Domain
Before 2018.1, a sandbox account was taken offline when an administrator requested a refresh of the account. After a sandbox account is on the NetSuite domain, accounts are no longer taken offline when a refresh is requested. Users can use the sandbox account while the new copy is being prepared.
When the new copy is ready to be activated, administrators receive an email notification to activate the sandbox. To activate the sandbox account after a refresh, go to the Sandbox Accounts page in your production account, and select the Activate Sandbox button. When the new copy of the sandbox account is activated, the previous version is deleted. All old data is replaced with a new copy of the production account data.
Important: Be sure to warn all active users to save their current work before you activate the new copy of the sandbox account. For details, see the help topic Preserving Sandbox Changes.
For more information, see the help topic Requesting a Refresh.
8) WSDL Versions 2012.1 and Older to be Disabled
Note: For any existing integrations in your NetSuite account, please check with your developer to ensure they are using an up to date WSDL version.
NetSuite WSDL versions 2011.2 and older will be disabled when version 2019.1 becomes available. NetSuite WSDL version 2012.1 will be disabled when version 2019.2 becomes available.
Integrations that use the 2011.2 or older endpoints will cease to operate when your account is upgraded to 2019.1. Integrations that use the 2012.1 endpoint will cease to operate when your account is upgraded to 2019.2.
Access to URLs with retired WSDL versions will be disabled. Any SOAP operation that uses a retired WSDL version will return a response of “INVALID_VERSION.” This will affect web services integrations, as well as single sign-on (inbound SSO) and SuiteSignOn (outbound SSO) integrations that use web services APIs.
Upgrade your client applications to use the latest generally available WSDL version before your upgrade to the 2019.1 release.
For more information about the availability of earlier endpoints, see the help topic Support for Existing WSDL Versions.
1. Fixed Assets Management Enhancements
Custom Segment Support for Fixed Assets Management
Customers that use the Custom Segments feature will now be able to extend the functionality to their fixed assets. This feature will make your custom segments available in the following Fixed Assets Management records:
- Asset Proposal Record
- Asset Record
- Acquisition Depreciation History Record
- Depreciation History Record and associated journal entries
- Transfer Depreciation History Record and associated journal entries
- Revaluation History Record and associated journal entries
- Disposal History Record and associated journal entries
To take advantage of this feature, you must enable the Custom Segments feature (see the help topic Enabling the Custom Segments Feature). You must also apply the custom segment to the FAM record where you want it to appear. For more information, see the help topic Applying a Custom Segment to Record Types.
In FAM journals, the custom segment is shown on the main body or the line item, depending on how you mapped the fields. You can also choose to show the custom segments in fixed assets reports by customizing the XML report template. For more information, see the help topic Customizing the Asset Report Template.
Note: The ability to filter FAM reports by custom segments is currently not available
Change in Generating Depreciation Schedule Values
Note: This update is targeted to be available in March 2018.
In the previous version, if a change in the asset affects its depreciation values, the system will delete the existing depreciation schedule and create a new one.
Starting with Fixed Assets Management version 18.1, changes to assets that affect its depreciation amount will no longer trigger an automatic reset of depreciation schedule values. Existing depreciation schedule values will still be deleted. New depreciation schedule values, however, will be generated every Sunday, 12 AM PST, or when the scheduled script is triggered manually. For more information, see the help topic Changing the Depreciation Scheduled Script Runtime.
Note: Generation of depreciation schedule values can be interrupted by other FAM processes.
Tax Methods in the Asset Revaluation Page
In Fixed Assets Management version 18.1, asset and tax records are now linked to an accounting book. For non multi-book accounts, all records will be tagged to the primary accounting book. With this change, the tax methods will now show in the Asset Revaluation page. Records are arranged by accounting book, GL posting tax methods, and then non GL posting tax methods.
2) Customer Record Shared with Multiple Subsidiaries
If you use NetSuite OneWorld, prior to 2018.1 you could assign a customer record to a single subsidiary. The Multi-Subsidiary Customer feature permits you to share a customer or sub-customer record with multiple subsidiaries. Then you can select any of those subsidiaries on core transactions created for that customer. The primary subsidiary assigned to a customer is selected by default on any transactions involving that customer. You can also associate transactions with any secondary subsidiary assigned to the customer. The subsidiary you select on transactions is maintained throughout the transaction workflow. For example, when you select a subsidiary on a sales order, that subsidiary appears on the subsequent invoice.
The Multi-Subsidiary Customer feature enables you to save a multi-subsidiary customer as a multisubsidiary vendor to create a single entity of multiple types. Single-entity records are useful when you want to have one entity represent both a customer and a vendor.
The Multi-Subsidiary Customer feature also enables you to view a multi-subsidiary customer’s hierarchy (primary subsidiary, any assigned secondary subsidiary, and any subcustomer) at Lists > Relationships > Customers.
Note: The subsidiaries you can view are based on your permissions.
The Multi-Subsidiary Customer feature also enables you to view the following:
- Customer balance information on the customer record
- Secondary subsidiary information on core reports
- Customer Statement by currency and by subsidiary
Important: You can define multiple secondary subsidiaries though the user interface and SuiteScript. To define secondary subsidiaries in SuiteScript, use the Customer-Subsidiary Relationship record type. It is not yet possible to define secondary subsidiaries through CSV import.
If you have shared multiple subsidiaries with a vendor record, you can share a customer record that is also paired with a vendor record. Such pairings display on the Relationships subtab on the customer record.
To use SuiteScript to define secondary subsidiaries on a vendor record, use the VendorSubsidiary Relationship record type.
For details about the Multi-Subsidiary Customer feature, see the help topic Assigning Subsidiaries to a Customer.
We also encourage you to complete the recommended NetSuite pre-release tasks.