Multiple Business Units Without Five Bank Accounts

A design studio, a product line, a consulting arm — the moment a small business runs more than one of these under the same roof, someone asks the obvious question: how do we keep each one's money separate? The default answer is usually a new bank account per unit, and it works, right up until it doesn't.

Why a bank account per unit seems like the obvious fix

It's the most literal way to guarantee separation — money in account A can't accidentally get counted as account B's revenue, because they're physically different accounts. For a business with two units and a founder who checks both statements personally, this is genuinely fine. The problem shows up as the number of units grows, or as more people need to actually work with the money.

Every new account is another login, another set of statements to reconcile, another place a transfer between units has to be manually recorded on both sides. A payment that should be shared across two units — a joint marketing spend, an office lease split by headcount — has nowhere clean to live. It either gets recorded once and manually apportioned in a spreadsheet, or paid from one account and "settled" with an internal transfer that itself needs tracking. The separation you wanted becomes its own bookkeeping job.

What you actually need is separate balances, not separate accounts

The thing that has to stay separate is the number — how much belongs to which unit — not the physical bank account the money sits in. A single shared account can hold several honest, independent balances at once, as long as every transaction that touches it is tagged to the unit it belongs to the moment it happens. Read one unit's balance on its own, or roll every unit up into one company-wide number — same underlying money, two different views of it.

This isn't a workaround for not having enough bank accounts. It's usually the more accurate model: a joint expense really is one transaction split two ways, not two separate transactions that happen to add up to the same total. Tagging captures that reality; a second bank account forces you to pretend it isn't one transaction at all.

Where this actually breaks down

Tagging only works if it happens at the moment of entry, by whoever's entering the transaction — if "which unit does this belong to" is a question answered later, from memory, the split degrades into a guess within a few months. It also needs the underlying software to actually support it. A lot of accounting tools treat "which entity" as a top-level setting you pick once when you sign up, not a field you can attach to every line — bolting multi-unit support onto a single-entity product usually means paying for a much higher tier, if it's possible at all.

What good tagging actually looks like

1. Every invoice, bill and bank line gets tagged to a unit at the point it's created — not reconciled after the fact.
2. A genuinely shared expense gets split by percentage at entry, not recorded once and apportioned later in a separate sheet.
3. Anyone who only needs to see one unit's numbers can be limited to exactly that — they shouldn't need company-wide access just to do their job.
4. The company-wide roll-up and the single-unit view come from the same data, so they can never quietly drift apart.

The honest tradeoff

Separate bank accounts still have one real advantage: a bank statement is an external, unarguable source of truth for that unit's cash, and nobody inside the company can misconfigure a tag and quietly break it. Shared-account tagging trades that for flexibility — accurate joint expenses, one set of logins, roll-ups that update themselves — at the cost of needing the tagging discipline (or the software) to actually hold up. For most small businesses running two or three units with people who wear multiple hats, that trade is worth it. For a business that's really several fully independent companies sharing a name, separate accounts are still the more defensible default.