Versa Cloud ERP gives each operating entity its own accounting and transaction context inside the same firm. Administrators assign the entities a user may work with, select a default entity and grant the permissions required for that person's role. Daily documents and accounting activity then carry the applicable entity, while authorized finance users can use separate consolidated reporting across included entities.
This matters because multi-entity work has two different requirements. Teams need a shared system for group operations, but an order, invoice, bill or journal still needs to belong to the correct entity. Combining everything into one undifferentiated ledger makes tax, ownership, accountability and period review harder.
Establish the entity structure before transactions begin
Each entity has its own setup, including accounting periods, organization-level GL accounts and operational settings. A firm can also designate a primary consolidating entity and determine which enabled entities are included in consolidated financial reporting.
Administrators should agree on the legal and reporting purpose of every entity before configuring users or posting transactions. An entity should not be created merely as a convenient department label if the business actually needs a dimension, facility or responsibility center instead.
Give each user the entity access needed for the job
On a user record, an administrator selects the allowed entities and a default entity. Users who are expected to move between entities also need the applicable switching permission. Functional permissions remain separate: access to an entity does not automatically grant permission to post GL transactions, manage users or run consolidated reports.
| Control | Question it answers |
|---|---|
| Allowed entities | Which entities is this user assigned to work with? |
| Default entity | Which entity should be active when the user starts work? |
| Entity switching permission | May the user change the active entity during a session? |
| Functional permissions | What may the user view or do in that entity? |
| Consolidated Reports permission | May the user review a group-level financial report? |
A warehouse coordinator may be assigned only to the distribution entity, while a controller is assigned to all operating entities and the consolidating entity. The controller still needs reporting and GL permissions before reviewing consolidated results or posting an approved adjustment.
Check the active entity before creating or posting
The active entity provides the working context for entity-scoped screens and records. Users should confirm it before entering a customer order, supplier bill, receipt or manual journal. Switching the entity changes the work context; it does not move an existing transaction from one entity to another.
When one entity trades with another, Versa Cloud ERP can connect the operating documents rather than treating both sides as unrelated outside activity. With Inter-Entity Transactions enabled and the relationship configured, a posted invoice can create a related bill in the buying entity. Each side retains its own document and accounting record, and the link supports later reconciliation.
Treat consolidated reporting as a separate view
Entity-level records remain the source for day-to-day work and entity close. Reports → Consolidated Financial provides an authorized group view across entities included in consolidation. It does not erase entity ownership or repair an incorrectly recorded transaction.
The distinction is important for buyers evaluating fit. Versa Cloud ERP supports multiple entities in one firm, role-based access and a controlled group-reporting path. The business still defines its entity structure, assigns users deliberately and reviews each entity before relying on the consolidated result.
Ask the Versa Cloud ERP AI Advisor about multi-entity access and record separation
