Real multi-company: what to ask if you have more than one entity
Almost every system claims to support multiple companies. The gap between saying it and doing it shows up in four specific questions.
Two very different things with the same name
«Multi-company» means two completely different things depending on who says it:
- Several separate installations. Each company its own database, login and configuration. It works, but every change is made as many times as you have companies, and consolidating means a spreadsheet.
- A system that understands there are several companies. Data separated where it must be, shared where it makes sense, and one place to work.
The second is considerably harder to build, which is why the first gets sold under the same name.
The four questions that tell them apart
- Is a customer who buys from two of my companies stored twice? If they have to be created in each one, every correction has to be made twice, and one copy with a wrong tax ID is enough for those invoices to go out wrong.
- Can I switch company without logging in again? It looks like convenience and it's more than that: it tells you whether the system understands the concept or whether these are disguised installations.
- Are permissions per company? Someone may need to see everything in one and nothing in another. If permissions are global, they either see everything or nothing.
- Can I consolidate without exporting? See the whole without building a separate sheet every month.
And a fifth, the one that really matters: ask to see any screen — a customer list, a sales report — with two companies loaded. If anything from the other company shows up, even a name in a dropdown, that's a leak. In a system built properly it never happens.
What's shared and what isn't
The right line isn't «everything separate». There are things where sharing is the sensible answer:
- Shared: the customer and supplier catalogue with their tax ID — a tax number doesn't change depending on which of your companies is invoicing — plus countries and currencies.
- NEVER shared: the accounting, document numbering, balances, inventory, payroll, permissions and any operational data.
Getting that line wrong in either direction causes problems: over-sharing is a leak; over-separating forces you to maintain the same data in several places, and then they diverge.