ClearBudget is a private desktop budget planner focused on solvency rather than expense tracking.

Most budgeting software answers a retrospective question:

Where did the money go?

ClearBudget was built to answer a different one:

Will the month survive?

Not in aggregate. Not once all income has landed. Not after the damage is done.

Day by day. Bill by bill. Card by card.


Why this exists

A monthly total can look safe while the month itself is structurally unsafe.

Income may arrive late. Bills may cluster early. Credit card minimum payments may hide rising balances. A payment may be affordable at month end but impossible on the day it lands.

That is the gap ClearBudget was built to expose.

The application models the operational shape of a month rather than treating money as a flat number.

It tracks:

  • expected income
  • bill timing
  • skipped obligations
  • bank vs credit card payments
  • credit card utilisation
  • minimum payment pressure
  • future balance projection
  • mid-month solvency risk

The result is not a prettier ledger.

It is a local decision system for personal solvency.


Core behaviour

  • Month-by-month budget planning
  • Income tracking with reliability markers
  • Bill tracking with categories and due days
  • Per-bill active and skip controls
  • One-month bill skips without deleting templates
  • Bank and credit card payment methods
  • Credit card balances, limits, APRs and due dates
  • Minimum payment modelling
  • Month-end card balance projection
  • Forward solvency projection
  • Mid-month overdraft detection
  • Archive snapshots for completed months
  • Local SQLite persistence
  • Database import and export

Multi-user login system

ClearBudget now supports isolated user accounts with secure authentication.

Features include:

  • first-run admin setup wizard
  • per-user encrypted login credentials
  • isolated user databases
  • password recovery codes
  • user switching without restarting
  • admin-only user management

The goal was simple:

Multiple people should be able to use the application on the same machine without sharing financial state.


Display currency selection

The application now supports 25 display currencies covering major English-speaking territories.

Currency changes apply immediately across:

  • tables
  • labels
  • solvency panels
  • credit card projections
  • dialogs
  • projections

The setting is stored per-user inside the local database.


Desktop workflow improvements

Several usability improvements were added to make the application feel more like a polished desktop tool rather than a prototype:

  • database import/export moved into the File menu
  • live database reload after import
  • automatic table column sizing
  • destructive action confirmations
  • fresh-start "New Budget" workflow

Solvency

The solvency panel is the heart of the application.

It answers the question the budget view alone cannot:

Does this month actually hold together?

A month can have enough total income while still containing a temporary overdraft. A card can remain under its limit while still moving toward failure. A payment can be affordable overall while landing on the wrong day.

ClearBudget models those conditions directly.

The solvency system tracks:

  • projected balances
  • committed obligations
  • remaining bank payments
  • remaining card payments
  • utilisation pressure
  • minimum payments
  • interest drag
  • six-month forward risk

This turns vague financial anxiety into explicit state.

Once the state is explicit, decisions become smaller.


Credit cards

Credit cards are not treated as static debt numbers.

They are treated as pressure systems.

Each card tracks:

  • current balance
  • credit limit
  • APR
  • due day
  • minimum payment rules
  • projected closing balances
  • utilisation trend

That distinction matters because a credit card balance is not only money owed.

It is:

  • future interest
  • minimum payment drag
  • reduced headroom
  • compressed future cashflow

ClearBudget keeps those pressures visible before they become irreversible.


Local first

ClearBudget is intentionally local software.

The database lives on the machine. The interface runs as a desktop application. The model does not depend on bank integrations or hosted infrastructure.

That decision was deliberate.

Personal finance contains highly sensitive behavioural data even when account numbers are absent.

Income timing, debt pressure, payment sequencing and solvency risk are private operational information.

The problem did not require cloud infrastructure.

It required explicit state and predictable behaviour.


Architecture

ClearBudget is built with:

  • Python 3.11+
  • PySide6
  • SQLite
  • bcrypt password hashing
  • local-first persistence

The complexity is not scale.

The complexity is correctness.

A projection system that produces false confidence is worse than no projection at all.

The application therefore focuses heavily on explicit state transitions, timing correctness and predictable month modelling.


ClearBudget at a glance

Capabilities

  • Month-by-month budget planning
  • Income and bill management
  • Reliable income markers
  • Bill categories and due days
  • Per-month bill skips
  • Bank and credit card payment methods
  • Solvency status calculation
  • Mid-month overdraft detection
  • Credit card utilisation tracking
  • Interest and minimum payment modelling
  • Forward balance projection
  • Archive snapshots
  • Database import/export
  • Multi-user authentication
  • Per-user budget isolation
  • Display currency selection

Technology

  • Python 3.11+
  • PySide6 desktop interface
  • SQLite local database
  • bcrypt password hashing
  • Dark theme UI
  • Local-first architecture
  • Open source repository

What this taught me

ClearBudget reinforced a familiar engineering lesson:

A tool becomes useful when it models the real decision boundary.

A monthly total hides timing risk. A transaction list arrives too late. A category breakdown does not expose pressure. A credit card balance without projection hides trajectory.

The useful model is the one that exposes the failure mode early enough to act.

That is why ClearBudget focuses on solvency rather than accounting.

It is not trying to describe money perfectly.

It is trying to answer the operational question:

What breaks next and when?


ClearBudget is a working example of software built around structural clarity.

The value is not that it stores financial data.

The value is that it turns scattered obligation into an explicit operational model.