---
id: TST-ACC-BAT-094
title: Batch integration subledger entries.queries
kind: integration
product_area: accounting
module: batches
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js
implements:
  - ATS-ACC-BAT-016-02
  - ATS-ACC-BAT-018-02
  - ATS-ACC-BAT-018-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 its test workspace or fixed integration fixtures in the
  prepared local database.
assertion_sources:
  - scenario: ATS-ACC-BAT-016-02
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#lists
      no entry when history is asked for either: nothing is written as a
      reversal
  - scenario: ATS-ACC-BAT-018-02
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#lists
      the entries holding a line of the G/L account, and none for an account
      they do not hold
  - scenario: ATS-ACC-BAT-018-02
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#lists
      the entries of the business unit within the dates, and none outside them
  - scenario: ATS-ACC-BAT-018-02
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#pages
      the list with a limit and an offset
  - scenario: ATS-ACC-BAT-018-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#lists
      no current entry of the batch once it is unposted
  - scenario: ATS-ACC-BAT-018-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#lists
      no entry when history is asked for either: nothing is written as a
      reversal
  - scenario: ATS-ACC-BAT-018-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#reads
      the posting's original entries only, by id, with their lines, once it is
      reversed
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js
    note: >-
      The executable file is inspected at the pinned revision; duration is an
      unmeasured planning estimate.
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/persistence/subledger-entries.queries.integration.spec.js#suite
      header
    note: >-
      Real: the integration database, the posting, the persistence services.
      Doubled: none.
unbound_scope: null
---

# Batch integration subledger entries.queries

## Verification Boundary

This suite exercises the imported batch services or storage against the prepared local database. It does not imply that a deployed workflow is contacted.

## What This Suite Proves

Ledger filters, ordered detail, history options and workspace absence are checked against stored entries. The assertion anchors identify the supported portions of the bound scenarios.

## What It Does Not Prove

Local assertions do not establish deployment configuration, remote delivery guarantees, or unasserted lifecycle and concurrency paths.

## Real Dependencies and Test Doubles

PostgreSQL and the exercised persistence or accounting functions are real. Controlled clocks, imported test fixtures and any suite-specific doubles delimit the asserted behavior.

## Must Not Be Doubled

The database constraints, transaction boundaries and exercised accounting functions must remain real when qualifying the asserted persistence or generation behavior.