Do you need a budget too? Do you need to manage your finances but don't want to sell your soul share your personal data in order to chart your spending? Does the thought of exhaustively sharing your entire spending history in exchange for basic budgeting tools make you sigh? Unfortunately, this project probably still isn't right for you, as it's still very rough around the edges. Consider looking at other alternatives like:
The current goal is to create a simple tool that allows you to import, review, and categorize transactions for one or more credit or checking accounts, creating one or more budgets or forecasts to better manage your financial resources.
This repository encapsulates the work involved in orechestrating the behind-the-scenes work of making that all happen.
Starting database (first time)
docker run --name budget-database -e POSTGRES_PASSWORD=ineedabudget -p 127.0.0.1:5432:5432/tcp -d postgres
Connecting to database using psql
(Consider setting an environment variable for SQLALCHEMY_CONNECTION_STRING if you want to chagne it from the default)
psql -U postgres -h localhost
create database budget;
Creating new database migrations and upgrading your local database
cd database
alembic revision --autogenerate
alembic upgrade head
TODO:
- [DONE] basic database setup
- [DONE] basic csv parsing
- [DONE] FastAPI router for basic operations
- [DONE] OpenAPI json generator
- [DONE] React App for frontend
- [DONE] Transaction categories
- [DONE] Transaction rules
- [DONE] Apply rules manually
- [DONE] Transaction pagination in FE
- [DONE] Migrate rules to be account-specific (should categories be specific too? unsure)
- [Punt] (it's just one extra call) Apply rules when importing transactions
- Add hierarchy/ordering for categories when chosing transaction category Should add support for tracking balances in checking accounts
- Mark transactions that have been validated manually and exclude them from recategorization when changing rules
- Reporting by category and date (month, quarter, yty, etc)
- Define budgets (an account is tied to one budget, allows users to define amount per category for target spending/saving) (is it important to track historic budgets? I don't think so??)
- Forecasting (based on average run rates, comparing with budgets, allowing us to see differences based on changes to budgets)
- View optimized for categorizing uncategorized transactions
- ...
- Basic audit log?
- User accounts & authentication? Can we enforce only in-home access with simple password and router forwarding?
- Consider reimplementing in Electron w sqlite database to minimize footprint/make portable?