---
id: ADR-ACC-CLS-009
title: Snapshots and Job Events Supply the Closing Evidence
product_area: accounting
module: close
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The implementation retains immutable snapshots, request facts, run outputs and
  operational job history, without Platform record-history capture for close.
constrains:
  - DOM-ACC-CLS-004
  - DOM-ACC-CLS-003
  - WF-ACC-CLS-007
  - SVC-ACC-CLS-fiscal-close
origin: >-
  fiscal-close design L12 and L13 (close runs, readiness at close and audit
  persisted; a snapshot at close added); FND-ACC-CLS-038
alternatives:
  - option: Capture Platform record history for close records.
    why_not: >-
      The inspected close does not implement it; the sources do not establish a
      reason to reject capture or its effect on cancellation attribution.
  - option: Keep all evidence in job history alone.
    why_not: >-
      Customer export withholds those operational tables, so the business
      request and retained checklist need their own records.
consequences:
  - >-
    The record operation reconstructs evidence from the snapshot and linked
    runs.
  - >-
    Export omits job events but retains run outputs, including some warning and
    failure data.
  - >-
    Each corrected close receives a separate snapshot without overwriting
    earlier captured evidence.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    modules/fiscal-close/db/period-close-snapshots.table.ts,
    period-close-runs.table.ts; db/migrations/0064_fiscal_close_foundation.sql
    (write-once trigger, grants); docs/fiscal-close/README.md §6.3.
---

# Snapshots and Job Events Supply the Closing Evidence

## Context

Reviewers need evidence of what justified closure and who acted. Current storage distributes that evidence across customer records and operational execution history.

## Decision

Describe the existing snapshot and run model without claiming record-history capture. The earlier design’s standard-history promise remains a finding for Product to resolve.

## Alternatives Considered

Capture Platform record history for close records. The inspected close does not implement it; the sources do not establish a reason to reject capture or its effect on cancellation attribution.

Keep all evidence in job history alone. Customer export withholds those operational tables, so the business request and retained checklist need their own records.

## Consequences

The record operation reconstructs evidence from the snapshot and linked runs. Export omits job events but retains run outputs, including some warning and failure data. Each corrected close receives a separate snapshot without overwriting earlier captured evidence.