ATS-ACC-BAT-011 Assign new documents to the appropriate batch stream: Capability Test Specification
Markdown Design / Accounting / Batch Management / Recurring intake and assignment / Capability Test Specification Assign new documents to the appropriate batch stream: Capability Test Specification Coverage The scenarios define focused checks for this outcome. The coverage map distinguishes specified checks from unresolved proof; executable bindings identify inspected assertions and carry no execution result.
Routing selection must pass intake checks. Routing references prevent stream removal. These checks use the related capability’s outcome as part of the setup or verification. Unbound interactions remain proposed until a suite executes the complete chain.
Coverage Rule covered Transition not-applicable Validation covered Permission gap: FND-ACC-BAT-065 Edge covered Failure gap: FND-ACC-BAT-065 Boundary covered Concurrency covered Invariant covered Interaction covered Test Scenarios 13 scenarios proving CAP-ACC-BAT-011
03 Settings versions govern subsequent saves concurrency api negative test
Proves BR-CAP-ACC-BAT-011-03Preconditions The unit has no saved settings. Steps Read, create, then save with no version, an old version and the current version. Expected Read returns 404; creation starts version one; missing and stale versions return 400 and 409; the current version advances. Data Provide no fixtures beyond the stated setup. Bound to Source services-accounting:modules/batches/tests/e2e/batch-assignment-settings.e2e.spec.js #answers 409 StaleObject to a save at the version first read 04 Rule references stay inside the unit validation api negative test
Proves BR-CAP-ACC-BAT-011-04INV-DOM-ACC-BAT-001-10 Preconditions Two units each have recurring, merchant and bank configuration. Steps Save the first unit’s default and rules using the second unit’s references. Expected Each request identifies the invalid reference without creating settings. Data Provide two units. Bound to Source services-accounting:modules/batches/tests/e2e/batch-assignment-settings.e2e.spec.js #answers 400 to another unit’s recurring batch in a rule 07 Document intake uses assignment when no batch is supplied interaction browser negative test
Proves BR-CAP-ACC-BAT-011-09Preconditions Invoice and check criteria select recurring configurations and a default exists. Steps Issue an invoice and check without explicit batches, then delete settings and submit another payment. Expected The first documents use the selected current batches; the last request fails because a batch is required. Data Provide recurring batches with open batches. Bound to Source react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0510.spec.ts #ACT-ACC-0510 08 Evaluation reports the chosen position rule api negative test
Proves BR-CAP-ACC-BAT-011-10Preconditions One unit has settings and another has none. Steps Evaluate facts for both, then omit transaction type. Expected The configured unit returns its selection and winning position, with no position for the default; missing settings return 404 and missing type returns 400. Data Provide no fixtures beyond the stated setup. Bound to Source services-accounting:modules/batches/tests/e2e/batch-assignment-settings.e2e.spec.js #answers the first rule by position when two rules match 09 Readers cannot replace or delete settings permission api negative test
Proves BR-CAP-ACC-BAT-011-11Preconditions A reader and administrator share saved settings. Steps Read, evaluate, save and delete as the reader, then delete settings and the default recurring configuration as administrator. Expected Reader reads succeed and writes return 403; administrator deletion removes rules and releases the referenced configuration. Data Provide security fixtures. Bound to Source services-accounting:modules/batches/tests/e2e/batches-security.e2e.spec.js #is refused the save 403 permission_missing 10 Default selection respects document and order precedence edge unit proposed
Proves BR-CAP-ACC-BAT-011-12Preconditions One document is pro forma and another references an Open order batch. Steps Resolve each default, close the order batch and resolve again. Expected Pro forma has no batch; the Open order batch wins before assignment; closing it restores assignment selection. Data Provide fixtures appropriate to the stated accounting context. Source services-accounting:modules/batches/services/rules/batch-rules.ts :defaultBatchOf 13 Criteria vocabulary rejects repeated values validation api negative proposed
Proves BR-CAP-ACC-BAT-011-06Preconditions Routing already contains one saved rule. Steps Replace it with criteria containing a repeated payment type and then an unknown card type. Expected Both saves return validation refusals and the previous routing list remains unchanged. Data Owned records in an isolated workspace with the stated calendar and accounting setup. Source services-accounting:modules/batches/tests/e2e/batch-assignment-settings.e2e.spec.js #answers 400 to a transaction type the vocabulary does not have ← Previous Capability Test Specification ATS-ACC-BAT-010 · Advance a scheduled stream and post its predecessor: Capability Test Specification Next Capability Test Specification → ATS-ACC-BAT-012 · Inspect posting readiness before submission: Capability Test Specification