Accounting setup lifecycle

The Lifecycle

Transitions Explained

A product has no setup until finance supplies one through single or bulk saving. An absent setup is inserted; an existing setup is replaced at its current version. Deleting only the setup leaves the product available with no financial summary. Product deletion also removes the setup unless its deletion lock blocks the operation.

What Cannot Happen

A setup cannot change its product or business unit. Refused local writes leave the committed row and collections intact. The documented posting boundary keeps earlier posted accounts outside later setup edits.

Concurrency and Timing

The setup writer locks the product before reading prices and locking the setup. Bulk writes acquire product locks in identity order. A first setup write does not reject a supplied version merely because the setup is absent. Retirement does not prevent setup saving; explicit product authority for that difference remains missing.