Assign a product’s accounting treatment

Purpose

A finance specialist assigns accounts and dimensions to a product.

How It Works

A finance specialist assigns accounts and dimensions to a product. Those references must belong to the appropriate workspace and business unit. New references must be active, and account slots restrict account kinds. The service creates or replaces the setup independently from the product record. A replacement carries the setup version and complete child collections. A failed setup save preserves its previous configuration. Console creation may already have committed the product when the setup fails. Staff can correct the setup and retry without creating the product again. Independent permissions support specialists who manage accounts separately from catalogue details.

Relationships

This outcome uses create a product with a permanent identity.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Accounts and dimensions describe the product’s financial treatment.
Surfaces: consoleapi
Intent sources: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D3services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D11services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D12services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#R21services-accounting:docs/migrations/accounting-modernization/products-shared/README.md#D-7

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-DAT-004 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-PI-001 TC-PI-003 TC-PI-005

Permissions

Key	Checked at	Scope
`accounting.product-accounting.read`	api	tenant
`accounting.product-accounting.update`	api	tenant
`accounting.product-accounting.delete`	api	tenant

Business Rules

16 rules, 14 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	A product may lack an accounting setup, in which case its summary is empty and recorded posting policy uses unit defaults. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D3 proved by `ATS-ACC-PRD-015-01`, `ATS-ACC-PRD-015-14`, `TST-ACC-PRD-011`, `TST-ACC-PRD-026`	policy	service	test services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js#answers accounting: null on the product; react-console:acceptance/accounting/playwright/journeys/products/ACT-ACC-0121.spec.ts#ACT-ACC-0121
`02`must prove Proposed	Sellable products require a revenue account in their setup, while Legacy Products may omit it. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D3 proved by `ATS-ACC-PRD-015-02`, `TST-ACC-PRD-026`	validation	service	test services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js#answers 400 to an Accounting Product without a revenue GL account
`03`must prove Proposed	Setup accounts and dimensions belong to the product’s unit, except tax classes belong to the workspace as a whole. proved by `ATS-ACC-PRD-015-03`, `TST-ACC-PRD-026`, `TST-ACC-PRD-036`	validation	service, database	test services-accounting:modules/products/tests/integration/services/persistence/product-accounting-setups.integration.spec.js#refuses a revenue GL account of another business unit, naming both units
`04`must prove Proposed	Receivable and inventory slots require asset accounts, revenue requires income, deferred revenue requires liability, and write-off and cost of goods sold require expense. proved by `ATS-ACC-PRD-015-04`, `TST-ACC-PRD-009`, `TST-ACC-PRD-036`, `TST-ACC-PRD-066`	validation	service	test services-accounting:modules/products/tests/integration/services/persistence/product-accounting-setups.integration.spec.js#refuses an asset account as the revenue account, naming the slot and the types it takes, and writes no setup
`05`must prove Proposed	New setup references require active records; an inactive record retained in the same field remains acceptable. proved by `ATS-ACC-PRD-015-05`, `TST-ACC-PRD-026`, `TST-ACC-PRD-036`	validation	service	test services-accounting:modules/products/tests/integration/services/persistence/product-accounting-setups.integration.spec.js#refuses it newly named in another field
`06`must prove Proposed	A setup tax class overrides its kind default, and an already held class remains acceptable after retirement. origin: services-accounting:docs/migrations/accounting-modernization/products-shared/README.md#D-7 proved by `ATS-ACC-PRD-015-06`, `TST-ACC-PRD-026`, `TST-ACC-PRD-036`	policy	service, database	test services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js#keeps the class it already names after the class is retired
`07`must prove Proposed	A first setup needs no read version, but existing setups require their read version and reject stale replacement. proved by `ATS-ACC-PRD-004-11`, `ATS-ACC-PRD-015-07`, `ATS-ACC-PRD-015-15`, `TST-ACC-PRD-026`, `TST-ACC-PRD-036`	validation	service	test services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js#answers 400 to a replacement without the version read
`08`must prove Proposed	Setup replacement clears omitted values and replaces all child collections transactionally, preserving previous data if it fails. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D12 proved by `ATS-ACC-PRD-015-08`, `ATS-ACC-PRD-017-07`, `TST-ACC-PRD-036`	invariant	service	test services-accounting:modules/products/tests/integration/services/persistence/product-accounting-setups.integration.spec.js#leaves the previous setup and collections when a rule refuses the replacement
`09`must prove Proposed	Update-locked setups require explicit lock removal for replacement, either lock blocks deletion, and authorized setup editors may remove locks. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D11 proved by `ATS-ACC-PRD-006-11`, `ATS-ACC-PRD-015-09`, `ATS-ACC-PRD-015-16`, `TST-ACC-PRD-036`, `TST-ACC-PRD-044`	permission	service	test services-accounting:modules/products/tests/integration/services/persistence/product-accounting-setups.integration.spec.js#unlocks a setup locked against updates when the replacement states sys_locked null, then deletes it
`10`must prove Proposed	Deleting an accounting setup leaves its product intact with an empty accounting summary. proved by `ATS-ACC-PRD-003-05`, `ATS-ACC-PRD-015-10`, `ATS-ACC-PRD-015-15`, `ATS-ACC-PRD-015-17`, `TST-ACC-PRD-026`, `TST-ACC-PRD-036`	lifecycle	service	test services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js#deletes it, leaving the product with accounting: null
`11`must prove Proposed	Accounts, dimensions, merchant accounts and tax classes referenced by setups cannot be deleted while referenced. proved by `ATS-ACC-PRD-015-11`, `TST-ACC-PRD-026`, `TST-ACC-PRD-031`	invariant	database	test services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js#answers 409 to deleting a GL account a setup still names
`12`must prove Proposed	Setup reads, replacement and deletion require separate product-accounting permissions, independent of product permissions. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D3 proved by `ATS-ACC-PRD-015-12`, `TST-ACC-PRD-012`, `TST-ACC-PRD-028`	permission	api	test services-accounting:modules/products/tests/e2e/products-security.e2e.spec.js#is refused reading a product’s accounting setup
`13`must prove Proposed	A setup’s product and business unit are fixed at creation and cannot change. proved by `ATS-ACC-PRD-015-13`, `TST-ACC-PRD-031`	invariant	service, database	test services-accounting:modules/products/tests/integration/db/products.table.integration.spec.js#refuses a change of product_id (RHF01)
`14` Proposed	The console groups accounting into five cards, saves it separately after the product, and requires a receivable account beyond backend requirements. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#R21	policy	console	observed react-console:components/accounting-config/products/product-editor.tsx:useProductEditorState
`15` Proposed	Accounting permits creation and replacement of setups on retired products.	policy	service	observed services-accounting:modules/products/services/persistence/products.ts:lockProductForAccounting
`16`must prove Proposed	Changing an accounting setup after posting leaves the account recorded on the existing posted entry unchanged. proved by `ATS-ACC-PRD-015-14`, `TST-ACC-PRD-011`	invariant	service	test react-console:acceptance/accounting/playwright/journeys/products/ACT-ACC-0121.spec.ts#ACT-ACC-0121

Scenarios

Id	Given	When	Then	Provenance
`01`	A workshop has no accounting setup.	Finance supplies revenue, receivable and deferred accounts plus a department.	The setup starts at version one and the product summary identifies its revenue account.	test services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js#answers the summary on the product

Edge Cases

Id	Given	When	Then	Provenance
`02`	A caller has product management authority but no setup read authority.	The caller requests full accounting setup.	The setup read fails while product editing remains independently authorized.	test services-accounting:modules/products/tests/e2e/products-security.e2e.spec.js#is refused reading a product’s accounting setup

Planning

Implementation

Assign a product’s accounting treatment ​

Purpose ​

How It Works ​

Relationships ​