---
id: ADR-ACC-TRX-003
title: Versioned Preparation and Explicit Issued Corrections
product_area: accounting
module: transactions
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Prepared invoices use versioned whole replacement, while issued corrections
  use specific commands including permitted unposted amendment and preserve the
  original collection facts on receipts and credits.
constrains:
  - DOM-ACC-TRX-001
  - DOM-ACC-TRX-006
  - STATE-ACC-TRX-001
  - WF-ACC-TRX-002
  - WF-ACC-TRX-017
  - SCR-ACC-TRX-004
  - SCR-ACC-TRX-005
origin: >-
  Andrew’s A-7 and A-14 (2026-10-18) on reopening non-money fields and amending
  unposted invoices:
  services-accounting:docs/architecture/accounting-2.0/02-decisions.md#2.8
  Andrew's acceptance decisions of 2026-10-18 (about 15:35 UTC)
alternatives:
  - option: Patch selected preparation fields without a whole replacement.
    why_not: >-
      A partial merge could conceal concurrent changes that versioned
      replacement makes visible.
  - option: Permit unrestricted updates after billing issue.
    why_not: >-
      Financial changes need bounded commands with permissions and retained
      evidence.
consequences:
  - A stale prepared document is rejected instead of silently merged.
  - >-
    Receipt and credit core facts remain protected, while authorized invoice
    amendment is the specific exception for unposted charges.
  - >-
    The service implements amendment but the console review and submission
    adapters remain disconnected.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    docs/architecture/accounting-2.0/02-decisions.md, 05-lifecycles.md,
    06-integrity-model.md.
---
# Versioned Preparation and Explicit Issued Corrections

## Context

Staff correction needs to retain a financial explanation while still supporting editable preparation. The cited ruling already permits the unposted amendment path.

## Decision

The structured decision records the governing boundary and its observed limits. Its origin distinguishes Andrew’s rulings from reversible implementation choices and proposed publication policy.

## Alternatives Considered

The listed alternatives explain the competing responsibility or recovery approaches and why the recorded direction differs. They are explanatory comparisons, without evidence of a separate approval discussion for each alternative.

## Consequences

The consequence rows identify implementation obligations, current departures and gaps requiring further verification. Artifact status remains proposed until Andrew approves it.