2026-11-13
Financial Reporting for Divestitures: A Guide

Financial reporting for divestitures is the work of showing two stories at once. One story is the business that is leaving. The other is the business that stays. Deal teams need both before a buyer, a lender, or an auditor will rely on the numbers.
Call (718) 512-9660 if your team is rebuilding those two views from separate ledgers. Or request information and send the entity list. A read-only reporting layer can hold both views without replacing the ledgers.
A sale, a carve-out, and a spin-off do not use the same statements. The Journal of Accountancy describes a divestiture as the disposal of a whole line or subsidiary. It describes a carve-out as a portion pulled out of a larger business. A spin-off is a new legal entity whose shares go to existing owners. Each path asks finance for a different package. The 2020 accounting note also says the first fork is whether the company is disposing of assets or a business under ASC 805 or SEC rules. That archived note can be out of date, so treat it as a map, not a current rulebook.
This guide is for the controller or deal-finance lead who has to produce the package. It is not a classification memo. If the question is whether the disposal is a discontinued operation, start with the separate ASC 205 discontinued-operations reporting guide, then come back here for the operating package around it.
What financial reporting for divestitures has to produce.
Buyers rarely accept the consolidated pack as the whole answer. They want the perimeter of the deal, the history inside that perimeter, and a clear view of what the seller keeps. Finance usually ends up with four work products, even when the legal names differ.
| Work product. | Question it answers. | Who usually relies on it. |
|---|---|---|
| Carve-out or separate statements. | What did this perimeter earn, own, and owe on its own? | Buyer, auditor, and, for some public filings, the SEC. |
| RemainCo statements. | What does the continuing business look like after the data strip? | Board, lenders, and the seller's own close team. |
| Bridge schedules. | How do working capital, net debt, and shared costs get from the ledger to the contract? | Deal counsel and the purchase-agreement team. |
| Source tie-out. | Which entity, account, and transaction supports each line? | Quality-of-earnings reviewers and internal audit. |
BDO describes the seller's continuing statements as RemainCo financial statements. Those statements go through a data strip that removes the divested business, then a review of segments, footnotes, and management reports. The same update can move bank ratios, including a debt-covenant ratio. BDO's divestiture note puts it plainly: no two divestitures are alike, so the statement update has to start before the close calendar gets tight.
Separate statements are not only a buyer request. The Tax Adviser notes that divesting one or more legal entities may require separate financial statements. And that tax expense on those statements needs a systematic, rational allocation consistent with ASC 740. The standard does not prescribe one method. That 2026 tax-reporting article is the right depth for the tax question. This guide only flags that the method has to be chosen, documented, and used the same way in every draft.
Define the perimeter before you build the statements.
Most late surprises start as a fuzzy perimeter. "The Midwest stores" is not a reporting unit until finance can name the legal entities. The shared contracts, and the people who move with the deal. Write that list before the first historical draft.
A practical perimeter file has five columns. Legal entity. In or out. Shared, and with whom. System of record. Owner of the tie-out. If a contract, a lease, or a bank account serves both sides, it does not go silently to one column. It goes in the shared column with a proposed treatment and the person who will defend it.
Public-company sellers have a second test. Regulation S-X Rule 3-05 can require audited financial statements of a business acquired, or probably to be acquired, when its conditions are met. The public text says related businesses may be shown on a combined basis for periods under common control or management. It also says the rule does not apply to a business the registrant already wholly owns before the transaction closes. Read the current text at 17 CFR 210.3-05 with counsel. Do not guess period counts from a blog post.
Private groups still benefit from the same discipline. A family office or sponsor selling one asset out of a stack of entities needs the same named perimeter. Otherwise the historical pack mixes the asset being sold with cousins that are staying. Consolidated financial statements across systems are the starting point, not the deliverable. The deliverable is that consolidation filtered to the perimeter, with every exclusion explained.
Allocate shared costs without inventing a standalone company.
Carve-out statements fail when corporate cost is either dumped in full or waved away. Insurance, the head-office team, software, and a shared treasury function all sit in a parent ledger. The carve-out still has to show a rational charge for what the departing business used.
Pick a base the ledger can support. Headcount, revenue, square footage, or transaction count can all be rational. A base that exists only in a slide is not. Document the base, the periods it covers, and what you will not allocate. One-time parent costs that the buyer will not inherit belong in a bridge, not buried in operating expense.
The Journal of Accountancy's archived note says there are no set FASB rules for formulating carve-out financial statements. That is why the memo matters more than the formula. Reviewers look for a method they can re-perform, not for a universal percentage.
Do the same for cash. A sweep account that zeros every entity into a parent is not the carve-out's cash balance. Rebuild the cash the perimeter controlled, then show the sweep as a related-party or parent claim. Intercompany loans need the same treatment. State the balance, the rate, and whether the agreement survives the sale. If it does not survive, say what replaces it on day one.
Teams that already reconcile affiliates every month are ahead. The allocation memo can point at a tie-out instead of a fresh spreadsheet. Teams that reconcile only at year-end will spend the first weeks of the deal rebuilding history. That is a data problem, not a valuation problem.
Build the working-capital and net-debt bridge.
The purchase agreement rarely uses the general ledger as printed. It uses defined terms for cash, debt, and working capital. Finance's job is a bridge from the ledger to those definitions, with every adjustment named.
Start from a locked trial balance for each entity in the perimeter. Then list adjustments in the order a reviewer will test them. Cash that is trapped. Debt-like items such as unpaid bonuses or deferred revenue the contract treats as debt. Working-capital peg items. Related-party balances that settle at close. Tax items the tax team owns. Each line needs an amount, a source report, and a status: agreed, open, or out of scope.
Keep the quality-of-earnings work beside this bridge, not inside it. A quality of earnings report tests whether earnings repeat. The bridge tests whether the balance sheet matches the contract. Mixing them produces a schedule nobody can foot.
Update the bridge on a calendar, not when someone asks. A weekly pack during exclusivity is enough for most private deals. Daily packs make sense only in the last two weeks, and only if the source ledgers can refresh that fast. A pack built from last month's export will lose the room the first time the buyer reruns cash.
Restate what the seller keeps.
RemainCo reporting is the half teams postpone. The data strip is not "delete a column." Shared vendors, shared employees. And allocations that used to net inside the group all change meaning once the counterparty is gone.
BDO's checklist is the right order. Strip the divested activity from the historical statements. Revisit segments if internal reporting will change. Rewrite footnotes that described the group as it was. Then rerun the ratios lenders actually test. A covenant written on consolidated EBITDA can look fine in the old pack and tight in the continuing pack.
Management reports need the same strip. A dashboard that still includes the sold entities will send the operating team the wrong run-rate. Label pre-disposal and post-disposal views in the title, not in a footnote. People forward the page, not the footnote.
If the disposal meets the discontinued-operations tests, presentation changes again. Both the operating results and the gain or loss on disposal are presented when ASC 205-20-45 applies. The tests themselves live in the ASC 205 guide linked above. Do not run them from memory in the middle of a data pull.
Tax follows the structure. Held-for-sale classification can create deferred tax assets or liabilities when book and tax bases differ. The Tax Adviser piece is explicit that the accounting follows the deal facts. Put a tax reviewer on the RemainCo draft before it circulates, not after the board book is locked.
How multi-entity teams keep the package current.
Divestiture reporting breaks when each entity lives in a different file and the mapping lives in one person's workbook. The deal does not create that problem. It exposes it. A sponsor with portfolio companies on different ledgers, or an operator with a stack of property and operating entities, already knows the pattern.
The fix is a reporting layer that reads the general ledger and does not replace it. Why Helix describes Helix Reports as a read-only reporting layer for teams that work across many entities, many ledgers, acquisitions, and migrations. Source systems named there include Yardi, Sage, MRI, AppFolio, and QuickBooks. The import is read-only. Helix does not write back to those ledgers, and it is not an ERP or a fund administrator.
That boundary matters in a sale. The carve-out pack should tie to the same transactions the close uses. A normalized view can sit beside the source view, with drill-down from a reported line to the entry that supports it. Intercompany pairs can be investigated without waiting for a year-end workbook. None of that classifies the disposal, calculates tax, or signs the audit. Those judgments stay with the finance team and its advisors.
How Helix Reports works is the short version of the operating cycle: connect the ledgers, normalize accounts, reconcile, and refresh the reports. For a divestiture, the same cycle feeds the perimeter file. You filter to the entities in the deal, keep the entities that stay in a separate view, and stop rebuilding both from exports. Scope and pricing sit on the pricing page, not in a blog estimate.
Sponsors who will still report the companies they keep can use the same layer after close. Private equity portfolio reporting covers that ongoing need. It is a different question from the sale package, so keep the two packs labeled apart.
Run the reporting work on a close calendar.
A useful sequence is short enough to put on one page. The point is to freeze definitions before the data room fills up with competing versions.
- Name the perimeter, the shared items, and the tie-out owner for each entity.
- Lock the historical periods and the ledger each period comes from.
- Write the allocation memo for shared costs, cash sweeps, and intercompany balances.
- Draft carve-out statements and RemainCo statements from the same locked data.
- Build the working-capital and net-debt bridge to the contract definitions.
- Route tax, covenant, and disclosure questions to the people who own them.
- Refresh on a set calendar and retire every prior version.
Version control is part of the control, not a courtesy. Date the file, name the ledger cutoff, and say which bridge lines are still open. A buyer who receives three "final" packs will not trust the fourth.
Call (718) 512-9660 if you want to talk through whether a read-only reporting layer fits the entities in the deal. You can also request information and describe the systems and the perimeter. Helix will not replace your auditor or your deal counsel. It can stop the package from depending on a single workbook.
Frequently Asked Questions.
What is financial reporting for divestitures?
It is the set of statements and bridges that show the business being sold and the business that remains. The usual pieces are carve-out or separate statements, RemainCo statements, a working-capital and net-debt bridge, and a tie-out to source transactions.
How is a carve-out different from a spin-off?
A carve-out pulls a portion of a business out of a larger subsidiary or line. A spin-off moves that business into a new legal entity and distributes the new shares to existing owners, who keep their shares in the original company. The statements follow the path you actually chose.
Do public companies need special historical financials?
Sometimes. Regulation S-X Rule 3-05 can require audited financial statements of a business acquired or probably to be acquired. Whether it applies, and for which periods, is a filing question for counsel. Private deals often ask for a similar history even when the rule does not.
Where should discontinued-operations accounting sit?
In its own workpaper, owned by technical accounting. Use the ASC 205 guide for the classification, presentation, and disclosure questions. Keep this package focused on the perimeter, the allocations, and the bridge.
Can reporting software prepare the divestiture statements?
It can keep the ledgers, the mappings, and the refreshes in one place. It should not make the GAAP call, the tax allocation, or the contract definition. Those stay with the finance team and its advisors. A read-only layer is useful because the pack still ties back to the source entry.