Verify that the Advanced Intercompany Journal Entries feature is enabled and that an intercompany clearing account exists for each subsidiary pair
Construct the journal entry payload specifying the primary subsidiary on the header and including line-level subsidiary overrides for lines belonging to other subsidiaries
For each cross-subsidiary line, reference the intercompany payable or receivable account appropriate for the direction of the entry
Post the journal via the SOAP add operation or the REST Record API POST, targeting the advancedintercompanyjournalentry record type
Verify that NetSuite auto-generated the elimination entries by querying for related journal entries linked to the same intercompany transaction ID
Run the Intercompany Reconciliation report to confirm the cross-subsidiary balances net to zero
Known gotchas
Each line must have a subsidiary explicitly set; leaving the subsidiary implicit causes NetSuite to assign all lines to the header subsidiary, which defeats the intercompany purpose
The intercompany clearing account must be designated as an intercompany account type in the chart of accounts; using a regular account blocks automated elimination generation
Period-end eliminations are not created automatically for advanced intercompany journals in all NetSuite configurations; confirm whether your setup requires manual elimination journal entries
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp