---
id: ADR-ACC-BAT-001
title: Resolve and retain accounting when the batch posts
product_area: accounting
module: batches
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Batch execution generates the ledger and resolves accounting configuration at
  that time, retaining the resulting snapshot on posted document lines.
constrains:
  - DOM-ACC-BAT-003
  - DOM-ACC-BAT-004
  - SVC-ACC-BAT-batches
  - WF-ACC-BAT-005
  - WF-ACC-BAT-007
origin: >-
  D-03 (Andrew, 2026-10-15, confirmed 2026-10-17: batch post kept) and A-1
  (Andrew, 2026-10-18: accounts resolved and frozen at batch posting), recorded
  at services-accounting:docs/architecture/accounting-2.0/02-decisions.md §1 and
  §2.8
alternatives:
  - option: Generate accounting on document issuance.
    why_not: The recorded choice retains batch review before ledger completion.
  - option: Capture the posting accounts during issuance.
    why_not: Invoices must be issuable before customers finish account setup.
consequences:
  - >-
    Missing account setup is explained as a posting-validation failure with
    source and financial context.
  - >-
    Corrections use retained original accounting rather than silently adopting
    changed configuration.
  - >-
    Changed configuration affects later execution without rewriting completed
    accounting.
  - Preview uses the same resolution logic to locate incomplete setup.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    docs/architecture/accounting-2.0/02-decisions.md; 08-batch-posting.md §1-§2;
    modules/batches/services/engine/posting-documents.ts, posted-accounting.ts
---

# Resolve and retain accounting when the batch posts

## Context

The recorded product ruling keeps collection review as the accounting boundary and removes finished account configuration as a prerequisite for invoice issuance.

## Decision

The decision field restates the existing recorded direction for this design boundary. This examination does not grant a new approval.

## Alternatives Considered

The alternatives above identify the competing implementation choices and their consequences. They preserve the distinction between a recorded product ruling and a proposed engineering boundary.

## Consequences

The consequence rows describe obligations and known implementation limits at this boundary. Related artifact references retain the affected design homes.