AI automation
A ledger that never double-counts a dollar
SixFlow's internal finance system: live revenue and expense tracking from three sources, a monthly close, a cash-floor partner payout model, and a hosted dashboard.
The problem
Money lived in three places that didn't talk to each other: a bank account, a credit card, and Stripe. Reconciling them by hand each month risked the one mistake that actually matters: counting the same dollar twice, once as revenue and once as the deposit that revenue produced.
Partner payouts had no floor. Without one, a lean month could pull the business's own cash cushion out from under it just to make a distribution look normal.
What we built
Plaid and Stripe feed a unified ledger with one idempotency rule: every transaction keys on its source and external ID, so nothing lands twice. Stripe revenue is recognized from Stripe's own balance transactions; the matching payout deposit in the bank account is marked as an internal transfer, never counted again as revenue.
n8n stays thin: it fetches, upserts raw rows, and calls Postgres RPCs. All the actual math, dedup, transfer-matching, categorization, and the monthly close, lives in version-controlled SQL. Anything ambiguous gets flagged into a review queue instead of silently guessed at, and the payout formula respects a cash floor: nothing is distributable until the floor clears, then the surplus splits automatically by a fixed percentage between the business and its partners.
The result
Every dollar counted once, split automatically once the floor clears
3
money sources unified: bank, card, Stripe
0
dollars ever counted twice, by design
30/30/40
the payout split, enforced automatically above the floor