Where bookkeeping should hand off to a controller

A controller engagement is useful when the books need decisions and review that the current bookkeeping scope does not cover. Examples include an unsupported opening balance, a material customer prepayment, intercompany differences, or a recurring close that cannot be completed without the founder choosing accounting treatments.

Job titles vary across firms. Some experienced bookkeepers already prepare detailed schedules and review unusual entries; some controller packages are mostly reporting calls. Write down the work that is currently missing before adding another title to the team.

The bookkeeper might collect statements, post approved entries, reconcile cash, and prepare a schedule of prepaid expenses. The controller could review that schedule, decide which exceptions need further work, and approve the close. Whoever holds each role should understand both the handoff date and the evidence expected.

Avoid assigning both providers to maintain the same schedule independently. That creates two versions and an extra reconciliation. Use one working schedule with identifiable preparation, review comments, corrections, and approval.

Create an exception queue for transactions the preparer cannot resolve from existing policy. Include the account, amount, period, source document, and question. The reviewer should respond with a treatment or a request for specific missing facts, rather than a general instruction to investigate.

For example, an annual software payment might require a routine prepaid schedule, while a contract that combines software access and implementation could require a more detailed assessment. The second item should not wait until the reporting meeting merely because the payment has already been categorized.

Accounting review does not automatically authorize a controller to release money, hire employees, sign contracts, or change vendor bank details. Separate the approval of a journal entry from the approval of a payment. A person can review the books without having unrestricted access to move funds.

Document who approves assumptions that depend on business judgment, such as expected collection of a disputed invoice. The controller can explain the reporting effect, but the sales or operations team may hold the facts needed to support the estimate.

After the first close, inspect where work stopped: missing statements, unanswered policy questions, late operational data, or an unclear approval owner. Change the sequence around those bottlenecks. Adding more reviewers rarely helps when nobody knows which version is ready for review.

At the next close, check whether the same exceptions recur. Keep a short accounting-policy note for resolved recurring issues so the bookkeeper can handle them consistently. Reserve controller time for the items that still need judgment and for checking that the process is working.