---
id: TST-ACC-BKS-168
title: Fiscal Year Rules rule suite
kind: unit
product_area: accounting
module: books
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-accounting
files:
  - modules/books/tests/unit/fiscal-year-rules.spec.js
implements:
  - ATS-ACC-BKS-009-02
  - ATS-ACC-BKS-009-03
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Each example owns its input values and configured doubles.
assertion_bindings:
  - scenario: ATS-ACC-BKS-009-02
    source: >-
      services-accounting:modules/books/tests/unit/fiscal-year-rules.spec.js#names
      the year by its calendar year alone
  - scenario: ATS-ACC-BKS-009-02
    source: >-
      services-accounting:modules/books/tests/unit/fiscal-year-rules.spec.js#names
      the year by both calendar years it spans
  - scenario: ATS-ACC-BKS-009-02
    source: >-
      services-accounting:modules/books/tests/unit/fiscal-year-rules.spec.js#gives
      the year twelve monthly periods from January to December
  - scenario: ATS-ACC-BKS-009-02
    source: >-
      services-accounting:modules/books/tests/unit/fiscal-year-rules.spec.js#suffixes
      the year name with the two-digit period number
  - scenario: ATS-ACC-BKS-009-03
    source: >-
      services-accounting:modules/books/tests/unit/fiscal-year-rules.spec.js#refuses
      a year starting a month after the same calendar day five years ahead
      (ACCT-M1 D10.2)
  - scenario: ATS-ACC-BKS-009-03
    source: >-
      services-accounting:modules/books/tests/unit/fiscal-year-rules.spec.js#limits
      the 29th of February to the 28th of February five years on, unless that
      year is a leap year
unmapped: false
evidence:
  - provenance: test
    source: 'services-accounting:modules/books/tests/unit/fiscal-year-rules.spec.js'
execution_notes: >-
  The file exists at the pinned revision; this registration records no execution
  result.
---

# Fiscal Year Rules rule suite

## Verification Boundary

The suite evaluates books configuration logic directly. Its boundary is the called functions and configured dependencies, rather than a running service.

## What This Suite Proves

The individual assertion references identify the acceptance outcomes this file exercises. When a scenario spans several suites, this file supplies only its listed assertions; qualification must include the other bindings and any recorded coverage finding.

## What It Does Not Prove

Direct function checks do not prove route enforcement, transaction behavior or deployed integration. No result is claimed for the pinned revision until the suite runs and its evidence is reviewed.

## Real Dependencies and Test Doubles

The called rule or mapping functions are real code. Test inputs and any dependency doubles remain confined to individual examples.

## Must Not Be Doubled

The production function or carried adapter named by the file remains the subject under test; a second implementation of its expected answer is not a substitute.