--- id: ATS-ACC-BKS-018 scope: CAP-ACC-BKS-018 product_area: accounting module: books revision: 2 status: proposed approved_by: null approved_at: null source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f scenarios: - id: ATS-ACC-BKS-018-01 title: Describe upcoming local occurrences level: api proves: - BR-CAP-ACC-BKS-018-01 preconditions: A New York weekday schedule runs at nine. steps: Preview it with a fixed reference and with the current time. expected: >- The response describes timing and five weekday instants/local times without problems. negative: false data_needs: The setup needs no extra fixture records. bound_to: - TST-ACC-BKS-177 provenance: test source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers 200 with the sentence it reads as, and neither problems nor warnings category: rule binding_evidence: - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers 200 with the sentence it reads as, and neither problems nor warnings - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers the next five runs, skipping the weekend, each as the instant and the local time - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers only weekdays - id: ATS-ACC-BKS-018-02 title: Fill the omitted time zone level: api proves: - BR-CAP-ACC-BKS-018-02 preconditions: The workspace uses Chicago time. steps: Preview without a zone. expected: Occurrences use nine on the Chicago clock. negative: false data_needs: The setup needs no extra fixture records. bound_to: - TST-ACC-BKS-177 provenance: test source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#reads it in the tenant’s zone from platform.tenants category: rule binding_evidence: - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#reads it in the tenant’s zone from platform.tenants - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers its runs at 9 AM on Chicago’s clock - id: ATS-ACC-BKS-018-03 title: Report impossible and excessive recurrence level: api proves: - BR-CAP-ACC-BKS-018-03 preconditions: Definitions include no weekly weekdays and an hourly interval. steps: 'Preview both, imposing a daily minimum on the hourly case.' expected: >- Problems are returned; the impossible definition has no description or runs. negative: true data_needs: The setup needs no extra fixture records. bound_to: - TST-ACC-BKS-177 provenance: test source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers a weekly schedule on no weekday as a problem, with no sentence and no runs category: validation binding_evidence: - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers a weekly schedule on no weekday as a problem, with no sentence and no runs - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers the same hourly schedule as a problem when asked about a minimum interval of a day - id: ATS-ACC-BKS-018-04 title: Authorize history through its subject level: api proves: - BR-CAP-ACC-BKS-018-04 preconditions: The schedule belongs to a recurring batch and has runs. steps: Read history with subject-read access and with application access only. expected: The subject reader succeeds and the access-only caller receives a refusal. negative: true data_needs: The setup needs no extra fixture records. bound_to: - TST-ACC-BKS-177 provenance: test source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers the runs to a caller who may read recurring batches category: permission binding_evidence: - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers the runs to a caller who may read recurring batches - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers 403 to a caller who may open Accounting but not read the recurring batch the schedule belongs to - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers 403 to a caller holding only accounting.application.access - id: ATS-ACC-BKS-018-05 title: Claim safely and pause repeated failures level: api proves: - BR-CAP-ACC-BKS-018-05 - BR-CAP-ACC-BKS-018-06 - BR-CAP-ACC-BKS-018-07 - INV-DOM-ACC-BKS-006-06 preconditions: >- Due and disabled schedules, the spring gap and a repeatedly failing roll are prepared. steps: 'Race dispatchers, process the gap and run five failures.' expected: >- One claim is made, disabled work is skipped, the tested gap shifts to 3:30 locally and the fifth failure pauses work. negative: false data_needs: The setup needs no extra fixture records. bound_to: - TST-ACC-BKS-187 provenance: test source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#is claimed exactly once category: concurrency binding_evidence: - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#is claimed exactly once - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#is never claimed - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#runs once, at 03:30 local (07:30 UTC), the first instant after the gap - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#dates the batch the 9th, the local date of the roll - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses the schedule after the fifth failure in a row - id: ATS-ACC-BKS-018-06 title: Maintain owned timing and history level: api proves: - BR-CAP-ACC-BKS-018-10 preconditions: An owner’s schedule already has run records. steps: 'Submit invalid timing, make a valid change and delete the schedule.' expected: >- Validation refuses invalid timing, valid change updates its next occurrence and deletion removes its runs. negative: false data_needs: Isolated fixture records matching this scenario’s setup. bound_to: [] provenance: proposed source: 'services-accounting:modules/maintenance/services/persistence/schedules.ts' category: transition binding_evidence: [] - id: ATS-ACC-BKS-018-07 title: Resume and exhaust owned scheduling category: transition level: api proves: - BR-CAP-ACC-BKS-018-10 - INV-DOM-ACC-BKS-006-06 preconditions: >- Run-owned subjects have disabled, paused and finite enabled schedules with history. steps: >- Use independent fixtures to enable disabled and paused schedules and exhaust a finite enabled recurrence. Separately remove schedules while each is enabled, paused, disabled or ended and read their former history. expected: >- The referenced lifecycle determines next occurrences and standing, and deletion removes the corresponding history. negative: false data_needs: >- Run-owned records for the stated setup; retain the initial values for comparison. bound_to: [] provenance: proposed source: >- specs/accounting/books/design/state-models/STATE-ACC-BKS-004-schedule-lifecycle.md:transitions state_model: STATE-ACC-BKS-004 transitions: - - disabled - enabled - - paused - enabled - - enabled - ended - - enabled - deleted - - paused - deleted - - disabled - deleted - - ended - deleted binding_evidence: [] - id: ATS-ACC-BKS-018-08 title: Run-history page-size endpoints category: boundary level: api proves: - BR-CAP-ACC-BKS-018-08 preconditions: >- An isolated workspace has records needed for both eligible and ineligible examples. steps: 'Request history at limits one, two hundred and two hundred and one.' expected: >- Eligible limits return bounded newest-first pages and the excessive limit is refused. negative: true data_needs: >- Run-owned records for the stated setup; retain the initial values for comparison. bound_to: [] provenance: proposed source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers the newest runs first, as many as the limit, every property of each binding_evidence: [] - id: ATS-ACC-BKS-018-09 title: A scheduled roll records its resolved period category: interaction level: api proves: - BR-CAP-ACC-BKS-018-06 - BR-CAP-ACC-BKS-010-02 preconditions: >- Run-owned records satisfy the preconditions of the referenced capability proofs. steps: >- Execute a due local-day roll with generated coverage and inspect its batch date, year, period and history. expected: >- The batch and run record agree with the period selected for the occurrence local day. negative: false data_needs: >- Run-owned records for the stated setup; retain the initial values for comparison. bound_to: - TST-ACC-BKS-187 provenance: test source: - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#runs once, at 03:30 local (07:30 UTC), the first instant after the gap - >- services-accounting:modules/books/tests/e2e/fiscal-years.e2e.spec.js#answers 404 to the day after the last year, generating nothing exercises: - CAP-ACC-BKS-018 - CAP-ACC-BKS-010 workflows: - WF-ACC-BKS-008 binding_evidence: - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#dates the batch the 9th, the local date of the roll - id: ATS-ACC-BKS-018-10 title: Keep one occurrence identity through unfinished-run redelivery category: invariant level: api proves: - INV-DOM-ACC-BKS-006-05 - BR-CAP-ACC-BKS-018-05 preconditions: >- A run-owned occurrence is claimed and its handler has not recorded a terminal outcome. steps: >- Interrupt the handler before completion and redeliver the same run message. Repeat with duplicate deliveries and inspect stored run identities and recorded handler attempts. expected: >- The occurrence retains one stored run identity; the recorded attempts expose any repeated work without treating claim uniqueness as exactly-once handler execution. negative: true data_needs: >- An isolated due schedule, recording publisher, separate consumer invocations and a handler with a controlled interruption point. bound_to: [] provenance: proposed source: >- specs/accounting/books/design/objects/DOM-ACC-BKS-006-accounting-workspace.md:INV-DOM-ACC-BKS-006-05 binding_evidence: [] finding: FND-ACC-BKS-079 evidence: - >- Verified source file: services-accounting:modules/maintenance/services/persistence/schedules.ts - >- Verified source file: services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js - >- Verified source file: services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js product_intent: proposed state_transition_coverage: - state_model: STATE-ACC-BKS-004 from: absent to: enabled trigger: Save an enabled schedule provenance: observed source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:createOwnedSchedule scenarios: [] gap: FND-ACC-BKS-079 - state_model: STATE-ACC-BKS-004 from: absent to: disabled trigger: Save a disabled schedule provenance: test source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#has no next run (the premise) scenarios: [] gap: FND-ACC-BKS-079 - state_model: STATE-ACC-BKS-004 from: enabled to: enabled trigger: Claim work or save a changed definition provenance: test source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#runs next at 06:15 the following morning after it scenarios: - ATS-ACC-BKS-018-06 - state_model: STATE-ACC-BKS-004 from: enabled to: paused trigger: Pause after the fifth recorded failure provenance: test source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses the schedule after the fifth failure in a row scenarios: - ATS-ACC-BKS-018-05 - state_model: STATE-ACC-BKS-004 from: enabled to: disabled trigger: Disable future scheduling provenance: test source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#is never claimed scenarios: [] gap: FND-ACC-BKS-079 - state_model: STATE-ACC-BKS-004 from: disabled to: enabled trigger: Enable a disabled schedule provenance: inferred source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:updateOwnedSchedule scenarios: - ATS-ACC-BKS-018-07 - state_model: STATE-ACC-BKS-004 from: paused to: enabled trigger: Enable a paused schedule provenance: inferred source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:updateOwnedSchedule scenarios: - ATS-ACC-BKS-018-07 - state_model: STATE-ACC-BKS-004 from: enabled to: ended trigger: Exhaust the recurrence provenance: inferred source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:ScheduleSummary scenarios: - ATS-ACC-BKS-018-07 - state_model: STATE-ACC-BKS-004 from: enabled to: deleted trigger: Remove an enabled schedule provenance: observed source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:deleteSchedule scenarios: - ATS-ACC-BKS-018-07 - state_model: STATE-ACC-BKS-004 from: paused to: deleted trigger: Remove a paused schedule provenance: observed source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:deleteSchedule scenarios: - ATS-ACC-BKS-018-07 - state_model: STATE-ACC-BKS-004 from: disabled to: deleted trigger: Remove a disabled schedule provenance: observed source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:deleteSchedule scenarios: - ATS-ACC-BKS-018-07 - state_model: STATE-ACC-BKS-004 from: ended to: deleted trigger: Remove an ended schedule provenance: observed source: >- services-accounting:modules/maintenance/services/persistence/schedules.ts:deleteSchedule scenarios: - ATS-ACC-BKS-018-07 - state_model: STATE-ACC-BKS-004 from: enabled to: paused trigger: Pause an invalid saved definition provenance: observed source: >- services-accounting:modules/maintenance/aws/lambda/DISPATCHER.ts:handler; services-accounting:package-lock.json scenarios: [] gap: FND-ACC-BKS-079 coverage: rule: covered transition: covered validation: covered permission: covered edge: 'gap: FND-ACC-BKS-079' failure: 'gap: FND-ACC-BKS-079' boundary: covered concurrency: covered invariant: 'gap: FND-ACC-BKS-079' interaction: covered coverage_notes: rule: scenarios: - ATS-ACC-BKS-018-01 - ATS-ACC-BKS-018-02 provenance: documented source: - ATS-ACC-BKS-018-01 - ATS-ACC-BKS-018-02 transition: scenarios: - ATS-ACC-BKS-018-06 - ATS-ACC-BKS-018-07 provenance: documented source: - ATS-ACC-BKS-018-06 - ATS-ACC-BKS-018-07 validation: scenarios: - ATS-ACC-BKS-018-03 provenance: documented source: - ATS-ACC-BKS-018-03 permission: scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: - ATS-ACC-BKS-018-04 edge: scenarios: [] provenance: unknown source: FND-ACC-BKS-079 reason: >- No scenario isolates this category for the capability at the pinned revision. gap: FND-ACC-BKS-079 failure: scenarios: [] provenance: unknown source: FND-ACC-BKS-079 reason: >- No scenario isolates this category for the capability at the pinned revision. gap: FND-ACC-BKS-079 boundary: scenarios: - ATS-ACC-BKS-018-08 provenance: documented source: - ATS-ACC-BKS-018-08 concurrency: scenarios: - ATS-ACC-BKS-018-05 provenance: documented source: - ATS-ACC-BKS-018-05 invariant: scenarios: - ATS-ACC-BKS-018-10 provenance: unknown source: FND-ACC-BKS-079 reason: >- No scenario isolates this category for the capability at the pinned revision. gap: FND-ACC-BKS-079 interaction: scenarios: - ATS-ACC-BKS-018-09 provenance: documented source: - ATS-ACC-BKS-018-09 rule_coverage: - rule: BR-CAP-ACC-BKS-018-01 scenarios: - ATS-ACC-BKS-018-01 provenance: documented source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers the next five runs, skipping the weekend, each as the instant and the local time - rule: BR-CAP-ACC-BKS-018-02 scenarios: - ATS-ACC-BKS-018-02 provenance: documented source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#reads it in the tenant’s zone from platform.tenants - rule: BR-CAP-ACC-BKS-018-03 scenarios: - ATS-ACC-BKS-018-03 provenance: documented source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers the same hourly schedule as a problem when asked about a minimum interval of a day - rule: BR-CAP-ACC-BKS-018-04 scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers 403 to a caller who may open Accounting but not read the recurring batch the schedule belongs to - rule: BR-CAP-ACC-BKS-018-05 scenarios: - ATS-ACC-BKS-018-05 provenance: documented source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#is claimed exactly once - rule: BR-CAP-ACC-BKS-018-06 scenarios: - ATS-ACC-BKS-018-05 - ATS-ACC-BKS-018-09 provenance: documented source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#runs once, at 03:30 local (07:30 UTC), the first instant after the gap - rule: BR-CAP-ACC-BKS-018-07 scenarios: - ATS-ACC-BKS-018-05 provenance: documented source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses the schedule after the fifth failure in a row - rule: BR-CAP-ACC-BKS-018-10 scenarios: - ATS-ACC-BKS-018-06 - ATS-ACC-BKS-018-07 provenance: documented source: 'services-accounting:modules/maintenance/services/persistence/schedules.ts' related_coverage: - capability: CAP-ACC-BKS-010 scenarios: - ATS-ACC-BKS-018-09 provenance: documented source: >- specs/accounting/books/planning/capabilities/CAP-ACC-BKS-018-run-accountings-scheduled-work-on-time-and-show-what-it-ran.md workflow_coverage: - workflow: WF-ACC-BKS-008 interactions: - ATS-ACC-BKS-018-09 provenance: documented source: >- specs/accounting/books/design/workflows/WF-ACC-BKS-008-dispatch-and-run-scheduled-accounting-work.md gap: FND-ACC-BKS-079 coverage_interpretation: >- Covered means a specified scenario exists. Proposed scenarios and registered bindings do not establish a passed run or verified conformance. invariant_coverage: - invariant: INV-DOM-ACC-BKS-006-01 scenarios: - ATS-ACC-BKS-012-01 - ATS-ACC-BKS-012-02 provenance: documented source: >- services-accounting:modules/books/tests/integration/services/persistence/payment-methods.integration.spec.js#refuses to be deactivated, 409 payment_method_system - invariant: INV-DOM-ACC-BKS-006-02 scenarios: - ATS-ACC-BKS-012-03 - ATS-ACC-BKS-012-04 provenance: documented source: >- services-accounting:modules/books/tests/integration/services/persistence/payment-methods.integration.spec.js#refuses an offline method offered in the portal, naming the rule - invariant: INV-DOM-ACC-BKS-006-03 scenarios: - ATS-ACC-BKS-011-03 - ATS-ACC-BKS-013-06 provenance: documented source: >- services-accounting:modules/books/tests/integration/services/persistence/tax-classes.integration.spec.js#translates the refusal of each restrict foreign key to a tax class into a 409 naming it, the invoice lines among them - invariant: INV-DOM-ACC-BKS-006-04 scenarios: - ATS-ACC-BKS-017-01 provenance: documented source: >- services-accounting:modules/books/db/settings.table.ts:settings_template_references_trigger - invariant: INV-DOM-ACC-BKS-006-05 scenarios: - ATS-ACC-BKS-018-10 provenance: documented source: >- services-accounting:modules/maintenance/db/schedules.table.ts; services-accounting:modules/maintenance/aws/lambda/CONSUMER.ts:handler; services-accounting:package-lock.json - invariant: INV-DOM-ACC-BKS-006-06 scenarios: - ATS-ACC-BKS-018-05 - ATS-ACC-BKS-018-07 provenance: documented source: >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses the schedule after the fifth failure in a row - invariant: INV-DOM-ACC-BKS-006-07 scenarios: - ATS-ACC-BKS-019-04 provenance: documented source: >- services-accounting:modules/maintenance/tests/integration/db/declaration-completeness.integration.spec.js#leaves no tenant-keyed table undeclared - invariant: INV-DOM-ACC-BKS-006-08 scenarios: - ATS-ACC-BKS-019-05 provenance: documented source: >- services-accounting:modules/maintenance/tests/integration/services/exports/seed-everything.integration.spec.js#stops a batch whose record carries a Stripe secret’s shape, blocked with nothing staged - invariant: INV-DOM-ACC-BKS-006-09 scenarios: - ATS-ACC-BKS-019-06 provenance: documented source: >- services-accounting:modules/maintenance/tests/unit/lifecycle/tenant-availability.spec.js#serves only an active tenant that is not disabled, and refuses every other combination permission_coverage: - key: accounting.application.access where_checked: api scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: >- specs/accounting/books/planning/capabilities/CAP-ACC-BKS-018-run-accountings-scheduled-work-on-time-and-show-what-it-ran.md - key: accounting.recurring-batches.read where_checked: service scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: >- specs/accounting/books/planning/capabilities/CAP-ACC-BKS-018-run-accountings-scheduled-work-on-time-and-show-what-it-ran.md - key: accounting.batches.read where_checked: service scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: >- specs/accounting/books/planning/capabilities/CAP-ACC-BKS-018-run-accountings-scheduled-work-on-time-and-show-what-it-ran.md - key: accounting.reconciliation-batches.read where_checked: service scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: >- specs/accounting/books/planning/capabilities/CAP-ACC-BKS-018-run-accountings-scheduled-work-on-time-and-show-what-it-ran.md - key: accounting.reconciliation-exceptions.read where_checked: service scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: >- specs/accounting/books/planning/capabilities/CAP-ACC-BKS-018-run-accountings-scheduled-work-on-time-and-show-what-it-ran.md - key: accounting.recurring-billing-runs.read where_checked: service scenarios: - ATS-ACC-BKS-018-04 provenance: documented source: >- specs/accounting/books/planning/capabilities/CAP-ACC-BKS-018-run-accountings-scheduled-work-on-time-and-show-what-it-ran.md reviewed_at: '2026-10-23' --- # Preview, run and review scheduled Accounting work: Capability Test Specification ## Coverage - Describe upcoming local occurrences. - Fill the omitted time zone. - Report impossible and excessive recurrence. - Authorize history through its subject. - Claim safely and pause repeated failures. - Claim safely and pause repeated failures. - Claim safely and pause repeated failures. - Maintain owned timing and history. The structured coverage map distinguishes specified examples from remaining findings. Proposed examples require executable proof before qualification. ## Interactions With Related Capabilities - A scheduled roll records its resolved period. Related-capability and workflow references identify the seams each scenario exercises. The lifecycle coverage record retains transitions that still need individual proof. The occurrence identity also has a proposed redelivery example; no single-execution promise is inferred from claim uniqueness. ## Binding Review The pinned service and browser assertions support the registered bindings. Original test references remain beside each scenario so partial evidence and unresolved conformance remain reviewable.