FAS-ACC-BKS-02 Accounts and Reporting Destinations acceptance
Markdown Planning / Accounting / Books, Business Units and Chart of Accounts / Feature Acceptance Suite 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.
Show evidence (sources, provenance, origins, pinned commits)Scenarios 5 scenarios proving FEAT-ACC-BKS-02 as a whole.
01 Make the chart usable through default assignments behaviour proposed
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. Data Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. Source ATS-ACC-BKS-005-01 ,ATS-ACC-BKS-006-04 05 Keep independent code collections when the unit changes regression negative proposed
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. Data Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. Source ATS-ACC-BKS-005-01 ,ATS-ACC-BKS-008-01 ← Previous Feature Acceptance Suite FAS-ACC-BKS-01 · Business Units and Currency Policy acceptance Next Feature Acceptance Suite → FAS-ACC-BKS-03 · Calendar Coverage acceptance