Transactions
The append-only member payment ledger — every debit and credit, with a reliable audit trail and historical balances.
What it is
Transactions is the member payment ledger: a complete record of every debit and credit across the club. It’s built as an append-only log, which means entries are added rather than rewritten. That gives you a dependable audit trail and lets you reconstruct any member’s balance at any point in time.
Two kinds of entries live here side by side. The billing pipeline writes flight and duty charges automatically, keeping them tied to the activity that produced them. You also enter manual transactions for everything else — payments received, adjustments, fees, and credits. The golden rule is to keep those automated, activity-linked rows separate from your manual entries: to change what a flight or duty cost, fix the flight or the rule and let billing re-run, rather than editing the ledger by hand.
How to use it
- Enter a manual transaction — record a single payment, fee, or adjustment at
/transactions/new. - Bulk-enter transactions — post many entries at once at
/transactions/bulkwhen settling a batch. - Export the ledger — download transactions at
/transactions/exportfor reporting or reconciliation. - Leave billing rows alone — don’t hand-edit flight or duty charges; adjust the source activity and let the pipeline rewrite them.
Related
- Members — whose balances this ledger tracks.
- Pricing Rules — what generates the automated flight charges.
- Periodic Transactions — scheduled charges that post here automatically.
- Transaction Types — the categories entries are classified under.