The result: you know which entries you approved, which ones posted, and which ones need further work.
Before you review
Have the source documents or instructions available. Check that your role allows approval for this company. A colleague can prepare the work even when a different person is responsible for approving it.Plan
Ask your assistant to prepare a plan for a specific company, job, and period. That includes bank-feed lines: your assistant codes them and builds the plan, and the console is where you review and approve it.Prepare a plan for Ridgeline’s March Amex charges. Show the proposed coding, total, warnings, and any entries that cannot post. Do not apply it yet.Zeno checks the proposed work against the connected ledger, including names, duplicates, closed periods, and applicable confirmed rules. Read those results; a plan being available does not mean every line is ready.
The same request asked twice
Zeno keeps one plan per request. When your assistant asks for exactly the same work again (the same lines, dates, and amounts, whatever it calls the batch), the plan it already made comes back instead of a second copy, as long as that plan is still open and was made within the last day. If an older copy is still open, the new plan is made and both pages say so, so you can reject one. If the same request has already posted, Zeno refuses it and names the run that posted it. Your assistant can plan it again as a deliberate repeat only when you ask for the work to be done a second time. The plans list marks a plan that has an identical copy, and its page says whether the other copy is waiting or has already posted, with a link to it. Approve one copy; reject the others. The same applies to single changes outside a plan: the same change asked twice comes back as the approval already waiting.Review
Open the plan’s review page. Work through the evidence in this order:
Exclude lines that need more work, or ask your assistant to correct the work
and prepare a new plan. Review the revised plan before approving it.
Approve only the plan as you intend it to post. Zeno records your verdict
against that version of the plan, including your exclusions.
Single changes outside a plan
Some changes are one call rather than a plan: editing, voiding or deleting one document, emailing an invoice, a company setting. Your assistant’s first call writes nothing and gives you a link. In a chat app that shows Zeno’s pages, such as ChatGPT or Claude, the request is also drawn right in the conversation, the way a plan is. Each waiting request is also listed on the console’s Plans page, above the plans, marked awaiting approval, and counted in the number beside Plans. Read exactly what it will do, in the chat or in the console, and approve or turn it down, with your own words if you like. Only then can that exact call run, once.Apply
After approval, ask your assistant to apply the approved plan. This is the step that changes QuickBooks.After you approve
When the plan or the single change is drawn inside the chat, approve it there. Your Approve or Turn down click is passed to the conversation as your own message, and your assistant carries on: it posts the plan or runs the change. ChatGPT may flag that message with a warning, because it came from Zeno’s page rather than from your keyboard. It is your decision, and it is safe to continue. Your assistant acts only when you send it a message. Chat apps do not let an outside service such as Zeno start a turn, so an approval you give in the console reaches the chat only if your assistant is still waiting for it. It waits a short while after giving you the link, so a quick decision is usually picked up. If the chat has gone quiet, go back and say “approved” (or “rejected”); it reads your decision from Zeno and carries on. Neither path can approve anything on its own or send anything twice. Zeno accepts an approval only from a signed-in person’s click, and an approved single change, such as emailing an invoice, runs once however many times the assistant is told. If the reviewed plan or its exclusions changed, Zeno refuses to apply it. Prepare a new plan and review the current version. Zeno also refuses to apply a plan when an identical plan has already posted, and names that run. If a run already exists, read that result before retrying; repeating an apply does not create a second run for the same plan. An entry that another plan’s run has already posted is skipped, and the run’s result names that run. For a feed plan, lines that have since been linked to existing transactions, excluded, or posted elsewhere are skipped too. The plan shows them as already posted with an explanation. A plan with no remaining work is stalled.Check what posted
Read the run’s result rather than assuming every entry succeeded. Compare its posted total and entry count with what you approved, inspect failed or skipped lines, and confirm the entries in the QuickBooks register. If the connection was interrupted, inspect the recorded run before deciding what to retry. Zeno retains entry identifiers to avoid posting the same work twice; do not create a different source reference simply to bypass a refusal.Reverse
When a posted run needs to be undone, identify the run and review the affected entries before requesting its reversal. Reversal changes QuickBooks again; it does not erase the original run’s history. Zeno uses the transaction’s supported reversal operation: voiding where available, deleting where needed, and restoring recorded prior values for changes. Check the reversal result for anything that could not be undone.Restoring a deleted document creates a new QuickBooks identifier. Restoring a
void or an edit can act on the original document. The reversal result says
which happened.
Names go through the same door
Creating or changing a vendor, customer, account, or other name also needs a plan. Read Create, Modify, and Deactivate lines as carefully as transaction lines. Correct a near match before adding a second spelling of an existing name. Deactivating a name removes it from selection while preserving its posted history. Reversing a names run deactivates created names, reactivates retired ones, and restores the changed fields recorded before the write. Reactivating a parent does not automatically reactivate children that QuickBooks retired with it; inspect the reversal result.What a plan carries but does not keep
Do not include a vendor’s tax identifier, an employee’s Social Security number, or a date of birth in a plan. Zeno refuses those fields because plans and review history are retained. Enter them directly in QuickBooks Online. A plan may still mark a vendor for 1099 reporting. A Desktop import leaves vendor tax identifiers behind and lists the vendors that need to be finished in QuickBooks Online.Tool reference
How your assistant prepares the different kinds of plan
How your assistant prepares the different kinds of plan
These workflows all produce a plan for review. See the
hosted tool reference for parameters and restrictions.