---
id: TST-ACC-BKS-177
title: Schedules API suite
kind: api-lifecycle
product_area: accounting
module: books
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-accounting
files:
  - modules/maintenance/tests/e2e/schedules.e2e.spec.js
implements:
  - ATS-ACC-BKS-018-01
  - ATS-ACC-BKS-018-02
  - ATS-ACC-BKS-018-03
  - ATS-ACC-BKS-018-04
  - FAS-ACC-BKS-06-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  The suite owns isolated workspace identities and database fixtures; cleanup
  removes only its seeded records.
assertion_bindings:
  - scenario: ATS-ACC-BKS-018-01
    source: >-
      services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers
      200 with the sentence it reads as, and neither problems nor warnings
  - scenario: ATS-ACC-BKS-018-01
    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
  - scenario: ATS-ACC-BKS-018-01
    source: >-
      services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers
      only weekdays
  - scenario: ATS-ACC-BKS-018-02
    source: >-
      services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#reads
      it in the tenant’s zone from platform.tenants
  - scenario: ATS-ACC-BKS-018-02
    source: >-
      services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers
      its runs at 9 AM on Chicago’s clock
  - scenario: ATS-ACC-BKS-018-03
    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
  - scenario: ATS-ACC-BKS-018-03
    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
  - scenario: ATS-ACC-BKS-018-04
    source: >-
      services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers
      the runs to a caller who may read recurring batches
  - scenario: ATS-ACC-BKS-018-04
    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
  - scenario: ATS-ACC-BKS-018-04
    source: >-
      services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers
      403 to a caller holding only accounting.application.access
  - scenario: FAS-ACC-BKS-06-04
    source: >-
      services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers
      403 to a caller holding only accounting.application.access
unmapped: false
evidence:
  - provenance: test
    source: 'services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js'
execution_notes: >-
  The file exists at the pinned revision; this registration records no execution
  result.
---

# Schedules API suite

## Verification Boundary

The suite sends requests through the local Accounting handler and enforcing route dispatcher. PostgreSQL stores the run-owned configuration and applies its database safeguards.

## What This Suite Proves

The individual assertion references identify the acceptance outcomes this file exercises. When a scenario spans several suites, this file supplies only its listed assertions; qualification must include the other bindings and any recorded coverage finding.

## What It Does Not Prove

Local database execution does not prove deployed infrastructure, external provider availability or console behavior. No result is claimed for the pinned revision until the suite runs and its evidence is reviewed.

## Real Dependencies and Test Doubles

PostgreSQL, migrations and the exercised persistence paths are real. Test-owned execution contexts, clocks and local Platform records supply deterministic setup; the file’s imports and fixtures identify any additional doubles.

## Must Not Be Doubled

The database constraints, transaction paths and production persistence functions named by the assertions must remain real. A memory store cannot establish the recorded database proof.