Rhythm 2.0 Specifications

Appearance

ATS-ACC-BAT-014Resolve posting accounts and retain their snapshots: Capability Test Specification

Markdown

ATS-ACC-BAT-014

Resolve posting accounts and retain their snapshots: Capability Test Specification

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Proves capability
CAP-ACC-BAT-014

Design

Executed by
TST-ACC-BAT-011, TST-ACC-BAT-012, TST-ACC-BAT-013, TST-ACC-BAT-097, TST-ACC-BAT-102, TST-ACC-BAT-105, TST-ACC-BAT-110, TST-ACC-BAT-115

KindAcceptance test setProduct areaAccountingModuleBatch ManagementRevision2

Read atservices-accounting f47cb263react-console baf6dae3rhythm-v2-docs 37405d50

Resolve posting accounts and retain their snapshots: Capability Test Specification ​

Coverage ​

The scenarios define focused checks for this outcome. The coverage map distinguishes specified checks from unresolved proof; executable bindings identify inspected assertions and carry no execution result.

RuleProof Specification or Gap
BR-CAP-ACC-BAT-014-01ATS-ACC-BAT-014-01
BR-CAP-ACC-BAT-014-02ATS-ACC-BAT-014-01, ATS-ACC-BAT-014-10
BR-CAP-ACC-BAT-014-03ATS-ACC-BAT-014-02, ATS-ACC-BAT-014-08, ATS-ACC-BAT-014-09
BR-CAP-ACC-BAT-014-04ATS-ACC-BAT-014-03
BR-CAP-ACC-BAT-014-05ATS-ACC-BAT-014-03
BR-CAP-ACC-BAT-014-06ATS-ACC-BAT-014-04
BR-CAP-ACC-BAT-014-07ATS-ACC-BAT-014-04
BR-CAP-ACC-BAT-014-08ATS-ACC-BAT-014-05
BR-CAP-ACC-BAT-014-09ATS-ACC-BAT-014-06
BR-CAP-ACC-BAT-014-10ATS-ACC-BAT-014-07
BR-CAP-ACC-BAT-014-11ATS-ACC-BAT-014-11

Account correction changes readiness. Account refusal leaves no partial ledger. Resolved destinations drive generated entries. These checks use the related capability’s outcome as part of the setup or verification. Unbound interactions remain proposed until a suite executes the complete chain.

Coverage

  • Rule covered
  • Transition not-applicable
  • Validation covered
  • Permission not-applicable
  • Edge gap: FND-ACC-BAT-068
  • Failure covered
  • Boundary gap: FND-ACC-BAT-068
  • Concurrency gap: FND-ACC-BAT-068
  • Invariant covered
  • Interaction covered

Test Scenarios

11 scenarios proving CAP-ACC-BAT-014; 7 bound to an existing test.

01 Posting resolves configuration after issuanceruleapitest
Proves
BR-CAP-ACC-BAT-014-01 BR-CAP-ACC-BAT-014-02
Preconditions
Unit and product accounts are initially absent.
Steps
Issue invoices, memos and a write-off, configure accounts and post.
Expected
Issuance needs no accounts; posting uses current product and unit settings, including unit defaults for the unconfigured debit-memo line.
Data
Provide the gl-at-posting fixtures.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#issues the invoice and creates the memos and the write-off with no GL account, default or setup anywhere
02 Missing account errors identify the affected linefailurebrowsernegativetest
Proves
BR-CAP-ACC-BAT-014-03
Preconditions
The batch contains a valid invoice and another lacking product revenue configuration.
Steps
Post, configure the missing account and retry.
Expected
The first attempt writes nothing and identifies the invoice, line and revenue purpose; the configured retry succeeds.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#fails the batch naming the gala invoice, its line and the missing revenue purpose, the dues invoice unnamed
03 Snapshots preserve historical account choicesinvariantapitest
Proves
BR-CAP-ACC-BAT-014-04 BR-CAP-ACC-BAT-014-05 INV-DOM-ACC-BAT-003-04
Preconditions
October has posted.
Steps
Inspect snapshots, change product configuration and post a November memo against October.
Expected
Snapshots retain accounts and resolution time; the memo uses those choices and October remains unchanged.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#alters neither October’s posted entries nor its snapshot
04 Write-off policy selects the debit accountrulebrowsernegativetest
Proves
BR-CAP-ACC-BAT-014-06 BR-CAP-ACC-BAT-014-07
Preconditions
Units use expense, original-revenue and allowance policies; one allowance account is missing.
Steps
Post their write-offs, change policy and reverse one.
Expected
The selected accounts follow each policy; missing allowance configuration fails its batch; reversal mirrors the original account choices.
Data
Provide the write-off policy fixtures.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/posting/write-off-policy.integration.spec.js#fails the batch naming the write-off, the allowance purpose and the unit; nothing posts, not even the invoice
05 Discounts reduce credited revenueruleapitest
Proves
BR-CAP-ACC-BAT-014-08
Preconditions
An invoice line has a discount.
Steps
Post the invoice.
Expected
Revenue is net with no separate discount line; the snapshot retains gross, discount, net, discount account and method.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#preserves the discount in the posted snapshot: the gross, the discount and the net on the line, the discount product’s revenue account and the net-of-revenue method
06 Tax account resolution has a fallbackvalidationapinegativetest
Proves
BR-CAP-ACC-BAT-014-09
Preconditions
A taxed invoice exists and a later invoice lacks both rate and unit tax accounts.
Steps
Post each, configure the unit default and retry the later invoice.
Expected
Tax uses and snapshots the selected account; the missing-account failure identifies rate and unit before configuration permits retry.
Data
Provide tax rates.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/posting/rebuilt-tax.integration.spec.js#puts the batch in error naming the rate and the unit when neither the rate nor the unit names a tax payable account, writing no entry
07 Posting reads current dimensions and splitsruleapitest
Proves
BR-CAP-ACC-BAT-014-10
Preconditions
One invoice product’s split rises from twenty-five to fifty percent after issuance; another has department and project settings.
Steps
Post both invoices.
Expected
Posting credits fifty dollars through the revised split, and the revenue lines retain the configured department and project codes.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/posting/rebuilt-documents.integration.spec.js#credits the revenue as the splits stand at posting: 50.00 to the line’s revenue account, 50.00 to the split’s, not the 25% the product had at issue
08 Account correction changes readinessinteractionapiproposed
Proves
BR-CAP-ACC-BAT-012-03 BR-CAP-ACC-BAT-014-03
Preconditions
Morning’s invoice product has no resolvable revenue account.
Steps
Preview, configure the missing account and preview again.
Expected
The first result names the missing account and the second includes Morning as a candidate.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/services/engine/preview-batches.ts:previewBatchPostings; services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#fails the batch’s validation with an error naming the invoice, the missing accounts receivable account, the product’s setup and the unit’s default
09 Account refusal leaves no partial ledgerinteractionapiproposed
Proves
BR-CAP-ACC-BAT-013-10 BR-CAP-ACC-BAT-014-03
Preconditions
Morning holds an issued invoice whose product and unit have no revenue account.
Steps
Submit posting and inspect the batch, entries and the line’s resolution error.
Expected
Morning is Error with an identifying account reason and no current entries.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/tests/integration/services/posting/rebuilt-posting-edges.integration.spec.js#posts January, puts April in error naming the application whose credit's batch is not posted, and May in error as April's dependent; services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#fails the batch’s validation with an error naming the invoice, the missing accounts receivable account, the product’s setup and the unit’s default
10 Resolved destinations drive generated entriesinteractionapiproposed
Proves
BR-CAP-ACC-BAT-014-02 BR-CAP-ACC-BAT-015-03
Preconditions
An issued invoice line lacks product accounting but the unit has its revenue default.
Steps
Post the batch and inspect the line snapshot and revenue ledger line.
Expected
Both identify the unit’s resolved revenue account.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/tests/integration/services/posting/gl-resolution-at-posting.integration.spec.js#posts the invoice to the resolved accounts: the receivable from the unit’s default, the revenue from the product’s setup, the discounted line net of its discount; services-accounting:modules/batches/tests/integration/services/posting/rebuilt-tax.integration.spec.js#posts the invoice per line: the receivable debited the total with the tax, revenue credited the net, and a tax credit per tax line to its account
11 Cross-unit revenue requires both clearing accountsvalidationapinegativeproposed
Proves
BR-CAP-ACC-BAT-014-11
Preconditions
A product uses another unit’s revenue account and the required inter-unit mappings are incomplete.
Steps
Attempt posting with one mapping missing, supply the pair through a controlled fixture and retry.
Expected
The first attempt refuses generation; the complete mapping permits balanced inter-unit account movements.
Data
Owned records in an isolated workspace with the stated calendar and accounting setup.
Source
services-accounting:modules/batches/db/business-unit-inter-entity-accounts.table.ts; FND-ACC-BAT-011

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.

Rhythm Software