GT Finance

A private finance operating system that imports transactions, separates recurring reality from one-offs and keeps ambiguous records in a review queue.

system · active

Designer and builder · Updated Aug 2026

  • Personal finance
  • Data ingestion
  • Classification
  • Decision support

01 · Problem

Bank and card records describe money movement, but they do not explain a typical month, distinguish transfers from spending or surface transactions that need judgement.

02 · System

Importers normalize transactions into one ledger, classification rules separate fixed, discretionary, transfer and irregular activity, and a review surface keeps unresolved records explicit.

03 · Outcome

The dashboard produces monthly cash-flow views, a normalized planning baseline, expected-payment checks and an exception queue from the same transaction store.

Context

Planning from a raw statement overweights unusual months and double-counts transfers such as credit-card payments. The system is designed around financial meaning rather than statement layout.

Architecture

  1. 01CSV and Gmail transaction ingestion
  2. 02Normalized local transaction store
  3. 03Rule-based categorization and recurrence modelling
  4. 04Human review queue for unknown or ambiguous records
  5. 05Server-rendered monthly dashboard and planning baseline

Decisions & trade-offs

Keep uncertainty visible

Uncategorized records remain outside the fixed/discretionary totals and appear in a review queue instead of being forced into a misleading category.

Evidence

  • Separates transfers from income and spend to avoid double counting
  • Amortizes annual costs into a representative monthly baseline
  • Flags missing expected transactions and irregular activity

What this taught me

  • A useful finance dashboard explains what the numbers mean before it visualizes them.
View source

Follow the system

Tool usedNext.jsToolkit