Source
Supported bank CSV files remain the starting evidence.
Financial software should explain where its numbers come from. This is the operating logic behind Money Calculated: source records preserved, transformations structured and limitations made clear.
Every stage solves a different data-quality problem. Keeping them separate makes errors easier to find and rules easier to improve.
Supported bank CSV files remain the starting evidence.
Dates, amounts, text and account fields are standardised.
Useful fields are derived without overwriting the source.
Priority-based rules assign financial meaning.
Measures and dashboards answer defined questions.
Known exceptions receive deliberate treatment when a broad rule would be wrong.
Movements between owned accounts are identified before spending totals are produced.
Reusable patterns assign specific categories to repeatable activity.
Unresolved records remain reviewable instead of being silently forced into a category.
| Measure | Working definition | Important exclusions |
|---|---|---|
| Income | External money received and classified as income | Transfers between owned accounts; reversed items |
| Expenses | External outflows classified as genuine costs | Internal transfers; savings movements |
| Net cash flow | Income less genuine expenses for the selected period | Account-to-account movement |
| Savings rate | Net saving or positive cash-flow measure divided by relevant income | Definitions vary; the system states the version used |
| Specific categorisation | Records assigned beyond a broad fallback label | Unresolved or generic fallback rows |
Why definitions matter: There is no single universal personal-finance taxonomy. Money Calculated prioritises consistent, visible definitions so comparisons remain useful over time.

Join early access for a finance system built to show its work, preserve your control and improve with honest feedback.