← All cases · Money back · in operation · since July 2026
A ledger that matches the bank
A mis-posting of roughly €56,500 prevented; 16,138 ledger rows, 15,976 of them identical to the banking records.
Figure: rund 56.500 € Falschbuchung verhindert · measured 29 September 2026
Request: „Triage the bank transactions.“
- Reconcile transactions from the banking app (MoneyMoney) against my own cost register.
- Present open items as a batch; every decision becomes a rule, so the next quarter asks less.
- Write only through a single sanctioned path with validation — never by hand into the table.
- After every run, prove it: ledger row count equals banking row count.
An Excel household book that always trailed the bank by a few weeks and never quite matched.
Every assignment in the batch, every new rule, every booking above a threshold.
An export dropped 63 of 210 transactions and looked complete — I nearly sent a reminder for an invoice that had already been paid.
Reconciliation as a daily metric (ledger = bank) is the four-eyes principle for systems — the human only reviews the delta.
The Excel household book has given way to a ledger holding 15,936 transactions from 27 accounts since 2009. The AI reconciles bank transactions against the cost register and presents open items as a batch; each of my decisions becomes a rule, so the next quarter asks less. Writes go through a single validated path only — never by hand. That path intercepted a mis-posting of roughly 56,500 euros before it hit the books. Since October, every run ends with: ledger rows equal banking rows, 15,976 to 15,976.
Evidence in my own archive · as of 24 October 2026.