--- id: FAS-ACC-BKS-04 title: 'Shared Terms, Receipt Methods and Tax Mapping acceptance' feature: FEAT-ACC-BKS-04 product_area: accounting module: books revision: 1 status: proposed product_intent: proposed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-ACC-BKS-011 - CAP-ACC-BKS-012 - CAP-ACC-BKS-013 scenarios: - id: FAS-ACC-BKS-04-01 title: Configure shared definitions for several units kind: behaviour exercises: - CAP-ACC-BKS-011 - CAP-ACC-BKS-012 - CAP-ACC-BKS-013 relies_on: - ATS-ACC-BKS-011-02 - ATS-ACC-BKS-012-03 - ATS-ACC-BKS-013-02 preconditions: Two business units share one workspace and have eligible tax destinations. steps: >- Create a shared term, eligible payment method and class with zone rates, then inspect the choices in both unit contexts. expected: >- Shared definitions keep their workspace identity while tax destinations retain their unit context. 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-011-02 - ATS-ACC-BKS-012-03 - ATS-ACC-BKS-013-02 binding_evidence: [] - id: FAS-ACC-BKS-04-02 title: Apply a method behavior to the unit fee choice kind: interaction exercises: - CAP-ACC-BKS-012 - CAP-ACC-BKS-003 relies_on: - ATS-ACC-BKS-012-01 - ATS-ACC-BKS-003-06 preconditions: >- A complete unit fee rule and the three payment method behaviors are available. steps: >- Evaluate fee eligibility for each method, change the bank-debit fee switch and repeat the evaluation. expected: >- The method behavior and changed unit policy determine fee eligibility together. 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-171 provenance: test source: - >- services-accounting:modules/books/tests/unit/rules/card-fee-rules.spec.js#charges a card behaviour always, a bank debit only when the rule says so, and never an offline method or without a rule binding_evidence: - >- services-accounting:modules/books/tests/unit/rules/card-fee-rules.spec.js#charges a card behaviour always, a bank debit only when the rule says so, and never an offline method or without a rule - id: FAS-ACC-BKS-04-03 title: Preserve protected methods on provisioning retry kind: lifecycle exercises: - CAP-ACC-BKS-012 - CAP-ACC-BKS-019 relies_on: - ATS-ACC-BKS-012-02 - ATS-ACC-BKS-019-01 preconditions: A newly provisioned workspace has its initial methods. steps: >- Rename a system method, retry provisioning, deactivate a non-system method and read both method groups. expected: >- Retry preserves the permitted system-method edit and its protection; non-system availability remains independently editable. 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-012-02 - ATS-ACC-BKS-019-01 binding_evidence: [] - id: FAS-ACC-BKS-04-04 title: Inspect shared definitions without granting maintenance kind: permission exercises: - CAP-ACC-BKS-011 - CAP-ACC-BKS-012 - CAP-ACC-BKS-013 relies_on: - ATS-ACC-BKS-016-01 preconditions: >- An application-authorized reader and administrator have run-owned shared definitions. steps: >- Read terms, methods and tax setup as the reader and attempt every supported write, then repeat eligible writes with the administrator grants. expected: >- Resource grants govern every shared definition independently and refused writes preserve stored setup. 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-016-01 binding_evidence: [] - id: FAS-ACC-BKS-04-05 title: Expose an installment reference when term removal fails kind: regression exercises: - CAP-ACC-BKS-011 - CAP-ACC-BKS-016 relies_on: - ATS-ACC-BKS-011-03 preconditions: A term is referenced only by an installment schedule. steps: >- Attempt term deletion through the public API and read it after the refusal. expected: >- A useful dependency conflict replaces the unexplained error and the referenced term remains stored. 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-011-03 binding_evidence: [] evidence: - provenance: documented source: >- specs/accounting/books/planning/features/FEAT-ACC-BKS-04-payment-terms-methods-and-tax-setup.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-04-01 - FAS-ACC-BKS-04-02 - FAS-ACC-BKS-04-03 - FAS-ACC-BKS-04-04 - FAS-ACC-BKS-04-05 why: >- Establish cumulative feature acceptance from the pinned specification and executable evidence. --- # Shared Terms, Receipt Methods and Tax Mapping: Feature Acceptance Suite ## What the Feature Must Do as a Whole The feature supplies shared definitions that several units use. Acceptance combines shared identity, protected method behavior and the unit destinations selected by transitional tax configuration. ## Interactions Between Capabilities Method behavior affects fee eligibility, and provisioning retries must preserve permitted method edits. Referenced shared terms remain protected while the intended dependency refusal awaits a regression implementation. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish the feature’s cumulative acceptance boundary and record unimplemented joined outcomes. |