Rhythm 2.0 Specifications

Appearance

DOM-ACC-REC-003Payout Reconciliation

Markdown

DOM-ACC-REC-003

Payout Reconciliation

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Specified by
CON-ACC-REC-003

Design

Owned by
SVC-ACC-REC-reconciliation

KindDomain objectProduct areaAccountingModuleReconciliationRevision3

Read atservices-accounting f47cb263react-console baf6dae3

Payout Reconciliation ​

What It Models ​

A reconciliation retains the explanation of one or more deposits from the same merchant. Preparation selects effects and records deductions; approval seals the explanation and creates its accounting requests.

Identity and Attributes ​

The numbered record keeps immutable financial context. Open display states describe preparation, and approval recomputes holdings rather than trusting maintained counters.

Relationships ​

The explanation owns payout links, settlement claims and dismissals, including retained release history. Manual effects stay in the settlement collection, while concerns and readiness refer to the explanation.

Invariants ​

The structured invariants define compatibility, exclusive holdings, approval independence, sealing and request integrity. Dismissals have no version effect, and finalization can repair counters from actual holdings.

How It Is Stored and Shared ​

Batch Management consumes ledger requests and determines their posted status. Close consumes readiness; Reconciliation also hosts shared Accounting request-key infrastructure without owning other modules’ commands.

Open Design Questions ​

The independence waiver lacks an audited setting command. Contributor eligibility and atomic draft saving remain product decisions.

Relationships

ToCardinalityOwnershipCrosses a serviceOn archive or delete
DOM-ACC-REC-001one-to-many (one to fifty payouts)The explanation owns links and claims; settlement records remain in the outstanding ledger.no
DOM-ACC-REC-002one-to-many claims; one-to-many manual entries it createdThe explanation owns links and claims; settlement records remain in the outstanding ledger.no
DOM-ACC-REC-004one-to-manyThe concern retains its own references to affected records.no
DOM-ACC-REC-005many-to-one per periodAssessment reads the relationship without owning the underlying record.no

Invariants

InvariantProtectsEnforced atProvenance
INV-DOM-ACC-REC-003-01
Every payout link and claim shares its reconciliation’s fixed unit, merchant and currency.
databaseobserved
services-accounting:modules/reconciliation/db/reconciliation-batches.table.ts:reconciliation_batches_link_target_uq
INV-DOM-ACC-REC-003-02
Finalization requires an exact zero difference recomputed from integer claim and payout amounts.
service, databasedocumented
services-accounting:docs/milestones/plans/ACCT-M8-plan.md#4. Assumptions (from the design; each becomes a rule in the catalog if not already)
INV-DOM-ACC-REC-003-03
Stored lifecycle permits open to finalized or voided, then finalized to reversed.
service, databaseobserved
services-accounting:modules/reconciliation/services/rules/transitions.ts:BATCH_TRANSITIONS
INV-DOM-ACC-REC-003-04
Approval seals the record and holdings; reversal permits release, while reversed and voided records remain terminal.
databaseobserved
services-accounting:modules/reconciliation/db/reconciliation-batches.table.ts:reconciliation_batches_seal_trigger
INV-DOM-ACC-REC-003-05
New holdings require an open record and whole-item claim amounts.
databaseobserved
services-accounting:modules/reconciliation/db/reconciliation-batch-links.table.ts:seal_reconciliation_batch_children
INV-DOM-ACC-REC-003-06
The default independence requirement excludes preparers; disabling it marks every approval waived.
servicedocumented
services-accounting:docs/milestones/plans/ACCT-M8-plan.md#D3. Whether the preparer may finalize
INV-DOM-ACC-REC-003-07
A reversal approver must differ from the requester.
service, databaseobserved
services-accounting:modules/reconciliation/db/reconciliation-batches.table.ts:reconciliation_batches_reversal_approver_check
INV-DOM-ACC-REC-003-08
Unique effect keys prevent duplicate accounting requests in the workspace.
databaseobserved
services-accounting:modules/reconciliation/db/reconciliation-postings.table.ts:reconciliation_postings_event_key_uq
INV-DOM-ACC-REC-003-09
Immutable requests stay within a unit, contain one to twenty lines and balance per currency at commit.
databaseobserved
services-accounting:modules/reconciliation/db/reconciliation-postings.table.ts:reconciliation_postings_balance_trigger
INV-DOM-ACC-REC-003-10
Batch Management writes ledger entries; unreversed operational posting determines request completion.
servicedocumented
services-accounting:docs/reconciliation/architecture.md#16.2 The route: ledger requests ride in batches (agreed 2026-10-17)
INV-DOM-ACC-REC-003-11
Collection bounds are ten thousand claims, two hundred lifetime manual entries, fifty payouts and fifty evidence files.
service, databaseobserved
services-accounting:modules/reconciliation/db/reconciliation-batches.table.ts:MAX_BATCH_CLAIMS
INV-DOM-ACC-REC-003-12
Preparation updates totals atomically with its financial changes; finalization can replace counters with recomputed holdings.
serviceobserved
services-accounting:modules/reconciliation/services/batch-lifecycle/finalize-batch.ts:finalizeReconciliationBatch

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