PAY = money out · SAVE = deposits into the chosen sub-ledger piggy bank · percent inputs use TWO bases: the four splits (Split-Kipp, Split-Brian, Split-Brendan, Split-Loan) are a % of remaining; every other input tier is a % of the check. Each row's percent cell is labelled with the base it uses · filling % clears $ and vice-versa · edits autosave after 1s (no save button) · Check left is the check balance remaining after each row depletes it, top to bottom — the computed memo rows show — there because they never move the balance · Remaining is a computed residual — if it goes negative (the check is over-allocated) the percent splits show — and are skipped on commit rather than committing a negative deposit · Transfer to Treasury (Σ of every tier that saves into a bank), Wire To Brian (Brian Pay + Overhead + Kipp Owe + Split-Kipp + Split-Brian), and Wire To Brendan (Brendan Pay + Split-Brendan + Split-Loan) are computed subtotals — memo totals that re-sum rows which already depleted the check, so they never reduce it themselves · COGS is derived (units sold × per-product rate — set the rates in the COGS block below), never typed in · use + Add row to add your own PAY tier and the ✕ on a row you added to remove it (the built-in rows can't be deleted) · Commit SAVE tiers deposits every SAVE tier's amount into its piggy bank below — it is idempotent, so re-committing the same check deposits nothing again.

Set a collect-per-unit dollar rate per product. The waterfall's COGS tier is then Σ (units sold this cycle × that product's rate) — money set aside to fund the next POs. No FIFO cost layers · rates are global (not per cycle) · units come from the selected cycle's settlement window · edits autosave after 1s (no save button).

Each bank is a persistent running balance. It goes UP when a SAVE waterfall tier commits a check, and DOWN when you type an amount and press Move dollar. The funds check runs on the server inside one transaction — a draw larger than the balance is rejected outright, so a bank can never go negative and never overdraft. Every movement lands in the Activity Log below. Use Adjust to SET or CORRECT a balance (signed — + credits, − debits); the reason is required and travels with the entry. The never-negative guard applies to an adjustment too.

Two loans, tracked differently. Brendan is amortizing: editable terms plus a real payment schedule imported from the Loan sheet tab (read-only here — the wedge never writes it). Kipp is a free-running balance: no schedule, no terms, and it may go negative — that is intentional, so unlike the piggy banks above there is deliberately no funds guard. − Paydown lowers a balance (good — shown green in the history below), + Increase raises the debt (shown red). Note this is the OPPOSITE colouring to the piggy-bank Activity Log, where money coming in is the green one — here a smaller number is the good direction. Every adjustment is recorded in the loan history at the bottom of this block. Term edits autosave after 1s (no save button); they never move a balance.

Every sub-ledger movement, newest first. + is a deposit (a SAVE waterfall tier committing a check), − is a Move-dollar draw. Balance after is the bank's balance recorded at that moment, not a recomputation. Times are shown in your local timezone.