-
AI Bookkeeper's page now shows this period against the last
The browser page of AI Bookkeeper compares profit and loss for your From and To dates with the period just before, account by account, largest move first.
-
Receipt dates: why product codes made a Malaysian receipt read as 2031
ai-bookkeeper's receipt reader now trusts a date plus clock time over code-like numbers to pick day-first or month-first. SROIE date accuracy: 96.7% to 97.1%.
-
Reading shop names off OCR'd receipts: 33% to 37%
ai-bookkeeper's receipt reader now skips OCR noise, GST and state lines when picking the merchant, measured on 626 real receipt scans.
-
Receipt shop names from real OCR: 37% to 43% after one small fix
Tesseract on 626 real shop receipts: the AI bookkeeper's merchant reader gains 6.7 points from a bracket fix, plus a failed attempt to gain more.
-
Where the receipt reader stops: 16 wrong totals out of 625
On 626 real Malaysian receipts the ai-bookkeeper reader gets 97.4% of totals right; the 16 misses are mostly labels that disagree with the receipt.
-
A tax code stuck to a price made a receipt read as 50,063.00
Scoring ai-bookkeeper on 626 real SROIE receipts found an OCR repair that turned 7.50ZR into 7.5025. The fix moved date accuracy from 96.7% to 98.0%.
-
We ran 626 real receipt photos through tesseract. The totals dropped from 96% to 75%.
Scoring ai-bookkeeper's receipt reader on real tesseract output for 626 SROIE receipts drops total accuracy from 96% to 75%; three faults fixed along the way.
-
A bank file in the wrong order no longer looks like a missing transaction
When a bank file's rows are neither in order nor reversed, ai-bookkeeper now searches for the one order whose running balances chain, not a missing row.
-
Reading a bank statement PDF by its opening and closing balance
An Odoo demo statement PDF broke ai-bookkeeper's text reader three ways; the opening and closing balances now settle which rows are money in and which are out.
-
Old Money and Quicken files imported as the year 2095
Two-digit years in old Money and Quicken files were read as 20yy, putting 1995 lines in 2095.
-
A loyalty-voucher line no longer passes for the receipt total
ai-bookkeeper's receipt reader took 'TOTAL SV' voucher counts for the total on some Malaysian receipts; fixing it lifted SROIE accuracy from 96.6% to 97.0%.
-
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.
-
Changepoint detector: a bootstrap penalty for clumpy counts
Counts that come in busy and quiet runs fool a Poisson changepoint test; a block-bootstrap penalty cut false alarms from 89% to 11% on synthetic series.
-
Checking the changepoint detector on 112 years of coal-mining disasters
The textbook Poisson changepoint series, run through changepoint-detector: it finds the fall near 1892 and its 95% range holds the published 1890.
-
Making a volatility-break detector less jumpy on messy noise
changepoint-detector's
meanvarmodel looks for changes in a series' level or volatility. It assumes independent Gaussian noise, and on heavy-tailed or... -
A bootstrap penalty for the mean model cuts false alarms on autocorrelated noise
changepoint-detector --bootstrap now covers the mean model: on AR(1) noise at 0.3, false alarms fall from 80% to 13%; a 2 sd step is still found 98% of runs.
-
Changepoint detector on real currency shocks: which volatility option helps?
Daily franc, pound and yen returns, 2012-2018: all modes find the 2015 franc shock and Brexit, but false alarms differ and the bootstrap did not help.
-
Finding the UK seat-belt law in 192 months of road casualties
The changepoint detector dates a documented 1983 drop in British driver casualties to the right month, and shows why count data needs the overdispersion option.
-
Why the bootstrap penalty missed the Swiss franc shock
On real franc returns the changepoint-detector bootstrap barely raised its penalty. The pilot fit standardised the 2015 shock away, kurtosis 111 down to 4.3.
-
A 95% range for a bend in clumpy counts, checked on seeds we never tuned on
On two seeds never used for tuning, the tempered 95% range for a growth-rate bend covered 101 of 107 bends (94.4%); steep bends run optimistic.
-
A second round of the dispersion penalty doesn't fix GARCH false alarms
Re-measuring the dispersion factor for a second round cuts GARCH false alarms from 30% to 27%: a negative result.
-
Where drywall sheets end: 18 joints off the studs in a sample house
Hung naively, a sample house's 8 ft drywall sheets end between studs 18 times. Snapping each cut to a stud costs 4 sheets and fixes all 18.
-
E-invoice Preflight adds Finland: no B2B mandate yet
Two new country pages say what is reported for Finland: B2B e-invoicing voluntary, government on structured invoices, EU rules from 2030.
-
Austria's e-invoice rules in one page: government only, business voluntary
A new E-invoice Preflight page separates Austria's law (federal suppliers, EN 16931, ebInterface or Peppol) from B2B mandate forecasts no law has adopted.
-
E-invoice Preflight adds Brazil: NF-e, and a CNPJ check that now has to handle letters
A Brazil page explains the state-authorised NF-e and tests CNPJ and CPF check digits in the browser, letters included, with the check's measured blind spot.
-
E-invoice Preflight adds Cyprus: public buyers receive, businesses are not yet required
Cyprus makes public bodies accept e-invoices, not suppliers send them; no domestic B2B mandate is reported before the EU's 2030 step.
-
E-invoice Preflight adds Japan: a T-number check and the October 2026 credit step-down
A new Japan page checks a qualified-invoice registration number in the browser and shows the 80% to 50% transitional credit step on 1 October 2026.
-
Luxembourg's e-invoice mandate now has a bill number
Luxembourg's e-invoice plan is now draft law No. 8815, with receiving deadlines into 2028 and size thresholds.
-
E-invoice Preflight adds Sweden: public sector first, B2B optional
A new Sweden page says what is reported: public suppliers on e-invoices since 2019, Peppol BIS 3.0 preferred, B2B optional until EU rules in 2030.
-
E-invoice Preflight adds Switzerland: federal suppliers only
Switzerland requires e-invoices from suppliers to the federal administration, not between businesses; the page says which claims sources disagree on.
-
E-invoice Preflight adds Turkey, and says what it cannot check
Turkey's e-Fatura and e-Arşiv rules summarised from vendor guides, with a plain statement that a free EN 16931 checker has no UBL-TR rules.
-
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.
-
Malta has no B2B e-invoicing mandate yet, and what that means for a checker
einvoice-preflight now has a Malta page: B2B is voluntary, public bodies take Peppol invoices, EU rules arrive in 2030.
-
The Nile's 1898 dam break, found four ways
Four changepoint settings on the real Nile flow series all date the dam break to 1899; only the autocorrelation setting is honest that the date is less certain.
-
Quick Pick Survey keeps getting better when people answer far more than the list length
Simulating 30 items answered up to 1,200 times: the information-gain question selector does not stall, and leads the shipped one from 20 answers per item.
-
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.
-
The roster builder now finds the last uncovered hour
A solver check showed the shift roster builder leaving 1 to 2 hours open on half of 12 test weeks. A coverage-only search pass now closes all of them.
-
Proving the fewest open shifts: branching on the price closes 5 of 7 gaps
The shift roster builder now proves its roster leaves the fewest possible hours open on 10 of 12 seeded weeks, up from 5, against an independent solver.
-
A Russian quote header made our reply reader think the prospect wrote the whole history
Testing sales-agent's quote stripper on 12 real mail-client emails from mailgun/talon found one miss: non-English 'wrote:' lines. Fixed, with tests.
-
Our sales-reply triage ignored every non-English auto-reply and opt-out
The sales agent's reply triage now recognises German, French, Spanish, Italian, Portuguese and Dutch auto-replies and opt-outs.
-
Our scheduling guides quoted numbers the engine no longer produced
Every guide page on shift-roster-builder quotes figures from its own engine, and a test re-derives them from the sample cafe. Two of those tests had been...
-
Checking a shift scheduler against an independent solver found a search gap, not a proof gap
Eight seeded 10-person, 28-shift weeks, checked against HiGHS: two weeks left more shifts open than needed, and more search steps fixed one.
-
Closing the last open hour in a staff roster by solving a small piece exactly
The shift roster builder's search now repairs open hours by freeing three people's shifts and solving them exactly, matching the integer-programming optimum.
-
An off-the-shelf solver says our shift scheduler leaves hours on the table
An open-source ILP solver proved optimal rosters on 12 seeded weeks in under a second; our shift scheduler missed the best by 1-2 hours on five.