Keep transaction batches and details correct

Purpose

Staff maintain posting placement and descriptive information without rewriting money history.

How It Works

Staff open a transaction to correct its reference, memo or notes. Required explanations cannot be cleared. Before posting, they can select another eligible batch in the same unit. Moving a receipt also moves the applications originally batched with it. Eligible date corrections append opposite old-date entries and new-date entries. Posting prevents financial placement and date changes while permitted text corrections remain available. Unsupported lifecycle or batch choices are refused.

Relationships

Correct issued bills before posting supplies or continues the related financial work.
Find money records and understand available work supplies or continues the related financial 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: Staff maintain posting placement and descriptive information without rewriting money history.Posting prevents financial placement and date changes while permitted text corrections remain available. Unsupported lifecycle or batch choices are refused.
Surfaces: consoleapi
Intent sources: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-6services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-7services-accounting:docs/milestones/plans/ACCT-M2-plan.md#D9services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D12

Controls

25 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 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-DAT-002 TC-DAT-003 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`accounting.invoices.update`	api	tenant
`accounting.credit-memos.update`	api	tenant
`accounting.debit-memos.update`	api	tenant
`accounting.write-offs.update`	api	tenant
`accounting.payments.update`	api	tenant
`accounting.credits.update`	api	tenant
`accounting.credit-applications.update`	api	tenant

Business Rules

8 rules, 8 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	A destination must be an open or in-error transaction batch in the record’s unit; closed, posted, period-close and foreign-unit destinations are refused. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D12 proved by `ATS-ACC-TRX-002-11`, `ATS-ACC-TRX-003-12`, `ATS-ACC-TRX-004-07`, `ATS-ACC-TRX-015-01`, `ATS-ACC-TRX-015-09`, `TST-ACC-TRX-030`	validation	service	test services-accounting:modules/transactions/tests/integration/services/batches-for-documents.integration.spec.js#it refuses a system batch, which is period close’s: a transaction batch only (batch_not_open)
`02`must prove Proposed	Without explicit batch selection, the unit’s assignment rules choose an active recurring batch for the record kind, and unusable or absent assignment is refused. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#D12 proved by `ATS-ACC-TRX-015-02`, `TST-ACC-TRX-030`	policy	service	test services-accounting:modules/transactions/tests/integration/services/batches-for-documents.integration.spec.js#it is refused batch_required once the chosen recurring batch’s active batch is closed (BA-12), naming the reason
`03`must prove Proposed	Eligible records move only between unposted batches of the same unit; posting, posted and downloaded batches block movement, while selecting the current batch is a no-op. origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-6 proved by `ATS-ACC-TRX-002-11`, `ATS-ACC-TRX-003-12`, `ATS-ACC-TRX-004-07`, `ATS-ACC-TRX-006-10`, `ATS-ACC-TRX-015-03`, `ATS-ACC-TRX-015-09`, `ATS-ACC-TRX-016-08`, `TST-ACC-TRX-039`	lifecycle	service	test services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it is refused batch_not_open on a reassignment out of the batch
`04`must prove Proposed	Moving a receipt also moves allocations sharing its batch and records an audit event without changing receivable value. origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-6 proved by `ATS-ACC-TRX-006-10`, `ATS-ACC-TRX-015-04`, `ATS-ACC-TRX-015-09`, `ATS-ACC-TRX-016-08`, `TST-ACC-TRX-039`	policy	service	test services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it moves the allocation rows batched with it
`05`must prove Proposed	Drafts and void records cannot move, and quotes receive no batch until conversion. origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-6 proved by `ATS-ACC-TRX-015-05`, `TST-ACC-TRX-039`	validation	service	test services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it refuses a void payment
`06`must prove Proposed	Supported reference, memo and note fields remain editable and can be cleared, but required reasons cannot become blank. origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-7 proved by `ATS-ACC-TRX-015-06`, `TST-ACC-TRX-012`, `TST-ACC-TRX-039`	policy	service	test services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it never clears a required field (a credit’s reason), and changes its memo
`07`must prove Proposed	Unposted date corrections require an open period and append opposing old-date and replacement new-date receivable entries. origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-7 proved by `ATS-ACC-TRX-015-07`, `TST-ACC-TRX-039`	lifecycle	service	test services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it negates the facts on the old accounting date and restates them on the new one, the originals untouched
`08`must prove Proposed	Each record kind’s update authority governs movement and details, and payment Edit Details is connected in the console. proved by `ATS-ACC-TRX-015-08`, `TST-ACC-TRX-003`, `TST-ACC-TRX-012`	permission	api, console	test services-accounting:modules/transactions/tests/e2e/payments.e2e.spec.js#it is refused the batch and details routes without accounting.payments.update (403)

Scenarios

Id	Given	When	Then	Provenance
`01`	A payment’s batch is closed but not posted.	Select another eligible batch in the same unit.	The receipt and associated applications move together with an event identifying both batches.	test services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it writes the reassign event with both batches and the rows moved, and no fact
`02`	The check reference and business date were entered incorrectly.	Correct both before posting.	The new reference is retained and correcting entries move its receivable effect to the selected date.	test services-accounting:modules/transactions/tests/integration/services/document-edits/reassign-and-edit.integration.spec.js#it moves the payment date and the accounting date while the payment is unposted

Planning

Implementation

Keep transaction batches and details correct ​

Purpose ​

How It Works ​

Relationships ​