One platform, many companies.
Group structures, subsidiaries, franchises, and managed clients — isolated where they have to be, consolidated where it helps, on one deployment.
Company isolation·Group consolidation·Shared masters
Isolation and consolidation at the same time.
The difficulty is never one or the other. It is wanting a subsidiary's users to see nothing outside their entity while the group sees everything, with one item master underneath both.
Isolation
What one company cannot see or touch.
Company as a permission boundary
A user scoped to one entity cannot read, report on, or reach another entity's records — including through a question to an agent.
Separate ledgers
Each company has its own chart, its own fiscal calendar, its own currency, and its own period locks.
Separate numbering
Naming series per company, so document references do not reveal group-wide volumes to a client or a franchisee.
Independent close
One entity can close a period while another is still posting, which is the normal state of affairs in a group.
Sharing
What is deliberately held once.
Shared item and party masters
One definition of an item, a customer, or a supplier, used by every company that needs it, with per-company defaults on top.
Per-company defaults
The same item with a different income account, warehouse, tax template, and price list in each entity.
Shared configuration
Workflows, print formats, and custom record types defined once and applied where you choose.
Selective sharing
Sharing is opt-in per record type. A managed-services client's customers are not shared just because their items are.
Between companies
Transactions that cross the boundary properly.
Inter-company transactions
A sale from one entity to another creating both sides, linked, so neither has to be keyed twice.
Inter-company stock transfer
Moving stock between entities as a delivery and a receipt with the ledger entries on both sides, not an invisible adjustment.
Cross-charge
Internal projects and shared services charged between entities with the entries posted rather than journalled at year end.
Elimination
Inter-company balances identified for elimination in consolidation rather than found by hand.
Consolidation
Reading the group as one thing.
Consolidated statements
Balance sheet and profit and loss across a company tree, with the hierarchy defined as records.
Currency translation
Subsidiaries reporting in their own currency, translated at the rates you specify for the group view.
Drill through to the entity
A consolidated figure opens into the entity, then the posting, then the document — the boundary does not stop the drill.
Group and entity dimensions
Report by entity, region, or your own dimensions across the whole group without a separate reporting structure.
Operating a portfolio
For accountants, franchisors, and managed-service operators.
One login, many clients
A practice user moves between client companies without a separate account for each.
Per-client branding
Documents and portals carrying the client's identity rather than yours or ours.
Client self-service
A client's own users see only their entity, with their own permissions, on the same deployment.
Onboarding from a template
A new entity created from a configured template — chart, workflows, roles — rather than assembled each time.
From a new subsidiary to a first posting.
The second step is the one to get right, because deciding what is shared after the fact is considerably harder than deciding it now.
- 01
Create
The company is added to the tree with its own chart, calendar, currency, and numbering series.
- 02
Decide sharing
Which masters and configuration it shares with the group, and which it holds independently. Recorded, not assumed.
- 03
Scope access
Roles are granted against the entity, so its people see it and the group sees through it.
- 04
Post
It transacts independently, appears in consolidation, and inter-company movements create both sides.
The specification.
What a group finance function and a security reviewer each check.
- Boundary
- Company is a first-class permission boundary
- Ledgers
- Chart, calendar, currency, and period lock per company
- Masters
- Shared, with per-company defaults, opt-in by record type
- Inter-company
- Both sides created and linked, with elimination flagging
- Consolidation
- Company tree, currency translation, drill to document
- Numbering
- Independent series per company
- Isolation option
- Separate database per tenant where required
- Onboarding
- New entity from a configured template
The limits of one deployment.
Multi-tenancy on shared infrastructure is the right answer often, and not always. Here is where it stops being it.
- Shared infrastructure has a shared fate
- One deployment means one upgrade window and one outage. Where a client contractually cannot share that, they need their own instance and it costs more.
- Regulatory isolation may force separation
- Some regimes require a separate database or a separate region. That is supported, and it means giving up some of the sharing above.
- Shared masters need shared governance
- One item master across eight entities needs somebody who owns it. Without that, sharing produces arguments rather than savings.
- Consolidation is not statutory reporting
- The group view is a management consolidation. Where statutory group accounts have specific requirements, treat this as the input to them, not the output.
Next step