Automating Intercompany Transactions: A Finance Leader's Guide to NetSuite AIM

If you close the books for more than one subsidiary, you already know where the week goes. Someone exports intercompany balances, someone else hunts for the matching entry in another entity, and the elimination journal gets rebuilt by hand every single period. NetSuite AIM exists to take that work off your team. Once it is turned on in NetSuite OneWorld, AIM creates, posts, and reconciles intercompany transactions as they happen, then generates elimination entries at close. This guide walks a finance leader through what AIM does, what it does not do, how to turn it on, and where teams get tripped up.

What is NetSuite Automated Intercompany Management (AIM)?

AIM is a NetSuite OneWorld feature that standardizes and automates intercompany activity across subsidiaries. Instead of recording each intercompany transaction and its elimination by hand, NetSuite links the two sides of the transaction, keeps them reconciled, and produces the elimination journal entries your consolidation needs. For a controller managing five or fifteen entities, that shifts the close from data cleanup to review.

Before AIM, month-end close could feel like a manual balancing act. Entities are on different posting schedules, intercompany reconciliations remain open deep into the close cycle, and the consolidated view is never reliable until the very last minute. NetSuite's AIM changes that entirely. Transactions post simultaneously across all entities, eliminations run automatically, and your team gains a clean consolidated picture well ahead of where they used to be.

Running a multi-entity NetSuite environment and want a second set of eyes on the setup? Talk to a NetSuite consultant.

What AIM automates across your subsidiaries

When AIM is active in OneWorld, it takes over the repetitive parts of intercompany accounting:

• Intercompany transactions and advanced journal entries. AIM automates intercompany journal entries plus sales, purchases, and inventory transfers between subsidiaries. Advanced intercompany journal entries let you set one originating subsidiary and multiple receiving subsidiaries, and choose any transaction currency configured in your system.
• Automated reconciliation. NetSuite matches and reconciles intercompany sales and purchase transactions across entities, cutting manual matching.
• Coordinated inventory transfers. AIM manages arm's-length intercompany inventory movements, including intercompany drop-ship orders.
• Automatic elimination entries. At period-end close, NetSuite reviews transactions marked for elimination and creates the elimination journal entries, removing internal profit or loss.
• Faster close and consolidation. By identifying intercompany activity and automating eliminations, AIM reduces manual entry and speeds period-end reconciliation.
• A clear audit trail. The Intercompany Elimination Report shows source transactions and the elimination entries NetSuite generated for the period.

Manual intercompany vs. AIM: what actually changes

Do you need OneWorld to use AIM? Prerequisites and what AIM does not do

Yes, AIM requires NetSuite OneWorld. It depends on multiple subsidiaries, intercompany accounts, and an elimination subsidiary, so it does not apply to a single-entity account.

Prerequisites before you turn it on:

• NetSuite OneWorld with your subsidiary structure set up
• Intercompany accounts and an elimination subsidiary configured
• Intercompany preferences reviewed for your accounting policy
• Intercompany customers and vendors mapped for the subsidiaries that trade with each other

What AIM does not do (set expectations here, this is where teams get surprised):

• It does not fix incorrect subsidiary, currency, or account setup. Bad master data still produces bad output.
• It does not decide your transfer-pricing or tax treatment. Those are policy calls AIM then executes.
• It does not remove the need to mark transactions for elimination and run the elimination process.
• It does not replace consolidation review. It gives reviewers a cleaner, traceable starting point.

How to enable AIM in NetSuite (step by step)

Before you turn AIM on, get the prerequisites in place, because the feature cannot be disabled once it is enabled:

• You must be on NetSuite OneWorld.
• Create one or more elimination subsidiaries under your root subsidiary first. AIM expects them to exist before you enable it.
• Enable the Multi Subsidiary Customer feature.
• If you use Multiple Currencies, also enable the Multi-Currency Vendor and Multi-Currency Customer features.

Then enable and configure AIM:

1. Go to Setup > Company > Enable Features and open the Accounting subtab.
2. Under Advanced Features, check Automated Intercompany Management, then save. (This cannot be undone later.)
3. Review your intercompany preferences so they match your accounting policy.
4. Confirm your elimination subsidiaries and the intercompany accounts used for eliminations. NetSuite also adds system accounts automatically, including the Cumulative Translation Adjustment-Elimination (CTA-E) account once a qualifying transaction posts.
5. Set up your intercompany customers and vendors, using the Represents Subsidiary field so each entity maps to the right subsidiary.
6. Mark the relevant transactions for elimination.
7. At period end, run the Eliminate Intercompany Transactions task, which AIM adds as the final step of the Period Close Checklist.
8. Run the Intercompany Elimination Report to review the eliminations and keep the audit trail.

Where teams go wrong: field notes from NetSuite implementations

A few patterns show up again and again when finance teams first adopt AIM:

• Transactions never flagged for elimination, so the automated entries never generate.
• Elimination subsidiary or intercompany accounts set up loosely, which sends eliminations to the wrong place.
• Currency and multi-book assumptions left unchecked, so multi-currency entities do not tie out.
• Running eliminations too early, before all intercompany activity for the period has posted.
• Expecting AIM to reconcile messy master data. It automates the process, it does not clean the inputs.

A multi-subsidiary close, before and after AIM

For multi-entity finance leaders, the payoff is simple: less time assembling intercompany and elimination entries, more time reviewing results. If your close still runs on spreadsheets and manual matching, that is the gap AIM is built to close.

Ready to modernize your intercompany close?

If manual intercompany work is stretching your close, a short assessment usually surfaces the quick wins. Get a NetSuite Health Assessment and see where AIM and related automation fit your entities.