Workspace scope and multi-workspace workflows
Workspace scope and multi-workspace workflows
A BusDK workspace directory is intentionally single-entity: one workspace represents exactly one internal business entity, and all datasets in that workspace belong to that entity by construction. This keeps posting, period close, reconciliation, and validation rules local to one entity, so cross-entity constraints do not leak into the operational data model.
Multi-company workflows such as company groups, consolidation, shared reporting, or parallel bookkeeping are handled by higher-level commands that accept multiple workspace directories as inputs. Those commands produce outputs that remain separated per input workspace unless an explicit consolidation output is requested, so the boundary between entities stays reviewable and script-friendly.