---
id: TST-ACC-TRX-083
title: Ar snapshot items queries suite
kind: integration
product_area: accounting
module: transactions
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/transactions/tests/integration/services/persistence/ar-snapshot-items.queries.integration.spec.js
implements: []
implements_parts: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Suite-marked records in the prepared local test database; fixture teardown
  removes owned records.
provenance: test
source: >-
  services-accounting:modules/transactions/tests/integration/services/persistence/ar-snapshot-items.queries.integration.spec.js
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/persistence/ar-snapshot-items.queries.integration.spec.js
    assertion_titles:
      - the A/R snapshot items’ reads (integration)
      - countOpenItems
      - counts the four open items at September’s end as known then
      - counts none before the first fact was recorded
      - counts none of another tenant’s items
      - tallyArSnapshotItems
      - >-
        answers the run’s items per business unit and currency, the balance as
        exact text
      - answers nothing for a run of another tenant
      - listArSnapshotItemCheckFailures
      - finds no failure in the published run
      - >-
        names the misfiled item, the zero balance, the negative invoice and the
        reversal credit whose credit is not in the run
      - listPublishedArAgingItems
      - answers every column of a published item
      - >-
        answers an unapplied item with no due date, no days past due and its
        negative balance
      - pages in kind and id order after the cursor
      - answers one business unit’s items only
      - >-
        answers nothing for a run that is not the published version, though its
        rows exist
      - answers nothing after a cursor naming no item kind
      - answers none of the run to another tenant
    imports:
      - 'const { randomUUID } = require(''node:crypto'');'
      - 'const { sql } = require(''drizzle-orm'');'
      - 'const { stage } = require(''@rhythmsoftware/macroservice-testing/stage'');'
      - '} = require(''../../../../services/persistence/ar-snapshot-items'');'
      - '} = require(''../../ar-aging-fixtures'');'
      - "\t\t\tarranging.require();"
      - "\t\t\tarranging.require();"
      - "\t\t\tarranging.require();"
      - "\t\t\tconst { run } = arranging.require();"
      - "\t\t\tconst { run } = arranging.require();"
      - "\t\t\tconst { run } = arranging.require();"
      - "\t\t\tconst { planted } = arranging.require();"
      - "\t\t\tconst { run, world } = arranging.require();"
      - "\t\t\tconst { run, world } = arranging.require();"
      - "\t\t\tconst { run } = arranging.require();"
      - "\t\t\tconst { run } = arranging.require();"
      - "\t\t\tconst { planted } = arranging.require();"
      - "\t\t\tconst { run } = arranging.require();"
      - "\t\t\tconst { run } = arranging.require();"
    test_double_declarations: []
---

# Ar snapshot items queries suite

## Verification Boundary

The suite exercises transaction commands and database protections in the local prepared test environment. Registration records the existing executable file; it does not report a run or establish product approval.

## What This Suite Proves

The executable assertions exercise this module, but no capability or feature scenario binding is established for this file. Its individual assertion titles remain in the evidence register for subsequent mapping.

## What It Does Not Prove

Local commands and route invocations do not establish deployed routing, live processor guarantees or the complete staff browser experience. An unbound feature chain remains proposed, and this registration carries no execution result.

## Real Dependencies and Test Doubles

The suite uses the imported commands, route handlers or persistence code against the local test database. Fixture helpers supply accounting context; any stepped clock, dummy processor or substituted external client is retained in the evidence declarations.

## Must Not Be Doubled

The command or persistence behavior under assertion and its relevant database protections must remain real. Substituting the final financial result removes evidence of transactional effects.