01Documents ride with postings
Upload and list QuickBooks attachments so the source receipt or PDF is present on the transaction a reviewer sees.
02Plans pin exact work
The plan records included lines, exclusions, warnings, totals, and a digest before a human is asked to decide.
03Duplicate checks look backward
Preflight checks the existing ledger before proposing another write with the same identity.
04Firm memory looks forward
Confirmed coding rules, client knowledge, playbooks, and prior decisions return in the next relevant task.
05Runs keep QuickBooks identities
Every result records its status and ledger id, so success, failure, exclusion, and reversal remain traceable.
06Reads stay useful
Ask live questions, run QuickBooks-native reports, inspect settings, and investigate without turning every inquiry into a gated workflow.
07Getting data in needs no templates
Import any spreadsheet or bank export without mapping it by hand. Your assistant reads a sample and identifies the columns; Zeno applies that structure to every row and posts one reviewable batch. The same approved plan can create missing vendors, customers, and accounts. Reading the shape costs the same for fifty rows as for fifty thousand. Self-describing formats such as IIF and OFX are parsed directly, so their published grammar cannot drift halfway down the file.
08Taking data out is reviewable too
Void, delete, or correct duplicated bills, bad imports, and wrong-month batches through one approval table and one reversible run. Each document is pinned to the revision you reviewed. If somebody edits a row later, Zeno refuses it instead of sweeping it into the batch. The run also keeps a copy of every document before making a change.