What to keep in-house when you outsource bookkeeping support

The line is authority, not difficulty

Owners often keep the hardest bookkeeping task in-house and hand over the easiest one. That is backwards. The better line is authority: who may move money, change a vendor record, or approve a write-off.

Difficulty can be taught, but authority should not be delegated by accident. A task can be simple and still be the wrong thing to hand over.

Write the boundary before the first login. List the tasks the role may complete, the tasks it may prepare for approval, and the tasks it may not touch. Keep the list short enough to fit on one page.

Review it whenever the role gains a new system or a new vendor. A boundary that lives only in a conversation will be redrawn by whoever is busiest.

Tasks that can move with review

Data entry from receipts, invoice coding against an approved chart, bank statement downloads, and vendor record updates are common candidates. Each has a visible source and a checkable result. Move them only when a reviewer can compare the entry to the underlying document.

Start with a small batch and check every item before adding volume. A task that cannot be checked from a source is not ready to move.

Month-end checklists, account reconciliations, and report preparation can also move when the owner reviews the output. Set a materiality threshold for the review so the owner looks at the items that matter. A reconciliation without a reviewer signature is a draft, not a control.

Keep the reviewer's name and date on the record. If the same person prepares and approves, the control is only a formality.

Tasks that stay with the owner

Bank account access, payment release, credit decisions, tax filings, and any adjustment that changes reported income should stay with a named internal authority. A coordinator may prepare the file, but someone with accountability must approve it.

Do not let a shared password blur that line, because a shared login erases the evidence of who acted. Name the approver in the role brief and in the system.

Legal and tax interpretations also stay inside. If a transaction needs a judgment about treatment, the coordinator can flag it and supply the facts. The decision belongs to the owner or the adviser, and the record should show who decided.

Keep the question and the answer together so a later reviewer can see the reasoning. A pattern of similar questions may mean the chart of accounts needs repair.

Watch for a role that both prepares and releases a payment, even at a small amount. The combination removes the check that makes the delegated task safe. Keep preparation and release in different hands, or add a second reviewer for the release step.

If the team is too small to separate the tasks, increase the review rather than ignoring the gap. A written exception is better than a silent one.

Write approval limits into the role

Approval limits should be specific: an amount, a vendor type, a frequency, and an expiry date. A limit that says up to a reasonable amount is not a limit. Put the numbers in the role brief and in the system where the work happens.

Test the limit with one real invoice before go-live. If two people read the limit differently, it is not written clearly enough.

Name a deputy for absences and set the same limits. Record temporary increases with a start date, an end date, and a reviewer. Remove the increase when it expires rather than relying on memory.

Keep a short log of limit changes so the current rule can be reconstructed. A limit that changes silently is worse than no limit, because people believe a control exists.

Design the evidence trail for a clean handoff

Each entry should link to the source document, the date received, the person who coded it, and the reviewer. Keep the bank statement or receipt in one approved location rather than in an email thread. A later question should be answerable without the original coordinator.

Use a stable identifier across the accounting system and the source folder. That identifier is what lets a reviewer follow the item from receipt to report.

Record corrections as new entries with a reason, not by overwriting the original. The trail should show what changed and who approved it. That is what makes a handoff reviewable months later.

Keep a short correction log beside the account so the pattern is visible. If corrections cluster around one vendor or one code, fix the source rather than the entry.

Revisit the boundary as trust grows

Trust is not a reason to skip the review. When the error rate is low, reduce the sample size or extend the review interval, but keep the control. Document the change and the evidence behind it.

A smaller sample still needs a named reviewer and a recorded result. The point is to match effort to risk, not to remove the check.

Add responsibility only after a clean review cycle in the new scope. If the error rate rises, return to the previous boundary without debate. The goal is a stable role with clear limits, not a permanent test of good intentions.

Put the next boundary review on the calendar with the evidence you will use. A review that depends on a feeling will drift.