Complete accounting setup for a group of products

Purpose

Finance requests the products still lacking accounting setup.

How It Works

Finance requests the products still lacking accounting setup. The API keeps ordinary product filters and paging while defaulting to active products. A specialist can submit several complete setups in one request. Each setup uses the single-product validation contract. The bulk operation locks products in a consistent order before writing. One refusal rolls back every setup in the request. Its error identifies the offending position and product. The console currently provides only a per-row missing-setup indicator, leaving this workflow available through the API.

Relationships

This outcome uses assign a product’s accounting treatment. This outcome uses locate products and inspect their configuration.

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: Finance can complete multiple setups in a single transaction.
Surfaces: api
Intent sources: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D3

Controls

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

Business Rules

7 rules, 5 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	Products lacking a setup use the regular product filters, sort, paging and shape, with active status selected unless another status is requested. proved by `ATS-ACC-PRD-015-17`, `ATS-ACC-PRD-017-01`, `TST-ACC-PRD-025`, `TST-ACC-PRD-037`	policy	service	test services-accounting:modules/products/tests/e2e/product-accounting-setups.e2e.spec.js#answers the active products with no setup, by name
`02`must prove Proposed	The bulk API accepts one to one hundred distinct product setups and uses single-setup replacement semantics for each. proved by `ATS-ACC-PRD-017-02`, `TST-ACC-PRD-025`, `TST-ACC-PRD-036`	validation	api, service	test services-accounting:modules/products/tests/integration/services/persistence/product-accounting-setups.integration.spec.js#refuses 101 setups before reading any product
`03`must prove Proposed	A failing bulk setup rolls back the entire request and identifies its position and product. proved by `ATS-ACC-PRD-017-03`, `ATS-ACC-PRD-017-06`, `ATS-ACC-PRD-017-07`, `TST-ACC-PRD-025`, `TST-ACC-PRD-036`	invariant	service	test services-accounting:modules/products/tests/integration/services/persistence/product-accounting-setups.integration.spec.js#refuses a rule of a later setup naming its position and product, the earlier create rolled back
`04`must prove Proposed	Duplicate, absent and other-workspace product identities reject the bulk request before any setup persists. proved by `ATS-ACC-PRD-017-04`, `TST-ACC-PRD-025`, `TST-ACC-PRD-028`, `TST-ACC-PRD-036`	validation	service	test services-accounting:modules/products/tests/e2e/products-security.e2e.spec.js#refuses tenant B a bulk save naming tenant A’s product as unknown
`05` Proposed	Bulk writes acquire product locks in identity order, avoiding conflicting acquisition orders between bulk saves. proved by `ATS-ACC-PRD-017-06`	invariant	service	observed services-accounting:modules/products/services/persistence/products.ts:lockProductsInIdOrder
`06`must prove Proposed	The missing-setup list requires product-accounting read permission and bulk replacement requires product-accounting update permission. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D3 proved by `ATS-ACC-PRD-017-05`, `TST-ACC-PRD-028`	permission	api	test services-accounting:modules/products/tests/e2e/products-security.e2e.spec.js#is refused listing the products without an accounting setup
`07` Proposed	The console marks missing setups on individual rows but provides no dedicated missing-setup list or bulk editor.	policy	console	observed react-console:components/accounting-config/products/products-page.tsx:AccountingCell

Scenarios

Id	Given	When	Then	Provenance
`01`	Products in two units lack accounting setup.	Finance saves one unit’s setups and requests the remaining list.	Only the other unit’s product remains on that list.	test services-accounting:modules/products/tests/e2e/product-accounting-setups.e2e.spec.js#leaves only the product of the other unit without a setup

Edge Cases

Id	Given	When	Then	Provenance
`02`	The third bulk entry selects another unit’s revenue account.	Finance submits the bulk setup request.	No setup persists and the error identifies that entry and product.	test services-accounting:modules/products/tests/e2e/product-accounting-setups.e2e.spec.js#refuses another unit’s account in a later setup 400, naming it, and writes nothing

Planning

Implementation

Complete accounting setup for a group of products ​

Purpose ​

How It Works ​

Relationships ​