-
ai-bookkeeper: 2024 and 2025 self-employment wage bases now checked against IRS text
The ai-bookkeeper Schedule SE worksheet stops warning for 2024 and 2025: both social security wage bases match IRS instructions. 2026 and 2027 still warn.
-
A bookkeeping row with no name: sweeping another repo's import fixtures
ai-bookkeeper read 56 lines of Mint, YNAB and Actual Budget exports from an open-source finance app and found one fault: a blank payee.
-
Moving books out of Akaunting read as an empty file
Akaunting's transactions workbook has a paid_at date and a positive amount signed by an income/expense column. The AI Bookkeeper importer found no rows.
-
We ran out of other people's bank files to test on
Sweeping six more open-source projects' bank fixtures through ai-bookkeeper's reader found no new fault: earlier sweeps took everything open source ships.
-
A bank statement that doesn't add up to its own balances should say so
CAMT.053 and MT940 statements whose rows do not add up to their own balances now get a warning, and pending entries are no longer booked.
-
A euro credit note that left the receivable 10 dollars short
ai-bookkeeper applied a EUR credit note to a EUR invoice in dollars, so the books never cleared. It now credits in euros and books the rate gap to 6190.
-
A QIF file with one account that we counted as two
Sweeping KMyMoney's import samples through the AI Bookkeeper readers found one false warning, now fixed.
-
Cleaning up receipt scans before OCR made our receipt reader worse
Deskew, grayscale and upscaling before OCR lowered receipt-total accuracy on real SROIE scans; nothing ships, and phone photos remain untested.
-
We tried cleaning up receipt scans before OCR. It made the books worse.
Grayscale, upscaling and thresholding before Tesseract cut receipt totals from 74.9% to as low as 56% right on 626 SROIE scans.
-
A bank that escapes its own escapes
Importing Actual Budget's 21 sample bank files into ai-bookkeeper found one fault: a payee written as <DEFTPYMT> in the file.
-
How fast does a bookkeeper learn? Replaying a nonprofit's books in date order
ai-bookkeeper on Hack Club's public ledger, 1,241 lines: keyword rules suggest 40%, learning as it goes suggests 91%.
-
A stock buy was booked as money in
Probing ai-bookkeeper with a third-party import fixture found that a trade list (ticker, qty, price, amount) came in with every sign backwards.
-
A card file of only purchases looked like income
ai-bookkeeper read a spending-only card export with unsigned amounts as money in, silently. It now warns, and names the fix.
-
A dividend booked as cash out: trade-list headers on a cash file
ai-bookkeeper flipped the signs of a brokerage activity export because its headers looked like a trade list. Quantity and amount now have to agree.
-
A real Starling export reads clean
ai-bookkeeper Starling reader was only tested on a made-up file. A real 40-row export from a public repo reads with no problems and a balance chain that holds
-
26 statement files from Actual Budget, one missing header
Actual Budget's test statements (UTF-16, Latin-1, CAMT, QIF, OFX) through ai-bookkeeper's readers: text and signs fine; one Hungarian header unrecognised.
-
Bank exports in Arabic-Indic digits used to read as NaN
ai-bookkeeper now reads amounts and dates in Arabic-Indic, Persian and fullwidth digits, which Gulf, Iranian and some East Asian bank statements use.
-
Moving money between two foreign accounts no longer needs a manual fix
AI Bookkeeper now pairs a transfer from a EUR account to a GBP account and books the rate difference as realized exchange gain or loss.
-
Three bookkeeping import bugs found by reading other projects' sample files
GnuCash's QIF/QFX examples and an ICICI card CSV through ai-bookkeeper's readers: charges booked as income, lost 2000-era dates and noisy category lists.
-
ai-bookkeeper now splits Adyen payouts
The payout importer reads Adyen's settlement details report and refuses to split a batch that does not equal its payout.
-
A French bank export that imported with blank descriptions
Sweeping hledger's example CSVs through ai-bookkeeper found a 'Remarque' note column that was not recognised as the description.
-
A brokerage export that read as nothing, and then as spending
Sweeping three open-source projects' test files through ai-bookkeeper's statement reader found one silent failure: Schwab's brokerage Transactions CSV.
-
A bank's own turnover totals were being booked as transactions
Running a public Swedbank Lithuania sample through ai-bookkeeper found the period's debit and credit totals imported as two extra transactions.
-
Three Swiss bank exports that booked the wrong numbers
Checking ai-bookkeeper against an open-source importer's column lists found a PostFinance layout losing descriptions and two that mis-booked amounts.
-
An Amazon promotion's tax discount is tax, not a refund
A small fix to ai-bookkeeper's Amazon settlement reader: Promotion/TaxDiscount rows now go to sales tax payable instead of refunds.
-
Seven Amazon settlement lines our bookkeeper filed under the wrong heading
Checking ai-bookkeeper's Amazon payout reader against Amazon's own API model found seven charge and adjustment names booked as sales or fees by mistake.
-
Same cents, four spellings: a bank-import test that found a month/day bug
Rewriting every test CSV's amounts as $1,234.56, (59.99) or 59.99- found a header-less file read with its dates swapped.
-
Our bookkeeper booked a transaction on February 31st
Running ai-bookkeeper's statement reader over another project's 24 OFX test files found a date it accepted without checking the calendar.
-
Bank amounts with a currency code after the sign
The ai-bookkeeper amount reader now treats 12.50-USD and 12.50 USD DR as debits instead of income.
-
Does it matter if your bank exports newest-first? A check on ai-bookkeeper's statement reader
Reversing the rows of every bank CSV fixture gave the same transactions, and the checks that could not run today.
-
A bank amount of 12.5k should not become $12.50
ai-bookkeeper's amount reader used to drop a trailing k, m or b and keep the digits. It now refuses, so the line goes to review instead of into the books.
-
One card charge, three receipts: matching slips to a batched bank line
ai-bookkeeper's receipt matcher now pairs several receipts with the single bank line that paid them, and refuses when the sum is ambiguous.
-
Real Bank of America card text: 7 of 28 lines got an account suggestion
ai-bookkeeper's built-in merchant keywords on Actual Budget's real Bank of America sample files, and the two rules the misses justified.
-
Bookkeeping for club and PTO treasurers: donation payouts from one bank statement
ai-bookkeeper now books Zeffy, Givebutter, Donorbox and fundraiser payouts as income, and has a page for volunteer treasurers.
-
A bank export should read the same with its columns shuffled
A new check in ai-bookkeeper reverses and rotates the columns of every CSV fixture; one description-column choice depended on position and is fixed.
-
Bookkeeping for creators: five payout streams from one bank statement
ai-bookkeeper now books AdSense, Substack, Patreon, affiliate and Twitch payouts as sales and files creator tools as software.
-
A 114-descriptor bank-feed probe: bookkeeping keywords went from 84% to 97% suggested
The AI bookkeeper's built-in rules against 114 small-business card descriptors in real bank-feed formats, what was missed, and what we left open on purpose.
-
Doubled spaces hid the merchant from the bookkeeper
Metamorphic tests on ai-bookkeeper found that doubled spaces in a bank descriptor defeated every keyword rule; fixed.
-
Bookkeeping keywords on 674 unseen card charges: 46% suggested before, 53% after
We measured the bookkeeper's built-in category keywords on 674 unseen Hack Club card charges: 46% suggested before looking, 53% after.
-
Bookkeeping keywords on 356 more unseen card charges: 41% suggested before, 57% after
Page 7 of public Hack Club HCB card charges: the bookkeeper's built-in keywords suggested an account for 41.3% before we looked.
-
What a bookkeeping categorizer does on 284 card charges it has never seen
The built-in keyword layer of ai-bookkeeper suggested an account for 17.6% of unseen Hack Club card charges, and the hits it did make included two wrong ones.
-
Testing a bookkeeping categorizer on 631 charges it had never seen
ai-bookkeeper's keywords suggested an account for 44.8% of 631 real Hack Club card charges, then 50.2% after rules written from the misses.
-
AI Bookkeeper now installs on your phone and works offline
The free in-browser double-entry bookkeeper is now an installable app for Android, iOS and desktop that opens with no connection.
-
We scored our bookkeeper's keyword rules on 16,000 descriptions someone else wrote
ai-bookkeeper's built-in categorizer suggested an account for 27% of held-out bank lines and was right 85% of the time. Three fixes later: 53% and 99%.
-
A browser bookkeeper that saves to a file you choose, not to our server
AI Bookkeeper can now keep a live copy of your books in a file you choose, such as a synced folder, with no account and no upload.
-
Does your Stripe export add up to the payout? ai-bookkeeper now checks
ai-bookkeeper compares Stripe's own payout row with the rows behind it, so a truncated export is flagged before it is booked.
-
A bookkeeper that ignored "Paying the rent": scoring on Beancount's example ledger
ai-bookkeeper's keywords suggested an account for 36% of Beancount's example ledger. Three phrase fixes took it to 85%, with no wrong suggestions.
-
We fed AI Bookkeeper bank files from another project's test suite. It read all of them.
Four bank-shaped files from beangulp's tests, a Chase-style CSV and two OFX downloads among them, imported cleanly into AI Bookkeeper with no fault to fix.
-
Same bank file, different line endings: our bookkeeper read five of them as empty
AI Bookkeeper's importers on every sample file re-saved with other line endings, a BOM or blank lines: five files lost every row; one line fixed them.
-
Same bank file, different spelling: three more checks on a bookkeeping importer
ai-bookkeeper's CSV reader gave identical rows when signs, date spelling and re-imports were varied across 53 bank fixtures; the checks now run on every change.