Real capture of the public interface · October 30, 2026
The problem
When income, card bills, Pix payments and receipts live in different places, understanding what is actually left takes manual work. Mixing forecasts with settled transactions makes that picture even less reliable.
What I built
I am developing an open-source product that brings transactions, recurring entries and documents together. PDF, image and CSV imports are reviewed before saving, with suggested categories and possible duplicate warnings.
Impact across front and back
Front-end
Actual-versus-forecast views, filters and a reviewable import queue. The interface presents suggestions and possible duplicates before saving a transaction.
React
TypeScript
Revisão de importação
Back-end
Integer-cent amounts in PostgreSQL, per-user policies and private documents. Authentication, recurring-entry rules and privileged server operations form the product foundation.
PostgreSQL
Supabase Auth
RLS
Storage privado
Decisions behind the solution
Precision before charts
Integer cents and transfers separated from income and expenses keep totals consistent.
A forecast is not a balance
Future recurring entries stay planned until confirmed. Actual-versus-forecast views preserve the context of each amount.
Automation with review
Local PDF processing and open-source OCR for scanned documents. The person reviews the extracted data before creating transactions.
Privacy as a product decision
Authentication, per-user policies and private document storage. Static tests complement operational checks across accounts.
Cases for duplicates, recurring entries, parsers, security and UI.
Results in context
An evolving project. The repository records remaining work in flows such as instalments; the screenshot shows public sign-in, without exposing account financial data.
