Business unit lifecycle

The Lifecycle

Transitions Explained

Units default to active and can also be created inactive. Creation commits the currency setup and two initial fiscal years together. Availability changes are ordinary record replacements; row and bulk console actions use the same single-record operation.

Removal is physical. Accounts and projects must be removed first, and other restricting references can still block the owned cascades. A freed code can identify a later new unit without restoring the original record.

What Cannot Happen

Founding currency and fiscal boundary do not change through an update. Deactivation retains the configuration and its dependencies. Calendar coverage is atomic at creation, but subsequent eligible year deletion can remove the initial years.

Concurrency and Timing

A stale replacement is refused. Record locks protect their stated operations. Currency foreign keys constrain racing references, while the accounting-method guard has no equivalent lock on the batches it counts.