Finance and controls
Exact amounts, traceable entries, and a clear path from recorded work to payment.
Updated
A money system needs more than a precise total on a screen. The amount must follow explicit currency and rounding rules, the transaction must have a history, and the recorded result must be checked against an independent source. A balanced journal can still contain a wrong amount or a duplicate. Reliable financial work makes those different questions visible.
This reading path begins with the representation of money and the guarantees of double-entry bookkeeping. Read the two together: exact arithmetic protects calculation, while balanced postings protect a relationship between entries. Neither replaces source documents, deduplication, approval, or reconciliation. The design should make it possible to explain how a number was formed and what evidence confirms it.
The case studies extend those principles into household records, payroll, contribution margin, quoting, fee collection, and the signed agreements behind payment obligations. Their summaries describe the implemented scope; the visible status distinguishes production systems from completed builds. Use them to follow an amount from its source through calculation and review to its final record. Before automating that path, decide who owns discrepancies, how a correction is recorded, and what evidence closes the obligation.
Decisions to make
How will currency and rounding be represented?
Choose integer minor units or an exact decimal representation appropriate to the calculation. State the currency, precision, and rounding point explicitly, including conversions and intermediate rates. Test boundary amounts and totals across the real input and output paths so a display that looks correct does not conceal a changed value.
What does a balanced entry actually prove?
Require equal debits and credits before the journal commits, and derive balances from the recorded entries. Preserve corrections with a link to their original transaction. Then check separately for wrong amounts, duplicates, omissions, and classification errors: those can all satisfy the balancing rule while leaving the financial record incorrect.
What evidence closes the payment loop?
Keep the signed agreement, source hours, invoice, receipt, or fee record connected to the calculated amount and any adjustment. Distinguish an obligation, an approved payout, and a confirmed payment. Assign unresolved differences to an owner and reconcile against an independent record before presenting the operation as financially complete.
Start reading
- Never Use Floating Point for Money
Avoid binary floating point for money. Integer minor units and exact fixed-point decimals are both valid designs when currency and rounding rules are explicit.
- Why Money Apps Need Double-Entry Bookkeeping
Double-entry bookkeeping stops unbalanced transactions and gives every balance an audit trail. Here is what it guarantees, and why reconciliation still matters.
Systems in practice
- Household Finance OS
A real double-entry ledger for a household, not a budgeting app.
Live in production
- Payroll & Ledger Engine
Hours to payroll to invoices to closed books, on one engine, exact to the cent.
Live in production
- Margin & Payout Tracker
Hours in, cents-based pay and contribution margin out, with evidence on recorded payouts.
Live in production
- Physician Revenue Tracker
Surgical fees logged by camera, tracked to paid.
Build complete
- Cost-Plus Rate Calculator
A quoting calculator that works offline, on any phone.
Live in production
- Contract Engagement Ledger
A live engagement ledger links counterparties to agreement records. Its July 3 published snapshot shows 123 counterparties and 215 executed agreements.
Live in production