---
id: ADR-ACC-BAT-005
title: Prepare scheduled posting before retirement commits
product_area: accounting
module: batches
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Scheduled close and rolling prepare an eligible predecessor posting job within
  their business transaction, using the run key, and start it after commit.
constrains:
  - WF-ACC-BAT-002
  - WF-ACC-BAT-003
  - SVC-ACC-BAT-batches
  - DOM-ACC-BAT-003
origin: >-
  D13 (Andrew, 2026-10-16: a rolled or auto-closed batch is posted
  automatically), recorded at
  services-accounting:docs/migrations/transaction-processing/batches/README.md#D13:
  automatic posting
alternatives:
  - option: Require staff to submit every scheduled predecessor manually.
    why_not: >-
      The recorded choice preserves automatic posting expected from prior
      scheduled behavior.
  - option: Run the accounting engine inside retirement.
    why_not: Posting needs its own durable execution boundary and observable progress.
consequences:
  - >-
    Before-commit rollback removes both retirement changes and prepared
    submission.
  - >-
    Failed start can leave a committed Pending job because no reconciler is
    registered.
  - >-
    Recognized preparation refusal preserves the Closed collection and its
    explanation in the run outcome.
  - >-
    Reactivation retirement still omits predecessor posting and remains an open
    policy difference.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    modules/batches/services/auto-post/automatic-posting.ts;
    services/auto-close/batch-auto-close.ts;
    services/roll/recurring-batch-roll.ts
---

# Prepare scheduled posting before retirement commits

## Context

Scheduled retirement and durable accounting have separate transactions. The recorded direction requires retirement to request accounting automatically.

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