Documentation

Budgets Documentation

Budget setup, effective limits, category spend, monthly overrides, usage states, alerts, and reconciliation.

Audience: Households planning spending and reviewers investigating budget status. · 6-page PDF · v6.26.1

Logo header · watermark · generation date · multi-page

How to read this document

Sections move from purpose → concepts → calculation process → worked examples → edge cases. Formula boxes use plain mathematical notation for clarity; they are conceptual summaries, not API contracts.

  • Point lists call out operator-visible behaviour.
  • Callouts mark warnings, limitations, or important qualifications.
  • Worked examples use round numbers so you can reproduce the arithmetic by hand.

Purpose

Budgets compare eligible expense activity with household-defined limits. They are planning controls, not bank-enforced spending caps.

  • Define limits for useful scopes such as categories
  • Apply period-specific limits where supported
  • Surface usage and warnings from ledger activity

Budget model

A budget has a scope, base limit, period context, and status. Its spend comes from matching expense records; the budget itself does not create or alter expenses.

  • Use non-overlapping scopes when possible.
  • Name budgets clearly.
  • Choose limits in the household reporting context.
  • Review active and archived states.

Base limits and monthly overrides

A month-specific override replaces the base limit for that month where the feature is enabled. It does not permanently rewrite the base.

Effective limit

MonthOverride ?? BaseLimit

Seasonal override

  1. Base Dining limit is 1,000.
  2. December override is 1,400.
  3. December usage is calculated against 1,400.
  4. January returns to 1,000 unless separately overridden.

The override affects its intended month only.

Eligible spend

Budget spend

Σ reporting amounts of matching included expenses in period

  • Transaction date determines period.
  • Category or configured scope determines matching.
  • Deleted or excluded entries do not contribute.
  • Cross-currency entries use comparable reporting values.
  • Recategorisation can move spend between budgets.

Usage calculation

Usage percentage

(Spent / EffectiveLimit) × 100

A zero or invalid limit requires guarded display rather than division.

Usage can exceed 100%; this describes overspend and does not block a transaction. Remaining amount can be negative.

Remaining

EffectiveLimit − Spent

Status and thresholds

Labels such as on track, near limit, or exceeded summarize usage. Public documentation does not promise secret threshold values as stable contracts.

No proprietary constants

The inputs and qualitative meaning are documented; internal alert timing, deduplication, and presentation thresholds may evolve.

Warnings and delivery

  • Warnings reflect current eligible spend.
  • A ledger correction can clear or retrigger a state.
  • Delivery settings and device permissions affect channels.
  • The budget page remains authoritative even if an alert is missed.

Not a payment control

AccountHouse cannot decline card transactions or reserve money when a budget is reached.

Currency and rounding

Budget comparison requires a common reporting currency. Original transaction values remain available for reconciliation, while the budget uses converted values at currency precision.

  • Bank settlement rates may differ.
  • Rate changes can alter comparable analytics.
  • Small rounding differences should be traced at record level.

Edits and historical interpretation

Changing a limit, override, category, expense, reporting currency, or date can change a displayed prior-period result. Treat the screen as a calculation from current valid data unless an explicit snapshot is identified.

  • Record household policy externally if immutable approvals are required.
  • Export relevant periods before major taxonomy changes.
  • Document unusual overrides.

Monthly review workflow

Close a budget month

  1. Confirm all expenses are entered.
  2. Review uncategorised and duplicate rows.
  3. Validate cross-currency conversion.
  4. Compare spend with the effective limit.
  5. Explain material variance.
  6. Set next month's override only when needed.

The reviewed result remains traceable to expense rows and the effective limit.

Edge cases

  • Refunds can reduce spend only under supported ledger treatment.
  • Late entries can move a completed-looking month.
  • One expense may appear in more than one analytical view; do not add overlapping budgets as if mutually exclusive.
  • Archived budgets may retain historical context.
  • Permission filtering can hide source details from some viewers.

Troubleshooting

  • Confirm selected month and household.
  • Inspect the effective limit and override.
  • Open matching expenses.
  • Clear filters.
  • Check category changes and conversion.
  • Refresh after cross-device edits.

Privacy, advice limits, and what we do not publish

AccountHouse is a household tracking and organisation tool. It is not a bank, payment processor, tax advisor, or investment advisor. Forecasts, health scores, balances, and alerts are informational.

  • Household data is scoped to your household; other families cannot see your ledger.
  • Public documentation explains product behaviour and calculation concepts, not proprietary internals.
  • Exact scoring weights, anomaly thresholds, cryptography parameters beyond high-level algorithms, and operational detection rules are reserved.
  • Budgets are informational plans and are not financial advice or guarantees of affordability.

Intellectual property boundary

This document describes what AccountHouse calculates and which inputs matter. It does not disclose source algorithms, secret constants, or implementation details sufficient to reconstruct proprietary systems.