---
id: ADR-ACC-TRX-015
title: Atomic Cancellation Preparation and Later Money Return
product_area: accounting
module: transactions
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Billing cancellation commits its component financial preparation under derived
  keys, executes electronic returns afterward and retains preparation with an
  explicit exception when a return fails.
constrains:
  - STATE-ACC-TRX-004
  - WF-ACC-TRX-010
  - SCR-ACC-TRX-006
  - SCR-ACC-TRX-021
  - SVC-ACC-TRX-transactions
origin: >-
  Andrew’s D-06 (Accounting owns the reversal operation; Commerce calls it):
  services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-06
  Ownership
alternatives:
  - option: Have Commerce independently sequence each financial command.
    why_not: >-
      The recorded owner is Accounting, which coordinates the component effects
      under one operation identity.
  - option: Undo billed reduction automatically after return failure.
    why_not: >-
      Corrected billing and money still owed back are separate financial
      concerns that require retained explanation.
consequences:
  - >-
    An unsuccessful return restores available receipt money while the
    cancellation records its outstanding exception.
  - >-
    Preview rolls back prepared financial documents but can consume
    independently allocated sequence numbers.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    docs/architecture/accounting-2.0/02-decisions.md, 05-lifecycles.md,
    06-integrity-model.md.
---
# Atomic Cancellation Preparation and Later Money Return

## Context

Cancellation spans local financial corrections and external money return. Atomic preparation cannot include provider work, so the operation retains the later return outcome.

## 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.
