CSV Journal Import using Local Chart of Accounts (Accounting Context) instead of Global Accounts

Question

Hi everyone,

I'm working on a NetSuite OneWorld implementation using Accounting Contexts with localized charts of accounts.

Currently, when importing journal entries via CSV Import, NetSuite requires the account field to reference the Global Account (or its Internal ID/External ID). As a result, we first have to map the local chart of accounts to the global chart of accounts in Excel before importing the journal.

I was wondering if there is any way to avoid this extra mapping step.

For example:

* An accountant has Spain selected in their Accounting Context Preferences.
* They prepare a CSV file using the Spanish local account numbers (e.g. 700000, 472000, etc.).
* Instead of importing the Global Accounts, could NetSuite automatically recognize the local accounts from the selected Accounting Context and post the journal to the corresponding Global Accounts?

In other words, is there any standard functionality, SuiteScript, CSV Import option, or customization that allows journal imports using the localized account numbers instead of the Global Accounts?

My goal is to allow local finance teams to upload their journals directly from their local accounting system without maintaining a separate Excel mapping between local and global accounts.

Has anyone implemented something similar, or is the Excel mapping (or a custom integration) currently the only option?

Thanks in advance for your insights!

Jeanne Padilla-Oracle · Accepted Answer

Hi @Mary Rivas,

Standard NetSuite CSV Import does not currently support using localized account numbers from an Accounting Context as the Journal Entry Account reference. The import still needs a valid NetSuite account reference, such as the global account name/number, Internal ID, or External ID. Accounting Contexts affect display and reporting, and localized account values can be searched, but they are not available as a CSV Import reference type for Journal Entry lines.

For Journal Entry imports, NetSuite expects the Account field to contain a valid NetSuite account reference. For example, the account can be specified using the account number and name (such as 1000 Checking) or another supported reference, such as the Internal ID. If the imported value does not match a valid account reference in NetSuite, the import will fail with an "Invalid account reference" error. This error can typically be resolved by ensuring the account value matches the account format used in NetSuite or by using the account's Internal ID.

So in your example, a CSV containing only Spanish local account numbers such as 700000 or 472000 would not be automatically interpreted against the accountant’s Spain Accounting Context preference and converted to the corresponding Global Account.

To avoid maintaining an Excel mapping, you could implement a custom solution in NetSuite. Options include creating a custom mapping record that links localized account numbers to Global Accounts, using a staging import with SuiteScript to translate local accounts before creating journal entries, or leveraging a User Event script during CSV import (subject to testing and script execution settings). Additionally, saved searches can export localized account information to help generate or validate the mapping table, although they do not provide native support for resolving localized account numbers during CSV imports.

I hope this helps.

—

Kindly click "Yes" on "Did this answer the question?" if you find the reply on your thread helpful. This will aid the others with the same question to easily find the correct answer. You will also earn points and may unlock the Answer Accepter badge.