Skip to main content
Zenofirm uses one governed bookkeeping workflow. The connection runs wherever the ledger can be reached safely: in the hosted firm workspace for cloud APIs, or on a Windows workstation for QuickBooks Desktop.

​
The short version

​
Run locally when

Your books live in QuickBooks Desktop and you want an AI doing bookkeeping in them — coding a month of card activity, entering a stack of bills, cleaning up a miscoded quarter. The runtime installs on the workstation, talks to QuickBooks on that machine, and keeps its history locally. It can work independently today and connect to the hosted firm workspace as the Desktop bridge develops. Every batch is proposed, shown to you as a table, and posted after you approve it.

​
Use the hosted firm workspace when

You need one place to see and govern work across clients, or the client’s ledger exposes a cloud API such as QuickBooks Online. The workspace holds the queues, source documents, plans, reviews, firm memory, and work record. Ledger-native accounting remains in QuickBooks.

​
The workflow does not change

Both runtimes use the same sequence:
  1. Read the authoritative ledger and prepare a plan.
  2. Resolve names, accounts, duplicates, and client rules.
  3. Put the proposal in front of the responsible person.
  4. Apply only the approved changes.
  5. Preserve the run record and a path through reversal.

​
Running local services together

QuickBooks serves one caller at a time. If another scheduled service also uses the company file, coordinate its schedule with interactive Zenofirm work. See running alongside the QuickBooks sync.