No licence ever blocks reads, reports, review or reversal. You can always read your own books, run a statement, look at a plan someone prepared, and reverse what this software posted. That holds when a key names another workstation, when a build is outside its update window, and when there is no key at all.The safety apparatus is never the upsell. Preflight, the approval table, the run journal, duplicate detection and recovery are identical in all three. Nobody’s cheaper plan is a more dangerous plan.
Which one you are
Practice exists so that a bookkeeping firm never pays for inventory it will not touch: it is the firm’s licence, and it stops short of the inventory domain. Enterprise is that same licence plus the inventory domain — read the Enterprise column and it is the Practice column with the last two rows added. A firm that is genuinely both buys one licence, not two.
The three differences, in detail
Cross-company questions
One question against every registered company at once —qb_query with allCompanies. It is what answers which clients have an unreconciled month, and what does this look like across all six entities.
This is what separates paid from Core, and deliberately not what separates Practice from Enterprise: a practice’s sweep across clients and a company’s consolidation across entities are the same feature, and the software cannot tell a client from an entity.
On Core, every registered company is still fully queryable on its own — run the same SQL once per company with the company argument. What Core leaves out is the aggregation across files, not access to the data.
Shared practice state
One journal, one memory and one review loop across several workstations — the arrangement in one journal for a whole team. Ann’s coding rules, the client knowledge everyone contributes to, and duplicate detection that spans the office rather than one desk. Included with Practice and with Enterprise. An Enterprise buyer’s two workstations are often just a bookkeeper and a controller looking at the same few entities, and they may never need it — but it costs nothing extra, so it is not a decision anybody has to make. If your data directory is on a share, writing to it needs this. Reading it never does: on any licence you can still open the console, read every run, plan and rule on that share, and reverse a run. A workstation meant to work on its own can also point-DataDirectory back at its own PC.
The inventory domain
Inventory adjustments, assembly builds, item receipts, and linking a purchase order onto a bill or a receipt. Included with Enterprise, because Intuit already taught this market the split: if your QuickBooks is Enterprise-shaped, so is your Zeno. On the other tiers, everything else about an inventory file still works —qb_report and qb_query still answer valuation, quantity-on-hand and open-purchase-order questions, purchase orders can still be written, and corrections to inventory transactions already in the file still work. What is not included is posting new inventory movement.
Enterprise-shaped lists, as they arrive
Units of measure, inventory sites, price levels, multicurrency and billing rate levels are features only QuickBooks’ higher editions have, and Zeno’s support for them lands in Enterprise as it is built. Setting one up is included with Enterprise; reading it is included everywhere, at every tier and with no licence at all — looking at a file’s price levels or units of measure is not a licensing event. Anything released inside your update window is covered permanently, like every other build your key covers.What a refusal looks like
A gate fires before anything is sent, and says so:Inventory postings — adjustments, assembly builds, item receipts and purchase-order linking — are included with Enterprise. This Core licence has not posted or changed anything; ‘build assembly’ was refused before anything was sent.Nothing reached QuickBooks, nothing is half-done, and the rest of the batch is unaffected.
qb_status shows what your licence covers at any time, under license.tier.
Firms with Desktop clients
A bookkeeping firm on Zeno for Firms does not buy these licences. A QuickBooks Desktop company file registered through the firm’s connector is a client book, counted and priced exactly like a QuickBooks Online company, and the connector is included on every workstation the firm enrols. Every registered file gets the whole Desktop surface, inventory included, and the 250-posting evaluation allowance does not apply to it. Enrolling takes one code from the console’s Clients page andqb_connect_firm on the workstation. If the firm’s subscription lapses, writes to registered files refuse with the firm’s own message; reads, reports, review and reversal continue, as they do under every licence here.
The licences below are for a single PC with no Zeno account.
Prices
One-time, per licence. Every key is perpetual, and each includes 12 months of updates.
When the public price moves, it changes new purchases and renewals — it does not re-price a key you already hold, and it cannot weaken one. Keys bought at the earlier beta prices are perpetual at what they paid. See a licence covers builds, not time.