Cashflow

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Plots the balance, not the revenue. A profitable month that nearly ran out of cash looks different here and identical everywhere else.

Derives In and Out from Payments and Expenses where they exist, so the chart maintains itself.

Balance carries forward, so correcting an early month recomputes every one after it rather than leaving a discontinuity.

Periods are a grouping key rather than a date, so weeks, months and quarters all work without a separate module.

How it works

1
Each period gets one row. In and Out are totals, not transactions.
2
With Payments and Expenses present the figures are summed from them, and the module needs no input at all.
3
Balance carries forward, so an edit to an early period recomputes every one after it.
4
The chart plots Balance. In and Out are the columns that explain its shape.

Best for

Trends and comparisons.

Not the right choice for

Exact values — pair it with a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Monthrequired	text	The period. A grouping key rather than a date, so quarters and weeks work unchanged.
Inrequired	money	Summed from Payments where that module exists; otherwise stated per period.
Outrequired	money	Summed from Expenses where that module exists; otherwise stated per period.
Balancerequired	money	Carried forward: previous balance plus In minus Out. Never stated directly.The only field here that answers a question rather than reporting one.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Backward-looking. No forecast, and no dependency on unpaid invoices — a month with a large receivable looks identical to one without.
Periods must be uniform. Mixing months and quarters in one dataset produces a chart with a meaningless axis.
It cannot see money that never came up in conversation, so it is a picture of what the agent was told.
One account. A business with several needs one dataset each and gets no consolidated view.

Before it works

What you have to provide, if anything.

Works alone if the owner states monthly totals.
Better with Payments and Expenses, which turn it from something maintained into something derived.

In practice

A seasonal business with a strong July and a dead August.

“Are we all right for August?”

What was said to the agent

What the agent built

Four months of In, Out and a carried balance, drawn from the payment and expense rows already recorded.

What changed

August came in at 9,200 against 20,100 out. The shortfall was visible in June, which is the difference between arranging an overdraft and needing one.

Better with

These do a different job on the same data. An agent can have all of them.

PaymentsLive

Payments arrive by several routes and the net figure never quite matches what was invoiced.

ExpensesLive

Small spending happens constantly and gets reconstructed painfully at tax time because nobody logged it when it happened.

Revenue KPILive

Someone checks the business daily or weekly and needs the headline figures without opening a report.

Questions

What data does the Cashflow page use?

It reads transaction records the agent has collected. In/out over time. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a chart the wrong choice?

Exact values — pair it with a table. It is best for: trends and comparisons.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.