Tonder reference (source blueprint)

These are Tonder's own docs for the finances engine, included verbatim as the blueprint that the Vecnet build spec is derived from. They describe Tonder's AWS / NoSQL implementation (DynamoDB, MongoDB, SQS, Lambda); the Vecnet spec is the Supabase/Postgres port of the same intent.

Precedence

If anything here conflicts with the build spec, the build spec wins. The reference docs describe how Tonder does it today; the spec describes how Vecnet rebuilds it. See the big shift for the port rationale.

How the reference maps to the spec

Tonder service (reference)	Vecnet docs
usrv-finances → finances/	Domain model · Data model · Flows
usrv-batch-transaction-report → cycle engine	Settlement reports
usrv-settlement → orchestration	Settlement orchestration

usrv-finances — the ledger engine

Doc	Covers
Architecture	hexagonal layering, the AWS stack
Domain glossary	enums, account codes, journal types
Accounts CRUD	account CRUD + balance mechanics
Accounting	double-entry: journals + ledger entries
Fee rules	fee-rule model + specificity matching
Fee calculation	fee formulas per transaction type
Configurations	per-business module flags
Transaction processing	the orchestrator (event → fees → accounting)
Settlements	approve/confirm settlement flow
Rolling reserve	scheduled reserve release
Internal transfers	fund movements / adjustments
Daily ledger	daily XLSX reports + balance snapshots

Settlement services

• usrv-batch-transaction-report — the settlement report / cycle engine (T+0 / T+1 / T+2).
• usrv-settlement — settlement orchestration + treasury (force_decrease).

The canonical master spec is also available verbatim: Full build spec (source).