---
id: ADR-ACC-BAT-011
title: Distinguish optional-version patches from versioned replacements
product_area: accounting
module: batches
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Batch details accept an optional-version patch; stream and routing
  configuration use versioned replacement, with completeness policy still
  unresolved.
constrains:
  - DOM-ACC-BAT-001
  - SVC-ACC-BAT-batches
  - SCR-ACC-BAT-004
  - SCR-ACC-BAT-005
  - SCR-ACC-BAT-006
origin: >-
  none recorded for this module; OQ-ACC-BAT-006 asks whether the
  complete-payload rule adopted for CRM records applies to these replacements
alternatives:
  - option: Require a version on every batch patch immediately.
    why_not: >-
      Existing examined callers omit it, so a new requirement would change their
      accepted request contract.
  - option: Patch configuration and each routing-rule position independently.
    why_not: >-
      Atomic ordered-list replacement preserves rule priority as one
      configuration change.
consequences:
  - A versionless batch request can overwrite concurrent form-field changes.
  - >-
    Omitted optional replacement values can be cleared; Product must resolve the
    existing completeness question.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263: modules/batches/aws/api/batches.schemas.ts,
    recurring-batches.schemas.ts, batch-assignment-settings.schemas.ts
---

# Distinguish optional-version patches from versioned replacements

## Context

The observed interfaces mix mutation styles. The current console batch adapter sends all editable form fields without a version, while configuration saves retain a version.

## Decision

This record describes the proposed boundary in its decision field. Its observed implementation does not constitute Andrew’s 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.