FAS-ACC-BKS-04 Shared Terms, Receipt Methods and Tax Mapping acceptance
Markdown Planning / Accounting / Books, Business Units and Chart of Accounts / Feature Acceptance Suite 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.
Scenarios 5 scenarios proving FEAT-ACC-BKS-04
02 Apply a method behavior to the unit fee choice interaction test
Exercises CAP-ACC-BKS-012CAP-ACC-BKS-003Relies on ATS-ACC-BKS-012-01ATS-ACC-BKS-003-06Preconditions 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. Data Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. Bound to 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 03 Preserve protected methods on provisioning retry lifecycle proposed
Exercises CAP-ACC-BKS-012CAP-ACC-BKS-019Relies on ATS-ACC-BKS-012-02ATS-ACC-BKS-019-01Preconditions 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. Data Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. Source ATS-ACC-BKS-012-02 ,ATS-ACC-BKS-019-01 04 Inspect shared definitions without granting maintenance permission negative proposed
Exercises CAP-ACC-BKS-011CAP-ACC-BKS-012CAP-ACC-BKS-013Relies on ATS-ACC-BKS-016-01Preconditions 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. Data Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. Source ATS-ACC-BKS-016-01 05 Expose an installment reference when term removal fails regression negative proposed
Exercises CAP-ACC-BKS-011CAP-ACC-BKS-016Relies on ATS-ACC-BKS-011-03Preconditions 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. Data Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. Source ATS-ACC-BKS-011-03 ← Previous Feature Acceptance Suite FAS-ACC-BKS-03 · Calendar Coverage acceptance Next Feature Acceptance Suite → FAS-ACC-BKS-05 · Document Content and Selection acceptance