Private equity and portfolios
Closing one subsidiary in a group: separating its records
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Closing a subsidiary cleanly means separating its records before shared systems, contracts and people change: identify what the entity owns, pull its history out of group tenants such as a shared ERP or email domain, name a custodian for retained records, and settle intercompany files. The rule: no shared tenant is pruned until the subsidiary's export is verified.
Key takeaways
- A subsidiary's records usually sit partly in its own subscriptions and partly in group tenants, so separation starts with a map of both.
- Dissolving the entity does not end retention duties; tax, employment and contract records still need a named custodian.
- Intercompany agreements, charges and loans need matching records on both sides before the subsidiary's books close.
- Settle who owns the subsidiary's records before dissolution, because a dissolved entity has limited power to approve later use.
What does separating a subsidiary's records involve?#
Separating a subsidiary's records means deciding, record family by record family, which belong to the closing entity, which the group must keep, and where each will live after the entity is dissolved. The work runs in parallel with the legal wind-down, not after it, because the people who know where things are tend to leave first.
In a software holding group, a small subsidiary rarely runs a fully separate stack. Its general ledger may sit in a multi-subsidiary NetSuite account, its email in the parent's Microsoft 365 or Google Workspace tenant, its tickets in a branded Zendesk instance shared with sister products, and its code in its own GitHub organization. Each of those needs a different separation method.
Ask three questions of every record family: who owns it, who must keep it, and who can approve its use or deletion. The answers drive the checklist below.
Shared group systems: where the subsidiary's history actually sits#
Shared group systems are the hardest part of a subsidiary closure because the subsidiary's records are mixed with records of entities that keep operating. Pruning a shared tenant too early can delete history the group still needs; leaving it untouched can leave a dissolved entity's personal data with no owner and no retention rule.
Oracle's NetSuite help notes that the Full CSV Export does not currently export all data and covers only certain lists, reports and the transaction detail report. A subsidiary extract therefore usually combines saved searches filtered by subsidiary, report exports and transaction detail, checked against what your own account's export actually covers.
| System type | How the subsidiary's records are mixed in | Separation approach |
|---|---|---|
| Multi-subsidiary ERP such as NetSuite | Transactions tagged by subsidiary in one ledger | Saved searches and reports filtered by subsidiary, not only the standard full export |
| Email and file tenant (Microsoft 365, Google Workspace) | Mailboxes and drives of subsidiary staff on the group domain | Export or hold departing mailboxes before licenses are reassigned |
| Shared CRM org | Accounts and opportunities owned by subsidiary users or record types | Filter by owner, record type or business unit; export activities and notes separately |
| Shared helpdesk | A brand or group inside one instance | Export that brand's tickets with comments and attachments |
| Engineering tools (Jira, GitHub) | Separate projects or organizations, sometimes shared | Archive the subsidiary's projects and repositories before seats are removed |
| Payroll and HRIS | Employees of several entities in one system | Keep the subsidiary's employment records under the group retention schedule |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
The subsidiary closure records checklist#
The subsidiary closure records checklist runs in the order that avoids irreversible loss: inventory first, exports and holds second, custody decisions third and deletions last. Give each step an owner in finance, IT or legal, and record completion in the closure file so the board can see what was done.
- Confirm the legal entity, its registered name and every trading name used on contracts, invoices and systems.
- List every system holding the subsidiary's records, including group tenants, its own subscriptions and outside providers such as payroll bureaus, accountants and storage vendors.
- Identify record families: ledger and tax filings, customer and vendor contracts, support history, CRM activity, engineering work, employment files and board minutes.
- Read each vendor contract for cancellation notice, export rights and post-termination deletion before giving notice.
- Export each record family with metadata, attachments and comments, then verify record counts against the source.
- Place holds where claims, audits or disputes are open.
- Name the custodian entity and the person responsible for retained records, and document both in a board or shareholder resolution.
- Settle intercompany balances and keep matching records on both sides.
- Decide with counsel which personal data must be kept, which can be deleted and which notices may apply.
- Only then remove seats, close subscriptions and prune shared tenants.
Intercompany records: what both sides must keep#
Intercompany records are the documents that tie the closing subsidiary to the rest of the group: service agreements, cost allocations, loans, guarantees and IP licenses. They matter after closure because the surviving entities' tax filings, audits and transfer pricing positions still rely on them.
The common mistake is to archive only the parent's side. When the group later needs to support a management fee or show that an intercompany loan was settled, the dissolved entity's signed copy and approval trail are the documents nobody can find.
| Intercompany record | What to keep | Why it matters after closure |
|---|---|---|
| Shared services or management agreement | Signed agreement, allocation method and invoices | Supports the charges in both entities' filings |
| Intercompany loans | Notes, balances, repayments or forgiveness approvals | Shows how balances were cleared before dissolution |
| IP licenses between parent and subsidiary | License, any assignment back and termination notice | Clarifies who owns code, brands and records the subsidiary created |
| Guarantees and credit agreement terms | Guarantee documents and lender correspondence | Lenders may require notice or consent for the closure |
| Transfer pricing files | Studies and supporting calculations | Remain part of the group's tax record |
How long must a dissolved subsidiary's records be kept?#
Retention periods for a dissolved subsidiary's records are set by tax law, employment law, contracts and open claims, and dissolution does not shorten them. The IRS says to keep records supporting income, deductions or credits until the period of limitations for that return runs out, generally three years with longer periods in specific situations, and to keep employment tax records for at least four years after the tax is due or paid, whichever is later.
Records about property, including equipment and other depreciable assets, follow a separate rule: the IRS says to keep them until the limitations period expires for the year the property is disposed of. State law, customer contracts, warranties and insurers can require longer retention, so the schedule is set entity by entity with tax advisers and counsel.
Keep retained records structured where you can. A folder of PDFs may satisfy a narrow retention duty, but an export that keeps tickets linked to accounts and invoices linked to contracts stays usable for audits, disputes and any later decision about the records.
Illustrative: a vertical software group closes a marina software subsidiary#
Illustrative: a fictional vertical software group closes a small subsidiary that sold marina reservation software, after moving its remaining customers to a sister product. The subsidiary's ledger sits in the group's NetSuite account, its staff use the group's Google Workspace domain, its tickets live as one brand in a shared Zendesk instance, and its code and pull requests sit in a separate GitHub organization.
The group CFO's team extracts transactions by subsidiary filter, exports the Zendesk brand with comments and attachments, archives the GitHub organization with issues and review history, and exports departing mailboxes before licenses move. A board resolution names the parent as custodian. Customer contracts are reviewed to see which let records move to the parent and which require notice.
With the records separated and ownership documented, the group can decide later whether to keep, archive, delete or license the support and engineering history, instead of losing that choice when the shared tenants are cleaned up.
Settle ownership before the entity disappears#
Ownership of a closing subsidiary's records should be settled before dissolution, because a dissolved entity has limited capacity to sign new agreements and its officers may be gone. If the group wants the parent to hold, use or license the records later, a transfer of those assets to the parent is typically documented in the wind-down, subject to customer contracts and privacy notices.
SourceX approaches a closing subsidiary's records as it would any supplier's, through the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery. The Rights step asks which entity owns the records now and which contracts limit their use, and the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization. Nothing is shared during the initial assessment.
Frequently asked questions
Can the parent keep a dissolved subsidiary's customer data?
Often, but it depends on the subsidiary's customer contracts, its privacy notices and the laws that applied to the data. Some contracts require return or deletion at termination, and some notices limit use to the original service. Counsel usually reviews these before records move, and the move is documented in the wind-down paperwork.
Who can approve use of the records after dissolution?
Usually not the dissolved subsidiary itself. State law gives a dissolved entity limited powers to wind up its affairs, and those powers vary. Groups therefore tend to transfer records and related rights to the parent or a surviving affiliate before dissolution, so a living entity with clear authority can approve later use.
Should we delete departing employees' mailboxes when we reassign licenses?
Not before an export or hold is in place. Mailboxes often hold the only copies of customer commitments, vendor terms and key decisions. Export them, apply holds for open matters, record where the copies live and who controls them, and delete later under the retention schedule.
Do the subsidiary's SaaS subscriptions need special handling?
Yes. Many vendors delete account data on a fixed schedule after cancellation, and some require notice before renewal. Read each contract's export and deletion terms, export and verify first, and cancel last. Where the data sits in a group subscription, separate it before the group reconfigures that tenant.
Is a closed subsidiary's history worth preserving beyond retention duties?
It can be. Support conversations, engineering work and operating records from a closed product still show how real problems were handled. Whether they can be licensed depends on ownership, customer contracts and privacy preparation, which is why the separation should preserve linked records rather than flatten them into documents.
Sources
- Oracle's NetSuite help says the Full CSV Export does not currently export all data; it covers accounting lists, classes, contacts, customers, departments, employees, items, notes, partners, saved reports you own, tasks, the transaction detail report and vendors. Source
- The IRS says to keep records supporting an item of income, deduction or credit until the period of limitations for that return runs out, generally 3 years, with longer periods in specified situations; employment tax records for at least 4 years after the tax becomes due or is paid, whichever is later; and property records until the limitations period expires for the year the property is disposed of. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.