Inspect posting readiness before submission

Purpose

Staff inspect the problems preview can detect before asking for a posting.

How It Works

Staff request validation from the batch page before posting. The task function runs the posting generation logic as a preview. It returns the batches and configuration problems found by the checks it performs. The console presents those explanations alongside readiness information. Preview creates no accounting records, although its fiscal-period read can hold a shared lock. Passing preview still leaves status and lock checks for the posting itself.

Relationships

Related outcome: Run and monitor a batch posting job, which addresses the connected batch work.
Related outcome: Resolve posting accounts and retain their snapshots, 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: Readers receive generation problems while recognizing that execution applies additional safeguards.
Surfaces: consoleapi
Constraints: The posting task function supplies preview using the generation logic.

Controls

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

Permissions

Key	Checked at	Scope
`accounting.batch-postings.preview`	api	tenant

Business Rules

7 rules, 5 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	Preview requires its own read permission, available to readers and auditors. proved by `ATS-ACC-BAT-012-01`, `TST-ACC-BAT-057`, `TST-ACC-BAT-124`	permission	api	test services-accounting:modules/batches/tests/e2e/batch-postings.e2e.spec.js#refuses a preview without the preview permission, 403
`02`must prove Proposed	A preview request must identify between one and one hundred batches. proved by `ATS-ACC-BAT-012-01`, `ATS-ACC-BAT-012-06`, `TST-ACC-BAT-057`, `TST-ACC-BAT-124`	validation	api	test services-accounting:modules/batches/tests/e2e/batch-postings.e2e.spec.js#refuses a preview that names no batch, 400
`03`must prove Proposed	Preview identifies missing, already posted, system and non-open-period batches plus generation failures such as missing accounts, stored rates or document dependencies, without applying every state and lock guard. proved by `ATS-ACC-BAT-012-02`, `ATS-ACC-BAT-012-05`, `ATS-ACC-BAT-014-08`	validation	service	observed services-accounting:modules/batches/services/engine/preview-batches.ts:previewBatchPostings
`04`must prove Proposed	Posted and Downloaded batches receive the already-posted explanation ahead of any other preview explanation. proved by `ATS-ACC-BAT-012-02`	validation	service	test services-accounting:modules/batches/tests/unit/rules/batch-posting-preview-rules.spec.js#says already posted, whatever other reason it has, for a posted batch
`05` Proposed	Preview gathers invoice products and identifies those without financial configuration.	calculation	service	test services-accounting:modules/batches/tests/integration/services/posting/rebuilt-documents.integration.spec.js#names the products of its invoices, and the late fee as the product without a financial configuration
`06`must prove Proposed	Preview mutates no batch or ledger record but holds shared fiscal-period locks until its read transaction finishes. proved by `ATS-ACC-BAT-012-03`, `ATS-ACC-BAT-012-04`, `ATS-ACC-BAT-013-21`	invariant	service	observed services-accounting:modules/batches/services/engine/preview-batches.ts:periodProblemOf; services-accounting:modules/batches/services/persistence/posting-periods.ts:lockPostingPeriodForDate
`07` Proposed	An otherwise eligible Error batch appears in the posting candidates with its previous error messages.	validation	service	test services-accounting:modules/batches/tests/unit/rules/batch-repost-rules.spec.js#lists it to post with its previous errors, not as ineligible

Scenarios

Id	Given	When	Then	Provenance
`01`	An invoice needs revenue accounting missing from both product and unit.	Staff request a posting preview.	The result reports the same missing-account cause as posting generation.	test services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#names the same reason in the preview
`02`	Preview finds no blocking issue for the receivables batch.	Staff open its page.	The documented readiness message reports that the preview found no blocker.	documented services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (step 2)

Planning

Implementation

Inspect posting readiness before submission ​

Purpose ​

How It Works ​

Relationships ​