Multi-entity rollout data referral opportunity: a playbook for NetSuite implementers

Short answer

Often only partly. Once a group runs its entities as NetSuite subsidiaries, each intercompany line names the subsidiary it posts to and, where journal approvals are on, an approver. Adjustments booked in the separate legacy books before go-live often show the entity in a memo at best and the approver nowhere. That split is the opening for an implementer: the rollout is already deciding what happens to that older history, so one metadata question to the controller can tell you whether the group holds an approval-traced correction record worth introducing.

Visual briefFull-size diagram
A multi-entity rollout on the left fans out to five record types it touches, which then converge on the right into a single owner-approved introduction.
Illustrative. One trigger event, five record types, one introduction decided by the owner.

This playbook sits under the guide on which entity owns the data in a multi-entity group. It covers when to raise the topic and how. The companion pages give you the tools to run it: a timed meeting agenda, a pre-switch-off checklist and an annotated introduction email.

The trigger: one account for every entity

The event is the moment a group with several legal entities, each previously on its own books, moves them into one NetSuite OneWorld account as subsidiaries. It forces three decisions that rarely get asked together: how the legal entities map to subsidiaries, how much history comes across, and what happens to the old books afterward.

The third decision is the one that matters for a referral. Once go-live is set, project plans prioritize opening balances and open items. Closed corrections between entities, with the memos and sign-offs behind them, are historical and easy to leave behind. Yet a run of years in which a finance team spotted, explained and approved cross-entity errors records how people actually exercised judgment, which a ledger balance does not.

Signals that a client is in it

You will usually know before anyone says "multi-entity". These are the cues worth noticing during discovery and design.

SignalWhere you notice itWhat it suggests
Several legacy company files or ledgersData migration workshopPre-rollout history sits in more than one place
Shared-services entity that employs finance staffOrg chart reviewApprovals may sit in a different entity from the books
Intercompany reconciliation done in spreadsheetsClose process walkthroughCorrections and their reasons live outside any ledger
Debate about migrating detail or balances onlyScope sign-offThe group is about to decide whether history survives
Legacy subscription renewal date on the planProject timelineA fixed date by which old books go read-only or away
New approval workflow for journalsConfiguration sessionsPost-go-live entries will carry an approver; old ones may not

Two or more of these together is enough to justify the question. None of them requires you to open a record.

The records the rollout puts at risk

Not the new entries. On a standard intercompany journal in NetSuite, every line posts either to the originating subsidiary or to the "To Subsidiary", and debits and credits must balance by subsidiary (Oracle NetSuite). With approvals required, an unapproved journal does not post (Oracle NetSuite), and system notes keep who changed what and when, with System Notes v2 adding the user's role and deleted-record information (Oracle NetSuite). The exposure is everything older.

Illustrative. A 410-person specialty food manufacturer runs four entities: a U.S. production company, a U.S. distribution company, an overseas sales subsidiary and an IP holding company that owns the brands. Its rollout plan migrates opening balances and two years of detail.

Record typeWhere it lives todayWhat the plan does with itEntity and approver traceable?
Cross-entity reclasses, years three to eightLegacy ledgers of each entityLeft behind; files archivedEntity yes, approver rarely
Reconciliation workbooks with notesController's shared driveNot in scopeEntity in tab names, approver in comments
Royalty true-ups to the IP holding companyLegacy ledger and emailBalances onlyPartly
Transfer-pricing adjustmentsTax adviser filesNot in scopeYes, with memo
Post-go-live intercompany journalsNetSuiteNativeYes, both subsidiaries and approver

What you write down is a count and a yes or no per row, never an entry.

The conversation, in five moves

Keep it inside a meeting you already run. Each move has a purpose and a natural stop.

  1. Anchor on the scope decision. "We're finalizing how much history migrates. Before we do, can I ask about the adjustments between entities?"
  2. Ask the qualifying question exactly. "Can the company identify the entity and approval behind each adjustment?" Note the answer separately for pre- and post-rollout periods.
  3. Size it in metadata. Roughly how many such adjustments a year, how many years survive, which system or folder holds them, and whether reasons are written down.
  4. Find the owner. Which entity employs the people who made and approved the corrections, and which officer could authorize a licensing discussion for the entity that holds the rights.
  5. Disclose, then offer. Say that you are a SourceX referral partner and may receive a reward if a qualifying license completes, paid by SourceX separately. Ask whether they want an introduction. A no closes the topic for this project.

The meeting agenda turns these moves into timed blocks if you need a standalone session.

Who can say yes, and what stays unknown

The controller can answer moves two and three. Only an authorized officer of the right entity can agree to a licensing review, and in an IP-holding structure that may not be the operating company you work with day to day.

Before you introduce anyone, check the baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. With an overseas subsidiary in the group, check where its records sit and what language they are in. Sign the Channel Partner Agreement first; the first valid introduction within the 90-day window is credited when the company submits a verified application. What stays unknown until SourceX reviews it: whether any records are selected, the rights review result, any price and any reward. The NetSuite partner page and the guide to spotting NetSuite referral cues cover fit; PE-owned groups are discussed under industrials value creation, and the network opportunity finder helps you sort a client list.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the controller's answer shows years of entity-traced corrections and the owner opts in, register as a partner, confirm the group against who qualifies and share the terms before you send the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is every multi-entity rollout a referral opportunity?

No. It is a moment to ask one question. Many groups will have thin pre-rollout history, too few employees or no appetite, and the right outcome then is to note it and move on.

Does raising this risk the implementation engagement?

Not if it stays a metadata question asked in the scope conversation you already have, followed by a plain disclosure and a no that ends the topic. Never let it delay a cutover decision.

Which entity signs if the group decides to proceed?

The entity that holds rights in the records, confirmed by the company and its counsel. That is often the one employing the finance team, but the group's own structure decides it.

Sources

  1. refer.sourcex.si/terms
  2. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  3. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  4. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/articl…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment