FinNote is a production-ready personal finance SaaS web application for individual users in Indonesia. It gives one person a private, precise register for their own money: income, expenses, transfers, accounts and wallets, monthly category budgets, savings goals, recurring bills, and reports — all in Indonesian, denominated in IDR (Rp), formatted with the id-ID locale and DD MMM YYYY dates, and rendered in the user's local timezone.
The product intent is a working financial instrument, not a mockup. Every figure the user sees must be produced by real CRUD operations, real database-backed aggregation, and real validation — never by hardcoded production data. Money is never computed with floating-point arithmetic. Each user's records are isolated from every other user's records at the database layer through Row Level Security, so a user can never reach another user's accounts, transactions, budgets, categories, goals, bills, or settings.
The audience is a single human role: an individual managing their own personal finances across cash, bank accounts, e-wallets, credit cards, and savings. They open FinNote in the morning on a phone and in the evening on a laptop. They want to feel in control of their spending, not entertained by it. The interface therefore recedes so the numbers can be read.
FinNote is delivered as a responsive web application built on Next.js with TypeScript and React, styled with Tailwind CSS and shadcn/ui components, iconography from Lucide, charts from Recharts, and persisted in Supabase PostgreSQL with Supabase Auth and Row Level Security.
The single accepted human actor is the Individual Finance User. They register themselves, verify their identity on return, recover a forgotten password, complete a short post-registration onboarding, and then work inside nine protected destinations: Dashboard, Transaksi, Akun, Anggaran, Target Tabungan, Tagihan, Laporan, Kategori, and Pengaturan. Anonymous entry surfaces — Landing, Sign Up, Login, and Account Recovery — sit outside the protected shell, and Onboarding sits inside the authenticated shell but before normal dashboard use.
All financial state is owned by the user who created it. Balances are derived from transactions rather than typed in by hand. Transfers move value between two of the user's own accounts without ever being counted as income or expense. Budget usage is derived from expense transactions. Savings goal progress is derived from contributions. Recurring bills generate transactions on their schedule without producing duplicates.
The system also performs background work that the user never directly operates: scheduled generation of due recurring transactions, and server-side aggregation of dashboard and report figures. These are supporting processes behind user-facing surfaces, not destinations.
Narrow exclusions. FinNote never stores online banking credentials. It never exposes secrets, service keys, stack traces, or database credentials. It does not show fake financial data in production when the user has no data. It does not build only a static UI.
Delivery ownership. FinNote is a first-party application. The user-facing surfaces — the anonymous entry and identity surfaces, onboarding, and all nine protected destinations — are owned and rendered by FinNote itself. Supabase provides the underlying PostgreSQL database, the authentication service, and Row Level Security enforcement; it is a provider of infrastructure, not a surface the user navigates to for product work. Recharts renders charts inside FinNote pages. No accepted capability is delegated to a third-party destination the user must leave FinNote to reach.
Access ownership. FinNote owns application identity. Because the user must privately own and resume durable financial records — balances, budgets, goals, bills, and settings that must remain bound to the correct person — identity is indispensable and is established by the application itself. First use is self-service registration; returning use is verified login; a forgotten password is recovered through a dedicated recovery surface. The anonymous entry surfaces (Landing, Sign Up, Login, Account Recovery) are reachable without a session. Onboarding and all nine product destinations require a session. A protected destination never owns the interaction that establishes access to itself.
Current versus future boundary. Everything described in this document is current. There is no accepted future horizon in the authoritative requirements: no deferred phase, no planned module, and no capability reserved for later. The only forward-looking statements in the source are prohibitions and quality gates, which are binding now.
Explicit exclusions that remain binding. No online banking credentials are ever stored. No secrets, service keys, stack traces, or database credentials are ever exposed. No fake financial data appears in production when the user has no data. No floating-point arithmetic is used for money. No normal-page horizontal scrolling. No excessive gradients, excessive animation, oversized cards, or decorative elements with no function. No blue or indigo anywhere in the interface.
Not applicable. No reference directive in this project declares a content_source, so no external factual inventory is carried into this document.
The page inventory is the closed, ordered contract: Landing, Sign Up, Login, Onboarding, Account Recovery, Dashboard, Transaksi, Akun, Anggaran, Target Tabungan, Tagihan, Laporan, Kategori, Pengaturan. Each appears exactly once below.
id-ID defaults. No financial data of any kind is shown, because no user is signed in.DD MMM YYYY, and tabular amounts. Generation is guarded so a duplicate recurring transaction is never produced for the same occurrence. Confirmation dialogs guard deletion.id-ID, DD MMM YYYY, and the user's local timezone.FR-1 — Self-service registration. As an Individual Finance User I should be able to register a FinNote account myself so that I can begin managing my own finances. Provenance: required_inference. Lifecycle: the user initiates from Sign Up; the system creates the identity and establishes a session; the observable result is an authenticated user entering Onboarding. Access state: anonymous entry. Failure/recovery: duplicate email, weak password, or malformed email produce clear inline errors; network or database failure produces a toast with retry and preserves entered values. Continuation: the user proceeds into Onboarding.
FR-2 — Returning login verification. As an Individual Finance User I should be able to log in with my credentials so that I can reach my own financial records. Provenance: required_inference. Lifecycle: the user initiates from Login; the system verifies the credentials and establishes a persistent session; the observable result is arrival at Dashboard, or at Onboarding if onboarding is incomplete. Access state: anonymous entry. Failure/recovery: invalid credentials produce a clear, non-revealing message; network or database failure produces a toast with retry. Continuation: the user reaches their protected destinations.
FR-3 — Logout. As an Individual Finance User I should be able to log out so that my financial data is not left accessible on a shared device. Provenance: explicit. Lifecycle: the user initiates from the authenticated shell; the session ends; the observable result is return to an anonymous surface. Access state: authenticated.

FinNote — Register Kapabilitas
FinNote adalah pencatat keuangan pribadi untuk pengguna perorangan di Indonesia — dari mahasiswa hingga pekerja tetap. Satu register untuk mencatat, menganggarkan, dan meninjau uang Anda dalam Rupiah.
Setelan bawaan
Akun FinNote bersifat pribadi. Setiap pengguna hanya dapat melihat dan mengelola akun, transaksi, anggaran, target tabungan, dan tagihannya sendiri.

FinNote — Register Kapabilitas
FinNote adalah pencatat keuangan pribadi untuk pengguna perorangan di Indonesia — dari mahasiswa hingga pekerja tetap. Satu register untuk mencatat, menganggarkan, dan meninjau uang Anda dalam Rupiah.
Setelan bawaan
Akun FinNote bersifat pribadi. Setiap pengguna hanya dapat melihat dan mengelola akun, transaksi, anggaran, target tabungan, dan tagihannya sendiri.
No comments yet. Be the first!