Rhythm 2.0 Specifications

Appearance

MOD-ACC-RECReconciliation

Markdown

MOD-ACC-REC

Reconciliation

Markdown
  • DocumentDraft

KindModule charterProduct areaAccountingModuleReconciliationRevision3

Read atservices-accounting f47cb263react-console baf6dae3

Reconciliation ​

Purpose ​

Reconciliation gives finance staff a shared place to explain processor deposits, review outstanding settlement money and prepare the reconciliation contribution to month-end close. Preparation, independent approval and later correction form distinct parts of the workflow. Supporting records make the explanation reviewable.

Boundary ​

This module owns the deposit explanation and its reconciliation records. Transactions supplies the source money movements; Books supplies financial configuration; Batch Management delivers approved accounting to the ledger; Month-End Close owns the period decision. Platform services provide permission evaluation, attention delivery and export execution. The console presents the reconciliation workflows described by these artifacts.

Features ​

FeatureName
FEAT-ACC-REC-01Processor Payout Records
FEAT-ACC-REC-02Deposit Matching
FEAT-ACC-REC-03Reconciliation Approval and Correction
FEAT-ACC-REC-04Expected Settlement Money
FEAT-ACC-REC-05Problem Investigation and Monitoring
FEAT-ACC-REC-06Period Assessment and Daily Summary
FEAT-ACC-REC-07Financial Record Controls

The feature groups organize the capability and journey catalogues. The frontmatter coverage catalogue connects the scoped operations, tables and permission keys to their specification homes.

Capabilities ​

IdFeatureTitleProduct intentEvidence
CAP-ACC-REC-001FEAT-ACC-REC-01Record processor payouts without duplicate entryconfirmedobserved
CAP-ACC-REC-002FEAT-ACC-REC-01Correct payout records while preserving finalized moneyconfirmedobserved
CAP-ACC-REC-003FEAT-ACC-REC-01Verify payouts using bank evidenceconfirmedinconsistent
CAP-ACC-REC-004FEAT-ACC-REC-01Find payouts with their status and activityconfirmedobserved
CAP-ACC-REC-005FEAT-ACC-REC-04Track payment effects and expected processor settlementconfirmedobserved
CAP-ACC-REC-006FEAT-ACC-REC-04Distinguish money in transit from missing settlementconfirmedobserved
CAP-ACC-REC-007FEAT-ACC-REC-04Explain partial or unrecoverable settlement moneyproposedobserved
CAP-ACC-REC-008FEAT-ACC-REC-02Prepare a payout explanation from matching evidenceconfirmedobserved
CAP-ACC-REC-009FEAT-ACC-REC-02Allocate settlement money to one explanationconfirmedobserved
CAP-ACC-REC-010FEAT-ACC-REC-02Document processor deductions and correctionsconfirmedobserved
CAP-ACC-REC-011FEAT-ACC-REC-03Finalize a balanced explanation with eligible approvalconfirmedobserved
CAP-ACC-REC-012FEAT-ACC-REC-03Abandon a draft and release its moneyconfirmedobserved
CAP-ACC-REC-013FEAT-ACC-REC-03Reverse an approved explanation and prepare its replacementconfirmedobserved
CAP-ACC-REC-014FEAT-ACC-REC-03Carry reconciliation accounting through operational postingconfirmedobserved
CAP-ACC-REC-015FEAT-ACC-REC-05Investigate and resolve reconciliation concernsconfirmedobserved
CAP-ACC-REC-016FEAT-ACC-REC-05Accept an understood problem with the required approvalconfirmedobserved
CAP-ACC-REC-017FEAT-ACC-REC-05Detect reconciliation concerns through scheduled checksconfirmedobserved
CAP-ACC-REC-018FEAT-ACC-REC-06Assess reconciliation work before period closeconfirmedobserved
CAP-ACC-REC-019FEAT-ACC-REC-06Review reconciliation stages and attentionconfirmedobserved
CAP-ACC-REC-020FEAT-ACC-REC-07Separate duties and retain trustworthy reconciliation recordsconfirmedpartially-observed

Journeys ​

IdFeatureTitleProduct intentEvidenceE2E policy
JNY-ACC-REC-001FEAT-ACC-REC-02Prepare and independently approve a processor depositconfirmedobservedrequired
JNY-ACC-REC-002FEAT-ACC-REC-01Record and check a payout against its bank statementconfirmedinconsistentrequired
JNY-ACC-REC-003FEAT-ACC-REC-03Reverse and replace an incorrect approved explanationconfirmedobservedrequired
JNY-ACC-REC-004FEAT-ACC-REC-04Resolve missing settlement after partial processor paymentconfirmedobservedrequired
JNY-ACC-REC-005FEAT-ACC-REC-06Complete reconciliation review before month-end closeconfirmedobservedrequired
JNY-ACC-REC-006FEAT-ACC-REC-07Assign separate preparation and approval responsibilitiesconfirmedpartially-observedrequired

Testing Artifact Tree ​

text
planning/
  features/      seven features name their acceptance suites
  acceptance/    seven feature acceptance suites
design/
  tests/         twenty capability test specifications
implementation/
  tests/         ninety-eight existing executable suite registrations

The artifact inventory in frontmatter names each test specification, feature suite and executable registration. Specified coverage and executable coverage remain separate from execution results; no registered source suite is run by this documentation back-fill.

Owns
Processor payouts and their verification, supporting documents and lifecycleSettlement obligations, expected timing, matching allocations and resolutionReconciliation drafts, payout membership, approval, abandonment and reversalAccounting requests awaiting operational batch postingReconciliation exceptions and their review recordsReconciliation findings supplied to fiscal closeOverview summaries, daily checks and the reconciliation audit historyRequest-key tracking and seeded settlement calendar definitions

Repositories Read

RepositoryPaths
services-accountingservices-accounting:modules/reconciliation
services-accounting:aws/accounting.service.ts (payouts, reconciliation-batches, settlement-items, reconciliation-exceptions permission groups; ReconciliationBuiltInPolicies)
services-accounting:aws/accounting.responsibilities.ts (accounting.reconciliation)
services-accounting:tests/unit/reconciliation-permissions.spec.ts
services-accounting:tests/unit/reconciliation-matching-routes.spec.ts
services-accounting:docs/reconciliation
services-accounting:docs/milestones/ACCT-M8-payout-reconciliation.md
services-accounting:docs/milestones/plans/ACCT-M8-plan.md
services-accounting:docs/forge-handoff/accounting.md (cited by the milestone record)
react-consolereact-console:app/(console)/console/[tenantId]/accounting/reconciliation
react-console:components/accounting/reconciliation
react-console:lib/accounting/reconciliation
react-console:lib/authz/permissions.ts and lib/authz/backend-aliases.ts (reconciliation keys)
react-console:e2e/mock/accounting-reconciliation.mock.spec.ts
react-console:acceptance/accounting/inventory (area REC)
react-console:acceptance/accounting/journeys/reconciliation-close (ACT-ACC-0590 to 0612, 0623 to 0629)
react-console:acceptance/accounting/playwright/journeys/reconciliation-close
react-console:acceptance/accounting/reports/defects/reconciliation-close.md

Does Not Own

RecordOwner
Financial configuration, account destinations, settlement overrides and approval settingsMOD-ACC-BKS (Books, business units and chart of accounts)
Source payment documents and their settlement obligationsMOD-ACC-TRX (Transactions)
Operational batches and the ledger posting of reconciliation requestsMOD-ACC-BAT (Batch management)
Fiscal periods, close locks, checklists and close recordsMOD-ACC-CLS (Month-end close)
Shared scheduled execution for accounting workMOD-ACC-BKS (Books; modules/maintenance)
Attention delivery and responsibility assignmentMOD-PFM-ELG
Role administration and permission evaluationMOD-PFM-SEC
Workspace export executionMOD-PFM-QRY
Future processor import workflowsMOD-PFM-INT

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