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.
| Attendee | Role in the meeting | Must arrive knowing |
|---|---|---|
| Group controller | Answers blocks one to three | Which legacy ledgers exist and how far back |
| CEO | Answers block four and decides | Which entity holds rights in the finance records |
| Implementation lead (you) | Chairs, keeps time, discloses | The 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.
| Block | Minutes | Agenda question | Who answers | Output |
|---|---|---|---|---|
| 1. Entity map | 0-4 | Which legal entity does each subsidiary represent, and which one employs the finance team? | Controller | Confirmed map, one line per entity |
| 2. Adjustment question | 4-10 | Can the company identify the entity and approval behind each adjustment, before and after go-live? | Controller | Yes, partly or no for each period |
| 3. The old books | 10-15 | What does the migration plan do with legacy detail, and what dates has the company set? | Controller | Move, read-only or retire, with dates |
| 4. Authority and opt-in | 15-20 | Who can authorize a licensing discussion, and do they want an introduction? | CEO | Introduce 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.
| Field | Illustrative entry |
|---|---|
| Entities confirmed | Parent, UK consultancy, shared services |
| Post-go-live adjustments | Entity and approver recorded |
| Pre-go-live adjustments | About 40 a year for 6 years; entity in memo, approver in email |
| Fate of legacy detail | Read-only after subscription end; workbooks retained |
| Authorized contact | CEO, for the entity holding the finance records |
| Decision | Introduce to SourceX |
| Disclosure given | Yes, 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.