Company-scoped workflows
Keep accounting workflows company-scoped.
Evaluate a small company footprint with explicit user and company limits, without assuming that separate-company work includes consolidation.
Match the package to the footprint
Catalog basis. These guide limits are separate from the upcoming package allowances and are not trial entitlements.
Count the people and companies that need the workflow now, then consider whether a foreseeable requirement would exceed the published limits. The catalog does not establish an additional-company add-on or an unlimited plan.
Scroll horizontally to see all columns on smaller screens. Keyboard: focus the table and use the arrow keys.
| Package | Included users | Included companies |
|---|---|---|
| Core | Up to 5 | 1 |
| Pro | Up to 25 | 3 |
Make company identity part of the review
Company-scoped workflows keep the company context relevant to the accounting work. In your own operating notes, identify the company alongside the customer, document, and review question. Consistent notes can make separate reviews understandable without treating them as one combined set of accounts.
- Confirm which company the work belongs to.
- Keep each company’s unresolved review questions identifiable.
- Treat a cross-company reporting requirement as a separate evaluation item.
Company scope is not consolidation
Catalog basis. These guide limits are separate from the upcoming package allowances and are not trial entitlements.
Arcaiva does not currently claim consolidation, intercompany automation, more than three included companies, complex multinational localization, or enterprise ERP implementation. Company-scoped is also not a certification or a comprehensive security assurance.