Defining Subsidiaries for OneWorld Transactions

Each transaction in NetSuite OneWorld, except advanced intercompany journal entries, is tied to one subsidiary. When a transaction includes an entity, such as a customer, the transaction is assigned to the same subsidiary as the entity. For transactions without entities, you must manually select a subsidiary. When you process transactions in bulk, such as fulfillments, bill payments, or commission authorizations, select the appropriate subsidiary to filter the list of transactions to process.

Intercompany journal entries post to two subsidiaries. These journal entries record transactions between subsidiaries. Each advanced intercompany journal record includes an originating subsidiary and one or more receiving subsidiaries. For more information, see Making Advanced Intercompany Journal Entries.

Some time entries and expense transactions may be associated with multiple subsidiaries. Each time or expense record is associated with the subsidiary of the employee. In addition, a customer or project can be defined for each line of these records. If the Intercompany Time and Expenses feature is not enabled, each line-level customer or project must be associated with the same subsidiary as the employee. If this feature is enabled and related accounting preferences are set, customers and projects from other subsidiaries can be selected at the line-level. For more information, see Enabling Intercompany Time and Expenses, Expense Reports, and Understanding Time Tracking.

When a transaction has line-level associations to more than one subsidiary, the general ledger posts only to the subsidiary identified in the transaction header. Advanced intercompany journal entries can be created to transfer time, expense, or both charges from one subsidiary to another. An automated adjustment process is available for intercompany expenses. For more information, see Creating Intercompany Adjustments for Time and Expenses.

Note:

In NetSuite OneWorld, List view pages and search results convert the transaction currency to the base currency of the user’s subsidiary. For more information about List view pages, see List View.

Related Topics

Creating Transactions
Working with Addresses on Transactions
Creating New Records as You Enter Transactions
Editing Records as You Enter Transactions
Using Transaction Links
Linking a Transaction to a Support Case

General Notices