Offshore Bookkeepers guide

A mid-close handoff note that keeps unfinished work reviewable

A practical handoff note for an offshore bookkeeping team that has to pass an unfinished close to another reviewer without losing ownership or evidence.

A practical handoff note for an offshore bookkeeping team that has to pass an unfinished close to another reviewer without losing ownership or evidence.
Table of contents

The short answer

  • Write the close state down at the moment of handoff, not from memory the next morning.
  • Give every open item an owner, a next action, a due point, and the evidence that would close it.
  • Keep preparation, review, and approval visibly separate so the next person knows what is decided and what is not.

A close rarely stops at a convenient boundary. A bookkeeper finishes the bank feeds, gets halfway through accruals, and then a shift ends, a client contact goes quiet, or a reviewer needs to step away. The ledger is not wrong, but it is also not finished. The next person inherits a screen full of partially completed work and a set of assumptions that exist only in the previous person's head.

A mid-close handoff note is the small control that prevents that gap from turning into rework. It is not a status report for management and it is not a second close checklist. It is a short, dated statement of where the work actually stands, written by the person handing it over, so the next reviewer can continue without guessing.

Why an unfinished close needs a written state

Most close checklists track whether an item is done. They are much weaker at describing an item that is half done. A checklist row marked "in progress" can hide very different situations: the source document arrived but the coding is unconfirmed, the coding is agreed but the approval is missing, or the entry is posted but the reconciliation has not been run.

Those differences matter because each one needs a different next action. If the handoff note says only "accruals in progress," the receiving bookkeeper has to reopen every file to discover which stage each item reached. That is where duplicate work starts, and it is also where an item quietly gets treated as complete because nobody wants to ask.

Writing the state down also protects the person handing over. A clear note shows what was completed, what was blocked, and what was deliberately left for a decision-maker. It turns an informal verbal handoff into a record that can be reviewed later if a question arises about timing or ownership.

Name the owner, the period, and the stopping point

The note starts with four facts: the entity, the reporting period, the close checklist version, and the exact point at which the handoff takes effect. "Close through the bank reconciliation, before accrual review" is a usable stopping point. "Most of the close" is not.

Name the person handing over and the person receiving. If a third person owns a decision, name that person too. A note that says "waiting on approval" without naming the approver will sit untouched.

Record the time and the time zone. Distributed teams often work across several zones, and "this afternoon" means different things in Manila, London, and New York. A timestamp removes the ambiguity.

Finally, state what the receiving person is authorized to do. Can they post a corrected entry within an agreed threshold, or only prepare it for review? Can they contact the client directly, or must the request go through the engagement lead? The boundary should match the role, not the urgency of the moment.

Record each open item as a testable statement

An open item should read like a small test, not a topic. "Fixed assets" is a topic. "Confirm whether the October equipment invoice should be capitalized or expensed, using the client's capitalization policy and the receiving record" is a testable statement.

For each item, record the account or workpaper reference, the amount at stake, the source document already obtained, the specific fact still missing, the person who can supply it, and the action that would close it. Add the date the item entered the queue so the next reviewer can see whether it is new or aging.

Use the same fields for every row. A consistent structure makes it possible to sort by owner or age and to spot items handed over more than once. Repeated handoffs are a signal that the item is blocked by something the team has not named.

Avoid writing conclusions the evidence does not support. "Client says the invoice is for a new machine" is an observation. "Capitalize the invoice" is a decision. Keep the observation in the note and leave the decision with its owner.

Separate what is prepared from what is decided

The most useful distinction in a handoff note is between preparation and authority. The offshore bookkeeper may have gathered the invoice, matched it to the purchase order, calculated the candidate amount, and drafted the journal. None of that means the entry is approved.

Use three states: prepared, reviewed, and approved. A prepared item has the evidence attached and the proposed treatment written down. A reviewed item has a named reviewer's conclusion. An approved item has the authorized person's decision and the date. If the team uses different words, define them in the note so the next person does not read "reviewed" as "approved."

This separation also protects the close timeline. An item can be prepared and waiting for approval without being described as incomplete work by the bookkeeper. The delay is visible in the right place, with the right owner, and the reviewer can decide whether to wait or to post an accrual.

Make the next reviewer's first hour productive

The receiving reviewer should be able to start with the highest-risk item, not with a tour of every file. Put a short priority list at the top: the items that affect the trial balance, the items with a client deadline, and the items that could change a previously reported number. Then list the routine work below.

Link directly to the workpaper, the source document, and the relevant checklist row. A link is faster and less error-prone than a description of where to look. If a link points to a location the receiving person cannot access, fix the permission before the handoff.

Include a short "do not touch" list for items that are under review or subject to a client instruction. The next person needs to know which entries are frozen and why. Without that, a well-intentioned correction can overwrite a decision that was already made.

End the note with the questions the sender would ask if they were staying. That surfaces the assumptions most likely to be wrong. The receiving reviewer can answer them, route them, or add them to the open-item list.

Close the note when the work actually closes

A handoff note is a living record until the close is complete. When an item is resolved, update the state and the date rather than deleting the row. The history shows how long the item took and who moved it, which is useful when the same bottleneck appears next month.

At the end of the close, the note should reconcile to the close checklist: every item is prepared, reviewed, approved, or explicitly carried forward with a reason. If an item was dropped, the note should say so and name the person who accepted the drop.

The final version belongs with the close workpapers, not in a chat thread. GAO's internal-control standards emphasize documented transactions and reviewable records, and IRS recordkeeping guidance makes the same point from the tax side: the record should let someone reconstruct what happened. A dated handoff note is a small but practical part of that record. It keeps an unfinished close from becoming an unowned one.

Questions owners ask

How long should a mid-close handoff note be?

Long enough to reconstruct the state of each open item and short enough that the next reviewer reads it. A one-page summary plus a linked open-item list usually works better than a long narrative.

Should the note repeat information already in the close checklist?

No. Reference the checklist item and add only the current state, the blocker, the owner, and the next action. Duplicating the checklist creates two versions that will disagree.

Who should write the handoff note?

The person who currently owns the work writes it before handing off. The receiving reviewer acknowledges it and records any question rather than silently reinterpreting the status.

Keep planning

Sources

  1. U.S. GAO, Standards for Internal Control in the Federal Government
  2. IRS, Recordkeeping