Rhythm 2.0 Specifications

Appearance

CAP-ACC-BKS-012Configure the methods used to receive money

Markdown

CAP-ACC-BKS-012

Configure the methods used to receive money

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

Planning

Feature
FEAT-ACC-BKS-04
Exercised by
FAS-ACC-BKS-04-01, FAS-ACC-BKS-04-02, FAS-ACC-BKS-04-03, FAS-ACC-BKS-04-04
Key concepts
CON-ACC-BKS-006
Actors
ACT-ACC-001, ACT-ACC-002, ACT-ACC-003, ACT-ACC-005
Related
CAP-ACC-BKS-019, CAP-ACC-BKS-003
Proved by
ATS-ACC-BKS-012

Implementation

Executable suites
TST-ACC-BKS-057, TST-ACC-BKS-093, TST-ACC-BKS-171, TST-ACC-BKS-174

KindCapabilityProduct areaAccountingModuleBooks, Business Units and Chart of AccountsRevision1

Read atservices-accounting f47cb263react-console baf6dae3

Configure the methods used to receive money ​

Purpose ​

Finance staff name payment methods and define how each is offered and recorded.

How It Works ​

The administrator reviews the methods available to the workspace. They adapt names and reference prompts to the finance team’s language. A newly added method chooses the payment behaviour that later workflows use. Availability determines where the method can be offered. Offline money remains work that staff record in the console. A change that conflicts with method behaviour is refused. System methods remain available, while other obsolete methods can be deactivated.

Relationships ​

Provisioning supplies system methods, and payment workflows interpret each method’s behaviour.

The Formal Contract

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

Outcomes
Configured methods retain the payment behaviour transactions interpret.Initial system methods remain present and active.Offline receipt remains a staff-only channel.
Surfaces
consoleapi
Intent sources
services-accounting:docs/architecture/accounting-2.0/02-decisions.md#2.11 The payment methods, deferred payment and order collection decisions (Andrew, 2026-10-18 evening); decision D-01services-accounting:docs/architecture/accounting-2.0/02-decisions.md#2.11 The payment methods, deferred payment and order collection decisions (Andrew, 2026-10-18 evening); decision D-05services-accounting:docs/architecture/accounting-2.0/02-decisions.md#2.11 The payment methods, deferred payment and order collection decisions (Andrew, 2026-10-18 evening); decision D-08

Controls

24 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-003 TC-IAM-004 TC-IAM-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-DAT-001 TC-DAT-004 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005

Permissions

KeyChecked atScope
accounting.payment-methods.readapitenant
accounting.payment-methods.createapitenant
accounting.payment-methods.updateapitenant

Business Rules

8 rules, 6 to be proved before approval. A rule's product intent is derived from its origin: 8 confirmed by a product decision, the rest inheriting this capability's confirmed.

IdRuleKindEnforced atProvenance
01must prove
Confirmed
A payment method chooses card, bank-debit or offline behaviour at creation and cannot later change that behaviour.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#2.11 The payment methods, deferred payment and order collection decisions (Andrew, 2026-10-18 evening); decision D-01
proved by ATS-ACC-BKS-012-01, ATS-ACC-BKS-012-10, TST-ACC-BKS-057, TST-ACC-BKS-093, TST-ACC-BKS-171
invariantapi, service, databasetest
services-accounting:modules/books/tests/e2e/payment-methods.e2e.spec.js#answers 409 payment_method_behaviour_immutable to another behaviour
02must prove
Confirmed
The five system methods—credit card, ACH, cash, paper check and wire—remain active and keep deposit handling, while permitted name, description, ordering, reference, availability and bounce choices may be changed.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#2.11 The payment methods, deferred payment and order collection decisions (Andrew, 2026-10-18 evening); decision D-01
proved by ATS-ACC-BKS-012-02, ATS-ACC-BKS-012-09, TST-ACC-BKS-093
policyservice, databasetest
services-accounting:modules/books/tests/integration/services/persistence/payment-methods.integration.spec.js#refuses to be deactivated, 409 payment_method_system
03must prove
Confirmed
Offline methods are console-only; every method has distinct nonempty channels, defaulting to console for offline, console and portal for bank debit, and all channels for card.
proved by ATS-ACC-BKS-012-03, ATS-ACC-BKS-012-07, TST-ACC-BKS-093
validationapi, service, databasetest
services-accounting:modules/books/tests/integration/services/persistence/payment-methods.integration.spec.js#refuses an offline method offered in the portal, naming the rule
04must prove
Confirmed
Only offline methods may allow bouncing or deposit into undeposited funds.
proved by ATS-ACC-BKS-012-04, TST-ACC-BKS-093, TST-ACC-BKS-174
validationservice, databasetest
services-accounting:modules/books/tests/integration/services/persistence/payment-methods.integration.spec.js#refuses a card method that may bounce
05must prove
Confirmed
A prompted reference has a label, and an unprompted reference has none.
proved by ATS-ACC-BKS-012-04, TST-ACC-BKS-093, TST-ACC-BKS-174
validationservice, databasetest
services-accounting:modules/books/tests/integration/services/persistence/payment-methods.integration.spec.js#refuses a prompted reference without its label
06
Confirmed
Methods have no delete operation despite the published delete permission; non-system methods can instead be deactivated.
policyapiobserved
services-accounting:aws/accounting.service.ts:PaymentMethodsPermissions
07must prove
Confirmed
Migration adds active cashier’s check, money order and offline card methods and inactive purchase-order and payroll-deduction methods, all outside the protected system set.
proved by ATS-ACC-BKS-012-05, TST-ACC-BKS-093
lifecycleservicetest
services-accounting:modules/books/tests/integration/services/persistence/payment-methods.integration.spec.js#writes cashier’s check, money order and offline card active, and the two legacy methods inactive, none a system method
08
Confirmed
Method lists sort by configured order and name and filter by behaviour, channel, public-link availability or active state.
policyapi, servicetest
services-accounting:modules/books/tests/integration/services/persistence/payment-methods.queries.integration.spec.js#orders by sort order, then name, then id, answering only the tenant’s methods

Scenarios

IdGivenWhenThenProvenance
01Staff need a check-number prompt on check payments.The administrator renames Paper Check and configures a required reference labelled Check #.The method remains offline and requests the reference when used.test
services-accounting:modules/books/tests/e2e/payment-methods.e2e.spec.js#renames a system method
02The administrator has defined an offline Lockbox method.They try to make it available in the portal.The save is refused because offline receipt is console work.test
services-accounting:modules/books/tests/e2e/payment-methods.e2e.spec.js#answers 400 to an offline method offered in the portal, naming the rule

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