Business Unit

What It Models

A business unit gives the customer a separate accounting context. Its base currency and fiscal boundary establish how money and dates are interpreted. Currency permissions, accounting policies, document choices and tender-fee settings provide the configuration financial workflows consume.

Identity and Attributes

The configuration code identifies the unit within its workspace. Creation can derive that code from the name; subsequent edits preserve it. Name, description, priority and availability can change.

The base currency and fiscal starting month are fixed. Currency rows and dated quotes are owned collections. The remaining policies govern posting, fees, downloads and document selection. Fee settings and direct write-off treatment survive an older client’s save when omitted, while an omitted document choice returns to built-in selection.

Relationships

Each unit supplies a chart, receiving destinations, reporting dimensions and calendar. Shared templates and workspace definitions are referenced separately. Restricting references from financial work can prevent removal of the unit or of records its deletion would cascade.

Invariants

Creation is one atomic write of the unit, currency setup and two fiscal years. This is a creation guarantee: permitted later calendar deletion can remove those years. Currency references and fixed founding values receive database protection. A fee-product check runs when the request names the product; it does not prevent later product changes.

How It Is Stored and Shared

Books provides ordinary configuration maintenance. Other Accounting modules use its shared tables and helpers within their own work. Maintenance reads the configuration for lifecycle operations and can remove it during workspace erasure. A read-only business-unit query exposes the agreed identifying fields.

The registered unit has no custom-field capability. Customer rows use forced row-level security. Configuration retains the current version and last-modified details rather than a revision history or change-event stream.

Open Design Questions

Product still needs to settle merchant fee overrides and configuration history. The console exposes neither tender-fee settings nor direct write-off treatment. The accounting-method check can miss a concurrently posted batch.