Rhythm 2.0 Specifications

Appearance

WF-ACC-BKS-001Create a Unit With Initial Calendar Coverage

Markdown

WF-ACC-BKS-001

Create a Unit With Initial Calendar Coverage

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-ACC-BKS-001, CAP-ACC-BKS-002, CAP-ACC-BKS-003, CAP-ACC-BKS-009

KindWorkflowProduct areaAccountingModuleBooks, Business Units and Chart of AccountsRevision1

Read atservices-accounting f47cb263react-console baf6dae3

Create a Unit With Initial Calendar Coverage ​

What It Does ​

Creating a unit establishes its founding currency and fiscal boundary together with initial calendar coverage. The base and supported currency rows and two complete fiscal years commit with the unit. This gives subsequent configuration and dated work a consistent starting point.

The Flow ​

When Something Fails ​

Input checks precede the transaction; every creation write shares that transaction. A refusal leaves no partial new unit. A duplicate retry after success fails under the same code, while a retry using a new code creates a distinct unit. Refreshing the console happens after commit and can leave the display stale without changing stored configuration.

Open Design Questions ​

The generated coverage is relative to the creation date. A unit opened near its year boundary may need an explicit extension soon afterward; the product has no examined early warning.

Controls

23 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-DAT-001 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-002 TC-PI-003

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software