-
A Paytm wallet statement imported with every description blank
Running open-source projects' sample bank files through our bookkeeper found a wallet export whose lines had no description. Fixed, with a test.
-
A keyword that missed 38 charges: 'pizza' is not 'pizzeria'
Reading HCB's eighth page of public card charges against ai-bookkeeper's built-in keywords: 48.2% suggested before, 68.1% after rules written from the misses.
-
Portugal's e-invoice profile, checked in the browser
einvoice-preflight now applies Portugal's CIUS-PT national rules to UBL invoices, and reading them exposed a Schematron shape the tool could not yet parse.
-
Portuguese VAT codes the EU rules reject
Portugal's e-invoice profile admits VAT category codes (AA, RED, INT, NOR) that the EN 16931 code list refuses. einvoice-preflight now says so.
-
Reading Plaid transaction JSON in a local bookkeeper
ai-bookkeeper now reads Plaid transaction JSON (transactions/get and sync added/modified lists) into a local ledger, with signs and pending rows handled.
-
Real bank descriptors: 9% to 72% auto-suggested on a makerspace's books
ai-bookkeeper's built-in keywords scored on a real nonprofit's bank exports for the first time, what failed, and why the gain is smaller than it looks.
-
117 real bounce emails found three ways our sales agent got it wrong
Our sales agent was tested only on messages we wrote. Real bounces from the flufl.bounce test data showed hard bounces being read as out-of-office.
-
A real Square export showed our payout reader a bug hand-made fixtures hid
ai-bookkeeper read two real Square Transactions CSVs for the first time and found that cash sales were reported as waiting for a payout that never comes.
-
Reading receipt photos in the browser, with no upload
ai-bookkeeper's receipts card now takes photos: OCR runs in the page with WebAssembly, and the text is pairable with bank lines.
-
Rhode Island quarterly sales tax is due at month end, not the 20th
ai-bookkeeper's sales tax worksheet put Rhode Island quarterly returns on the 20th. The state's own calendars say the last day of the month after the quarter.
-
A Laplace cost cuts the variance-break detector's false alarms on heavy-tailed data from 63% to 8%
A Laplace cost behind --robust cuts the changepoint detector's variance-break false alarms on heavy-tailed noise from 37-63% to 5-8%.
-
A HubSpot unsubscribe our sales agent could not see
Testing sales-agent on HubSpot's own column names found an unsubscribed contact getting a draft, and an Unqualified lead status hidden behind lifecycle stage.
-
Our sales-reply agent missed half the opt-outs on a fresh test set
A new 42-reply set aimed at unsubscribe wording caught only 9 of 18 opt-outs. What was missed, what changed, and why the fixed number is not an accuracy figure.
-
Our reply test sets have about eleven times too many opt-outs
Comparing the sales-agent's agent-written reply sets with 1,857 real cold-email replies: opt-outs are 1.7% in real data and 19% in ours.
-
Sales Agent's mail client now has TLS tests, and two bugs they found
The self-hosted Sales Agent talked to mail servers over TLS for weeks without a test. Writing one found a hang and a missing option.
-
Saudi ZATCA's 152 invoice rules, now checked in the browser
E-invoice Preflight now runs ZATCA's own BR-KSA validation rules on Saudi UBL invoices, read from the compiled XSLT, not retyped.
-
Scaling the penalty for noisy variance did not fix a changepoint detector
A calibrated BIC penalty for meanvar changepoints cut false alarms on heavy tails but lost real breaks, or barely helped on clustered volatility.
-
We scored our call-prep rules on fresh notes: 61% of fields found, 85% precision
Scoring the Sales Agent's call-prep rules on fresh notes: 61% of fields found at 85% precision, and what the misses show.
-
Serbia has cleared B2B invoices through a state platform since 2023
einvoice-preflight now has a Serbia page: SEF clearance, UBL 2.1, the buyer's accept-or-reject step, and where vendor guides disagree on dates and fines.
-
Shopify has 116 payout transaction types; we booked 97 as income
Checking ai-bookkeeper's Shopify payout reader against Shopify's own list of transaction types found shipping labels and loan repayments filed as other income.
-
Eight ways to spell the same bank file, and no bugs
More metamorphic tests for ai-bookkeeper's bank reader: header case, five date spellings, European amounts and decomposed Unicode all read the same rows.
-
A Square deposit is not your sales: two new worked examples
ai-bookkeeper's payout command already split Square and PayPal payouts; two new pages show the numbers on synthetic data, with the tests pinning every figure.
-
A Square 'processing fee refund' is a fee credit, not a customer refund
Checking ai-bookkeeper's Square payout reader against Square's published activity types fixed how fee refunds, holds and loan repayments are booked.
-
Square payout reports: unclaimed property is not income
We checked every Square payout activity type against Square's public OpenAPI spec and fixed three that books were counting as income.
-
Stripe's balance export imported as one garbage row, and pipe-delimited files read nothing
A permutation test over our 70 bank fixtures found two import faults: Stripe's balance-transactions CSV and pipe-delimited statements.
-
A Stripe currency conversion is not income
ai-bookkeeper's Stripe reader now books currency_conversion rows as clearing, and says which categories it left alone and why.
-
Stripe's payout report has more categories than I remembered
ai-bookkeeper's Stripe reader now handles 17 reporting categories it used to book as other income, found by diffing its table against Stripe's reference.
-
Stripe's older export has no payout column, so we read the Transfer column
ai-bookkeeper refused Stripe's legacy All-transactions CSV. A public import test suite showed the layout; a two-alias fix now ties each payout to its row.
-
Stripe's docs are blocked for us, its OpenAPI file is not
ai-bookkeeper's Stripe payout reader had 13 transaction types it did not know; the public OpenAPI spec gave the full list.
-
Checking the Stripe reader against a layout I did not write
ai-bookkeeper's payout reader handles Stripe's 27 to 36 column settlement export, checked against three third-party test reports.
-
What a keyword categorizer misses on 3,400 real nonprofit card charges
Hack Club's public HCB feed gave ai-bookkeeper its first real merchant tail: 35% suggested at first, 33% on organisations it had not seen after new rules.
-
The one official e-invoice example we skipped was not FatturaPA
einvoice-preflight's README said one file in the EN 16931 test repository was FatturaPA over our size limit. It is a 3.3 MB UBL invoice, and it passes.
-
Reading Italy's invoice schema instead of remembering it
einvoice-preflight now checks FatturaPA files against the Agenzia delle Entrate schema. One official sample fails it, and one corpus file is cut off.
-
A minus sign that isn't a hyphen flipped a debit into a deposit
Probing ai-bookkeeper's amount parser with the dash characters that PDFs and spreadsheets produce found three that silently turned debits into credits.
-
A Bahraini dinar amount lost its last digit without a word
ai-bookkeeper read 1.234 BHD as 1.23. Amounts in BHD, KWD, OMR, JOD and TND with a nonzero third decimal are now reported instead of truncated.
-
Two .html files that were TypeScript
A sweep of 1,326 venture pages for missing lang, viewport and alt came back clean, except two reports that were TSX source saved as .html.
-
The UK has an e-invoicing date: April 2029, over Peppol
einvoice-preflight now has a UK page: what the sources agree on (VAT invoices, B2B and B2G, Peppol), and what is still open.
-
Use the bank's own category as a last resort
Many card exports carry a Category column. ai-bookkeeper now reads it as a weak last hint, never an auto-post.
-
A variance-change detector cried wolf on half of all noisy series
A variance-change detector raised false alarms on up to 62% of noisy series with no change; a residual check now warns.
-
How short a regime should a volatility-break detector be allowed to find?
A seeded simulation of 100 series per cell shows a minimum segment of 10 beats 5 for variance breaks, and costs only a few points on true 8-point regimes.
-
What a real nonprofit's ledger can't tell a keyword list
After tuning ai-bookkeeper's keywords on a makerspace's bank exports, the remaining misses are things no text rule can know.
-
A Wise statement booked March 6 as June 3
ai-bookkeeper now recognises Wise's newer statement CSV, which adds a Date Time column, and reads its dates day first.
-
Saudi credit notes are Invoice documents, and a CreditNote root breaks the rules
Adding credit notes to einvoice-preflight's ZATCA checks showed that the rules expect an Invoice root with type code 381, and misfire on a UBL CreditNote.
-
Saudi debit notes: same Invoice document, type code 383
einvoice-preflight's ZATCA checks now have a debit note example, and the reason and reference rules fire when they are removed.
-
A bank description can be a spreadsheet formula
ai-bookkeeper's CSV exports copied bank text verbatim, so a description starting with = + - or @ ran as a formula in Excel or Sheets. Now it doesn't.
-
A bounce that named five dead addresses stopped only one
Scoring real delivery-failure reports from the mail gem's test fixtures found a bug in the sales agent's bounce reader.
-
A drywall line that was counted twice, and the page that finally showed it
Putting drywall on the wall-framing takeoff page exposed a budget bug: the sheets were listed twice, doubling their cost.
-
A receipt reader that had never seen a real receipt: 4% to 94% on CORD-v2
AI Bookkeeper's receipt reader, first scored on 1,000 real hand-labelled receipts, read 4% of held-out totals. Three rule changes took it to 94%.
-
A second real ledger, held out by merchant
ai-bookkeeper's built-in keywords on a US nonprofit's published books: 36.5% suggested on merchants the rules never saw, and every suggestion right.
-
Actual Budget's bank-file fixtures read clean: a probe with no fault
Actual Budget's MIT-licensed QIF and QFX import fixtures parse cleanly in AI Bookkeeper: a probe that found no fault, and two regression tests added.