The current Windows installer is named Zeno for QuickBooks Desktop. That is
the shipping name of the local package, not a separate bookkeeping product or
workflow.
What it does
- Codes and posts transactions in volume — bills, checks, card charges, journal entries, invoices, payments, vendor credits.
- Works a bank feed — the statement file you already download, staged as a queue, deduplicated, coded by your rules, and matched against what the company file already holds. A live bank connection is available as a paid add-on and fills the same queue.
- Remembers coding decisions, so the same vendor descriptor isn’t re-reasoned every month, along with notes about a client that a rule can’t express.
- Answers “why is this entry here” six weeks later, from its own record of what posted and where it came from.
- Reverses a batch by voiding each transaction it created.
- Runs financial reports — P&L, balance sheet, trial balance, agings — through QuickBooks’ own report engine, so the numbers match the client’s screen.
- Answers questions no report covers — totals, comparisons across periods, one query spanning every client on the workstation.
What makes it safe to point at a client file
Nothing posts in one step.qb_plan_batch reads your company file and returns a table. It writes nothing. A second, separate call posts what you approved.
The table is the same every time. The software renders the approval screen; the model doesn’t compose it. It has the same columns and the same ordering on every run and every workstation.
Re-running is safe. Each entry carries a key derived from its content and its source reference. If a batch is interrupted halfway, plan and apply it again — what already landed is skipped, not posted twice.
The person who approves doesn’t have to be the person in the chat. A plan can be reviewed line by line in the console, and exclusions recorded there are honoured when it posts, with the reviewer’s name against them.
Everything is written down. The console shows every run this workstation has posted, who approved it, what it was worth, and what failed.
It can be installed read-only. Every write tool refuses before it reaches QuickBooks. Install this way for a first look at a live file.
What it requires
- QuickBooks Desktop — Pro, Premier, or Enterprise — on the same Windows machine.
- QuickBooks running, with the company file you want open.
- A chat client that speaks MCP — Claude Desktop, Claude Code, ChatGPT Desktop, or Codex. The installer connects all four.
Start here
Install it
Installer, first connection, and the authorization prompt that appears inside QuickBooks.
Connect a chat client
What the installer registered with Claude, ChatGPT, and Codex, and the manual route.
Your first batch
Plan, read the table, approve, and undo it again.
Your first questions
Sync a local copy, ask one client, then ask the whole practice at once.
The bank feed
A month of statement lines as a queue: import, code, match, and post what is left.
What it can't do
The limits of the QuickBooks SDK. Read before you buy.
What it remembers
Coding rules, client knowledge, written procedures, and the work log.
Several company files
Registering a practice’s clients, and what QuickBooks lets you reach at once.
Which connection
How this differs from the Zeno operator and the QuickBooks sync.