Cashflow overview
Pouch’s cashflow intelligence answers one question for a customer: how much can they safely spend right now? It does this by turning their transaction history into three numbers.
| Figure | Meaning |
|---|---|
| Income | Detected recurring income, spread across its period |
| Expense | Detected recurring expense, spread across its period |
| Remaining | income − expense over the window — the free cashflow |
Income and expense are spread, not lumped
A salary doesn’t mean a customer has a month’s money on payday, and rent isn’t a surprise on the 1st. Pouch spreads each detected cycle evenly across its period:
- A monthly income is distributed across the month.
- A weekly expense is distributed across the week.
So on any given day the figures reflect a smooth, sustainable run-rate rather than the spikes of individual transactions.
Income and expense cycles are detected by Pouch’s own engine from the transaction stream — they are not read from a bank’s category tags. Editing a transaction (see Editing transactions) feeds back into detection.
Remaining
Remaining is income − expense measured over a window. The window is the smallest
active granularity — if income is monthly and expense is weekly, the window is weekly — and
it is anchored at a reference date (by default the current week’s Monday).
Only detected income and expense are counted; ad-hoc top-ups aren’t treated as recurring income.
Granularity
Each customer can have an income granularity and an expense granularity:
weekly · fortnightly · monthly · quarterly · annual · fixed_periodThe cashflow window uses the smaller of the two. You can read and update these settings via the Cashflow API.