Plenty of Indian businesses that look like one company from the outside are really several. A trading company and a services company run by the same founders. A Karnataka entity and an Uttar Pradesh entity, each with its own GSTIN. An older company kept alive for existing contracts next to a newer one that takes all fresh business. The people overlap, the customers often overlap, and the owners want one picture of the whole group. The tax authorities, the auditors and the customers' accounts teams want each company kept strictly apart.
Software for this kind of group has to do both at once. Here is how we think about the design, and where the trade-offs really are.
Why separate logins and separate software break down
The usual first answer is to give each company its own tool, or its own login to the same tool. It works for a few months and then wears down in predictable ways.
People end up with several identities. The finance lead who approves bills for three companies now has three usernames and three passwords, and three sets of notifications to watch. Sooner or later someone shares a login "just for this month", and every audit trail you have stops meaning anything.
Master data drifts. The same customer gets entered in each system with slightly different spellings, addresses and contact people. When the customer calls, nobody can see the full relationship across the group.
Group reporting becomes a spreadsheet job. If every company lives in a separate product, the only consolidated view is the one someone builds by exporting from each and pasting the results together. It is late, it is manual, and it quietly disagrees with the source systems.
The opposite mistake is just as bad. Putting every company into one undivided workspace fixes the logins and breaks everything else. Invoices from two GSTINs share one number series, letterheads print the wrong registered address, and a salesperson in one company can browse the other company's pipeline because nothing tells the system that the two are different.
The goal is one platform with real walls inside it, where the walls are decided by design rather than by which login someone happened to use.
What isolation should actually mean
"Keep the companies separate" is vague until you list what has to be separate. In practice there are four layers.
Data. Customers, deals, tickets, invoices, purchase orders, stock and documents belong to one organisation. In DexVee every organisation-owned record carries its organisation, and the active workspace is applied to every read and write in the data layer itself, not left to each screen to remember. A new type of record cannot quietly skip this: the backend checks at startup that every organisation-owned data type is covered, and refuses to start if one is not. We think that last property matters most. Isolation that depends on every developer remembering a filter will eventually fail. Isolation that fails closed is the only kind worth having.
Numbering series. Each workspace keeps its own document counters, so one organisation's invoice and order numbers never use up another's. Inside a single workspace, a legal entity can opt into its own invoice and bill prefix, so two companies under one roof can each issue a clean, continuous series that their auditors will recognise.
Letterheads and branches. A document has to print the details of the company and branch that actually issued it: the right registered address and the right GSTIN. In DexVee each legal entity holds its own tax registration, currency and branches, and each branch holds its own GSTIN and GST return frequency. Estimates, sales orders, proforma invoices and invoices print the issuing branch's letterhead details, worked out by the same rule that decides the tax split, so the letterhead and the CGST/SGST-or-IGST treatment always agree.
Roles. Access is granted per organisation. A person's membership in each workspace carries its own workspace role (owner, admin, member or viewer), and being an admin in one company gives no rights in another. An organisation can also limit sign-in to its own authorised email domains, so an address outside those domains cannot be used to sign in to it.
Settings belong to the workspace as well. Tags and settings made in one organisation stay in that organisation.
Two shapes: separate workspaces, or entities inside one
Groups tend to fit one of two shapes, and the right one depends on what the companies share.
Several legal entities inside one workspace. This suits companies that sell to the same customers, under one management team, from shared staff. Each legal entity has its own tax registration, branches and optional number prefix, and entities can be arranged into business groups. Customers and contacts are shared, so the full relationship stays visible. To stop documents from crossing over, DexVee routes each transaction to an entity: an explicit choice wins, a document created from another (an invoice from a sales order, say) inherits its parent's entity, and a fresh document falls back to the default entity for the customer's country. That inheritance rule is what keeps one entity's estimate from becoming another entity's invoice halfway through the chain.
Separate workspaces. This suits companies that must not see each other at all: different customers, different staff, perhaps different owners in future. Each workspace is a fully separate organisation with its own data, settings, numbering and members. People who work across companies hold a membership in each and switch between them.
Many groups use both: a separate workspace for the business that has to stand alone, and several entities inside the main workspace for companies that really operate as one.
Switching between workspaces
The switching experience decides whether people respect the walls or start working around them.
In DexVee you sign in once. If you belong to more than one organisation, a workspace picker lists each one with your role and plan. If you belong to only one, the picker is skipped and you go straight to your dashboard. Choosing a workspace starts a new session scoped to that organisation alone. It is not a filter on a shared view. You can only switch into organisations you are a member of, and an inactive organisation cannot be entered. From inside the app, the Organisation page offers a "Switch workspace" link whenever you have more than one.
Two design choices are behind this. First, one identity per person, so audit trails always point to a real human however many companies they serve. Second, one active organisation per session, so nobody is ever unsure which company's data is on screen or which company a new record will be saved to.
Consolidated or separate reporting
Owners nearly always ask for "one dashboard for the group". It is worth being precise about what that means.
Within one workspace, consolidate by entity. DexVee's Organisation Roll-up, available to admins, shows each legal entity and its branches with revenue collected and open pipeline against each one. Revenue counts what has actually been received, not just what was billed. Totals are grouped by currency and never added across currencies, because an INR entity and an SGD entity summed together give a number that means nothing. Where a figure can only be traced to the entity and not to a specific branch, the branch is shown without a number instead of a made-up split.
Across separate workspaces, keep reporting separate. If two companies are isolated strongly enough to need separate workspaces, a report that blends their data would undo that isolation. Their reports stay inside their own walls. A group that needs a combined board pack across fully separate organisations is better served by exporting each company's figures than by giving one login a view into all of them.
The useful question is not "can we consolidate?" but "who should be able to see the consolidated number?". Within a workspace, that is the admins. Across workspaces, by design, it is nobody inside the platform.
The trade-offs
No structure is free, and it is better to choose with the costs in view.
- Entities in one workspace give you shared customers, one login and entity-level roll-up. The cost is that everyone in the workspace sits inside one wall. Row-level permissions still apply, but the companies are not hidden from each other in the way separate workspaces are.
- Separate workspaces give you the strongest separation and a clean exit if one company is later sold or spun off. The cost is duplicated master data where customers overlap, separate setup for each company, and no cross-company reporting inside the platform.
- Moving later is real work. Splitting one workspace into two, or merging two into one, means moving records, numbering and history. It is worth getting the shape roughly right at the start, even if the details change.
A simple test helps: if one of these companies were sold tomorrow, would its data need to leave cleanly? If yes, give it its own workspace. If the companies are really one business with several registrations, keep them as entities together.
Where this lives in DexVee
Legal entities, branches, entity routing and the Organisation Roll-up are part of DexVee's finance and billing and analytics and reporting tooling. Multi-organisation workspaces, where one person moves between several fully separate organisations, are part of the Enterprise offering, priced to your requirements alongside custom integrations and dedicated onboarding. See pricing for what each plan includes, or contact us to talk through the shape that fits your group.