Correct batch details before posting

Purpose

Staff correct a workable batch while preserving details already used by posted accounting.

How It Works

Staff open Edit Details and correct the batch information relevant to their work. The service checks whether the batch can still accept the change. A changed date can also change the fiscal context. A supplied version lets the save detect intervening edits. Update locks require a separate release before an ordinary correction. Posted accounting prevents ordinary field edits, and a refusal leaves the saved batch intact.

Relationships

Prerequisite: Collect a business unit’s documents in a new batch, which addresses the connected batch work.
Related outcome: Use the batch’s permitted lifecycle actions, which addresses the connected batch work.
Related outcome: Arrange automatic close and posting, which addresses the connected batch work.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Eligible corrections retain collection identity and recalculate affected fiscal placement.
Surfaces: consoleapi
Intent sources: services-accounting:docs/migrations/transaction-processing/batches/README.md#Status as actions (job tp-batch-lifecycle, Andrew's UI brief of 2026-10-15)services-accounting:docs/migrations/transaction-processing/batches/README.md#D14 and migration 0060 (Andrew, 2026-10-16)

Controls

22 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-DAT-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005

Permissions

Key	Checked at	Scope
`accounting.batches.update`	api	tenant
`accounting.batches.update`	console	tenant

Business Rules

10 rules, 10 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Details edits accept name, code, description, date, type, currency, automatic close, external reference and lock, while rejecting status changes through that editor. origin: services-accounting:docs/migrations/transaction-processing/batches/README.md#Status as actions (Andrew's UI brief of 2026-10-15) proved by `ATS-ACC-BAT-003-01`, `ATS-ACC-BAT-003-13`, `ATS-ACC-BAT-005-07`, `TST-ACC-BAT-060`	validation	api	observed services-accounting:modules/batches/aws/api/batches.schemas.ts:batchPatchSchema
`02`must prove Proposed	Neither the owning business unit nor the originating recurring-batch reference can be reassigned. proved by `ATS-ACC-BAT-003-02`	invariant	api, service, database	observed services-accounting:modules/batches/services/rules/batch-rules.ts:BATCH_FROZEN_FIELDS
`03`must prove Proposed	Posted, downloaded and archived batches reject ordinary field corrections but permit a request that changes only their lock. proved by `ATS-ACC-BAT-003-03`, `ATS-ACC-BAT-003-12`, `ATS-ACC-BAT-004-09`, `TST-ACC-BAT-085`	lifecycle	service	observed services-accounting:modules/batches/services/persistence/batches.ts:changeBatch; services-accounting:modules/batches/services/rules/batch-rules.ts:assertBatchChangesAllowed
`04`must prove Proposed	A batch currently posting rejects field changes until more than five minutes have passed since its last change. proved by `ATS-ACC-BAT-003-04`	lifecycle	service	observed services-accounting:modules/batches/services/rules/batch-rules.ts:assertBatchChangesAllowed
`05`must prove Proposed	Changing the date recalculates the fiscal period and rejects entry into a non-open period, while an edit that stays within its period does not require that period to remain open. proved by `ATS-ACC-BAT-003-05`, `TST-ACC-BAT-085`	calculation	service	test services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#refuses moving an open batch’s date into a closed period (journey 0516/0520 setups: the rule stands)
`06`must prove Proposed	Renaming cannot take a name already held by another batch in the same unit. origin: services-accounting:docs/migrations/transaction-processing/batches/README.md#D14 and migration 0060 (Andrew, 2026-10-16) proved by `ATS-ACC-BAT-001-11`, `ATS-ACC-BAT-003-06`, `ATS-ACC-BAT-003-11`, `TST-ACC-BAT-055`, `TST-ACC-BAT-085`	validation	service, database	test services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#refuses a rename to a name another batch of the unit has 409, name_in_use (D14)
`07`must prove Proposed	A supplied stale version prevents a details save, although the details API allows the version to be omitted. proved by `ATS-ACC-BAT-003-07`, `TST-ACC-BAT-060`, `TST-ACC-BAT-085`	validation	service	observed services-accounting:modules/batches/aws/api/batches.schemas.ts:batchPatchSchema; services-accounting:modules/batches/services/persistence/batches.ts:changeBatch
`08`must prove Proposed	An update lock blocks ordinary edits, and a caller with update permission can release it only in a separate request containing no other changes. proved by `ATS-ACC-BAT-003-08`, `TST-ACC-BAT-085`	policy	service	test services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#refuses an edit sent with the lock’s release
`09`must prove Proposed	An ordinary batch cannot be changed into a period-close system type. proved by `ATS-ACC-BAT-003-09`, `TST-ACC-BAT-074`	policy	service	test services-accounting:modules/batches/tests/integration/services/close/system-batch-guard.integration.spec.js#refuses changing an ordinary batch’s type to a system type, the batch unchanged
`10`must prove Proposed	Update permission controls details editing, and the console marks Edit Details unavailable with an explanation for a caller lacking it. proved by `ATS-ACC-BAT-003-10`, `TST-ACC-BAT-027`	permission	api, console	test react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0540.spec.ts#ACT-ACC-0540

Scenarios

Id	Given	When	Then	Provenance
`01`	A versioned editor is open when another caller closes and archives the batch.	The editor saves against the earlier version.	The stale save is refused, and a reloaded ordinary edit is also refused by archive protection.	documented react-console:acceptance/accounting/journeys/batches-posting/ACT-ACC-0506.json
`02`	An October batch has already posted.	A caller changes its date to early November.	The refused edit preserves the batch date and fiscal period.	test services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#refuses moving the date of a posted batch, and the batch keeps its date and fiscal period (DEF-ACT-0502)

Planning

Implementation

Correct batch details before posting ​

Purpose ​

How It Works ​

Relationships ​