Solution
Multi-Company Management
You run more than one legal entity, more than one plant, or more than one branch — a manufacturer with several facilities, a distributor with multiple warehouses — and today that means either a separate system per entity or one shared login where anyone can see everyone else's numbers.
What it is
Managing multiple companies with Vercentlabs ERP means structural isolation by company and branch, scoped and time-bound roles, and real consolidation when you need a combined view — relevant to a manufacturer running several plants or a distributor running multiple warehouses under one legal umbrella, not just a holding-company structure.
State change
Before and after
The solution is presented as a change in operating state: what fails today, and what replaces it when the system is connected.
Before
01Either N separate systems (one per company) that never reconcile with each other, or one shared system with no real separation — every user sees every company's data whether they should or not.
After
02One platform, structurally isolated by company and branch — a user's access is scoped to the companies, branches, or even departments they're actually granted, with consolidation and intercompany posting available when you need a combined view.
Intervention
What replaces the problem
Each intervention is a concrete operating mechanism, not an aspirational benefit statement.
- 01
Isolation is structural, not a filtered view
Organisations, companies, branches, departments, and cost centers form a real hierarchy with granular, membership-scoped access — company and branch, not an all-or-nothing switch a careless admin could flip.
- 02
Roles can be scoped and time-bound per company or branch
Role assignments can be scoped to specific companies, branches, or departments, and can carry a start and expiry date — a contractor or auditor's access doesn't outlive the engagement.
- 03
Consolidation is a real capability, not a manual spreadsheet roll-up
Accounting supports multi-entity consolidation and intercompany posting as part of its close/planning capability group — a combined view exists when you need it, without breaking each entity's own isolated books.
- 04
One numbering and role framework, provisioned once
A one-transaction organisation bootstrap seeds roughly 12 roles and 29 numbering series at signup — adding a new company doesn't mean rebuilding your role and numbering structure from scratch.
Platform Architecture
Vercentlabs' platform architecture is the cross-cutting control plane every module runs on — multi-tenant and multi-company data isolation, role-based access control, a governed approvals and workflow engine, and an immutable audit trail, built once and inherited by all 12 modules rather than reimplemented per module.
Open capability →System map
Where the intervention lives.
The problem may look like one process, but the solution usually spans several modules and at least one cross-module workflow.
Buyer questions
Questions buyers ask
Direct answers about fit, scope and how this solution behaves in the real system.
Can a user work across two companies if their role genuinely requires it?
Yes — access is scoped per company/branch/department by design, but a role assignment can be granted across multiple scopes where that's the real access someone needs. It's not an all-or-nothing single-tenant switch.
Is consolidation automatic, or does someone have to run it?
Multi-entity consolidation and intercompany posting are real capabilities inside Accounting's close/planning workflow, not a background job — they run as part of a deliberate close/reporting step, keeping each entity's own books independently accurate.
Does time-bound role access apply to auditors and contractors too?
Role assignments generally can carry a start and expiry date and can be scoped to a specific company or branch — a reasonable fit for an auditor or contractor engagement, though this is a platform capability, not an auditor-specific feature.
Related diagnostics