01● Active
VK Dairy Entity A
Independent GSTIN · Separate statutory books
Requirement 01Foundation
Multi-Entity Management
A controlled structure for three legal entities—one user experience for the team, separate statutory records for compliance, and a consolidated view for management.
“VK Dairy operates through three different entities. They would like to understand whether all three entities can be managed through a single Zoho login and/or unified dashboard, while maintaining appropriate entity-wise accounting, reporting, and access controls.”Requirement reproduced from the supplied enquiry document.
One identity.
Three organizations.
One management view.
Configure a separate Zoho Books and Zoho Inventory organization for each legal entity. Invite authorized users with the same corporate email identity, allowing them to switch organizations without maintaining separate credentials.
Use Zoho Analytics as the shared reporting layer. It consolidates approved data from all three organizations while retaining an entity key for filtering, access control and auditability.
Architecture decisionLegal separation is preserved in transaction systems. Consolidation happens in the reporting layer—not by mixing statutory books.
Federated multi-entity model
Each entity remains independently governed while common users and leadership receive a cohesive experience.
VK
ONE CORPORATE IDENTITYAuthorized Zoho Users
02● Active
VK Dairy Entity B
Independent GSTIN · Separate statutory books
03● Active
VK Dairy Entity C
Independent GSTIN · Separate statutory books
A
CONSOLIDATED MANAGEMENT LAYERZoho Analytics
Unified viewCross-entity MIS · Row-level security · Group KPIs
Operating model
Separate transaction organizations
Each legal entity gets its own Books and Inventory organization, GST configuration, document series, banks, ledgers and warehouses.
Shared user identity
The same email can be invited into multiple organizations. The organization switcher simplifies access while permissions stay entity-specific.
Governed common masters
Customers, vendors and items receive an enterprise code plus entity-specific IDs. Ownership rules prevent duplicate records.
Unified management analytics
Analytics combines entity data with entity filters and row-level access. It supports MIS—not statutory ledger consolidation.
Cross-entity executive dashboard
Leadership sees group performance first, then filters or drills into an entity.
EXECUTIVE DASHBOARD
Group overview
₹1.18 CrTotal
- ● Current 62%
- ● 1–30 days 19%
- ● 31+ days 19%
Entity-aware access control
Access is assigned by legal entity, application, role and—where supported—location.
CONCEPTUAL MOCK-UP
Access control matrix
| User role | Entity A | Entity B | Entity C | Analytics scope |
|---|---|---|---|---|
| GrGroup CFO | Admin | Admin | Admin | All entities |
| EnEntity A Accountant | Finance | — | — | Entity A |
| StStores Manager | Inventory | Inventory | View | Assigned locations |
| MaManagement Viewer | View | View | View | Group MIS |
What this fulfills
- One login for authorized users
- Separate entity-wise books and stock
- Entity and group reporting
- Role and location-aware access
- Consolidated management MIS
Important controls
- Subscriptions are normally per organization
- Intercompany flows need matched references
- Common master governance is mandatory
- Analytics does not replace audited consolidation
- Tax structure requires finance sign-off
Approve the federated three-organization model as the foundation for all remaining requirements.
The accounting, inventory, production, delivery and WhatsApp designs will inherit this entity-routing model.