ANS-1147 · ACCOUNTING & FINANCIAL CONFIGURATION

How to Manage GL Account Changes for Historical NetSuite Transactions?

Understand the complexities of altering general ledger accounts on past NetSuite transactions and learn the recommended approach for managing account changes.

Short answer

Modifying GL accounts on historical NetSuite transactions is generally not recommended due to significant impacts and system limitations, especially for paid-in-full or closed-period transactions. The best practice is to inactivate old accounts and use new ones for future transactions, ensuring historical data remains intact while preventing future use of deprecated accounts.

Scenario

Organizations often encounter situations where general ledger accounts used on past NetSuite transactions require modification. This typically arises from changes in accounting policies, chart of accounts restructuring, or correction of initial setup errors. Users seek to understand the feasibility and implications of altering GL accounts on transactions that have already been processed, sometimes in closed accounting periods.

Solution

Modifying general ledger accounts on historical NetSuite transactions is generally not recommended due to the significant impacts and potential system limitations. Editing transactions that have been fully processed, particularly those within closed accounting periods, is not considered a good practice and may require reopening periods, which can have broad implications. NetSuite may also prevent changes to transactions that are marked as "Paid in Full" due to their finalized status.Instead of editing historical transactions, the recommended approach is to manage account changes by inactivating the old accounts and utilizing new accounts for all future transactions.

  1. Inactivate Old Accounts

    Mark the general ledger accounts that are no longer in use as inactive. This action prevents them from being selected on new transactions and records.

  2. Historical Data Preservation

    Inactive accounts will continue to appear on historical transactions and reports, ensuring data integrity and continuity for past financial records.

  3. Analyze and Update Related Records

    Any chart of account change necessitates a thorough analysis to identify all impacted transactions and records. Specific examples include:

    • Accounts Receivable (A/R) Account Changes: Requires updates to Accounting Preferences and individual customer records.
    • Revenue Account Changes: Requires updates to Item records.

Expert NetSuite Support

Need help with this NetSuite issue?

Accounting & Financial Configuration consulting and configuration support

Talk to a consultant