Business Unit
What It Is
A business unit identifies the set of books in which the customer records financial work. An association may keep one set for its central office and another for a foundation or chapter. Each unit supplies an accounting context that staff can recognize by name, while its permanent identity continues through later name corrections. The unit includes a description and optional priority as well as its founding currency and fiscal start month.
An administrator establishes the unit before configuring its accounts and recording transactions. Creation also supplies the initial fiscal calendar, so staff have periods to work with immediately. The unit brings together the choices that make its books usable: currencies, accounting policies, rates, document selections and export preferences. This is comparable to the company context in accounting software, where the same account code can have meaning in more than one company.
What It Is Not
A unit does not identify the customer being billed. A CRM organization identifies that party, while the business unit identifies the customer’s own books. A chapter can have a unit when it keeps separate accounts, but a membership grouping alone does not require one. Workspace-wide choices, such as refund approval or named payment methods, sit above the unit rather than becoming different copies for every chapter.
How It Is Used
Controllers establish units when finance begins using Accounting or when another bookkeeping entity opens. Staff then meet the unit in their working context, scoped lists and transaction choices. A well-chosen context helps staff select the intended accounts and calendar before entering money. A wrongly chosen founding currency or fiscal month requires a new unit; existing dependency checks can prevent removal of the mistaken unit until its setup is released.
Its Facets
Founding choices. Base currency defines the currency of the books, while the start month organizes the calendar. Both deserve review before creation because later setup depends on them.
Foreign-currency support. Supported currencies have their own rate-source and missing-price choices. These settings belong to the unit’s use of a currency rather than to a new independent financial entity.
Exchange rates. Dated quotes let pricing and conversion use an applicable rate without replacing the unit’s base currency. Manual and provider maintenance have different correction paths.
Accounting policy. Recognition method and write-off treatment supply decisions to posting. Staff should understand when a setting takes effect rather than assume entry permanently freezes it.
Tender fees. The configured product and fee amounts describe the charge applied to eligible payment behaviour. This is separate from selecting a merchant processor.
Documents and exports. Template selections, software package and download detail connect the unit’s books to customer documents and external accounting work.
Working context. Priority influences the default selection when staff have no eligible remembered choice. The working unit is a person’s current context, not a second unit record.
How It Relates
The chart and fiscal calendar belong to the unit. Document templates can serve several units, so the unit selects rather than owns their content. Products, financial documents, batches and reconciliations use the unit supplied by this module. The read-only query representation lets other financial information be presented with a recognizable unit name.
What It Could Become
The product should settle whether merchant accounts can override unit fee policy before designing that extension. Consolidated reporting and inter-entity presentation could make relationships between units easier to understand. Those possibilities need explicit decisions rather than an assumption that several units automatically form a consolidation structure.