One ledger for dues and event revenue
Dues invoices and event revenue land on the same ledger, backed by a real Postgres payments layer rather than the deterministic demo data most of the rest of the product runs on for the pitch build. That distinction matters if you're evaluating this seriously: the finance numbers you'd see in a pilot are the real payment records, not seed data.
Payment rails built for where chambers actually operate
Stripe covers most Western card processing; TapPay, JKoPay, and LinePay cover Taiwan and broader APAC payment methods that a Stripe-only tool simply can't take. A bilateral or bi-national chamber running dues in more than one region needs this, not as a nice-to-have but because the alternative is manually reconciling wire transfers.
Reconciling to QuickBooks, not to faith
The finance workspace syncs two-way with QuickBooks Online, matching every payment, line item, and tax code automatically. The reconciliation panel shows exactly what's synced and when, so month-end close isn't a research project — it's a status you can check.