--- id: FAS-ACC-BKS-02 title: Accounts and Reporting Destinations acceptance feature: FEAT-ACC-BKS-02 product_area: accounting module: books revision: 1 status: proposed product_intent: proposed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-ACC-BKS-005 - CAP-ACC-BKS-006 - CAP-ACC-BKS-007 - CAP-ACC-BKS-008 scenarios: - id: FAS-ACC-BKS-02-01 title: Make the chart usable through default assignments kind: behaviour exercises: - CAP-ACC-BKS-005 - CAP-ACC-BKS-006 relies_on: - ATS-ACC-BKS-005-01 - ATS-ACC-BKS-006-04 preconditions: An administrator has an isolated unit and eligible accounts. steps: >- Create accounts, open the default drawer, fill the required purposes and inspect the chart notice and assignment read-back. expected: >- Saved local destinations satisfy the displayed setup needs and remove the notice. negative: false data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: [] provenance: proposed source: - ATS-ACC-BKS-005-01 - ATS-ACC-BKS-006-04 binding_evidence: [] - id: FAS-ACC-BKS-02-02 title: Release receiving and tax references before chart removal kind: interaction exercises: - CAP-ACC-BKS-005 - CAP-ACC-BKS-006 - CAP-ACC-BKS-007 - CAP-ACC-BKS-013 relies_on: - ATS-ACC-BKS-005-04 - ATS-ACC-BKS-005-05 - ATS-ACC-BKS-007-01 - ATS-ACC-BKS-013-01 preconditions: >- A chart account serves a default and receiving accounts; another is mapped by a tax rate. steps: >- Attempt removal under each dependency, clear the defaults, remove receiving records and tax mapping, and retry chart removal. expected: >- Each remaining dependency prevents removal; fully released accounts become removable. negative: false data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: - TST-ACC-BKS-009 provenance: test source: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0010.spec.ts#ACT-ACC-0010 binding_evidence: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0010.spec.ts#ACT-ACC-0010 - id: FAS-ACC-BKS-02-03 title: Retire a former default destination kind: lifecycle exercises: - CAP-ACC-BKS-005 - CAP-ACC-BKS-006 relies_on: - ATS-ACC-BKS-005-05 - ATS-ACC-BKS-006-02 preconditions: An active account serves a standard purpose. steps: >- Attempt deactivation, clear that purpose twice, deactivate the released account and inspect its activity and assignment. expected: >- Protection holds while assigned; repeated clear is safe and the retired account is no longer a default. negative: false data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: - TST-ACC-BKS-007 provenance: test source: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0008.spec.ts#ACT-ACC-0008 binding_evidence: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0008.spec.ts#ACT-ACC-0008 - id: FAS-ACC-BKS-02-04 title: Inspect accounts and reporting dimensions as a reader kind: permission exercises: - CAP-ACC-BKS-005 - CAP-ACC-BKS-006 - CAP-ACC-BKS-007 - CAP-ACC-BKS-008 relies_on: - ATS-ACC-BKS-016-01 - ATS-ACC-BKS-016-09 preconditions: >- Run-owned chart, receiving records, defaults and dimensions are configured. steps: >- Inspect every relevant list and editor as a reader, attempt each supported mutation and compare the configuration. expected: >- Inspection is available and the refused writes preserve accounts, defaults and dimensions. negative: true data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: - TST-ACC-BKS-011 provenance: test source: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0013.spec.ts#ACT-ACC-0013 binding_evidence: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0013.spec.ts#ACT-ACC-0013 - id: FAS-ACC-BKS-02-05 title: Keep independent code collections when the unit changes kind: regression exercises: - CAP-ACC-BKS-005 - CAP-ACC-BKS-008 relies_on: - ATS-ACC-BKS-005-01 - ATS-ACC-BKS-008-01 preconditions: Two units are available in the working context. steps: >- Use one code for a chart account, department and project in each unit, then repeat each code in its original collection. expected: >- Unit and collection boundaries preserve distinct identities while local duplicates remain refused. negative: true data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: [] provenance: proposed source: - ATS-ACC-BKS-005-01 - ATS-ACC-BKS-008-01 binding_evidence: [] evidence: - provenance: documented source: >- specs/accounting/books/planning/features/FEAT-ACC-BKS-02-chart-of-accounts.md - provenance: test source: >- Pinned executable suites and their individual assertion references are listed in the suite register. regression_record: - revision: 1 change: initial scenarios: - FAS-ACC-BKS-02-01 - FAS-ACC-BKS-02-02 - FAS-ACC-BKS-02-03 - FAS-ACC-BKS-02-04 - FAS-ACC-BKS-02-05 why: >- Establish cumulative feature acceptance from the pinned specification and executable evidence. --- # Accounts and Reporting Destinations: Feature Acceptance Suite ## What the Feature Must Do as a Whole The feature brings chart destinations, purpose assignments, receiving records and reporting dimensions into one unit context. Acceptance checks that configuration remains usable as references are added and released. ## Interactions Between Capabilities Default assignments and receiving or tax references change whether chart records can be retired. Shared unit context connects the editors while each code collection keeps its own identity. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish the feature’s cumulative acceptance boundary and record unimplemented joined outcomes. |