Passive tracking was not the product goal.

Start with the monthly plan, then confirm what really happened. The app can prepare recurring work and show incomplete items, but it never turns a due item into payment history by itself.

No bank sync is a tradeoff, not a magic security shield.

Enter activity yourself or import a CSV file; the app does not ask for bank-link credentials. You still need to protect the server, passwords, database, HTTPS setup, and backups described in the trust center.

A monthly budget grouped into income, fixed expenses, recurring bills, flexible spending, and payments with planned and actual amounts.
The month stays reviewable as a set of planned and actual records, not only as a summary chart.

Manual does not have to mean repetitive.

Reuse recurring templates, clone a useful month, and preview CSV rows before importing them. Automate setup, then keep payment status and corrections under your control.

Every total should have a path back to evidence.

Open review counts, account movements, and chart totals to see the records behind them. Preview imports and restores before they write data so mistakes are easier to catch.

Self-hosting is part of the product decision.

Run the Docker Compose stack, choose when to update it, and keep its PostgreSQL data recoverable. The PolyForm Noncommercial license permits the covered noncommercial use, modification, and redistribution; commercial use needs separate permission.

The app is for a specific kind of budgeter.

Use FinanceTracking.app when you want a monthly review you can inspect and you are comfortable running the server. Choose another product when automatic bank updates, vendor operations, shared household editing, or native mobile apps matter more.