Skip to content

CAP-ACC-BAT-008Bring waiting batches to the posting team’s attention

Markdown

CAP-ACC-BAT-008

Bring waiting batches to the posting team’s attention

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

KindCapabilityProduct areaAccountingModuleBatch ManagementRevision1

Read atservices-accounting f47cb263react-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
Waiting collections have accountable attention items that resolve or refresh as their state changes.
Surfaces
consolejob
Constraints
Platform supplies the responsibility audience and attention presentation.

Controls

23 controls apply, from the corpus control catalogue.

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

Business Rules

7 rules, 7 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.

IdRuleKindEnforced atProvenance
01must prove
Proposed
Closed, Verified, Posting and Error transaction batches qualify as awaiting posting, whereas system batches do not.
policyservicetest
services-accounting:modules/batches/tests/unit/attention/batches-awaiting-posting.spec.js#holds for a transaction batch in exactly closed, verified, posting and error
02must prove
Proposed
Entering a waiting state publishes one required attention item in the batch transaction for its unit’s posting responsibility.
policyservicetest
03must prove
Proposed
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.
calculationservicetest
04must prove
Proposed
Posting, reopening, archiving or deleting resolves the item, and a subsequent close starts a new attention generation.
lifecycleservicetest
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
05must prove
Proposed
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.
calculationservicetest
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
06must prove
Proposed
An hourly sweep restores missing items, clears stale ones and refreshes deadlines using the current allowance.
policyservicetest
07must prove
Proposed
The provider declares a bulk Post action bound to the posting operation, but console grouping and execution by business unit remain unverified.
no proof recorded yet
policydocumented

Scenarios

IdGivenWhenThenProvenance
01The workspace allows five posting days and has a posting responsible.Staff close a batch on Monday afternoon.Its attention deadline falls five calendar days after close, and posting resolves the item.test
02No person holds the workspace’s posting responsibility.A batch enters a waiting state.The documented attention item remains without a recipient until the responsibility is assigned.documented

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.