Multi-entity rollout data introduction email: an annotated draft for NetSuite implementers

Short answer

Can the company identify the entity and approval behind each adjustment? This email should state the controller's answer, period by period, so send it only once that answer is known and the owner has agreed to an introduction. The draft below has a subject line, three short paragraphs and a metadata-only ask, and every line is annotated: why it is there, and what must never go in it.

Visual briefFull-size diagram
An email draft builds line by line, subject, context, offer and disclosure, while a margin note appears beside each line explaining its purpose.
Illustrative draft. Bracketed fields are placeholders; the margin notes summarize the annotations on this page.

It is one of the tools under the guide on which entity owns the data in a multi-entity group. The rollout playbook covers when to raise the topic, and the meeting agenda produces the yes this email confirms.

The draft, ready to adapt

Illustrative. Bracketed fields are placeholders. The worked case behind it is a fictional 240-person commercial HVAC services group with three entities, which moved onto one NetSuite account this year.

Subject: [Group name]: introduction to SourceX on your pre-rollout adjustment history

Hi [Owner first name],

Thanks for the time in [meeting name] on [date]. As [Controller name] confirmed, [Group name] can show which entity booked and which entity received each intercompany adjustment since go-live, with the approver recorded, and the legacy books hold about [number] earlier corrections a year going back to [year], with the entity named and the approver in [where]. You asked to hear what that history might be worth to an AI data buyer, so I'm introducing [SourceX contact name], copied here.

SourceX licenses approved business data directly from companies for AI training and evaluation, and runs the agreement, rights review, data preparation, delivery and payout. Their first conversation uses the same kind of facts you gave me (counts, years, systems and who owns them), not the records themselves. Whether to take it further, and on what terms, is your decision.

One disclosure: I'm a SourceX referral partner. If a licensing agreement completes and SourceX pays [Group name], SourceX may pay me a reward measured on what your company is actually paid. It is paid separately and is never deducted from your payment. If you would rather not proceed, nothing changes in our rollout work.

[Your name]

Line by line: why each sentence is there

LineWhy it is thereNever put in it
SubjectNames the group and the topic so the owner can find it laterThe word "opportunity", a dollar figure or "urgent"
"Thanks for the time in [meeting]"Anchors the email to a yes the owner already gaveAnything implying this is the first they have heard of it
"As [Controller] confirmed..."States the qualifying answer in the controller's termsEntry amounts, counterparties, account names or screenshots
"since go-live, with the approver recorded"Separates what the new account captures from the older booksA claim that every old entry is complete
"about [number] earlier corrections a year going back to [year]"Gives SourceX a size and span to assessExact totals you were not given, or estimates presented as fact
"You asked to hear..."Records that the owner requested the introductionPressure, deadlines or "before it's too late"
"SourceX licenses approved business data..."Says plainly what SourceX doesClaims about buyers, prices or acceptance odds
"same kind of facts... not the records themselves"Reassures the owner nothing is shared at this stageAn offer to forward files on their behalf
"Whether to take it further... is your decision"Keeps authority with the ownerAny suggestion you will negotiate for them
"One disclosure..."States the relationship and the measuring base before any agreementA projected reward amount
"never deducted from your payment"Answers the question owners ask firstVague wording such as "a small fee"
"nothing changes in our rollout work"Separates the referral from your engagementLinking the rollout schedule or price to their answer

The facts behind the second paragraph

The sentence about post-go-live entries is not boilerplate; it reflects how NetSuite records intercompany work. On a standard intercompany journal, each line posts to either the originating subsidiary or the "To Subsidiary", and debits and credits balance by subsidiary (Oracle NetSuite). That is why you can say the entity is visible since go-live. Only say the approver is recorded if the controller has confirmed approvals are required for intercompany journals in their account. For legacy books, use the controller's words exactly: "entity named in the memo, approver in email" is honest; "full audit trail" usually is not.

The disclosure paragraph, tested

Disclosure belongs in writing and before any agreement. CFA Institute's Standard VI(C), written for investment professionals but a sound model for any adviser, asks for the nature of a referral benefit (for example a flat fee or a percentage basis) and its estimated value to be disclosed before a formal agreement (CFA Institute). The draft names the basis (what the company is actually paid) and the payer (SourceX, separately). It leaves out a figure because none can be estimated honestly at this stage; if your own professional rules require a range, use the program's published terms: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap.

Three checks before you hit send:

  1. Would the owner be comfortable if the controller read this paragraph? If not, rewrite it.
  2. Does it say who pays the reward and that it does not reduce the company's payout?
  3. Does it leave the owner a clear, consequence-free way to say no?

Variations, and what stays fixed

SituationChangeKeep
Owner asked you to copy the controllerAdd the controller in copy and thank them by nameAddress the owner, who decides
Legacy books already switched offReplace the legacy sentence with what the company exported and keptThe metadata-only framing
Records sit in an IP holding entityName the holding entity as the one whose officer would decideThe disclosure paragraph, unchanged
Owner prefers a call firstSend two lines offering a call, then this email afterwardThe written disclosure

For help filling the placeholders, the introduction email builder and the email preparation worksheet walk through each field.

Before you send: eligibility and attribution

Sign the Channel Partner Agreement before you submit the introduction. The company needs 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. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, and one partner is credited per company. Whether records are selected, the rights review result and any payout stay unknown until SourceX reviews the company. More on fit for implementers is on the NetSuite partner page.

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.

Once the owner has said yes and the draft passes the three checks, register as a partner, confirm the group against who qualifies and link the terms in your email.

  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

Should I send the email before the owner has agreed in person?

No. The email confirms a yes the owner has already given. A cold email about their finance history from their implementer reads as overreach, however carefully it is written.

Can I copy the controller?

Copy whoever the owner asks you to. The controller often holds the facts SourceX will ask about, but the email is addressed to the person with authority to decide.

Should I mention how much the reward could be?

Say how it is measured and that SourceX pays it separately. A projected figure would be guesswork, because nothing about price is known until SourceX reviews the company.

Sources

  1. refer.sourcex.si/terms
  2. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  3. cfainstitute.org/standards/professionals/code-ethics-standard…

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