domain: docs.oracle.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm NetSuite OneWorld is enabled and that intercompany accounts are configured under Setup > Accounting > Intercompany Preferences, including the due-to/due-from account mappings per subsidiary pair.
Create an Advanced Intercompany Journal Entry via the REST Records API by POST-ing to /services/rest/record/v1/advintercompanyjournalentry with the subsidiaries, lines, and currency in the request body; or use SuiteScript nlapiCreateRecord('advintercompanyjournalentry') on the server side.
Include in each line: entity (subsidiary), account, credit/debit amount, and the intercompany account reference; NetSuite will auto-generate the offsetting due-to/due-from lines if the preferences are configured.
Set the approved field to true (or route through an approval workflow) to make the entry posting; unapproved entries remain in a pending state and do not affect balances.
Query posted intercompany entries via SuiteQL against the Transaction and TransactionLine tables, filtering by type = 'AdvInterCoJrnlEntry' and the relevant period, to verify balances before running consolidation.
Reverse intercompany accruals at the start of the next period by posting a reversing journal entry with the same fields but reversed signs, or by using NetSuite's built-in reversal feature on the entry record.
Known gotchas
The SyncToken equivalent in NetSuite is the lastmodifieddate field; always fetch a record before updating to avoid overwriting concurrent changes, as there is no optimistic locking by default on journal entry records via REST.
Period-lock settings on the subsidiary can prevent posting; ensure the accounting period is open for both the originating and destination subsidiaries before attempting the POST.
Intercompany entries that span entities with different base currencies will generate CTA entries automatically; verify the CTA account is configured in consolidation preferences to avoid unposted FX differences.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?