---
id: JNY-ACC-BAT-001
title: Staff complete a daily collection and review its ledger result
feature: FEAT-ACC-BAT-01
product_area: accounting
module: batches
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
supersedes:
- ACT-ACC-0500
- ACT-ACC-0502
- ACT-ACC-0517
- ACT-ACC-0545
- ACT-ACC-0550
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
actor: ACT-ACC-012
goal: Bring the day’s documents through collection, closing and posting, then reconcile the accounting result.
capabilities:
- CAP-ACC-BAT-001
- CAP-ACC-BAT-007
- CAP-ACC-BAT-002
- CAP-ACC-BAT-012
- CAP-ACC-BAT-004
- CAP-ACC-BAT-008
- CAP-ACC-BAT-013
- CAP-ACC-BAT-015
- CAP-ACC-BAT-018
screens:
- /console/{tenantId}/accounting/batches
- /console/{tenantId}/accounting/batches/new
- /console/{tenantId}/accounting/batches/{batchId}
steps:
- n: 1
  surface: /console/{tenantId}/accounting/batches/new
  action: Select the unit and today’s date, give the collection a useful name and create it.
  capability: CAP-ACC-BAT-001
  expected: The created record is Open in the current fiscal context, with consistent values across list, detail
    and API.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0500.spec.ts#ACT-ACC-0500
- n: 2
  surface: /console/{tenantId}/accounting/invoices/new (and the payment screens)
  action: Issue invoices and record payments into that collection.
  capability: CAP-ACC-BAT-007
  expected: Eligible issued documents enter the Open batch; drafts and pro forma documents remain outside it.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0517.spec.ts#ACT-ACC-0517
- n: 3
  surface: /console/{tenantId}/accounting/batches/{batchId}
  action: Review the totals and transaction list on the detail page.
  capability: CAP-ACC-BAT-002
  expected: Live totals describe the eligible documents while the list can still show voided records.
  provenance: documented
  source: services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (step 2)
- n: 4
  surface: /console/{tenantId}/accounting/batches/{batchId} (Validation card)
  action: Run validation for the collection.
  capability: CAP-ACC-BAT-012
  expected: Generation checks report no problem for the selected collection.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0517.spec.ts#ACT-ACC-0517
- n: 5
  surface: /console/{tenantId}/accounting/batches/{batchId} (More Actions › Close)
  action: Finish the day’s intake with Close.
  capability: CAP-ACC-BAT-004
  expected: The state becomes Closed, further intake stops and posting attention is required.
  provenance: documented
  source: services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (step 3)
- n: 6
  surface: /console/{tenantId}/accounting/batches/{batchId} (Post)
  action: Submit Post and accept its confirmation.
  capability: CAP-ACC-BAT-013
  expected: The progress panel completes its two stages and shows Posted.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0517.spec.ts#ACT-ACC-0517
- n: 7
  surface: /console/{tenantId}/accounting/batches/{batchId} (Subledger Entries tab)
  action: Expand the ledger entries for review.
  capability: CAP-ACC-BAT-015
  expected: Applicable counted documents have balanced entries using the batch accounting date and document-specific
    ledger patterns.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0550.spec.ts#ACT-ACC-0550
- n: 8
  surface: Reports & Dashboards › Subledger Entries
  action: Report on the unit and fiscal period.
  capability: CAP-ACC-BAT-018
  expected: The report presents the batch section and total with a balanced result.
  provenance: documented
  source: services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (step 5)
alternates:
- from_step: 2
  condition: No batch was supplied on the document.
  path: Assignment selects the recurring configuration’s current intake target.
  outcome: The document receives its batch without manual selection.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0510.spec.ts#ACT-ACC-0510
- from_step: 6
  condition: Posting is requested before intake is closed.
  path: The confirmation explains that accounting completion ends intake.
  outcome: The Open batch can complete posting.
  provenance: test
  source: services-accounting:modules/batches/tests/unit/actions/batch-actions.spec.js#answers an open batch’s actions
    with their labels, placements, targets, confirmations and the warning
failures:
- from_step: 1
  condition: The requested date belongs to a closed fiscal period.
  path: Creation reports the period refusal while preserving the entered form.
  outcome: Staff must select an eligible accounting date before creating the collection.
  provenance: documented
  source: services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (step 8)
- from_step: 6
  condition: A document lacks a prerequisite for generation.
  path: The failed attempt identifies that document and leaves no partial entries.
  outcome: Staff follow the recovery workflow to resolve the prerequisite and retry.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0521.spec.ts#ACT-ACC-0521
rules_in_play:
- BR-CAP-ACC-BAT-001-01
- BR-CAP-ACC-BAT-001-04
- BR-CAP-ACC-BAT-007-01
- BR-CAP-ACC-BAT-002-03
- BR-CAP-ACC-BAT-004-02
- BR-CAP-ACC-BAT-008-02
- BR-CAP-ACC-BAT-013-03
- BR-CAP-ACC-BAT-015-02
- BR-CAP-ACC-BAT-015-14
- BR-CAP-ACC-BAT-007-04
assertions:
- id: AS-JNY-ACC-BAT-001-01
  statement: Applicable counted documents have balanced entries in the batch’s accounting placement.
  provenance: test
  source: react-console:acceptance/accounting/playwright/journeys/batches-posting/ACT-ACC-0517.spec.ts#ACT-ACC-0517
- id: AS-JNY-ACC-BAT-001-02
  statement: Posted documents cannot be reassigned or voided through ordinary intake changes.
  provenance: test
  source: services-accounting:modules/batches/tests/integration/services/posting/rebuilt-documents.integration.spec.js#refuses,
    in the database, moving a document out of a posted batch (RHA05)
- id: AS-JNY-ACC-BAT-001-03
  statement: Posting resolves the collection’s waiting attention item.
  provenance: test
  source: services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#resolves
    a posted batch posted, after its posting kept it open
- id: AS-JNY-ACC-BAT-001-04
  statement: The period report includes the collection in a balanced result.
  provenance: documented
  source: services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (step 5)
e2e_policy: required
e2e_reason: Browser acceptance is required to connect collection creation, visible posting progress and the reported
  accounting result.
evidence:
- 'Inspected references: Examined pinned react-console (baf6dae3): acceptance/accounting/journeys/batches-posting/ACT-ACC-0500.json,
  0502, 0517, 0545, 0550 with corresponding browser specifications; components/accounting/batches/**.'
- 'Inspected references: Examined pinned services-accounting (f47cb263): docs/milestones/walkthroughs/ACCT-M3-handoff.md;
  step-level capability citations.'
proved_by: []
---

# Staff complete a daily collection and review its ledger result

## Story

Bring the day’s documents through collection, closing and posting, then reconcile the accounting result. The cited steps show how the relevant capabilities connect. Documented walkthrough expectations remain distinct from tested behavior, and the alternative paths identify where staff need a different workflow.
