Unpost a batch for correction and replacement posting

Purpose

Administrators reopen posted work for correction while retaining the record of the earlier posting.

How It Works

An administrator chooses Unpost and confirms the accounting removal. The action or job checks the batch, fiscal period and dependent work. The current ordinary posting’s ledger entries are then removed within the transaction. Its posting record and job history remain available. Staff can correct or reassign the reopened documents before posting again. A guarded-deletion refusal leaves the prior accounting intact and fails the job.

Relationships

Prerequisite: Run and monitor a batch posting job, which addresses the connected batch work.
Related outcome: Place documents in eligible batches and protect posted work, which addresses the connected batch work.
Related outcome: Protect ledger balance, immutability and workspace isolation, which addresses the connected batch work.
Related outcome: Post and reverse fiscal-close system batches, 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 ordinary recovery removes the current ledger result while preserving posting history.
Surfaces: consoleapijob
Constraints: Fiscal reopening retains a separate system-batch reversal path.
Intent sources: services-accounting:docs/accounting/batches.md#Unposting deletes the entries (Andrew, Reporting D7, 2026-10-21)services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-4

Controls

25 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-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-CRY-004 TC-DAT-001 TC-DAT-004 TC-LOG-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.batch-postings.unpost`	api	tenant

Business Rules

11 rules, 11 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	Unposting needs the administrator unposting permission, which the ordinary posting staff tier does not grant. proved by `ATS-ACC-BAT-016-01`, `TST-ACC-BAT-027`, `TST-ACC-BAT-055`, `TST-ACC-BAT-057`, `TST-ACC-BAT-119`	permission	api, console	test services-accounting:modules/batches/tests/e2e/batch-postings.e2e.spec.js#refuses an unposting without the unposting permission, 403, and leaves the batch posted
`02`must prove Proposed	Unpost admits Posted, Downloaded and posting work unchanged for more than one hour. proved by `ATS-ACC-BAT-016-01`, `ATS-ACC-BAT-016-15`, `TST-ACC-BAT-027`, `TST-ACC-BAT-055`, `TST-ACC-BAT-057`, `TST-ACC-BAT-096`, `TST-ACC-BAT-119`	lifecycle	service	test services-accounting:modules/batches/tests/e2e/batch-actions.e2e.spec.js#refuses unposting a batch that is not posted 409
`03`must prove Proposed	Ordinary unposting deletes the current posting’s entries and lines without creating reversals or removing another batch’s entries. origin: services-accounting:docs/accounting/batches.md#Unposting deletes the entries (Andrew, Reporting D7, 2026-10-21) proved by `ATS-ACC-BAT-016-02`, `ATS-ACC-BAT-016-12`, `ATS-ACC-BAT-016-13`, `ATS-ACC-BAT-017-08`, `ATS-ACC-BAT-018-07`, `TST-ACC-BAT-017`, `TST-ACC-BAT-057`, `TST-ACC-BAT-076`, `TST-ACC-BAT-092`, `TST-ACC-BAT-094`, `TST-ACC-BAT-112`	lifecycle	service, database	test services-accounting:modules/batches/tests/integration/services/posting/unpost-deletes-entries.integration.spec.js#deletes the batch’s entries and their lines, and tells how many entries
`04`must prove Proposed	The posting remains marked reversed with the unposting time and job, and retained job history preserves who acted and when. origin: services-accounting:docs/accounting/batches.md#Unposting deletes the entries (Andrew, Reporting D7, 2026-10-21) proved by `ATS-ACC-BAT-016-02`, `TST-ACC-BAT-017`, `TST-ACC-BAT-057`, `TST-ACC-BAT-076`, `TST-ACC-BAT-092`, `TST-ACC-BAT-094`, `TST-ACC-BAT-112`	invariant	service	test services-accounting:modules/batches/tests/integration/services/posting/unpost-deletes-entries.integration.spec.js#keeps the posting history: the first posting reversed, the second current
`05`must prove Proposed	Unposting voids the posting’s open revenue-recognition schedules. origin: services-accounting:docs/accounting/batches.md#Unposting deletes the entries (Andrew, Reporting D7, 2026-10-21) proved by `ATS-ACC-BAT-016-02`, `TST-ACC-BAT-017`, `TST-ACC-BAT-057`, `TST-ACC-BAT-076`, `TST-ACC-BAT-092`, `TST-ACC-BAT-094`, `TST-ACC-BAT-112`	lifecycle	service	test services-accounting:modules/batches/tests/integration/services/persistence/revenue-recognition-schedules.queries.integration.spec.js#reads the current schedule by its id, and none once its posting is not the current one
`06`must prove Proposed	The batch returns to Open with posting time, statistics and dependents cleared so its documents can be corrected or reassigned. origin: services-accounting:docs/accounting/batches.md#Unposting deletes the entries (Andrew, Reporting D7, 2026-10-21) proved by `ATS-ACC-BAT-002-09`, `ATS-ACC-BAT-004-13`, `ATS-ACC-BAT-007-11`, `ATS-ACC-BAT-016-02`, `ATS-ACC-BAT-016-08`, `ATS-ACC-BAT-016-09`, `ATS-ACC-BAT-016-10`, `TST-ACC-BAT-017`, `TST-ACC-BAT-057`, `TST-ACC-BAT-076`, `TST-ACC-BAT-092`, `TST-ACC-BAT-094`, `TST-ACC-BAT-112`	lifecycle	service	test services-accounting:modules/batches/tests/e2e/batch-postings.e2e.spec.js#unposts a posted batch as a durable job: the batch is open again and its entries are deleted
`07`must prove Proposed	A Posted or Downloaded dependent prevents unposting unless that dependent is included in the same unposting request. origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-4 proved by `ATS-ACC-BAT-016-03`, `TST-ACC-BAT-105`	invariant	service	observed services-accounting:modules/batches/services/rules/batch-posting-rules.ts:ensureBatchesCanBeUnposted
`08`must prove Proposed	Unposting is refused outside an Open fiscal period. origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-4 proved by `ATS-ACC-BAT-016-04`, `ATS-ACC-BAT-016-14`, `ATS-ACC-BAT-020-09`, `TST-ACC-BAT-010`, `TST-ACC-BAT-070`	validation	service	test services-accounting:modules/batches/tests/integration/services/close/posting-period-guard.integration.spec.js#refuses the batch action `unpost` (`period_not_open`), submitting no job
`09`must prove Proposed	Reposting creates a fresh current posting and entry set and writes fresh line snapshots. origin: services-accounting:docs/accounting/batches.md#Unposting deletes the entries (Andrew, Reporting D7, 2026-10-21) proved by `ATS-ACC-BAT-013-24`, `ATS-ACC-BAT-016-05`, `ATS-ACC-BAT-016-11`, `TST-ACC-BAT-057`, `TST-ACC-BAT-105`, `TST-ACC-BAT-112`	lifecycle	service	test services-accounting:modules/batches/tests/integration/services/posting/unpost-deletes-entries.integration.spec.js#writes one fresh set when the batch is posted again, equal in size to the first
`10`must prove Proposed	A refused guarded deletion preserves batch, posting and entries and fails the job, and rejects postings already reversed, containing reversal entries or belonging to another workspace. proved by `ATS-ACC-BAT-016-06`, `ATS-ACC-BAT-016-15`, `TST-ACC-BAT-096`, `TST-ACC-BAT-112`, `TST-ACC-BAT-113`	invariant	service, database	test services-accounting:modules/batches/tests/integration/services/posting/unpost-refusal.integration.spec.js#keeps the posting, its entries and the batch as they were, and fails the unposting step with the refusal
`11`must prove Proposed	Update-locked and system batches reject ordinary unposting through either actions or jobs. proved by `ATS-ACC-BAT-016-07`, `TST-ACC-BAT-063`, `TST-ACC-BAT-074`, `TST-ACC-BAT-076`	policy	service	test services-accounting:modules/batches/tests/e2e/system-batches.e2e.spec.js#answers an unposting naming the system batch with its job, and the job fails with the refusal

Scenarios

Id	Given	When	Then	Provenance
`01`	A posted rehearsal batch contains an invoice assigned to the wrong stream.	An administrator unposts, reassigns the invoice and posts the corrected batch.	The ordinary entries disappear on unposting and one fresh set represents the later posting.	documented services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (steps 6 and 7)
`02`	A staff caller has posting permission but no unposting permission.	The caller inspects a Posted batch and requests Unpost.	The console omits the unauthorized action and the API refusal preserves the posting.	test react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0540.spec.ts#ACT-ACC-0540

Planning

Implementation

Unpost a batch for correction and replacement posting ​

Purpose ​

How It Works ​

Relationships ​