---
id: CAP-ACC-BAT-008
title: Bring waiting batches to the posting team’s attention
feature: FEAT-ACC-BAT-01
product_area: accounting
module: batches
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
supersedes: []
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
intent_sources: []
purpose: A posting attention item makes unfinished batch work visible to the people responsible for it.
outcomes:
- Waiting collections have accountable attention items that resolve or refresh as their state changes.
concepts:
- CON-ACC-BAT-001
actors:
- ACT-ACC-012
- ACT-ACC-014
surfaces:
- console
- job
permissions: []
rules:
- id: BR-CAP-ACC-BAT-008-01
  proved_by: [ATS-ACC-BAT-001-13, ATS-ACC-BAT-008-01, ATS-ACC-BAT-008-06, TST-ACC-BAT-120]
  statement: Closed, Verified, Posting and Error transaction batches qualify as awaiting posting, whereas system
    batches do not.
  kind: policy
  enforced_at:
  - service
  must_prove: true
  provenance: test
  source: services-accounting:modules/batches/tests/unit/attention/batches-awaiting-posting.spec.js#holds for a
    transaction batch in exactly closed, verified, posting and error
  origin: none
- id: BR-CAP-ACC-BAT-008-02
  proved_by: [ATS-ACC-BAT-008-02, TST-ACC-BAT-082]
  statement: Entering a waiting state publishes one required attention item in the batch transaction for its unit’s
    posting responsibility.
  kind: policy
  enforced_at:
  - service
  must_prove: true
  provenance: test
  source: services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#publishes
    one open item of the batch with every element mapped
  origin: none
- id: BR-CAP-ACC-BAT-008-03
  proved_by: [ATS-ACC-BAT-008-02, TST-ACC-BAT-082]
  statement: The item identifies the batch by code or name and includes its unit, document count and period end,
    refreshing the existing item when those facts change.
  kind: calculation
  enforced_at:
  - service
  must_prove: true
  provenance: test
  source: services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#keeps
    one open item, its first generation, with the new label and number
  origin: none
- id: BR-CAP-ACC-BAT-008-04
  proved_by: [ATS-ACC-BAT-004-11, ATS-ACC-BAT-006-07, ATS-ACC-BAT-008-03, ATS-ACC-BAT-008-07, ATS-ACC-BAT-008-08, ATS-ACC-BAT-008-09, ATS-ACC-BAT-013-19, TST-ACC-BAT-082]
  statement: Posting, reopening, archiving or deleting resolves the item, and a subsequent close starts a new attention
    generation.
  kind: lifecycle
  enforced_at:
  - service
  must_prove: true
  provenance: test
  source: services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#resolves
    a reopened batch reopened, and its next close opens the second generation
  origin: none
- id: BR-CAP-ACC-BAT-008-05
  proved_by: [ATS-ACC-BAT-008-04, TST-ACC-BAT-082, TST-ACC-BAT-120]
  statement: The deadline adds the workspace’s posting allowance in local calendar days to the last change, accepting
    zero through thirty whole days and defaulting invalid or missing values to two.
  kind: calculation
  enforced_at:
  - service
  must_prove: true
  provenance: test
  source: services-accounting:modules/batches/tests/unit/attention/batches-awaiting-posting.spec.js#answers the
    default 2 for a missing, fractional, out-of-bounds or mistyped value
  origin: none
- id: BR-CAP-ACC-BAT-008-06
  proved_by: [ATS-ACC-BAT-008-05, TST-ACC-BAT-082]
  statement: An hourly sweep restores missing items, clears stale ones and refreshes deadlines using the current
    allowance.
  kind: policy
  enforced_at:
  - service
  must_prove: true
  provenance: test
  source: services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#publishes
    the batch whose item was lost
  origin: none
- id: BR-CAP-ACC-BAT-008-07
  proved_by: []
  statement: The provider declares a bulk Post action bound to the posting operation, but console grouping and execution
    by business unit remain unverified.
  kind: policy
  enforced_at: []
  must_prove: true
  provenance: documented
  source: services-accounting:modules/batches/attention/batches-awaiting-posting.attention.ts:batchesAwaitingPosting
  origin: none
  note: The provider declaration is evidence of the action contract, not an executed console flow; FND-ACC-BAT-032
    records the gap.
scenarios:
- id: SC-CAP-ACC-BAT-008-01
  given: The workspace allows five posting days and has a posting responsible.
  when: Staff close a batch on Monday afternoon.
  then: Its attention deadline falls five calendar days after close, and posting resolves the item.
  provenance: test
  source: services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#dues
    the item five days after the close
- id: SC-CAP-ACC-BAT-008-02
  given: No person holds the workspace’s posting responsibility.
  when: A batch enters a waiting state.
  then: The documented attention item remains without a recipient until the responsibility is assigned.
  provenance: documented
  source: services-accounting:docs/milestones/walkthroughs/ACCT-M3-handoff.md#Start here (step 3)
edge_cases: []
constraints:
- Platform supplies the responsibility audience and attention presentation.
depends_on:
- CAP-ACC-BAT-004
related:
- CAP-ACC-BAT-013
journeys:
- JNY-ACC-BAT-001
open_questions: []
evidence:
- 'Pinned services-accounting (f47cb263), examined sources: attention/batches-awaiting-posting.attention.ts, services/rules/batch-attention-rules.ts,
  services/persistence/batch-attention-items.ts, services/attention/batches-awaiting-posting-sweep.ts, aws/lambda/BATCHES_ATTENTION_SWEEP.ts,
  aws/logic/batches-attention-sweep.lambda.ts; tests unit/attention/batches-awaiting-posting.spec.js, integration/services/persistence/batch-attention-items.integration.spec.js;
  docs/attention.md.'
- 'Pinned react-console (baf6dae3), examined sources: components/accounting/batches/batch-list-screen.tsx (the businessUnit
  link the attention item''s bulk action opens).'
controls: [TC-IAM-001, TC-IAM-005, TC-IAM-006, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-TEN-004, TC-DAT-001, TC-DAT-004, TC-LOG-005, TC-AVL-001, TC-AVL-004, TC-MON-001, TC-MON-002, TC-MON-004, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005]
exercised_by: [FAS-ACC-BAT-01-02, FAS-ACC-BAT-01-03]
suites: [TST-ACC-BAT-082, TST-ACC-BAT-120]
---

# Bring waiting batches to the posting team’s attention

## Purpose

A posting attention item makes unfinished batch work visible to the people responsible for it.

## How It Works

Rhythm watches batches entering states that await posting. Their unit and posting responsibility determine the attention audience. The item carries identifying information and a deadline calculated in the workspace calendar. Changes refresh the existing item rather than creating duplicates. Leaving the waiting state resolves it. A recurring sweep repairs missing or stale items, while the provider’s bulk-action declaration still needs proof of its console execution.

## Relationships

- Prerequisite: Use the batch’s permitted lifecycle actions, which addresses the connected batch work.
- Related outcome: Run and monitor a batch posting job, which addresses the connected batch work.