PROJECT_02 / Full-stack development
A connected workflow for transactions, budgets, and financial review.
STACKNext.js · React · Flask · Python · PostgreSQL · Supabase
The application connects income and expense records with planning and review. Budgets, savings goals, recurring bills, credit accounts, and trip groups share a monthly workflow instead of living in separate trackers.
My contribution
I built the frontend, Flask API, database integration, and reporting workflows, expanding the application from expense entry into a broader monthly finance tool.
The core workflow moves from entering financial activity to reviewing its effect on the month. Dashboards and PDF reports provide different views of the same recorded information.
Next.js provides the user interface, Flask handles backend requests, and PostgreSQL stores structured financial data. The project moved from a local database to Supabase-hosted PostgreSQL; Supabase also supports authentication.
Technical decisions
The frontend can focus on entry and review while Flask handles data processing behind an API boundary.
PostgreSQL supports the relationships between monthly records, categories, budgets, and linked activity.
Transactions belong to monthly records and categories. Budgets provide planning context, while recurring bills and trip groups connect related activity. This is a conceptual view of the workflow, rather than a database schema export.
The Next.js client sends requests to Flask services that process expense records and connect the interface to persistent storage. Keeping that boundary explicit makes the path from a form to a saved record easier to understand and debug.
The dashboard provides an overview; category breakdowns and report views support a closer review. Screenshots show different parts of the financial workflow.
The tool evolved into a usable personal finance platform with budgeting, recurring obligations, savings, credit tracking, trip spending, PDF reports, and audit logging.