---
id: TST-ACC-CLS-038
title: Carried batch closing checks
kind: unit
product_area: accounting
module: close
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/fiscal-close/tests/unit/carried/fiscal-years/logic/validate-period-closing-batches.spec.js
implements:
  - ATS-ACC-CLS-005-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: The suite owns in-memory inputs and declaration fixtures.
binding_policy: >-
  Each binding identifies the assertions this suite executes; combined scenarios
  may require other bound suites. Existence is not a recorded execution result.
evidence:
  - >-
    services-accounting:modules/fiscal-close/tests/unit/carried/fiscal-years/logic/validate-period-closing-batches.spec.js
  - provenance: test
    source: >-
      services-accounting:modules/fiscal-close/tests/unit/carried/fiscal-years/logic/validate-period-closing-batches.spec.js
    assertion_titles:
      - 'Validate Period Closing (batches, on the readiness engine)'
      - should throw an error if batches are open
      - '2.0: is blocked by the archived batch of 1.0\'
      - '2.0: passes when every batch is posted or downloaded'
real_dependencies: >-
  The suite calls pure rules, mappings or declarations with supplied inputs and
  test contexts. No deployed workflow is exercised.
product_intent: proposed
implementation_evidence: observed
---
# Carried batch closing checks

## Verification Boundary

The suite exercises pure rules, mappings or declarations with supplied inputs. It checks those functions directly rather than executing a complete close.

## What This Suite Proves

The carried assertions compare batch states and close-owned exclusions while retaining the newer refusal of archived ordinary batches.

## What It Does Not Prove

This register records assertion scope without claiming a passing run or complete coverage of every rule and scenario variant.

## Real Dependencies and Test Doubles

The suite calls pure rules, mappings or declarations with supplied inputs and test contexts. No deployed workflow is exercised.

## Must Not Be Doubled

Run the production rule, mapper or declaration being asserted. Supplied inputs are appropriate here; they do not establish database, public API or deployed workflow behavior.