Posting and ordinary recovery: Feature Acceptance Suite

What the Feature Must Do as a Whole

Readiness, submission, resolution, generation and recovery form one accounting outcome. The suite follows failures and correction as well as successful completion.

Interactions Between Capabilities

Missing destinations affect readiness and generated entries. Recovery revisits snapshots and current entries rather than assuming that a completed job alone proves replacement accounting.

Regression Record

Revision	Change	Scenario	Why
1	initial	all	Establish cumulative feature acceptance from the pinned planning and design outcomes.

Show evidence (sources, provenance, origins, pinned commits)

Scenarios

5 scenarios proving FEAT-ACC-BAT-03 as a whole.

01 Posting connects readiness accounts and entries behaviour proposed

Exercises: CAP-ACC-BAT-012 CAP-ACC-BAT-013 CAP-ACC-BAT-014 CAP-ACC-BAT-015
Relies on: ATS-ACC-BAT-012-03 ATS-ACC-BAT-013-02 ATS-ACC-BAT-014-01 ATS-ACC-BAT-015-03
Preconditions: Morning contains a valid taxed accrual invoice and configured accounts.
Steps: [object Object]
Expected: Readiness identifies Morning, the job completes and the stored entry balances with the resolved destinations.
Data: An isolated workspace, business unit and owned fixtures matching the stated accounting setup.
Source: rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-012-check-before-posting-what-would-stop-a-batch.md#ATS-ACC-BAT-012-03; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-013-post-batches-to-the-subledger-as-one-watched-job.md#ATS-ACC-BAT-013-02; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-014-resolve-and-freeze-the-accounts-when-a-batch-posts.md#ATS-ACC-BAT-014-01; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-015-turn-each-document-into-its-balanced-entry.md#ATS-ACC-BAT-015-03

02 Account correction changes preview and posting interactionnegative proposed

Exercises: CAP-ACC-BAT-012 CAP-ACC-BAT-013 CAP-ACC-BAT-014 CAP-ACC-BAT-015
Relies on: ATS-ACC-BAT-012-02 ATS-ACC-BAT-013-08 ATS-ACC-BAT-014-02
Preconditions: Morning holds an issued invoice with no resolvable revenue account.
Steps: [object Object]
Expected: The first accounting attempt leaves no entry; the correction permits a successful retry using the newly resolved destination.
Data: An isolated workspace, business unit and owned fixtures matching the stated accounting setup.
Source: rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-012-check-before-posting-what-would-stop-a-batch.md#ATS-ACC-BAT-012-02; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-013-post-batches-to-the-subledger-as-one-watched-job.md#ATS-ACC-BAT-013-08; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-014-resolve-and-freeze-the-accounts-when-a-batch-posts.md#ATS-ACC-BAT-014-02

03 Ordinary recovery creates a replacement current set lifecycle proposed

Exercises: CAP-ACC-BAT-013 CAP-ACC-BAT-014 CAP-ACC-BAT-015 CAP-ACC-BAT-016
Relies on: ATS-ACC-BAT-013-03 ATS-ACC-BAT-014-03 ATS-ACC-BAT-016-02 ATS-ACC-BAT-016-05
Preconditions: Morning has a current posting and its fiscal period remains Open.
Steps: [object Object]
Expected: Recovery restores Open without old entries; replacement posting creates fresh snapshots and one current entry set.
Data: An isolated workspace, business unit and owned fixtures matching the stated accounting setup.
Source: rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-013-post-batches-to-the-subledger-as-one-watched-job.md#ATS-ACC-BAT-013-03; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-014-resolve-and-freeze-the-accounts-when-a-batch-posts.md#ATS-ACC-BAT-014-03; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-016-take-a-posting-back-and-post-again.md#ATS-ACC-BAT-016-02; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-016-take-a-posting-back-and-post-again.md#ATS-ACC-BAT-016-05

04 Preview posting and recovery have distinct grants permissionnegative proposed

Exercises: CAP-ACC-BAT-012 CAP-ACC-BAT-013 CAP-ACC-BAT-016
Relies on: ATS-ACC-BAT-012-01 ATS-ACC-BAT-013-01 ATS-ACC-BAT-016-01
Preconditions: Reader, staff and administrator personas share an isolated postable batch.
Steps: [object Object]
Expected: Readiness succeeds for reader; reader posting and staff recovery fail with 403; permitted accounting work succeeds.
Data: An isolated workspace, business unit and owned fixtures matching the stated accounting setup.
Source: rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-012-check-before-posting-what-would-stop-a-batch.md#ATS-ACC-BAT-012-01; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-013-post-batches-to-the-subledger-as-one-watched-job.md#ATS-ACC-BAT-013-01; rhythm-v2-docs:specs/accounting/batches/design/tests/ATS-ACC-BAT-016-take-a-posting-back-and-post-again.md#ATS-ACC-BAT-016-01

05 A stored-write refusal leaves the entire request intact regressionnegative proposed

Exercises: CAP-ACC-BAT-013 CAP-ACC-BAT-014 CAP-ACC-BAT-015 CAP-ACC-BAT-016
Relies on: ATS-ACC-BAT-013-07
Preconditions: A postable request contains valid documents and a controlled database write refusal.
Steps: [object Object]
Expected: The transactional refusal fails the job and preserves pre-request accounting without a partial generation.
Data: An isolated workspace, business unit and owned fixtures matching the stated accounting setup.
Source: services-accounting:modules/batches/tests/integration/services/jobs/deployed-task-handler.integration.spec.js#fails the job on a step the database refuses: refused once, recorded by the failure task, the batch open and nothing written

Planning

Posting and ordinary recovery: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

Interactions Between Capabilities ​

Regression Record ​

Scenarios

Posting and ordinary recovery: Feature Acceptance Suite

What the Feature Must Do as a Whole

Interactions Between Capabilities

Regression Record