Books, Business Units and Chart of Accounts
Purpose
Finance staff establish and maintain the configuration used by Accounting’s financial workflows. Separate business units bring together calendars, financial destinations, currencies and policy, while shared workspace definitions and templates support work across those units. Accounting also supplies scheduling and its part of Platform’s data lifecycle.
Boundary
This module owns bookkeeping configuration and its shared operational contribution. Transactions owns money documents and customer terms; batch management owns posting; close owns period transitions; reconciliation owns settlement. Product configuration and Billing orchestration retain their own records, and Platform owns security, provider connections, query execution and workspace lifecycle orchestration. Tax determination belongs to Commerce under the recorded realignment, although the transitional implementation remains hosted here.
Features
| Feature | Concepts | Capabilities | Journeys | Intent |
|---|---|---|---|---|
FEAT-ACC-BKS-01 — Business Units and Currency Policy | 1 | 4 | 3 | confirmed |
FEAT-ACC-BKS-02 — Accounts and Reporting Destinations | 1 | 4 | 0 | confirmed |
FEAT-ACC-BKS-03 — Calendar Coverage | 1 | 2 | 1 | confirmed |
FEAT-ACC-BKS-04 — Shared Terms, Receipt Methods and Tax Mapping | 0 | 3 | 0 | confirmed |
FEAT-ACC-BKS-05 — Document Content and Selection | 1 | 2 | 1 | confirmed |
FEAT-ACC-BKS-06 — Workspace Policy and Operations | 1 | 4 | 1 | proposed |
Five active concepts explain the module; the earlier payment-and-tax grouping remains superseded. Shared payment and tax facets have their conceptual home in the workspace while their capabilities remain in the shared-definition feature. Operation, declaration and permission coverage is complete within the pinned scope; evidence homes cover all current service test files, while some individual assertions still lack bindings.
Capabilities
| Capability | Feature | Outcome | Intent | Implementation |
|---|---|---|---|---|
CAP-ACC-BKS-001 | FEAT-ACC-BKS-01 | Establish a separate set of books for each business unit | confirmed | observed |
CAP-ACC-BKS-002 | FEAT-ACC-BKS-01 | Enable supported foreign currencies for a business unit | confirmed | observed |
CAP-ACC-BKS-003 | FEAT-ACC-BKS-01 | Set a unit’s accounting and tender-fee policies | confirmed | partially-observed |
CAP-ACC-BKS-004 | FEAT-ACC-BKS-01 | Maintain dated exchange rates for a unit | confirmed | partially-observed |
CAP-ACC-BKS-005 | FEAT-ACC-BKS-02 | Maintain a business unit’s chart | confirmed | observed |
CAP-ACC-BKS-006 | FEAT-ACC-BKS-02 | Assign accounts to standard posting purposes | confirmed | inconsistent |
CAP-ACC-BKS-007 | FEAT-ACC-BKS-02 | Configure where received money lands | confirmed | partially-observed |
CAP-ACC-BKS-008 | FEAT-ACC-BKS-02 | Organize reporting by department and project | confirmed | observed |
CAP-ACC-BKS-009 | FEAT-ACC-BKS-03 | Extend and maintain a unit’s fiscal calendar | confirmed | observed |
CAP-ACC-BKS-010 | FEAT-ACC-BKS-03 | Locate the fiscal period for accounting work | confirmed | observed |
CAP-ACC-BKS-011 | FEAT-ACC-BKS-04 | Define invoice payment terms | confirmed | inconsistent |
CAP-ACC-BKS-012 | FEAT-ACC-BKS-04 | Configure the methods used to receive money | confirmed | observed |
CAP-ACC-BKS-013 | FEAT-ACC-BKS-04 | Maintain tax payable mapping during the Commerce transition | proposed | inconsistent |
CAP-ACC-BKS-014 | FEAT-ACC-BKS-05 | Prepare Accounting document and export templates | confirmed | observed |
CAP-ACC-BKS-015 | FEAT-ACC-BKS-05 | Select templates for business documents | confirmed | partially-observed |
CAP-ACC-BKS-016 | FEAT-ACC-BKS-06 | Control access and safe changes to books configuration | confirmed | observed |
CAP-ACC-BKS-017 | FEAT-ACC-BKS-06 | Set accounting policy shared by the workspace | confirmed | partially-observed |
CAP-ACC-BKS-018 | FEAT-ACC-BKS-06 | Preview, run and review scheduled Accounting work | proposed | observed |
CAP-ACC-BKS-019 | FEAT-ACC-BKS-06 | Manage Accounting data through workspace lifecycle jobs | proposed | observed |
Journeys
| Journey | Outcome | Intent | Browser Policy |
|---|---|---|---|
JNY-ACC-BKS-001 | Prepare a new chapter’s books | confirmed | required |
JNY-ACC-BKS-002 | Replace a unit with incorrect founding currency | confirmed | required |
JNY-ACC-BKS-003 | Maintain calendar coverage for a unit | confirmed | required |
JNY-ACC-BKS-004 | Select a chapter’s own invoice wording | confirmed | required |
JNY-ACC-BKS-005 | Inspect books configuration as a reader | confirmed | required |
JNY-ACC-BKS-006 | Begin Canadian-dollar work in a US-dollar unit | confirmed | required |
Testing Artifact Tree
The structured tree names the feature acceptance suites in planning, capability test specifications in design and existing executable suites in implementation. Coverage findings distinguish proposed proof from execution and conformance evidence.