Multi-entity rollout meeting agenda: 20 minutes, four blocks, one decision on intercompany history

Short answer

Yes for adjustments booked in NetSuite with approvals switched on, and often not for corrections in the legacy books. A 20-minute meeting with the controller is enough to find out which. The agenda below runs four timed blocks: map the entities, ask the adjustment question for each period, establish what happens to the old books, and identify who can authorize a review. It ends with one recorded decision: introduce the owner to SourceX, or close the topic.

Visual briefFull-size diagram
A 20-minute clock face split into four wedges that fill in turn, numbered to match four agenda questions on entities, adjustments, the old books and authority, ending in a decision to introduce or close.
Illustrative 20-minute agenda. The second block asks the qualifying question; the last produces the decision.

The agenda belongs to the guide on which entity owns the data in a multi-entity group; the multi-entity rollout playbook explains when to call this meeting at all.

Who to invite and what to send ahead

Three people, one page of pre-read. The pre-read is the subsidiary list from the design workbook and the migration scope as it stands. Nobody brings records.

AttendeeRole in the meetingMust arrive knowing
Group controllerAnswers blocks one to threeWhich legacy ledgers exist and how far back
CEOAnswers block four and decidesWhich entity holds rights in the finance records
Implementation lead (you)Chairs, keeps time, disclosesThe scope decision date and the subsidiary map

If the officer cannot attend, run blocks one to three and book block four separately. The decision cannot be delegated to the controller.

The 20-minute agenda

Illustrative. A fictional 290-person engineering services group with three entities (a U.S. parent, a UK consultancy subsidiary and a shared-services company that employs the accountants) holds this meeting two weeks before migration scope is signed off.

BlockMinutesAgenda questionWho answersOutput
1. Entity map0-4Which legal entity does each subsidiary represent, and which one employs the finance team?ControllerConfirmed map, one line per entity
2. Adjustment question4-10Can the company identify the entity and approval behind each adjustment, before and after go-live?ControllerYes, partly or no for each period
3. The old books10-15What does the migration plan do with legacy detail, and what dates has the company set?ControllerMove, read-only or retire, with dates
4. Authority and opt-in15-20Who can authorize a licensing discussion, and do they want an introduction?CEOIntroduce or close

Block by block: weak and strong answers

Block 1, entity map (4 minutes). Weak: "It's all one company really." Strong: "Three subsidiaries: the parent, the UK consultancy and shared services. The accountants are employed by shared services, but the books belong to each entity." If names differ between contracts and the ledger, the guide to finding a company's legal entity name settles it later; do not spend meeting time on it.

Block 2, adjustment question (6 minutes). Ask it word for word, then split by period. Weak: "We've always been careful." Strong: "Since go-live, yes: journal approvals are required, so nothing posts without an approver, and each intercompany line shows both subsidiaries. Before that, about forty cross-entity corrections a year over six years, entity named in the memo field, approver only in email." That answer reflects how NetSuite behaves: with approvals required, unapproved journals do not post (Oracle NetSuite), and intercompany lines post to the originating subsidiary or the "To Subsidiary" (Oracle NetSuite).

Block 3, the old books (5 minutes). Weak: "IT will sort out the archive." Strong: "Two years of detail migrates. Older ledgers go read-only when the legacy subscription ends on the date in our renewal notice, and the reconciliation workbooks stay on the finance drive." Record only dates the company itself has set. If nobody knows, write "unknown"; the archive context checklist picks it up from there.

Block 4, authority and opt-in (5 minutes). Disclose first: you are a SourceX referral partner and may receive a reward if a qualifying license completes, paid by SourceX separately and never deducted from what the company receives. CFA Institute's Standard VI(C) sets a useful bar here, asking that the nature and estimated value of a referral benefit be disclosed before any formal agreement (CFA Institute). Then ask. Strong answers are short: "Yes, introduce me" or "Not this year." Both end the block.

What this meeting never covers

Leaving things out is part of the design. Each item below has a better home, or no home at all.

  • Viewing entries. No screen-sharing of journals, memos or emails. Counts and yes-or-no facts only.
  • Valuing the history. Nobody in the room can price it, and guessing creates expectations. Price is settled, if ever, after SourceX reviews the company.
  • Rights conclusions. If someone raises a contract or confidentiality concern, note it as a flag for counsel.
  • Delaying cutover. The rollout timetable does not move for this conversation.
  • Your reward amount. Disclose that a reward may be paid and how it is measured; do not forecast a figure.

The decision note the controller files

The meeting has done its job when this note exists, filed with the migration scope documents.

FieldIllustrative entry
Entities confirmedParent, UK consultancy, shared services
Post-go-live adjustmentsEntity and approver recorded
Pre-go-live adjustmentsAbout 40 a year for 6 years; entity in memo, approver in email
Fate of legacy detailRead-only after subscription end; workbooks retained
Authorized contactCEO, for the entity holding the finance records
DecisionIntroduce to SourceX
Disclosure givenYes, before the opt-in

Before sending any introduction, confirm 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. For a group with a UK subsidiary, that means checking the language of its records. Then sign the Channel Partner Agreement. Whether any records are selected, and on what terms, stays unknown until SourceX reviews the company. Use the introduction email when the decision is yes. Longer agenda formats where a records question also fits include the sell-side kickoff agenda and the portfolio review agenda; fit criteria for implementers are 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.

If block four ends with "introduce me", register as a partner before you send anything, check the group against who qualifies and give the officer a link to the terms.

  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

Can this be folded into a steering committee meeting?

Yes, as a 20-minute item, provided the controller and the CEO of the entity that holds the records are present. Without the second person, stop after block three and reschedule block four.

What if the controller wants to show me examples on screen?

Decline politely. The meeting runs on counts, dates and yes-or-no answers. Seeing entries adds nothing to the decision and puts records in front of someone who has no reason to see them.

Who keeps the decision note?

The controller files it with the migration scope documents. You keep only the outcome: introduce or close, and the name of the authorized contact if the answer is yes.

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. 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