The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | postBatches | Submit October’s invoices and November’s payments together. | CAP-ACC-BAT-013 | October reports the missing product revenue account and affected line; November reports its dependency and neither writes entries. | test |
| 2 | /console/{tenantId}/accounting/batches/{batchId} (Validation card) | Inspect the source collection’s validation result. | CAP-ACC-BAT-012 | The generation preview identifies the same account problem as posting. | test services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#names the same reason in the preview |
| 3 | /console/{tenantId}/configuration/accounting/products (the product's accounting setup, Products module) | Have an administrator supply the missing product revenue account. | CAP-ACC-BAT-014 | The new configuration is available without changing existing posted results. | test |
| 4 | /console/{tenantId}/accounting/batches/{batchId} (More Actions › Reopen) | Reopen the source collection to include a forgotten document. | CAP-ACC-BAT-004 | October becomes Open and its old errors clear. | test services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#clears the errors of an errored batch on reopen, so the open batch carries none (journey ACT-ACC-0521) |
| 5 | getDependentBatches (the readiness line) | Look up collections downstream of October. | CAP-ACC-BAT-002 | The dependency result includes the errored November collection. | observed services-accounting:modules/batches/services/persistence/batches.ts#dependentBatchesOf |
| 6 | postBatches | Submit both collections again. | CAP-ACC-BAT-015 | The source completes before its dependent, using the configured revenue account and source receivable. | test |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 4 | The source needs no additional document. | Retry accounting directly after correcting configuration. | The Error batch completes without a separate reopening. | test services-accounting:modules/batches/tests/unit/rules/batch-repost-rules.spec.js#ends posted with no errors when the second posting succeeds |
| failure | 6 | Another generation prerequisite is still missing. | The repeated attempt records only its current failure reasons. | Staff correct the remaining prerequisite before another submission. | test services-accounting:modules/batches/tests/unit/rules/batch-repost-rules.spec.js#ends error with the new errors alone when the second posting fails too |
| Id | Statement | Provenance |
|---|---|---|
01 | A failed collection retains neither partial entries nor frozen account snapshots. | test services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#leaves nothing partially posted: no entry, no snapshot, the documents issued and unposted |
02 | A dependent collection identifies the failed prerequisite when it cannot complete. | test |
03 | After configuration is corrected, both collections complete without old errors using the accounts resolved at posting. | test services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#posts both once the gala product is configured and the batch posted again |
End-to-end policy: required: Browser acceptance is required to show how staff investigate a generation failure, correct configuration and complete dependent work.