Coming soon: Zeno for QuickBooks
Desktop first, Online second. The Zeno bookkeeper runs inside a QuickBooks company file: an approval table you sign, coding rules kept from your corrections, a run journal, and batches you can undo by run id.
Almost everything we build assumes you’re moving your books onto Zeno. A lot of the firms we talk to are not going to do that, at least not this year, and the reason is always the same: the client is on QuickBooks, the file works, the accountant knows it, and nobody is migrating twelve years of history to save some clicks.
Fine. We’re releasing the bookkeeper into QuickBooks instead.
Zeno for QuickBooks ships shortly, Desktop first, Online second. It’s a standalone product. Desktop needs a company file and nothing else: no Zeno account, no cloud, no network. It runs on the machine the file is on.
Where it came from
Two things we already had, put together.
The first is four years of moving data in and out of QuickBooks. We’ve written the importers that reconstruct a client’s bills from line items and linked transactions, the extractors that read a Desktop company file into something queryable, the converters that move a file between accounting systems, and the sync that pushes Zeno’s own invoices and payments back into QuickBooks on a schedule. None of that was the product, and all of it taught us where qbXML lies to you, which queries drop rows without saying so if you don’t page them, and which transaction types can’t be voided once posted. That knowledge is the difference between a tool that writes to a client’s file and a tool you’d let write to a client’s file.
The second is the design of the Zeno bookkeeper: the approval table, the coding rules built from your corrections, the work log that records what was done and why, and the “explain this entry” that answers the question six weeks later. All of it was built and hardened here, against books we close ourselves. It transplants.
Plan, review, apply
The workflow is three steps, and the middle one is not automatable.
- Plan. Hand it a bank feed, a statement, or a folder of bills. It reads the company file, resolves every account, name, class, and item against what’s in that file, applies your saved coding rules, flags anything already posted, derives an idempotency key per entry, and returns a rendered approval table. It writes nothing.
- A human reads the table. This is the product. An AI can code four hundred transactions faster than you can read this paragraph. What it cannot do is sign off on them.
- Apply. The approved plan posts, every outcome is recorded with the document it came from, and you get back a run id that undoes it.
A batch of six comes back as two ready, two that need a look, one blocked, and one already posted last month. The exceptions are the interesting part of a plan, and hiding them behind a confidence score helps nobody.
It remembers
Decide once that this vendor’s charges go to that account under that class, and the decision sticks. It isn’t re-reasoned every month. Memory is organized in tiers with an enforced boundary, so a rule that applies to one client cannot leak into another’s file. On a practice licence, the run journal, the rule set, and the notes are shared, putting every workstation’s runs in one view.
Questions QuickBooks can’t be asked
QuickBooks answers one file at a time, through the reports it ships with. Zeno keeps a local mirror of each file, so you can ask one question across every client file without opening any of them, and get the file-level detail behind the answer. Reports come from the file’s own books rather than a reconstruction of them.
What it won’t do
QuickBooks Desktop has no network API, so this runs beside the company file on the same Windows machine. For a client’s machine, use remote desktop. It cannot void a posted transfer, because qbXML won’t. It reverses one by zeroing it, and tells you that’s what it did. Some transaction types aren’t covered yet. All of it is documented in one place, because the failure mode we care about most is a tool that does something other than what you thought it did.
This is also a different thing from the QuickBooks sync some of you already run. That sync is plumbing: it pushes Zeno’s invoices and payments into QuickBooks on a schedule. This does bookkeeping inside the company file. A firm can run both, as long as they’re scheduled around each other, since QuickBooks serves one caller at a time.
Trying it, and buying it
The evaluation is the full product with one limit: batches cap at ten entries per run. That’s enough to close out a day’s receipts and see the whole loop. No account, no card, and nothing leaves your machine. The installer is signed, per-user, and needs no admin rights. It finds the company files already on the machine, so setup is confirming a list rather than typing paths, and there’s a read-only mode if you’d rather look before anything can write. Claude does the reading and coding, so a paid Claude plan is separate from what you pay us.
Licences are a one-time purchase per workstation. Nothing phones home and we host none of it, so there’s no recurring cost to pass on. Introductory pricing for the first 50: $495 for a single workstation, $415 each at three or more, $325 each at ten or more. Twelve months of updates and support are included. After that, updates are optional at 25% a year, and declining them stops nothing; you stay on the version you have. Whatever state a licence is in, reads, single postings, and reversals keep working. It will not lock you out of your own books.
QuickBooks Online follows, on the same three-step loop.
Download it, point it at a company file, and hand it one day’s work. If the table it shows you isn’t one you’d sign, don’t buy it. Tell us either way: [email protected].