Salto for
NetSuite
Articles
SHARE
Sonny Spencer, BFP, ACA
September 11, 2022
7
min read
About Salto: Salto helps you and your team deploy, track, and manage your NetSuite customizations effortlessly. Learn more here.
The NetSuite chart of accounts lives at the very core of the system. It is integral to most NetSuite functional areas. While important to every business working with NetSuite, the chart of accounts will be unique to each of those businesses. This is key. The chart of accounts should be structured to meet business reporting requirements and in some cases to support ERP functionality (think indirect tax reporting).
It is possible to modify NetSuite accounts both in terms of account name and account number but doing so creates challenges for referencing historical data. It is generally recommended that new accounts be created vs modifying existing accounts and in doing so typically leads to other administrative tasks, for example updates to existing custom financial reports.
This can be avoided altogether if the accounts are created correctly the first time around.
NetSuite allows users to create custom fields on their chart of accounts. We will focus on the key native fields and their purpose:
Salto Suite Tip – This field is straightforward to populate in the UI by simply selecting the correct value from the account dropdown list. For populating the field value via CSV import, the field value must be in a specific format. Specifically “[Account Number] [Account Name]” for example “1000 Bank” could be a parent/summary account for all bank accounts in the chart of accounts.
Salto Suite Tip – The “Summary” check box cannot be populated via CSV import as the field is not exposed. This is because the action of checking this box in the UI also triggers the “Inactive” check box to be checked. This ensures users cannot post transactions to Summary accounts.
Salto Suite Tip – If managing NetSuite development work across multiple NetSuite environments becomes challenging, especially when working with NetSuite record internal ID’s, consider leveraging a tool, such as Salto, to compare NetSuite development across NetSuite environments. Doing so reduces the risk of production deployment errors. For example if a Suitescript deployment references an incorrect account ID in a script parameter (or hardcoded in the code directly) it can have a significant impact on production data, requiring hours of NetSuite Admin time to investigate and resolve the issue.
The chart of accounts import template includes all columns necessary for a successful CSV import into NetSuite, but does not include a NetSuite sample chart of accounts as these are unique to each business. Many of these fields are mandatory (see above), while others are very useful despite not being a required field e.g. “Description”.
Simply populate the CSV import template file with the chart of accounts structure for your company and complete a CSV import to create the accounts.
Navigate: Setup – Import/Export – Import CSV Records
Import Type = Accounting
Record Type = Chart of Accounts
When you get to Field Mapping, do not forget to update the “Subsidiary” reference type from “Names” to “Internal ID”, by clicking the pencil icon to the left of “Subsidiary” and setting the appropriate value.
Once the import is successful, you can validate the data by navigating to the NetSuite chart of accounts. So if you are wondering where to find chart of accounts in NetSuite:
Navigate: Setup – Accounting – Chart of Accounts
Salto Suite Tip – If you have any mandatory fields already created on the account record in NetSuite, these fields must be added as new columns in the CSV import template file, otherwise the import will fail when validating mandatory custom fields.
The key reason the order of accounts is critical is because of parent/child relationships between accounts, in other words the chart of accounts reporting hierarchy in NetSuite. For example, if you had 2 accounts, parent account 1100 and child account 1101, you must first create parent account 1100 so that it can be referenced on child account 1101.
Salto Suite Tip – With this in mind, it is strongly recommended to not use multi-threading when completing your NetSuite chart of accounts CSV import, as the order does matter.
A few best practices to keep in mind when first establishing your NetSuite chart of accounts:
1. When first migrating to NetSuite, consider maintaining your existing chart of accounts. Some implementation partners may suggest this is a good opportunity to revamp your chart of accounts and it is, but you must exercise caution in making this decision. Revamping the chart of accounts typically requires a mapping table back to the legacy chart of accounts. Even if maintained directly in NetSuite via a custom field on the account record, it still makes for more painful reconciliations, especially during an audit focused on the transition period from legacy chart of accounts to newly revamped chart of accounts. With everything else to be achieved during a NetSuite implementation you are likely better off focusing attention elsewhere and maintain the existing chart of accounts.
2. When a company does decide to revamp their NetSuite chart of accounts numbering or change chart of accounts in NetSuite, thought should be given to the number of digits assigned to an account. Smaller companies tend to utilize 4-digit accounts, whereas larger companies typically work with 6 (or more) digits. There are of course exceptions. The point being to consider your business needs before deciding up the appropriate numbering convention for the chart of accounts.
3. Prior to creating your chart of accounts or creating new accounts for an existing chart of accounts, ensure you are not combining NetSuite segments. For example, combining accounts with departments:
Instead, utilize the department dimension to keep the chart of accounts manageable. Some companies will do this with class and/or location. Start utilizing the individual NetSuite segments to better structure data for more dynamic reporting.
When implemented appropriately, the NetSuite chart of accounts will allow for dynamic financial reporting, with limited maintenance needed. More expansive charts of accounts, require additional oversight and maintenance. Not only of the chart of accounts structure, but also of existing financial reports that rely upon the chart of accounts and groupings of accounts within.
Salto for
NetSuite
NetSuite
SHARE
Sonny Spencer, BFP, ACA
September 11, 2022
7
min read
About Salto: Salto helps you and your team deploy, track, and manage your NetSuite customizations effortlessly. Learn more here.
The NetSuite chart of accounts lives at the very core of the system. It is integral to most NetSuite functional areas. While important to every business working with NetSuite, the chart of accounts will be unique to each of those businesses. This is key. The chart of accounts should be structured to meet business reporting requirements and in some cases to support ERP functionality (think indirect tax reporting).
It is possible to modify NetSuite accounts both in terms of account name and account number but doing so creates challenges for referencing historical data. It is generally recommended that new accounts be created vs modifying existing accounts and in doing so typically leads to other administrative tasks, for example updates to existing custom financial reports.
This can be avoided altogether if the accounts are created correctly the first time around.
NetSuite allows users to create custom fields on their chart of accounts. We will focus on the key native fields and their purpose:
Salto Suite Tip – This field is straightforward to populate in the UI by simply selecting the correct value from the account dropdown list. For populating the field value via CSV import, the field value must be in a specific format. Specifically “[Account Number] [Account Name]” for example “1000 Bank” could be a parent/summary account for all bank accounts in the chart of accounts.
Salto Suite Tip – The “Summary” check box cannot be populated via CSV import as the field is not exposed. This is because the action of checking this box in the UI also triggers the “Inactive” check box to be checked. This ensures users cannot post transactions to Summary accounts.
Salto Suite Tip – If managing NetSuite development work across multiple NetSuite environments becomes challenging, especially when working with NetSuite record internal ID’s, consider leveraging a tool, such as Salto, to compare NetSuite development across NetSuite environments. Doing so reduces the risk of production deployment errors. For example if a Suitescript deployment references an incorrect account ID in a script parameter (or hardcoded in the code directly) it can have a significant impact on production data, requiring hours of NetSuite Admin time to investigate and resolve the issue.
The chart of accounts import template includes all columns necessary for a successful CSV import into NetSuite, but does not include a NetSuite sample chart of accounts as these are unique to each business. Many of these fields are mandatory (see above), while others are very useful despite not being a required field e.g. “Description”.
Simply populate the CSV import template file with the chart of accounts structure for your company and complete a CSV import to create the accounts.
Navigate: Setup – Import/Export – Import CSV Records
Import Type = Accounting
Record Type = Chart of Accounts
When you get to Field Mapping, do not forget to update the “Subsidiary” reference type from “Names” to “Internal ID”, by clicking the pencil icon to the left of “Subsidiary” and setting the appropriate value.
Once the import is successful, you can validate the data by navigating to the NetSuite chart of accounts. So if you are wondering where to find chart of accounts in NetSuite:
Navigate: Setup – Accounting – Chart of Accounts
Salto Suite Tip – If you have any mandatory fields already created on the account record in NetSuite, these fields must be added as new columns in the CSV import template file, otherwise the import will fail when validating mandatory custom fields.
The key reason the order of accounts is critical is because of parent/child relationships between accounts, in other words the chart of accounts reporting hierarchy in NetSuite. For example, if you had 2 accounts, parent account 1100 and child account 1101, you must first create parent account 1100 so that it can be referenced on child account 1101.
Salto Suite Tip – With this in mind, it is strongly recommended to not use multi-threading when completing your NetSuite chart of accounts CSV import, as the order does matter.
A few best practices to keep in mind when first establishing your NetSuite chart of accounts:
1. When first migrating to NetSuite, consider maintaining your existing chart of accounts. Some implementation partners may suggest this is a good opportunity to revamp your chart of accounts and it is, but you must exercise caution in making this decision. Revamping the chart of accounts typically requires a mapping table back to the legacy chart of accounts. Even if maintained directly in NetSuite via a custom field on the account record, it still makes for more painful reconciliations, especially during an audit focused on the transition period from legacy chart of accounts to newly revamped chart of accounts. With everything else to be achieved during a NetSuite implementation you are likely better off focusing attention elsewhere and maintain the existing chart of accounts.
2. When a company does decide to revamp their NetSuite chart of accounts numbering or change chart of accounts in NetSuite, thought should be given to the number of digits assigned to an account. Smaller companies tend to utilize 4-digit accounts, whereas larger companies typically work with 6 (or more) digits. There are of course exceptions. The point being to consider your business needs before deciding up the appropriate numbering convention for the chart of accounts.
3. Prior to creating your chart of accounts or creating new accounts for an existing chart of accounts, ensure you are not combining NetSuite segments. For example, combining accounts with departments:
Instead, utilize the department dimension to keep the chart of accounts manageable. Some companies will do this with class and/or location. Start utilizing the individual NetSuite segments to better structure data for more dynamic reporting.
When implemented appropriately, the NetSuite chart of accounts will allow for dynamic financial reporting, with limited maintenance needed. More expansive charts of accounts, require additional oversight and maintenance. Not only of the chart of accounts structure, but also of existing financial reports that rely upon the chart of accounts and groupings of accounts within.