Statements and bills
Bank documents become the application input, with no line-by-line manual entry.
Application built to transform bank statements and credit-card bills into a structured financial view, automating classification, consolidation, planning and wealth projection.
The flow receives statements and bills as PDFs, interprets transactions, classifies data automatically, persists history in a database and feeds a web application for monitoring, planning and simulation.
Bank documents become the application input, with no line-by-line manual entry.
The application reads, extracts, processes and classifies every transaction 100% automatically.
Transactions, categories, planning and history are structured for analysis and projection.
A single interface brings together daily balances, credit card bills, reserves, projections and simulations.
The routine no longer depends on recording every transaction and instead works from bank-issued documents.
Transactions, dates, categories, reserves and planning had to be updated manually — and rework increased whenever the routine went a few days without updates.
Statements and bills feed the application, classification happens automatically and financial views are recalculated from a persistent database.
The same structure that organizes the past also supports tracking the present and simulating the future without rebuilding the analysis for every new question.
Financial management was spreadsheet-based and required manual entry of every transaction, reconciliation of dates and values, and continuous updates to categories, reserves and planning.
When updates were not frequent, work accumulated: days of transactions had to be reconciled, balances rebuilt and the impact of each expense, income item or bill reviewed manually.
The project was structured in layers: first interpret the documents correctly, then turn each transaction into reliable data, and only then build monitoring and projection views.
The workflow starts from bank-issued PDFs, keeping the input close to the original financial records.
Transactions are categorized without manual intervention for each entry.
SQLite organizes records so the application can query past, present and planning data in the same structure.
With a structured database, the dashboard can automatically recalculate balances, reserves, bills and projections.
Day-by-day projected balance including opening balance, transactions, net result and final projection.
Tracks the final credit card bill amount within the broader financial view.
Separation between immediate reserve, a second D+0 liquidity layer and the emergency fund.
Projections varying time horizon, starting value and contributions to evaluate different wealth scenarios.
It turns bank documents into a structured database that automatically updates cash flow, reserves, credit card bills and projections — without recurring manual entry.
The project combines document reading, classification rules, API, database persistence and a web interface in an architecture designed to be maintainable and extensible.
Statements and bills enter as PDF because that matches the bank’s real-world output, although the architecture can accept other source formats.
SQLite centralizes historical and planning data so the application does not need to rebuild calculations from separate files on every query.
understand the context · structure the problem · build a reliable solution