It supports the guide on which entity owns the data in a multi-entity group. The rollout playbook explains why this history matters; the checklist is the working document.
How to use the checklist
Fill it in with the controller, a line at a time, in the steering meetings you already hold. Every answer is a name, a date, a count or a yes or no. Nothing on it requires opening a journal, memo or email, and nothing on it should be copied out of the company's systems.
Illustrative. The worked entries come from a fictional 330-person dental laboratory group with five entities: four regional labs and a holding company that owns the equipment and employs the finance team.
Window 1: before the rollout is announced to the entities
At this point the legacy finance staff in each entity do not yet know their books are moving. It is the cheapest moment to record who did what.
| Confirm | Owner | If skipped | Illustrative entry |
|---|---|---|---|
| Which person approved cross-entity corrections in each legacy ledger | Group controller | Approver names leave with the people | Two regional accountants and the group controller |
| Where explanations for corrections were kept | Group controller | Reasons survive only in inboxes | Memo field in two labs, email in three |
| First year of usable detail in each ledger | Each entity's bookkeeper | Nobody can say how much history exists | 2017 for three labs, 2020 for two |
| Which entity employs the people who made the corrections | HR or controller | Wrong entity is asked to authorize later | Holding company |
Window 2: before cutover weekend
Migration scope is now fixed or nearly so. The question shifts from who knew to what moves.
| Confirm | Owner | If skipped | Illustrative entry |
|---|---|---|---|
| Whether detailed history migrates or only balances | Implementation lead and controller | Pre-rollout corrections exist only in the old system | Two years of detail; earlier years balances only |
| Whether journal approvals are switched on from day one | Controller | New entries also lack an approver | Required for all intercompany journals |
| Whether the new account will use System Notes v2 | NetSuite administrator | The changing user's role, and notes on deleted records, are not kept | Enabled |
| A reference list mapping each legacy ledger to its new subsidiary | Controller | Old corrections cannot be tied to the right entity | Five rows, one per entity |
Why the second and third rows matter: with approvals required, an unapproved journal does not post (Oracle NetSuite), and System Notes v2 records the user's role and keeps information about deleted records, which classic system notes do not (Oracle NetSuite). Both settings decide whether future corrections carry the entity and approver without anyone having to remember.
Window 3: before the legacy books go dark
The old subscriptions or servers have an end date. After it, read-only access may lapse and files may be deleted.
| Confirm | Owner | If skipped | Illustrative entry |
|---|---|---|---|
| The date access ends, as stated in the legacy contract or renewal notice | Controller | The deadline is guessed, or missed | Stated in the renewal notice; not assumed |
| A complete company-held export of each legacy ledger | IT lead | History disappears with the subscription | Exported and verified by IT |
| Reconciliation workbooks retained alongside the export | Group controller | Reasons for corrections are separated from the entries | Kept in the finance archive |
| Who holds credentials for the archive after go-live | IT lead | Nobody can open the export later | Role recorded, not the credentials |
| Decision on whether to explore a licensing review | CEO | The topic drifts without an answer | Explore after go-live |
If several small-business ledgers are being merged, the page on consolidating multiple QuickBooks companies covers the per-file questions; groups on another mid-market ledger can compare with Sage Intacct data for AI.
Dates only the company can supply
The checklist deliberately has no default deadlines. Every date on it must trace to a document the company holds: a renewal notice, a cutover plan, a decommissioning ticket. If a date cannot be traced, write "unknown" and move on. Inventing urgency to speed a decision would damage the trust the introduction depends on, and SourceX's own review does not run to the rollout's timetable.
Two dates usually matter most: the end of legacy access and the migration scope sign-off. The first decides whether history survives at all; the second decides whether it survives inside NetSuite or only in an export.
What the finished checklist tells you, and what it does not
A completed checklist answers the qualifying question at metadata level: for which years the company can identify the entity and approval behind each adjustment, where those records sit and who owns them. It also names the entity whose CEO would authorize a licensing discussion; where systems are shared across entities, see who owns data in a shared group system and the guide to finding a company's legal entity name.
It does not tell you whether SourceX would select any of it, what the rights review would find, or what any payout or reward would be. Before introducing anyone, check the baseline (50+ full-time employees at peak, contractors excluded; documented operating history; rights to license; 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. Then sign the Channel Partner Agreement. If the officer wants to proceed, use the meeting agenda to confirm the decision.
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.
When Window 3 ends with an officer choosing to explore a review, register as a partner, confirm the group against who qualifies and share the terms with that officer.