2018.2 Release


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.

Should you be using a NetSuite edition, please see the full NetSuite 2018.2 release notesView the NetSuite 2018.2 Release overview video here

Important: 2018.2 Access To Release Preview Changes

For this release, NetSuite are not automatically providing Release Preview accounts to all customers. Instead, NetSuite are supporting an option for customers to opt in to Release Preview for 2018.2. If you have not yet received 2018.2 Release Preview dates, and you would like access to a 2018.2 Release Preview account, you can use this option. NetSuite will send email notifications to impacted customers that will explain how to opt in to Release Preview.

Accessing Release Preview

Pre Release Tasks


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.

JCurve Edition 

1) Two-Factor Authentication (2FA) Required for NetSuite Access as Administrator, Full Access and Other Highly Privileged Roles

Who Will Be Impacted By This Change?

IMPORTANT: Users who login to NetSuite using an Admin, Full Access or other highly privileged roles will be impacted. Please ensure your NetSuite Administrator has reviewed the below changes.

What Is Changing?

For enhanced security, NetSuite 2018.2 requires two-factor authentication (2FA) for all Administrator, Full Access, and other highly privileged roles in all NetSuite accounts. This requirement includes access to production, sandbox, development, and Release Preview accounts.

This means a user needs to enter in an authentication code, in addition to their email and password before they can logon to NetSuite.

Note: The authentication code will be emailed or sent via text message to the user, depending on the delivery method they chose. 

How Can I disabled Two Factor Authentication For My Admin/Full Access Role?

This is mandatory for users using Admin, Full Access and other highly privileged roles. However you can set the duration of trusted device to a maximum of 30 days. This means you will only have to enter in the authentication code once every 30 days. 

The Administrator and Full Access roles are designated as 2FA authentication required by default, and this requirement cannot be removed. Certain highly privileged permissions mandate that a role be 2FA required by default. Any standard or customized roles that include these permissions are indicated in the Mandatory 2FA column on the Two-Factor Authentication Roles page.

For more information, see the following topics in Suite Answers:

■ Permissions Requiring Two-Factor Authentication (2FA)

■ Designating Two-Factor Authentication Roles

How To Set The Duration Of Trusted Device To A Maximum Of 30 Days.

Navigate to Setup > Users/Roles > Two-Factor Authentication Roles. Set Duration of Trusted Device to 30 Days and click Submit for your specified Role.


Additional 2FA Information

NetSuite offers a free 2FA solution that provides both online and offline methods for receiving verification codes.

See the help topic Two-Factor Authentication for more information.

The first verification code users need is sent by email. At the first 2FA login, users with highly privileged roles are prompted to set up their preferred and backup methods for receiving verification codes.

For more information, see the help topic Logging In Using Two-Factor Authentication (2FA).

For general information for Administrators about 2FA in NetSuite, see the help topic Two-Factor Authentication. For general information for all users, see the help topic Using 2FA.

2FA Changes Impacting NetSuite Integrations

IMPORTANT: If you have any integrations with NetSuite please speak with the developer and have them review the below changes to ensure your integration will continue to authenticate after the 2018.2 release.

Integrations that employ user credentials to access NetSuite might be affected by this change, particularly in the following situations:

■ NLAuth for RESTlets or for SuiteTalk (web services) integrations that employ the login operation using the passport element in the LoginRequest.

■ Inbound SSO integrations that use the mapSso operation.

Important: In your integrations, you might need to use certain functions that require a highly privileged role. You should transition these integrations to use token-based authentication (TBA) rather than user credentials, or specify a less-privileged role that does not require 2FA.

For more information, see the help topic Token-based Authentication (TBA).

For information about using TBA with your integrations, see the help topic Integration Management.

Concurrency Changes For NetSuite Integrations

IMPORTANT: If you have any integrations with NetSuite please speak with your administrator to run the Application Performance Management bundle to check for any potential concurrency issues prior to 2018.2 release. 

In the past, concurrency for web services and RESTlets was governed separately per user and authentication method. As of 2018.2, web services and RESTlet concurrency will be governed per account. The account governance limit applies to the combined total of web services and RESTlet requests.

Application Performance Management Suite App

IMPORTANT: You can install Netsuite's free Application Performance Management Suite App to help identify any concurrency or integration authentication issues prior to 2018.2 release.

Please see the below article for installation steps and how to use:

Application Performance Management

2) Better Protection from Malware and Spam in Inbound Email Messages

To better protect your NetSuite account, NetSuite have applied a new malware filter on inbound email. This filter completely blocks any email with attachments that contain malware. This blocking prevents the redistribution of malware that may be present in email attachments you receive. When malware is detected in an attachment, both the email and the attachment are blocked. The sender receives a message that the email bounced. The intended recipient is not notified about the blocked email. We also instituted a DNS blacklist query that prevents NetSuite from redistributing spam from suspected or known spammers and phishers. These two new safeguards help to ensure your email is delivered as intended.

3) Banking

The below changes are for the native bank reconciliation functionality in NetSuite. 

New Confirm Transaction Matches Page

Previously, you matched transactions by going to Transactions > Bank > Reconcile Account Statement. In NetSuite 2018.2, transactions are matched on the new Confirm Transaction Matches page at Transactions > Bank > Confirm Transaction Matches.


This page shows the side-by-side lists of transactions from imported statements and from NetSuite. On this page, you can do the following:

■ On the Unmatched subtab, match transactions as before.

■ On the Review Matches subtab, view matched transactions that have not been confirmed yet.

■ Click View Match Details to review the details of the match group for the transaction in a popup window.

■ In the Match Details popup window, click Undo Match to undo the match group. Doing this sends the transactions back to the list of unmatched transactions.

After you have reviewed the matched transactions, click Confirm Matches to clear those transactions and make them available for reconciliation on the Reconcile Account Statement page. Transactions are not cleared until you have confirmed them. To view the transaction processing status, go to Transactions > Bank > Confirm Transaction Matches > Status.

For details, see the help topics Matching Transactions and Confirming Transaction Matches.

After transactions matches have been confirmed, you can reconcile them on the Reconcile Account Statement page. On this page, you can do the following:

■ On the Matched subtab, view or undo the confirmed transaction matches. If you undo the match group, NetSuite removes the cleared flag and moves the transactions back to the unmatched list on the Confirm Transaction Matches page.

■ On the Reconcile subtab, clear the box next to any transactions you want to exclude from the reconciliation.

For details, see the help topic Reconciling Transactions.

To use the new Confirm Transaction Matches page:

■ For each account, check the Use Confirm Transaction Matches and Reconcile Account Statement Pages box in the Edit Bank Account page. NetSuite no longer automatically checks the box when you import a statement.

■ To view and select accounts, your user role must have the Accounts permission with an access level of View.

■ Ensure your role has the Reconcile permission. For details on permissions, see the help topic Setting Reconciliation Permissions.

Create New Charges, Deposits, and Credits While Matching

In addition to creating a new journal entry while matching, you can now create new Charges and Deposits (or Credits) as well. If you have an imported transaction selected in the match drawer, some fields are populated for you.

In 2018.2, go to Transactions > Bank > Confirm Transaction Matches. If the selected account is a bank account, you can:

■ Click Add New Charge to create a charge.

■ Click Add New Deposit to create a deposit.

If the selected account is a credit card account, you can:

■ Click Add New Charge to create a credit card debit.

■ Click Add New Credit to create a credit or refund back to the account.

Enter or edit the details in the popup window. NetSuite does not redirect you from the Confirm Transaction Matches page. Note: Tax code fields are not available.

Note: Tax code fields are not available in the popup window. If you require tax codes on your charges and deposits, use the full NetSuite pages. For example, if tax codes are mandatory for your checks, go to the Write Check page.

Exclude Transactions from a Reconciled Statement

Previously, all matched transactions within the specified date range were included in the reconciled statement.

In 2018.2, you can exclude any transactions that you do not want in your reconciled statement. Go to Transactions > Bank > Reconcile Account Statement, and then the Reconcile subtab. To exclude a transaction in a one-to-one match, clear the box for the transaction line. If the match is one-tomany or many-to-many, you must exclude all transactions that are part of the match group. Excluded transactions retain their matches and cleared status, but NetSuite excludes them from the reconciled statement. To switch from a list of all transactions to only the included transactions, click Show Included Only.

For details, see the help topic Reconciling Transactions.

Change to Statement Start and End Dates

Previously, the reconciled statement had a Statement Start Date, which was the beginning of the reconciliation period and Read Only. If there was a previously reconciled statement, the day after the Last Reconciled Date was the Statement Start Date value. Unreconciled transactions before the Statement Start Date did not display in the transaction lists.

In 2018.2, there is no longer a Statement Start Date field. Go to Transactions > Bank > Reconcile Account Statement. To filter the transactions that appear in the list by a date range, enter the dates into the From and To fields at the top of the pane. When you close a statement, there is no start or end date, only a Close Date, which is the value from the Statement End Date.

For details, see the help topic Reconciling Transactions.

Reconcile a Statement with an Amount Difference

In previous versions, you could only close a statement if the value of the Difference field was zero.

In 2018.2, you can now close a statement, even if there is an amount difference. Go to Transactions > Bank > Reconcile Account Statement, and then the Reconcile subtab.


For details, see the help topic Reconciling Transactions.

Changes to Reconciled Statements

With NetSuite 2018.2, you can no longer reopen reconciled statements.

Previously, reopening a statement sometimes resulted in incompatibility errors, preventing the statement from being closed again. This often occurred with statements that were closed in the original reconciliation pages, and then reopened from the Reconciled Statements page. Errors were often a result of having reconciled transactions without transaction matches or having more transactions matched for the same date range.

If you close a statement but then receive more transactions that you must include for that statement period, you can delete the reconciled statement for that period and reconcile the statement again. When you delete a statement, the transactions become unreconciled but remain matched and cleared.

To delete a reconciled statement, go to Transactions > Bank > Reconcile Account Statement > List. For more information, see the help topic Deleting Reconciled Statements.

Download and Decrypt Statement Files

For NetSuite 2018.2, after importing statement files, you can download a decrypted copy of the imported statement file.

You can only decrypt and download statement files you import after your account is upgraded to NetSuite 2018.2.

To view an imported statement, go to Transactions > Bank > Import Online Banking Data > List, and click View for the statement. To download a decrypted copy, click the hyperlinked file name in the File Name field.


For details, see the help topic Viewing Imported Account Statements.

New CSV Statement Format Requirements

For NetSuite 2018.2, the CSV bank statement file must contain the following additional columns:

■ NS Internal Customer ID - (Optional) The NetSuite internal customer ID. Content must be numeric. There is a limit of 12 characters.

■ NS Customer Name - (Optional) If the specified customer ID does not match any data, NetSuite uses the value to look up the customer ID. Content is free-form text. There is a limit of 512 characters.

■ Invoice Number(s) - (Optional) A comma-separated list of invoice numbers in a single field, with no spaces between numbers (for example, 132,133,134). If you use a script or comma-separated file instead of the CSV template in Excel, put quotation marks around multiple invoice numbers (for example, “132,133,134”). For each invoice number in the list, there is a limit of 128 characters. If the imported file specifies multiple invoices for a transaction, they must all belong to same customer and AR account.

Also, the “Name” column heading has been renamed "Payee/Payer Name".

The CSV template now contains these revised columns. Download the CSV template from Transactions > Bank > Import Online Banking Data, or create the file with the required columns and specifications. For details, see the help topic Preparing CSV Files for Import.

4) In-Transit Payments

The In-Transit Payments feature enables you to track when payments to vendors are in process. Use this feature for real-time information about ledger balances for Cash and Accounts Payable.

First, enter an in-transit vendor payment to initiate the payment. This in-transit vendor payment begins the payment process but does not post to the general ledger. Payments that are in-transit can be monitored and updated when the payment is confirmed or declined by the vendor bank. When you receive confirmation that the vendor's bank has received the funds, confirm the payment is complete. Payments can be confirmed and cleared at the same time.

This process enables you to more accurately track the actual date vendors receive payments and allows more accurate tracking of accounts payable funds in your general ledger. Specific bank account balances show in the general ledger and the accounts payable balance is debited only after payment confirmation is received from the vendor’s bank. Outstanding in-transit balances are visible on vendor records.

Some countries may require using In-Transit Payments for commercial payments. Using this feature, the status of in-transit payme


5) Help Center and SuiteAnswers Open in a New Browser Tab

Prior to this release, when you clicked a NetSuite UI link for the Help Center, it opened in a limited popup window. Some users requested a change to this behavior. Previously, when you clicked a SuiteAnswers link, it opened in the same browser tab as the NetSuite application, and you no longer had access to the NetSuite UI in the browser.

As of 2018.2, both the Help Center and SuiteAnswers open in a new browser tab when they are accessed. This change makes it easier for you to review documentation as you work in the NetSuite UI.

Improved Help Center Search

This release includes improvements to Help Center search to ensure that you receive the best possible search results. These improvements include:

■ Returning results for search keywords with typos – For example, if you enter “comtact” as a search keyword, the search returns results for “contact.” Text informs you of the term that was actually searched.

■ Returning results for search keywords synonyms – In some cases, search keywords that you enter may have a synonymous term that is used more in the Help Center. In these cases, results are returned for the keywords you entered, and a suggestion is made that you search for the preferred term instead.

Videos Tab Added to Help Center

A Videos tab has been added to the Help Center. Click the Videos tab to view a list of help videos that demonstrate how to perform specific tasks in NetSuite. When you click a link, you are redirected to the Oracle Learning Library to view the video.


6) Advanced Template Printing Support for Custom Records

Advanced Templates can now be used to print custom records. To print a custom record, click the Print button. When your organization updates to NetSuite 2018.2 a standard print template will be available for any existing custom record type. Administrators can customize a standard print template and assign it to a custom record type. Custom print templates are not updated when the custom record type is changed. For more information about customizing the custom record type print template, see the help topic Updating Custom Record Type Print Templates.

7) Ability to Customize Standard Field-Level Help

Administrators can now customize the field-level help for standard NetSuite fields and enter field-level help for other languages. Administrators or users with the Full level of the Customize Field Level Help permission can edit or remove the custom help for a field. To customize the help for a field, click the field label to view help for the field, and then click the Customize button.


NetSuite Edition 

1) System-Generated Journal for NetSuite OneWorld


NetSuite 2018.2 provides a new system-generated, read-only journal. This journal represents the general ledger impact of payments that are at varying states of completeness in your system. In some countries, in-transit payments are not considered received until the payment is deposited in the payee’s bank account.

To view system journals, on the bill payment record, click the Related Records subtab. Click the number link associated with the system journal you want to view. You must have at least View level of the Make Journal Entry permission to view system journals.

For details about payments in transit, see In-Transit Payments. For details about reconciling in-transit payments, see Confirm In-Transit Vendor Payments.

For additional information about system-generated journals, see the help topic System-Generated Journals for Payments.

2) Customization of the Subsidiaries Subtab on Vendor and Customer Records

If you have permission to customize record types, NetSuite 2018.2 provides two new record types for customizing vendor and customer records. The new record types are Customer-Subsidiary Relationship and Vendor-Subsidiary Relationship. These records are not visible in the user interface. However, the fields on these records are available through the Other Record Fields page at Customization > Lists, Records, & Fields > Other Record Fields > New.

On the Other Record Fields page, select the Customer-Subsidiary Relationship or Vendor-Subsidiary Relationship record type. Define the fields to be added to the Subsidiaries subtab. When the entity record is in Edit mode, you can modify the values in those fields.

The Custom Records and Custom Segments features must be enabled to customize the Subsidiaries subtab on vendor and customer records. If the Multiple Currencies feature is also enabled, you can add currency-specific fields to the Subsidiaries subtab. 

For information about custom record fields, see the help topics Other Record Fields and Creating a Custom Field.

3) Multi-Subsidiary Support for Time and Expenses

In NetSuite 2018.2, in OneWorld accounts, a Billing Subsidiary field has been added to time and expense transactions to support intercompany time and expenses for multi-subsidiary customers. For more information, see the help topic Enabling Intercompany Time and Expenses.

4) Fixed Assets Management Enhancements

Depreciation Monthly Report Enhancements

The Fixed Assets Management SuiteApp now lets you generate a Depreciation Monthly report for secondary books. Depreciation for posting secondary books are available when you generate the Depreciation Monthly report.

You can also customize the Depreciation Monthly report by adding columns through XML or through the report customization feature.

We also encourage you to complete the recommended NetSuite pre-release tasks.















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