> ## Documentation Index > Fetch the complete documentation index at: https://zenofirm.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Review and approve work > Check a proposed batch, approve the entries you want, and verify what reached QuickBooks Online. Use this guide when your assistant has prepared a plan and you need to decide whether it is ready to post. A plan contains proposed work; preparing it has not changed the ledger.

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](/docs/cloud/team) 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. You can also build a plan from coded bank-feed lines in the console. > 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. ## Review Open the plan's review page. Work through the evidence in this order: | Check | What to confirm | | - | - | | **Company and scope** | The plan belongs to the right client and contains the job you intended. | | **Dates and amounts** | The period, entry count, and totals agree with your source. | | **Coding** | Accounts, names, classes, and other dimensions reflect the intended treatment. | | **Warnings and blocked entries** | The issue is resolved or the affected entry is held back. | | **Duplicates and transfers** | An existing transaction or a two-sided transfer will not be recorded twice. | 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. ## Apply After approval, ask your assistant to apply the approved plan. This is the step that changes QuickBooks. If the reviewed plan or its exclusions changed, Zeno refuses to apply it. Prepare a new plan and review the current version. If a run already exists, read that result before retrying; repeating an apply does not create a second run for the same plan. For a feed plan, lines that have since been linked to existing transactions, excluded, or posted elsewhere are skipped. 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. Reversal remains available regardless of plan tier. Reads and review also remain available when a subscription restriction blocks new writes. ## 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 | Work | Planning tool | | - | - | | Documents, a list, or instructions | `qb_plan_batch` | | Coded bank-feed lines | `qb_plan_feed` | | Spreadsheet or IIF import | `qb_import_table`, `qb_import_iif` | | Correct, void, or delete existing documents | `qb_plan_cleanup` | | Create, change, or deactivate names | `qb_plan_names` | These workflows all produce a plan for review. See the [hosted tool reference](/docs/cloud/tools) for parameters and restrictions. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.