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.
Explore this page ↘Upcoming company allowances
Each upcoming package includes one company. Core adds a company for $50 USD/month; Pro adds one for $75 USD/month. The new offer is not yet available to purchase, and existing customer agreements are unchanged.
Each paid company has its own Plaid allowance: 2 connections on Core or 5 on Pro, shared by that company’s users and not pooled across companies. User allocation for additional companies remains to be confirmed.
| Package | Users for included company | Included companies | Each additional company |
|---|---|---|---|
| Core | 3 | 1 | $50 USD/month |
| Pro | 10 | 1 | $75 USD/month |
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
Separate company workflows and paid expansion do not include consolidation, intercompany automation, complex multinational localization or enterprise ERP implementation. Company scope is not a certification or a comprehensive security assurance.