---
id: TST-ACC-TRX-043
title: As of 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/invoices/as-of.integration.spec.js
implements:
  - ATS-ACC-TRX-020-06
implements_parts:
  - scenario: ATS-ACC-TRX-020-06
    assertion: >-
      it answers, as of today and known now, exactly the live balance of every
      open invoice (FC-07)
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/invoices/as-of.integration.spec.js#it
      answers, as of today and known now, exactly the live balance of every open
      invoice (FC-07)
  - scenario: ATS-ACC-TRX-020-06
    assertion: it does not see the credit recorded after the instant it is known at
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/invoices/as-of.integration.spec.js#it
      does not see the credit recorded after the instant it is known at
  - scenario: ATS-ACC-TRX-020-06
    assertion: >-
      it sees, between the write-off and its reversal, both the credit and the
      write-off
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/invoices/as-of.integration.spec.js#it
      sees, between the write-off and its reversal, both the credit and the
      write-off
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/invoices/as-of.integration.spec.js
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/invoices/as-of.integration.spec.js
    assertion_titles:
      - the receivable as of a date against the live balances (integration)
      - >-
        leaves three invoices open, at the balances the ledgers made (the
        premise)
      - >-
        answers, as of today and known now, exactly the live balance of every
        open invoice (FC-07)
      - >-
        sums the facts of today, known now, to the sum of the live balances
        (FC-07)
      - does not see the credit recorded after the instant it is known at
      - 'sees, as of a date before the credits, the invoices as issued'
      - >-
        sees, between the write-off and its reversal, both the credit and the
        write-off
    imports:
      - >-
        const { fixedClock } =
        require('@rhythmsoftware/macroservice-time/clock');
      - 'const { stage } = require(''@rhythmsoftware/macroservice-testing/stage'');'
      - >-
        const { createDraft } =
        require('../../../../services/invoices/invoice-drafts');
      - >-
        const { issueInvoice } =
        require('../../../../services/invoices/invoice-issue');
      - >-
        const { voidInvoice } =
        require('../../../../services/invoices/invoice-changes');
      - >-
        const { listInvoices } =
        require('../../../../services/persistence/invoices');
      - >-
        const { listOpenItemsAsOf, sumReceivableEventsAsOf } =
        require('../../../../services/persistence/receivable-events');
      - '} = require(''../../invoices-fixtures'');'
      - "\t\tconst { a, b, d } = history.require();"
      - "\t\thistory.require();"
      - "\t\thistory.require();"
      - "\t\tconst { a, b, d } = history.require();"
      - "\t\tconst { a, b, c, d } = history.require();"
      - "\t\tconst { a } = history.require();"
    test_double_declarations: []
---

# As of 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

Its cited assertions contribute evidence for known-time history matches current and former balances. The structured assertion bindings identify which parts of combined scenarios it executes.

## 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.