Finance setup for launching a new subsidiary: separate books?

In most cases, a new subsidiary should keep its own books from its first transaction. Finance setup for launching a new subsidiary works best when the legal entity, bank accounts, chart of accounts, and reporting calendar are settled before money moves. Then you can show a lender or investor a clear trail, one step at a time.

Why a subsidiary usually needs its own books

A subsidiary is usually a separate legal entity. It has its own name, its own contracts, and in many cases its own owners, managers, and tax filings. Those facts shape the bookkeeping. If the new company runs through the parent's accounts, its sales, bills, and payroll blend into the parent's records, and nobody can say later what the subsidiary earned or owed. Separate books exist to prevent that blending, not to add paperwork.

Consider a hypothetical software company that wants to open a services subsidiary to handle implementation projects for hospitals. The parent sells subscriptions and keeps a clean general ledger. The new services line will bill different customers, carry different staff costs, and need its own margin story. If both lines share one set of books, a lender reading the statements sees one blended number that answers none of its questions about the new line.

Separate books also support the reasons people create subsidiaries in the first place. Liability is often the first one: a contract problem in one entity should not spill into the other, but only if each entity keeps records that show where obligations sit. Each entity may also need its own federal employer identification number from the Internal Revenue Service, who is a outsourced CFO in Massachusetts and each may file its own returns. Tax treatment depends on the entity type you choose, so ask a tax adviser before you decide how the books should be split.

Separate books are not the same as separate thinking. The parent and the subsidiary still work together, share staff, and often pay for things on each other's behalf. The accounting job is to record those shared activities in a way that keeps each entity's results visible. A subsidiary with its own ledger but no clear rules for shared costs can look just as confusing as one with no ledger at all.

Later, when the parent controls the subsidiary, it usually reports the combined results in its own financial statements. This process is called consolidation, and the guidance sits in US GAAP, including ASC 810. You do not need to master that standard before you open a bank account, but your choices now make consolidation easier or harder. Clean subsidiary books are the raw material for that work.

A simple test helps at this stage. Imagine an outside reviewer asks for the subsidiary's books alone. Could you produce a list of accounts, a full set of transactions, and supporting documents without rebuilding anything from the parent's records? If the answer is no, the setup needs more work before the first transaction posts. That is a useful finding, not a failure.

Deciding the legal and ownership structure first

Before you open any account, decide what kind of entity the subsidiary will be and who owns it. The answer changes which books you need, how they connect to the parent, and what a future lender will ask to see. A corporation, a limited liability company, and a branch of the parent each carry different filings and different ownership rules. Your attorney and accountant should confirm the details for your state, because registration and reporting requirements vary.

Ownership matters as much as the entity type. If the parent owns all of the subsidiary, control is straightforward. If outside investors, partners, or a manager hold a share, the subsidiary's records need to show each owner's stake, and any distribution must follow the operating agreement or bylaws. Mixing those distributions with the parent's cash is a common early mistake, and it is hard to undo later.

Write down the purpose of the subsidiary in one short paragraph before you finalize anything. Name the product, the customers, and the reason the work sits in a separate entity. That paragraph becomes the test for later decisions. If a cost does not serve that purpose, it probably belongs in the parent. If a cost clearly serves it, it belongs in the subsidiary, even when the parent pays first.

Plan the reporting relationship early too. Will the subsidiary's finance lead report to the parent's finance lead, to the subsidiary's own managers, or to both? The answer drives who approves payments, who signs off on the month-end close, and who receives the financial statements. A subsidiary without a named reviewer tends to drift, because everyone assumes someone else is watching the numbers.

Use a short checklist to keep this step concrete:

1. Entity type and state of formation, confirmed with counsel. The choice affects filings, owner rights, and the books you keep.


2. Ownership percentages and investor rights, written in the governing documents. Your records should match these documents exactly.


3. A purpose statement that explains why the work sits in a separate entity. Use it to judge later costs.


4. A named person who approves payments and reviews the monthly close. Without one, review tends to slip.

Each item is simple on its own. The value comes from answering all four before the bank account opens, because the bank, the accounting system, and the parent's chart of accounts all depend on these answers.

Opening the bank accounts and payment flows

Each legal entity should have its own bank accounts. The subsidiary needs them to receive customer payments, pay vendors, and run payroll in its own name. Opening those accounts usually requires the entity's formation documents and the federal employer identification number. The bank will also ask who may sign, so decide that list with the same care you gave the ownership structure.

Shared accounts create the most confusion. Imagine the parent's operating account pays a subsidiary vendor bill this month, and the subsidiary's customer payment lands in the parent's account the next week. Neither transaction is wrong in itself. But the subsidiary's bank reconciliation now needs extra entries to explain where the cash went, and the work grows each time it happens. A simple rule helps: the subsidiary's bills get paid from the subsidiary's account, and any exception gets recorded as an intercompany transfer on the same day.

Payment flows also need a written policy. Who can release a wire? Who approves a card expense? What happens when an employee charges a subsidiary cost to a personal card? Write one page that answers those questions. It does not need to be elaborate, but everyone who spends money for the subsidiary must follow it, including founders who are used to paying for things personally.

Think about cash timing too. The subsidiary may spend for a while before customer payments arrive. The parent may cover that gap through a loan, an equity contribution, or a capital transfer, and each choice is recorded differently. A loan creates a repayment schedule and possibly interest. An equity contribution changes ownership records. A capital transfer may be a one-time event. Choose one method with your accountant before the money moves, not after.

Finally, set a reconciliation schedule. Bank reconciliations should happen regularly, usually at least monthly, and the person doing them should not be the same person approving payments. That separation is one of the simplest internal controls available to a small team, and it matters even more when two entities share a finance function.

Building a chart of accounts the parent can roll up

The chart of accounts is the list of categories every transaction goes into. For a subsidiary, the chart should look familiar to the parent but still reflect the subsidiary's own business. If the parent calls its service revenue "Professional Services Income" and the subsidiary calls it "Implementation Fees," the two will not add up cleanly. Pick one naming scheme and use it everywhere.

A practical approach is to start from the parent's structure and add accounts only when the subsidiary has a real need for them. Copying every account from the parent creates clutter. Starting from scratch creates mismatches. Most teams find that a middle path works best: a shared set of top-level categories, plus a few accounts that fit the subsidiary's own activity.

Numbering matters more than people expect. Consistent account numbers let a consolidation step map accounts by number instead of by guesswork. A common pattern reserves number ranges for assets, liabilities, equity, revenue, and expenses, and keeps the same ranges in the subsidiary. The exact scheme is a decision for your team and your software, but once you pick it, avoid changing it casually.

Classes, departments, or locations can help with reporting, but they do not replace a clean chart. Some teams run the subsidiary as a tag inside the parent's chart, which can work for internal management reports. It is less reliable for formal statements or for a lender who wants to see the subsidiary as its own entity. Ask which report each tool will produce for the subsidiary alone before you commit.

Write a short account dictionary, one line per account. Each line says what belongs in the account, what does not, and who is responsible for it. Here is a sample for the hypothetical subsidiary:

• Implementation revenue: fees billed to hospital customers for approved project phases only.


• Contract labor: outside consultants paid for subsidiary projects, with a signed statement of work on file.


• Intercompany payable: amounts the subsidiary owes the parent, cleared each month.

A dictionary like this sounds like extra work, but it saves time during the first close, when every unclear account turns into a question. It also gives a future reviewer a clear picture of what each line means without a long explanation.

Recording intercompany transactions and shared costs

An intercompany transaction is any deal between the parent and the subsidiary. Common examples include a loan from the parent, a management fee for shared services, a software license the parent pays for everyone, or a transfer of inventory. Each one needs a record on both sides, with the same amount, the same date, and a description both entities understand. When the two sides disagree, the combined numbers will not balance, and someone has to find the error by hand.

Loans and capital from the parent

A loan from the parent should have a written agreement that sets the amount, the interest rate if any, and the repayment terms. Without a document, the subsidiary may carry a balance that nobody can explain. An equity contribution is different. It usually changes ownership records rather than creating a debt. Mixing the two in the books is a frequent source of confusion during a funding review.

Shared costs and allocations

When the parent pays for shared services such as payroll, software, Boston or insurance, decide how to split the cost. A simple method uses headcount, revenue, or direct usage. Whatever method you choose, write it down, apply it the same way each month, and review it when the business changes. A method that made sense at launch may not fit a year later, once the subsidiary has grown.

Allocations should be reasonable and explainable. A lender does not expect perfect precision, but it does expect a logical method applied consistently. If you change the method, document the change and the reason, so that comparisons across periods stay fair.

Management fees need the same care. If the parent charges the subsidiary for leadership, systems, or support, the fee should match a real service and a stated rate or formula. Tax rules may limit how these fees are treated, so confirm the approach with your tax adviser before you set the rate.

Clear intercompany balances on a regular schedule, usually at each month end. Keep a schedule that lists each balance, the counterpart entity, the supporting document, and the date it cleared. This schedule is one of the first things a reviewer will ask for when they want to know whether the two sets of books tell the same story.

A final habit helps. Before you post a shared expense, ask which entity actually received the benefit. The answer is not always obvious, but a short note on the invoice, such as "supports subsidiary implementation work," turns a vague bill into a clear record.

Choosing accounting software for more than one entity

Software will not fix an unclear setup, but the wrong tool can make a clear setup hard to maintain. Several platforms handle more than one legal entity, and each represents subsidiaries differently. Before you choose, list the reports you need, the number of entities you expect, and the people Who is a outsourced CFO in Massachusetts will enter and review transactions. That list matters more than any feature comparison.

The table is a starting point, not a verdict. Vendors change product tiers and features, so confirm details directly with each provider and with your accounting advisor. Ask for a demonstration that uses your own chart of accounts and a sample intercompany transaction. A demo built by the vendor rarely shows the messy parts that matter most to you.

Think about who will use the system every day. A small team with one bookkeeper may prefer a simpler setup, even if it limits some reporting. A larger team with several reviewers may need permissions by entity, audit trails, and approval workflows. Matching the tool to the people who run it matters more than matching it to a list of features.

Plan the migration before you go live. Decide which opening balances move into the subsidiary's books, as of which date, and who checks them. If the subsidiary starts fresh, keep the parent's historical data where it is. A clean cutover date and a written opening balance memo prevent months of cleanup later.

Export formats also matter. You may need to share subsidiary statements with a bank, an investor, or an outside accountant. Check how each system exports the trial balance, general ledger detail, and reconciliations, and whether those files open cleanly in the tools your partners use.

One more point: avoid building a system that only one person understands. Document how entries are posted, how intercompany schedules are kept, and how the monthly close runs. If the system is designed well, a new team member should be able to follow the notes and produce the same reports without guessing.

Setting controls, approvals, and the reporting calendar

Controls are the rules that keep the books trustworthy when many people touch them. For a new subsidiary, controls often start small: one person prepares entries, another reviews them, and large payments need a second approval. These steps feel heavy at first, but they become the evidence a lender or investor looks for when testing whether the numbers hold up.

Internal controls that fit a small team

Separate duties wherever you can. The person who enters bills should not also approve payments, and the person who reconciles the bank should not also record cash receipts. When the team is too small to separate every duty, add a compensating step, such as a monthly review of a sample of transactions by the parent's finance lead.

1. Written approval limits for payments, with a higher level of approval needed above each threshold.


2. A monthly bank reconciliation reviewed by someone outside the preparation process.


3. A supporting document for every entry, stored with the transaction record.


4. Access rights that match each person's role in each entity.

Some teams borrow documentation habits from quality management standards such as ISO 9001, which emphasize written procedures and records. You do not need certification to benefit from that discipline. A short procedure manual for the close, the approval workflow, and the intercompany schedule gives the team something to follow and gives reviewers something to test.

A reporting calendar the team can keep

Set a calendar with clear dates for each recurring task: bank reconciliations, intercompany clearing, accrual entries, the monthly close, and management reports. Assign one owner per task. A calendar with no owners is only a wish list, and it fails the first month someone is traveling.

Decide which reports the subsidiary produces each month. Most teams want, at a minimum, a balance sheet, an income statement, a cash summary, and a schedule of intercompany balances. Add a forecast or budget comparison once the subsidiary has enough history to make the comparison meaningful. Early forecasts are often rough, and that is fine if they are labeled as estimates.

Review the calendar after the first few closes. Note which tasks ran late and why. Adjust the due dates, the owners, or the level of detail, so the calendar reflects how the team actually works rather than how you hoped it would work.

A trace test that shows whether the subsidiary's books stand on their own

Financing decisions depend on much more than bookkeeping, including the business plan, the market, the collateral, and the terms each funder offers. A clean setup does not guarantee that a loan or investment will close. What it does is remove one avoidable source of doubt, so the conversation can focus on the business itself. Keep that limit in mind as you read the test below.

The criterion is a trace test. Pick one recent month and ask whether you can trace every dollar that moved through the subsidiary to its own records. Start with the bank balance on the last day of the month. Then follow each deposit and payment to an invoice, a bill, a payroll run, or a documented transfer. If any item leads to a shared account with no explanation, the setup is not yet ready for an outside review.

Run the test on three areas: cash, intercompany balances, and reporting. For cash, the bank reconciliation should tie to the ledger without unexplained differences. For intercompany balances, the schedule should match the counterpart's records and show when each balance cleared. For reporting, the statements should come from the subsidiary's own ledger, not from a manual adjustment made the night before a meeting.

Ask a second question: could a different person on your team run the same test and reach the same result? If the answer depends on one person's memory, the process is fragile. Notes, documents, and a consistent chart of accounts make the test repeatable, and repeatable records are what a careful reviewer expects.

Also, write down what the test does not cover. It does not check the subsidiary's pricing, its market demand, or the tax position of your chosen structure. Those questions still need the right advisers. If the trace test passes, you have a stronger foundation for the next conversation. If it fails, you have a specific list of gaps to fix, one step at a time.