---
id: TST-ACC-REC-088
title: Outstanding standing at a requested day
kind: unit
product_area: accounting
module: reconciliation
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - modules/reconciliation/tests/unit/rules/outstanding-state.spec.js
implements:
  - ATS-ACC-REC-006-01
  - ATS-ACC-REC-006-02
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Suite-owned workspace fixtures and deterministic records removed by suite cleanup.
evidence:
  - 'services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js'
bindings:
  - scenario: ATS-ACC-REC-006-01
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is resolved when
        the item has a resolution, even with a finalized claim
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is settled when
        its active claim is finalized, even long overdue
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is in an open
        reconciliation when its active claim is open, even long overdue
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is not yet
        eligible with no eligible date
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is held with no
        expected settlement date, however late
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is under
        investigation with an open exception
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is accepted with
        an accepted exception
  - scenario: ATS-ACC-REC-006-02
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is late the day
        after its expected date, over the weekend
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is late on the
        last day of the grace
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is overdue the
        day after the grace ends
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/outstanding-state.spec.js#is still late on
        the Tuesday when the grace runs over Columbus Day
---

# Outstanding standing at a requested day

## Verification Boundary

This suite evaluates the production rules or declarations with controlled inputs. It does not perform a complete financial workflow.

## What This Suite Proves

The executable assertions identified in the binding records supply the registered scenario observations. When a scenario names several suites, this suite supplies its listed assertions and does not independently establish every clause.

## What It Does Not Prove

Database enforcement, API authorization, console behavior and deployed workflow completion require separate suites.

## Real Dependencies and Test Doubles

Production rules and declarations are real; fixtures supply literal amounts, dates and permission sets. No live database or deployed service participates.

## Must Not Be Doubled

The rule or declaration under examination remains production code; expected results remain independent literal observations.