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 2017.2 release summary.
1) Change to Imported Bank Statements
Instead of navigating to the Online Bank Statement page to view imported bank statements, the process has been streamlined so you can now view or delete imported bank statements on the Bank Statement Import list at Transactions > Bank > Import Online Banking Data > List. You can click the header of the column you want to sort by. The Online Bank Statement menu option and page have been removed. The Auto Match button has also been removed. If you want NetSuite to re-run the matching rules, you can re-import the statement file. When you delete a bank statement, NetSuite deletes all of the imported transactions for that statement and removes any matches made with NetSuite transactions. If you delete an imported statement and then import the same statement again, NetSuite does not mark the transactions as duplicates. You cannot delete a reconciled statement.
You can create a saved search to quickly locate a specific set of imported transactions. On the Search page, select Bank Statement Import to define your saved search.
Note: These enhancements are standard NetSuite Bank Reconciliation processes. Customers using the advanced reconciliation features by ERP Fast Forward are not effected. For more details on the advanced benefits of ERP Fast Forward reconciliation and payment processing please click here or contact your account manager.
Change to Bank and Credit Card Account Reconciliation Process
You can now match and reconcile transactions, all within the one page. Previously, you had to match transactions on the Online Bank Statement page and then reconcile the NetSuite account records on the Reconcile Bank Statement or Reconcile Credit Card Statement pages. After importing a statement, go to Transactions > Bank > Reconcile Account Statement. The new Reconcile Account Statement page shows side-by-side lists of imported statement transactions and NetSuite transactions. You can filter the lists and then select one or more transactions from each list to choose matches. As you match, NetSuite saves the work for the account as you go, so that you can choose to complete it at a later time. Click the Matched tab to view the transaction matches. You can still undo matches if the transactions have not yet been reconciled. To reconcile all the matched transactions, you must close the statement for the specified date range. This page replaces the Online Bank Statement page and the reconciliation process from previous versions.
To use the new Reconcile Account Statement page:
- For the accounts you want to be able to reconcile on the Reconcile Account Statement page, check the Use Imported Statement Reconciliation Form box on the Account page. If you import a QFX or OFX statement, and an account is identified, the box is automatically checked.
- If you want to import CAMT.053.001.06–formatted XML or BAI2-formatted TXT files, ensure that the required Bank Import Mapping fields are also set in the Account page.
- Ensure your role has the required permissions. If you do not import account statements, the original reconciliation pages are still available.
2) Create and Edit Custom Rules for Intelligent Transaction Matching
Note: Transactions need to exist in NetSuite in order to be matched. Transactions are not created automatically when you import your Online banking data.
Prior to 2017.2, the Auto Match feature included automatic transaction matching using only default system rules. You also had to view matched and unmatched transactions on the Online Bank Statement page. Auto Match is now called the Intelligent Transaction Matching feature and enables you to go to Transactions > Bank > Reconciliation Matching Rules to view system rules and create your own custom rules.
You cannot modify or remove system rules. NetSuite runs the system rules first and then runs the custom rules in the order you specify. The Online Bank Statement page, along with the Auto Match button, has been removed. If you want NetSuite to run the matching rules again, you can re-import the statement file. To use the Reconciliation Matching Rules page, ensure your role has the required permissions.
3) QIF Bank Statement File Format Deprecation
In NetSuite 2017.2, the QIF file format for statement import on the Online Banking Data Upload page is no longer supported. The developer of QIF, Intuit, discontinued support for the format several years ago in favor of the QFX format. The QFX format better mimics the OFX data created by most financial institutions for their Direct Connect data transmissions. OFX provides a faster and more accurate download experience.
The following industry-standard formats for importing transactions are supported in 2017.2:
- BAI2–formatted TXT (newly supported format)
- CAMT-formatted XML (newly supported format)
To import statement files, go to Transactions > Bank > Import Online Banking Data.
4) Enhanced Item Location Configuration
If you use the Multi-Location Inventory feature, you can now benefit from the new Enhanced Item Location Configuration feature. Previously, when you viewed the Locations subtab on an item record, data showed for all locations by default, as per screen shot below. For accounts using many locations, finding information could be difficult.
Location information is not displayed until a view is selected. The view selection determines which data columns show and data shows only for locations related to the selected View. Also, item location attributes are no longer automatically assigned to all locations.
You can enable the Enhanced Item Location Configuration feature via Setup > Company > Enable Features > Items & Inventory > Advanced Item Location Configuration.
5) Print Journal Entries Using Advanced PDF/HTML Templates
When the Advanced PDF/HTML Templates feature is enabled, NetSuite now provides the Standard Journal Entry PDF/HTML Template for printing individual journal entries. Below is an example of a Journal that has been printed using the standard Advanced PDF/HTML template.
Note: Please contact your account manager if you have any customisation requirements for Journals.
6) Inbound Shipment Management
Inbound Shipment Management (ISM) is now available in 2017.2. ISM enables companies with high volume and increased traceability shipping requirements to track, bill, and assign multiple purchase orders and lines to a single consignment.
- No visibility of location, status and other attributes of an incoming shipment.
- No visibility of in-transit inventory.
- When items from multiple POs are in a shipment, each PO must be received and billed separately.
- No support for FOB=Shipping Point scenarios.
User Benefits and Value Add of ISM
- Streamlined inbound logistics process
- Visibility of in-transit inventory and PO quantities allocation
- Faster and easier receiving and billing of incoming shipments
- One place to store, track and manage information about incoming shipments
- Flexibility by allowing users to add custom fields and deploy SuiteScripts
- Native support of FOB=Shipping Point, no workarounds required
ISM provides increased visibility of inbound shipments, enabling logistics coordinators to work more effectively and finance departments to significantly reduce the amount of time spent recording bills. Key benefits include:
The dedicated inbound shipment record keeps all key information in one place. You know exactly what quantities and items are expected on a shipment as well as expected shipment dates, landed dates, and bill of lading information.
PO lines can be quickly added to and bulk received on the ISM record. The entire shipment can be billed at one time, or individual items can be billed accordingly.
Ownership transfer permits customers to take ownership of a shipment at the FOB shipping point and automatically reflect these in the General Ledger. You can enable Inbound Shipment Management at Setup > Company > Enable Features > Transactions > Shipping and Receiving > Inbound Shipment Management. New inbound shipments are created at Transactions > Purchases > Create Inbound Shipment. The inbound shipment record is supported in client and server-side SuiteScript. The internal ID is inboundshipment. The record can be created, read, updated, deleted, and searched.
7) Improved Login Experience for Customer Center Users
As of 2017.2, you can present your Customer Center users with your own custom login page by default. An account administrator can specify an HTML file to be served by default as the Customer Center login page instead of the generic login page. This custom login page is generated from an HTML file (or files) stored in the File Cabinet of your account. A new setting on the General Preferences page lets you specify your custom Customer Center login page instead of the generic login page. Important: Ensure that your Account ID is included in the code for the forgot password link on your custom login page. Your custom Customer Center login page also serves as the default logout page, unless you specify that a different page be used. To configure a different logout landing page, go to Setup > Company > General Preferences. On the Centers subtab, select Customer Center as the Center Type, and then specify the Log Out Landing Page.
Example of a custom branded Customer Center login page.
8) Enhanced Error Messages for Document Print Failure
NetSuite 2017.2 includes enhancements to the error messages that appear when a PDF document does not print and fails with an error. These enhancements include additional details and a more readable structure. Newly included details are the template name, the line, and the column where the error occurred. The user can click Detail... to see a description of the error. This information makes it easier for administrators to troubleshoot issues with print templates. Enhanced error messages also appear when saving an advanced PDF/HTML template in the template editor. If the template has errors, the message displays the line and the column where the error occurred. The user can click Detail… to see a description of the error.
9) Changes in Web Services and RESTlet Concurrency Governance
In previous releases of NetSuite, concurrency for web services and RESTlets was governed separately per user and authentication method. NetSuite 2017.2 includes changes to concurrency governance. As of this release, web services and RESTlet concurrency is additionally governed per account. The new account governance limit applies to the combined total of web services and RESTlet requests.
In web services that use the login and logout operations or request-level credentials for authentication, the existing governance limits per user are kept. For web services with token-based authentication (TBA) and for RESTlets, there are no per-user limits for concurrent requests. The change in governance may provide increased concurrency for web services integrations that use TBA. This change provides more limits on RESTlet integrations, which are capped at the maximum concurrency defined for an account
The account concurrency limit for your account is displayed on the Web Services Preferences page, which you can access at Setup > Integration > Web Services Preferences (Administrator).
If you have exceed the limit you have the option to purchase Suite Cloud Plus. Please contact your account manager for further details.
Recommended Actions for your Developer:
Review your client applications to ensure they can handle the error codes. Upgrade your client applications to serialize your requests, or to try sending a request later if the client application receives the WS_CONCUR_SESSION_DISALLOWED response.
10) End of Support for Safari 8
As of 2017.2, the NetSuite application no longer supports the use of Safari 8. If you are using Safari 8, it is strongly recommended that you upgrade to the Safari 10 browser or switch to another supported browser. As of 2017.2, we no longer test or address any issues related to Safari 8. For a full list of currently supported browsers, see the help topic Supported Browsers for NetSuite.
1. Advanced Bill of Materials NetSuite
2017.2 presents a major update to NetSuite’s BOM management capabilities. The new Advanced Bill of Materials feature enables you to:
- Define multiple BOMs for single assembly items – specific BOMs can be now be applied throughout the entire product lifecycle.
- Apply location specific BOMs to an assembly – prior versions applied the same BOM across all locations.
- Use a single BOM across multiple assemblies – previously, BOMs could be applied only to a single assembly.
- Apply BOM defaulting at both the location and master level.
- Streamline BOM revision management using the new revisions record.
In 2017.2, if you use assembly items, you can enable the feature at Setup > Company > Enable Features.
A new bill of materials record type has been created to replace the combined assembly/bill of materials record used in prior versions. Existing BOMs are migrated to the new record format and stored as a legacy BOM. This migration provides you with a convenient rollback option during transition to the new format. New BOM records can be created by going to Lists > Supply Chain > Bill of Materials, or from within an assembly item record. In addition, all key product areas are compatible with the new style BOM.
For example, assembly orders, BOM inquiries, planned standard cost, supply plan, manufacturing routing, matrix assemblies, and many others are all compatible with Advanced BOM. Integral to the new bill of materials record is the Revisions subtab. From here you can view a complete history of the revisions made to the BOM, including changes to effective start and end dates. This simplified format also enables employees users to quickly create and apply a new revision from within the BOM record.
BOMs are assigned to an assembly record from the new Bill of Materials subtab located on the Manufacturing subtab. This subtab replaces the existing Components subtab. From here, you can also specify the revision version and BOM defaults. Both the bill of materials and bill of materials revision records are available for form and record customization of the header and support both client and server-side scripting. The two new fields, Bill of Materials and Bill of Materials Revision, are exposed to saved search. In addition, a System Notes subtab on each record maintains a log of all changes made to the BOM and revisions.
2. Fixed Assets Management Enhancements
Generate Depreciation Schedule
This feature enables you to forecast depreciation values for both accounting and tax methods. This process automatically creates the depreciation schedule for the entire asset life, upon its acquisition (when asset record is generated from a proposal). For assets that are manually created or imported via CSV, a scheduled script runs every week to check which assets do not have a depreciation schedule. The script creates the depreciation schedule based on the depreciation period and start date. The forecast values are also automatically adjusted when there are changes to the depreciation history record throughout the course of the asset’s life. This feature is automatically enabled for newly-installed bundles.
Asset Transfer Enhancements
You can now specify the date when an asset is transferred by setting the Transfer Date in the Asset Transfer page. You can enter a future date if you have enable the Allow Future Date Depreciation preference. The transfer date enables users to properly account for the asset cost and depreciation before and after a transfer. When you transfer an asset, a catch-up depreciation will be computed to ensure that depreciation is up-to-date. When processing bulk transfers, you can also summarize the generated journal entries by asset type, parent, or sub-category.
Support for Custom Segments
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 Asset Management records:
- 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 and invoices You must apply the custom segment to the FAM record where you want it to appear. You can also choose to show the custom segments in fixed assets reports by customizing the XML report template.
Unified Depreciation Engine
Historically, there are depreciation methods which are available for tax methods, but not for accounting methods. The unified depreciation engine combines the capabilities of accounting (book) methods and alternate (tax) methods, so that they can be used interchangeably. This feature will introduce the following changes in Fixed Assets Management:
- Alternate Depreciation Method – For Multi-book account users, a Posting check box will be available in the FAM - Alternate Depreciation record when you select an accounting book. When the Posting preference is enabled, the tax methods associated to the accounting book will generate depreciation journal entries.
- Annual Depreciation - Annual depreciation methods like 150DB & 200DB can now be used to generate depreciation journal entries. Users can create asset types that use 150DB and 200DB as the default accounting method. This accounting method will be carried over when an asset is created.
- Depreciation Method for Nordics and Benelux –The Fixed Assets Management SuiteApp adds preconfigured depreciation methods specific for the Nordic countries and Benelux. These depreciation methods will be available after installing the SuiteApp.
We also encourage you to complete the recommended NetSuite pre-release tasks.