Build a bookkeeping close handoff the reviewer can use

Define ready for review before sending the work

If the reviewer has to reconstruct what arrived, what was checked and what is missing, your team pays for the same investigation twice.

A complete client folder still leaves someone turning supplier invoices into spreadsheet rows. That is the step ParseMill handles: upload invoice PDFs, review extracted details and line items beside the source, then download Excel. Keep document requests and engagement tracking in your existing process.

This guide provides an original administrative handoff method. It does not prescribe accounting treatment, certify a close, or decide which issues your firm may carry forward. Your engagement scope and responsible accountant determine those decisions. Start with the work the firm already performs, and give each completed check a direct evidence link.

Put six things on the cover sheet

1. Identity and scope: client, entity, reporting period, preparer, reviewer and the agreed work included in this handoff.
2. Evidence index: links to the exact statement files, working schedules and relevant reports. Test access as an authorized reviewer; a path on the preparer's laptop is not a shared evidence link.
3. Completed checks: name each check, who performed it and when. A checkmark should point to what was checked rather than merely confirming that a file exists.
4. Open exceptions: state the question, supporting evidence, impact on the next step, decision owner and next review date.
5. Changes since the previous version: identify replaced files, revised schedules and new client answers. Link earlier versions according to your existing retention process.
6. Acceptance: leave space for the reviewer to accept the handoff, return a specific item, or request clarification. Record the time and resulting state.

Use the same identifier for an exception in the cover sheet and the detailed queue. Avoid copying the whole queue into an email: separate copies become inconsistent as people work. The cover sheet is a navigation aid and a record of handoff, not another ledger.

Worked example: a prepared package with one open exception

Synthetic example: Harbor Workshop is a fictional client. The team has prepared its September package. The rows below illustrate a handoff format, not a real customer result or a recommendation about accounting treatment.

The preparer sends one link and a specific note: September package version 2 is ready for review. EX-17 remains open; please decide whether it blocks release. This is more useful than hiding the exception behind a complete status. The reviewer can return EX-17 while accepting the rest of the preparation, if the firm's agreed process permits that distinction.

Use the records your software already provides

Intuit documents a saved reconciliation report after reconciliation. Link the relevant report in the package when it is part of your process; a generic screenshot of the account screen gives the reviewer less context. Confirm that the report is for the intended account and period.

Karbon's task documentation describes task descriptions, due dates and a single task assignee. If your team uses Karbon, those fields can hold the next action, evidence link and named owner. The cover sheet method is our recommendation, not a claim that Karbon automatically validates the package. You can also implement it in the firm's existing checklist or spreadsheet.

Make returned work precise and keep approval separate

When returning an item, the reviewer should identify the failed check, the evidence examined and what would resolve the issue. Replace please fix September with EX-17: client explanation still missing; obtain the explanation or record the responsible accountant's decision. The preparer then updates that item and records a new package version only where the evidence changed.

A returned handoff should not automatically resend every client request or reverse completed work. Review the affected items and their dependencies. Equally, a completed task list should not automatically change accounting permissions or lock a period. Intuit treats changes to a QuickBooks closing date as an administrator action; maintain your firm's designated authorization for such decisions.

Check whether the next cycle is easier to review

For one cycle, count packages handed over, packages returned for missing evidence, broken evidence links and questions without an owner. Record review waiting time separately from active preparation and review minutes. A package returned twice is one package with two returns, so keep those denominators distinct. Compare similar client work before interpreting any change.

Use those observations to revise one part of the cover sheet. If links fail, fix access and version naming. If reviewers repeatedly ask the same scope question, make it an explicit field. If judgment is the bottleneck, route that decision clearly instead of adding more checkboxes. The exception queue guide and workflow toolkit support this exercise. A ParseMill workflow audit can help examine a repeated handoff problem; any implementation is scoped separately.

Questions about this workflow