Transactions

3 accounts · synced 6 min ago via Akahu

Date range

Custom

Delete this transaction?

() will be removed. This can't be undone. Your spend totals and budget will refresh. You can add it again with + Add transaction. To restore it, re-import the CSV file.

What this is. The high-fidelity click-through for PRD-81 — manual transaction creation, Pro-user variant, re-seated in a near pixel-faithful rebuild of the real Transactions page (header search / filter / date-range chips, the deficit/surplus banner, and the two-column list with real row anatomy). A Pro user records a transaction the bank feed can't see (cash, third-party card, depreciation, spread bills); it then behaves like any other transaction.

Entry point: the "+ Add transaction" primary button — the only filled control in the Transactions header, sitting as the last element of the action cluster (right of search + filter), full-width under the header on mobile.
Page context (rebuilt for fidelity): header title + subtitle, "Search Transaction" input, filter funnel, "Date range" 7/14/30-day chips + Custom range (DD/MM/YYYY) + export; a full-width deficit/surplus banner (real SurplusBanner: signed figure + "Deficit"/"Surplus" + the "Oosh!" copy); then the Income | Expenses columns with date headings like "13 Jul 2026".
Row anatomy: 32px avatar (source indicator), raw bank description on the name line (+ a Transfer badge on transfer rows), and the real 11px meta sub-line "institution account | category | Card/R/P/C". The manual row keeps its user-typed description for contrast.
Form: Expense/Income toggle, large amount, date (today, no future dates), description, required category, and "More options" for bank account (default cash / no account) and entity.
States: default form, per-field validation errors, saving (double-submit guarded), API error, success (toast + new row), rows expanded (source indicator + Delete), delete confirm. Each is deep-linkable via ?screen=.
Source indicator = the avatar (decision, 15 Jul): the row source lives in the avatar, not a text pill. A manual row shows a grey outline pencil; a CSV-imported row shows a grey outline document icon; feed rows keep the letter avatar.
Delete scope: both manual and CSV rows expose Delete only — delete-only, no edit. Manual creation is Pro-only, but CSV delete is in scope for all users, row-by-row (CSV upload is not Pro, so its delete is not Pro-gated). Feed rows stay locked.
Totals reconcile: the banner figure and the two column totals all compute from the same seeded rows. Transfer rows are shown with a Transfer badge but excluded from the totals (matching the real app).

Non-Pro users see the entry point but get a Pro upgrade prompt instead of the form — that variant is a separate file (non-pro.html).

Faked vs real. Transaction data, categories, the search / filter / date-range controls and the 700ms save latency are faked. On build: rows come from the transactions API; the banner + totals come from useTransactionData; Save posts to the new manual-create endpoint (fires the observer + TransactionCreated); provider_id manual_%, nullable bank_account_id migration, cleanup-sweep exclusion, PostHog events and SortMe AI prompt guidance are real. See PROTOTYPE.md.