Transactions

Hide Transfers Hide Ignored

Get the most out of Transactions

Tag deductible spend, split shared costs, and keep every account in sync. Watch the video to learn how it works.

PLAY VIDEO

Delete this transaction?

() will be removed. This can't be undone here. 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. Rebuilt 2026-07-16 on the fidelity-system Transactions screen template, so the page around the feature is the real Transactions page (every region of the region manifest is present). 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, but is delete-only (no edit) and never changes an account balance.

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 + entity), full-width under the header on mobile.
Page context (real template): title, search, filter funnel (working popover, grey by default — no filter pre-applied), a Pro-only entity filter (shown in this Pro variant; hidden for free users), 7/14/30-day chips + Custom DateRangePicker (DD/MM/YYYY) + export; the real deficit/surplus banner (signed figure + "Deficit"/"Surplus" + "Oosh!" copy); two-column Income (#CAEDFF) / Expenses (#C7D6FF) list with tinted headers, sticky date groups, a pending block, full row anatomy, loading skeleton and empty state (both reachable via ?screen=). Conditional regions — applied-filter chips, the export-validation banner and the one-time onboarding card — are in the markup but hidden on a default load; they show only on their real trigger.
Row anatomy: 32px avatar (the source indicator), raw bank description on the name line (manual keeps its user-typed description), inline tag chips, note/entity icons, Ignored/Transfer/FX badges, the 11px meta sub-line "institution account | category | Card/R/P/C", and a neutral-grey signed amount (income is NOT green — matches TransactionsChild.tsx).
Form: Expense/Income toggle, large amount kept high in the sheet, date (today, no future dates), description, required category, and "More options" for bank account (default cash / no account) and entity.
States (all first-class, deep-linkable via ?screen=): default, form, form-error (per-field validation), form-saving (double-submit guarded), form-api-error (banner, fields preserved), saved (toast + highlighted new row), manual-row (manual + CSV + feed expanded together), delete-confirm.
Source indicator = the avatar (decision, 15 Jul): manual = grey outline pencil, CSV = grey outline document-currency-dollar, feed = merchant mark or monogram. No text pill.
Delete scope: 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. Feed rows stay locked.
Totals reconcile: the banner figure and the two column totals compute from the same seeded rows (including the manual + CSV rows); transfers and ignored rows are shown but excluded.

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.