ChiSabes
An organized view of accounts, transactions and financial commitments, with traceable changes.
Functional MVPPrivate application. The link opens the owner sign-in screen.
The problem
Recording transactions is not enough to understand finances. Transfers, debts and corrections need consistent rules to preserve balances and history.
Every screen tells a story.
Explore the project, screenshot by screenshot. From the big picture to the details that make a difference.
Overview
What it enables
Transactions and accounts
Income, expenses, transfers and balances derived from balanced entries.
Planning
Monthly budgets, goals and obligation tracking.
Traceability
Corrections through reversals and entity archiving to preserve history.
Decisions behind the solution.
- Next.js · PWA
- REST · Spring Boot
- PostgreSQL · Flyway
PostgreSQL as the operational source
The API applies financial rules through transactions; the interface consumes REST contracts.
Revocable sessions
In-memory access tokens and rotating refresh tokens in HttpOnly cookies.
PWA without offline financial storage
The installable experience does not save financial information in browser storage.
What I solved with this project.
- Bring accounts, transactions and commitments together under consistent financial rules.
- Preserve traceability when correcting transactions and pausing or resuming recurrences.
- Connect a PWA to authentication, a transactional API and PostgreSQL persistence.
How I support the work.
The repository includes backend, frontend and PostgreSQL integration tests and Playwright journeys. Recurrences can be paused and resumed without losing their next occurrence. Documentation records deployment using Vercel, Render and Neon.
Architecture
Components, data and integration.
Material to be addedTechnical decisions
Alternatives and implementation criteria.
Material to be addedTests and results
Journey validation and evidence.
Material to be added