01
Separate entity context
Configure and review each business with its own settings, user access, and financial context so teams are never working in the wrong ledger.
Entity context
Multi-Business
Switch confidently between businesses, ledgers, tax contexts, and permissions without mixing records across separate legal entities or operational units.
Capabilities
4 workflows
Operating sequence
4 steps
Buyer checks
3 evidence points
Core capabilities
Keep business units separate without losing operational speed
The workflow is organized around the questions a multi-entity operator asks every day: which business am I in, which settings are active, and which reporting view is legally or operationally correct for this context.
02
Context switching
Move between businesses and review the currently active entity without losing the surrounding record and reporting context.
03
Tax and fiscal isolation
Keep tax identity, fiscal-year settings, and reporting views aligned to the active business instead of duplicating them across all entities.
04
Permission-aware access
Support role and access configuration that aligns to each configured business and the responsibilities assigned to each team.
Operational value
Reduce context errors across your entity portfolio
Multi-business operations work best when the active entity is obvious and the business context is preserved through each action. Operators should be able to move from one business to another without ambiguity about the ledger, currency, tax profile, or permissions they are currently using.
- 1Safer operating context across business units
- 2Less risk of mixing entity records or tax settings
- 3Better confidence in statements and reviews performed under the correct entity context
Multiple entities create context-switching and control challenges
Accountants and operators often need to move between separate ledgers, tax registrations, currencies, and user roles without mixing one business's records into another's.
Illustrative entity review
An accountant switches from one configured business to another, checks the active entity, currency, fiscal year, role, and ledger context, then reviews the appropriate statements. The entity data described here is illustrative.
Who it is for
Accountants, holding-company operators, and teams responsible for more than one configured business or ledger context.
What users enter
- • Business profile, tax identity, and fiscal-year settings
- • Currency and ledger configuration
- • User roles and entity access
What users review
- • Active-entity context
- • Separate statements and tax-register views
- • A verified basis for any consolidated reporting claim
Dependencies to confirm
- • Plan capacity and account configuration
- • Confirmed consolidation and intercompany behavior
- • Currency and permission setup
How the workflow works
From action to accounting record
A concrete sequence makes it easier to evaluate where this module fits in your operating process.
- 01
Create entity
Set up the business profile, tax identity, currency, and fiscal-year context.
- 02
Assign access
Confirm which roles can work with the entity and its accounting records.
- 03
Switch context
Select the active business before reviewing or recording transactions.
- 04
Report separately
Review statements and tax registers in the correct entity context.
Product evidence
What to verify in a product walkthrough
The examples below describe the evidence a buyer should be able to inspect in the product. Demo values are illustrative and are not customer results.
| Entity selector | Active business, location, currency, fiscal yearA live entity-selector screenshot is not available in the verified asset set; request a product walkthrough before treating this as demonstrated behavior. |
|---|---|
| Isolation to verify | Ledgers, contacts, tax registers, dashboardsConfirm the separation and any consolidation behavior for your plan. |
| Plan boundary | Pricing currently lists one business on Trial, Basic, and StandardConfirm multi-business capacity and consolidated reporting with Sales before purchase. |
Scope and limitations
Clear boundaries build trust
- Multi-business availability, consolidation, intercompany handling, and currency support are plan- and configuration-dependent.
- The interactive entity data is illustrative and should not be interpreted as customer or production evidence.
- Separate statements and consolidated statements should be demonstrated independently before rollout.
Buyer questions
Frequently asked questions
Review the practical details, setup requirements, and boundaries that matter before adopting this workflow.
The site describes multi-business functionality, but the published pricing table currently lists one business on Trial, Basic, and Standard. Confirm the applicable plan and configuration.
Isolated ledgers are a stated product concept. Ask for an entity-switching demonstration and confirm which records and permissions are scoped to the active business.
Consolidated reporting should be verified separately from entity switching. Confirm currency, intercompany, and statement behavior before relying on consolidation.