The full finr feature set, organized by how people actually use the app.

finr is built around a local-first SMS pipeline that captures transactions, rebuilds summaries, powers analytics, and keeps export under direct user control.

Core

finr turns bank SMS into a local-first transaction stream without making the core tracking experience depend on a live backend.

  • SMS-based expense and income tracking
  • Automatic transaction detection from bank SMS alerts
  • Local-first processing on device
  • No runtime network dependency for core tracking
  • Fast transaction sync from inbox
  • Incremental sync for newly received SMS
  • Duplicate-safe transaction ingestion

Transaction Tracking

Each detected record can carry parsed banking context while still remaining fully editable by the user.

  • Tracks both debits and credits
  • Parses transaction amount, date, time, and sender
  • Detects bank, card/account suffix, and transaction channel where possible
  • Supports editing transaction details manually
  • Transaction history view with grouped presentation
  • Daily transaction rollups inside the main feed
  • Monthly summary cards inside the home timeline

Summaries

Summaries are rebuilt from local transaction state, so the feed stays accurate as messages arrive and records change.

  • Daily spend and income summaries
  • Weekly spend-limit alert blocks in the feed
  • Monthly spend and income summary cards
  • Rebuilt summaries when new SMS arrives or transactions change

Categorisation

finr supports a top-level category system with subcategory detail, automatic seeds, and parsed mapping where available.

  • Auto-seeded spending categories and subcategories
  • Category and subcategory tagging for transactions
  • Category mapping from parsed transaction class
  • Top-level category system with subcategory breakdowns
  • Category icons / emoji-based classification

Bank Intelligence

Bank identity, account suffix, and related metadata are inferred from sender patterns and enriched over time.

  • Bank detection from sender/message content
  • Bank/card number inference from known patterns
  • Bank logo association for supported banks
  • Backfill for older transactions missing bank details
  • Dedicated bank cards view

Views and Navigation

The app is organized around a timeline-first home screen with targeted drill-down views for review and analysis.

  • Home timeline view
  • Filtered transactions screen
  • Bank cards screen
  • Analytics screen
  • Hamburger menu navigation
  • Monthly summary card deep-link into analytics

Analytics

Phase 1 analytics is already implemented across weekly, monthly, and yearly views with multiple comparative chart types.

  • Yearly analytics view
  • Monthly analytics view
  • Weekly analytics view
  • Monthly spend vs income
  • Cumulative cash-flow trend
  • Category split
  • Daily running balance
  • Week-by-week debit vs credit
  • Top subcategory spend
  • Day-by-day weekly debit vs credit
  • Weekly spend curve

Alerts and Notifications

Notifications and in-app markers surface summary and budget signals without moving control away from the user.

  • Daily summary notification
  • Weekly spend-limit crossing notification
  • Monthly spend-limit crossing notification
  • In-app weekly alert card
  • Monthly limit-crossed indicator on summary cards
  • Notification permission handling

Limits and Controls

Weekly and monthly thresholds are configurable and immediately reflected back into current-period summary logic.

  • Configurable weekly spend limit
  • Configurable monthly spend limit
  • Limit-crossed state persisted into summaries
  • Current-period re-evaluation when limits change

Search, Filtering, and Review

Users can slice by date range, review records, and clean up transaction details before analysis or export.

  • Date-range filtering
  • Filtered transaction views
  • Export for filtered transaction sets
  • Review and cleanup workflow via editable transaction records

Export

Export supports both full-dataset portability and targeted handoff from a filtered or bank-specific view.

  • CSV export of transactions
  • CSV export for selected month or all months
  • CSV export for filtered results
  • CSV export for bank-card views

Data

The data layer is built to keep tracking stable, local, and available without forcing the product into a backend-first architecture.

  • Local Room database
  • On-device processing pipeline
  • Sender directory / sender metadata support
  • Transaction metrics storage

Developer and Power Features

finr also includes internal utilities that help with inspection, enrichment, and transaction-quality backfills.

  • Database inspection screen
  • Backfill utilities for bank enrichment