Rhythm 2.0 Specifications

Appearance

CAP-ACC-TRX-019Maintain customer-specific collection choices

Markdown

CAP-ACC-TRX-019

Maintain customer-specific collection choices

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-ACC-TRX-05
Exercised by
FAS-ACC-TRX-05-01, FAS-ACC-TRX-05-03, FAS-ACC-TRX-05-04
Key concepts
CON-ACC-TRX-005
Actors
ACT-ACC-012, ACT-ACC-002, ACT-ACC-021
Related
CAP-ACC-TRX-001, CAP-ACC-TRX-017, CAP-ACC-TRX-020
Proved by
ATS-ACC-TRX-019

Implementation

Executable suites
TST-ACC-TRX-006, TST-ACC-TRX-088

KindCapabilityProduct areaAccountingModuleTransactionsRevision1

Read atservices-accounting f47cb263

Maintain customer-specific collection choices ​

Purpose ​

Finance records exceptions to default collection behavior for a CRM party.

How It Works ​

Staff read the party’s saved terms or the marked defaults. Creating an exception produces one customer-terms record. Replacing it requires the version the editor read and supplies the complete intended settings. Missing settings return to their defaults rather than retaining earlier overrides. Invalid terms or protected records prevent the write. Removing the exception restores default behavior. Commerce reads these choices during checkout, while the product should provide a dedicated staff editor.

Relationships ​

  • Issue customer bills and numbered quotes supplies or continues the related financial work.
  • Explain a customer’s current financial position supplies or continues the related financial work.
  • Coordinate financial commands across applications supplies or continues the related financial work.

The Formal Contract

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

Outcomes
Finance records exceptions to default collection behavior for a CRM party.Removing the exception restores default behavior. Commerce reads these choices during checkout, while the product should provide a dedicated staff editor.
Surfaces
api
Intent sources
services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-06services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-02

Controls

24 controls apply, from the corpus control catalogue.

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

Permissions

KeyChecked atScope
accounting.customer-terms.readapitenant
accounting.customer-terms.manageapitenant

Business Rules

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

IdRuleKindEnforced atProvenance
01must prove
Confirmed
A contact or organization without saved terms receives marked defaults, and each party can have at most one saved terms record.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-06
proved by ATS-ACC-TRX-017-08, ATS-ACC-TRX-019-01, ATS-ACC-TRX-019-08, TST-ACC-TRX-006, TST-ACC-TRX-088
policyservice, databasetest
services-accounting:modules/transactions/tests/e2e/customer-terms.e2e.spec.js#it answers the defaults, saying so, before Acme has a record
02must prove
Confirmed
Creation omits a version and replacement requires the version read; duplicate creation and stale saves fail, while omitted settings revert to defaults.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-06
proved by ATS-ACC-TRX-019-02, ATS-ACC-TRX-019-08, TST-ACC-TRX-088
validationservicetest
services-accounting:modules/transactions/tests/integration/services/persistence/customer-terms.integration.spec.js#it refuses a replacement at a stale version, writing nothing
03must prove
Confirmed
Collection choices use fixed vocabularies, allow-lists permit at most fifty unique options with empty meaning unrestricted, and default payment terms must be active within the workspace.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-02
proved by ATS-ACC-TRX-017-08, ATS-ACC-TRX-019-03, ATS-ACC-TRX-019-09, TST-ACC-TRX-088
validationapi, service, databaseobserved
services-accounting:modules/transactions/aws/api/customer-terms.schemas.ts:customerTermsPutSchema
04must prove
Confirmed
Removing terms restores default behavior, and a stale version prevents deletion.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-06
proved by ATS-ACC-TRX-019-04, TST-ACC-TRX-088
lifecycleservicetest
services-accounting:modules/transactions/tests/integration/services/persistence/customer-terms.integration.spec.js#it refuses a delete at a stale version, keeping the record
05must prove
Confirmed
Payment terms referenced as a customer default are protected from deletion.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-06
proved by ATS-ACC-TRX-019-05, TST-ACC-TRX-088
invariantdatabasetest
services-accounting:modules/transactions/tests/integration/services/persistence/customer-terms.integration.spec.js#it keeps terms a party names from being deleted (409, the key)
06must prove
Confirmed
Terms read and manage authorities are separate, and Commerce can retrieve terms through its billing service at checkout.
origin: services-accounting:docs/architecture/accounting-2.0/02-decisions.md#D-06
proved by ATS-ACC-TRX-019-06, ATS-ACC-TRX-019-08, TST-ACC-TRX-006
permissionapitest
services-accounting:modules/transactions/tests/e2e/customer-terms.e2e.spec.js#it refuses the write and the delete without accounting.customer-terms.manage (403), the reader’s key not enough
07
Proposed
The product should provide a staff editor for customer terms; the current console only shows them alongside financial standing.
policyconsoleinferred
react-console:lib/accounting/transactions/types.ts
08must prove
Proposed
An update lock blocks replacing or deleting customer terms, while a deletion-only lock blocks removal.
proved by ATS-ACC-TRX-019-07, TST-ACC-TRX-088
validationserviceobserved
services-accounting:modules/transactions/services/persistence/customer-terms.ts

Scenarios

IdGivenWhenThenProvenance
01An employer remits for staff and uses forty-five-day terms.Save its customer terms and create an invoice without requested terms.Financial standing includes the saved choices and the invoice derives its forty-five-day due date.test
services-accounting:modules/transactions/tests/integration/services/invoices/customer-terms-precedence.integration.spec.js#it takes the bill-to’s default terms when the request names none, the due date 45 days after the invoice date
02Two editors started from the same terms version.Save the second editor’s replacement after the first succeeds.The obsolete version is rejected and the first saved state remains.test
services-accounting:modules/transactions/tests/e2e/customer-terms.e2e.spec.js#it refuses a replacement at a stale version: 409

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