Skip to content

JNY-ACC-BAT-003An administrator configures recurring intake and document routing

Markdown

JNY-ACC-BAT-003

An administrator configures recurring intake and document routing

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

KindJourneyProduct areaAccountingModuleBatch ManagementRevision1End-to-endRequired

Read atreact-console baf6dae3services-accounting f47cb263

The Formal Contract

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

Goal
Supply successive intake collections and route new documents through the configured choices without repeated manual batch selection.
Screens
/console/{tenantId}/configuration/accounting/recurringBatches/console/{tenantId}/configuration/accounting/batchAssignments/console/{tenantId}/accounting/batches

Steps

#SurfaceActionCapabilityExpectedProvenance
1/console/{tenantId}/configuration/accounting/recurringBatches (New Recurring Batch)Create dated weekday flows for card and check collections, with late-afternoon rolls.CAP-ACC-BAT-009Each configuration records its next run and an initial Open collection for today.test
2/console/{tenantId}/configuration/accounting/batchAssignmentsSet checks as the default and add a merchant-account card-payment rule.CAP-ACC-BAT-011Saved settings retain the ordered card rule in the first position.test
3evaluateBatchAssignment (Test Transaction panel)Evaluate representative card and check facts.CAP-ACC-BAT-011Card facts select the matching flow; check facts select the default.test
services-accounting:modules/batches/tests/e2e/batch-assignment-settings.e2e.spec.js#answers the default with no position when no rule matches
4/console/{tenantId}/accounting/invoices/new and the payment screensIssue an invoice and record both payment kinds without an explicit batch.CAP-ACC-BAT-007Assignment places each document in the selected current intake collection.test
5accounting.recurring-batch.roll (the schedule fires)Deliver the configured afternoon occurrence.CAP-ACC-BAT-010A new Open collection becomes current; the prior collection is closed if populated or removed if empty.test
6postBatches (requested by the roll)Let the roll submit accounting work for the closed collection.CAP-ACC-BAT-013Posting completes without a staff request and run history identifies the job.test

Alternate and Failure Paths

PathFrom stepConditionPath takenOutcomeProvenance
alternate5Delivery repeats an already-handled occurrence.The handler returns the existing result without opening or posting again.The occurrence retains one resulting collection and posting request.test
services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#opens nothing for the same occurrence delivered again, and answers the same batch
failure1Today is outside the unit’s configured fiscal calendar.Configuration is retained with the initial-intake refusal and no first batch.Calendar correction is needed before a later intake attempt can succeed.test
services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#saves a recurring batch whose first batch is refused, with the refusal and no batch
failure4The unit no longer has assignment settings.A payment without an explicit batch fails its intake requirement.Staff must select a batch or have assignment configuration restored.test
failure6Automatic posting preparation refuses the retired collection.The collection remains Closed and the run retains the reason.The recorded refusal requires follow-up rather than an assumed successful posting.observed

Assertions

IdStatementProvenance
01An omitted batch uses the current collection selected by the first matching assignment rule.test
02Successful rolling points configuration to the replacement; a protected prior collection can remain Open.observed
03The collection closed by rolling receives one automatic posting.test
04Run history identifies occurrence outcomes and the related collections and accounting work.test
services-accounting:modules/batches/tests/e2e/recurring-batches.e2e.spec.js#answers the run the consumer recorded, every property of it

End-to-end policy: required: End-to-end acceptance is required to connect saved configuration with assignment, occurrence delivery and automatic accounting work.

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.