Client onboarding and cleanup work: protecting bookkeeping capacity

A connected account is only the first gate

Document the legal entity, authorized client contact, account ownership, prior closed date, opening balances, accounting policies and the records needed for each account. Use vendor-supported invitations and role controls rather than shared bank credentials. Require the client to connect feeds or provide statements through the agreed secure channel; the bookkeeping team does not execute payments in this scope.

Keep requested, received and reviewed columns. A folder with statements may still be incomplete, duplicated or inconsistent with the opening trial balance. A reviewer marks whether the file is ready for a current close, requires bounded cleanup, or needs a qualified referral. Intuit’s described cleanup process starts when required information is available, which is a useful boundary for scheduling; its timing is not a promise for this team. Document dependency

Separate historical questions from current-month work

Write the cleanup’s start/end period, accounts, source documents, opening-balance issues, expected deliverables and change-order process. The case’s $900 cleanup task buys an assumed 12.0 delivery hours plus 2.0 owner hours. Three elapsed historical months do not necessarily require three current-close workloads; volume, data condition and exception causes must be assessed.

A capped task is viable only when its exclusions are usable. Missing lender statements, unreconciled loans, commingled transactions or unknown prior-year treatment can stop work. Refer tax/legal/assurance questions to appropriately qualified advisers, then resume only with an agreed record treatment. Do not quietly overwrite a closed period to force balances to tie, or represent ordinary management reports as reviewed/audited financial statements. Professional scope

Put the requested work in the paid calendar

Existing closes consume 192.0 hours; three onboarding files add 36.0 and two cleanup jobs 24.0. Total requested delivery is 252.0 hours against 224.0 usable hours, leaving a 28.0-hour shortage even though reviewer demand is within its ceiling. That month cannot be sold as fully deliverable without another paid resource or a changed schedule.

If twelve usable hours are needed for additional training/absence cover, safe capacity becomes 212.0 and shortage grows to 40.0 hours. Training has a paid cost and an opportunity cost. The selected usability already allows routine training; this extra scenario is an incremental disruption, not a second deduction of the same baseline hours. Training context

Sequence work and revise promises before accepting it

Protect already accepted current closes, then place ready onboarding files and bounded cleanup into named slots. Offer a later start, use a qualified paid subcontractor/employee with supervised access, or revise the cleanup scope. A second person must receive context and review; assigning the same difficult file to two people is not automatically twice the throughput. Leave an exception buffer whose hours are visible in the roster.

Record the promised close date only after readiness and resource approval. Ask the reviewer to approve opening balances and exception treatment before scheduling recurring delivery as routine. Use an engagement-specific handoff checklist: records received/reviewed, chart approved, accounts reconciled, unresolved items logged, outputs checked, owner questions routed and access removal/return procedure known. A completion email without this work is not a reconciled close.

Re-estimate when cleanup exceeds the bounded task

Suppose one cleanup task requires 24.0 delivery hours instead of 12.0, with the same reviewer time. Its modeled $900 fee now leaves −$290.60 after allocated delivery/review, processing and expected write-off. That adverse example is a reason to stop and obtain a revised scope, not to bill imaginary additional work or count unpaid owner overtime as a solution.

Keep active work separate from waiting days. If the client supplies missing evidence late, revise the calendar explicitly. Repeated exceptions can require a different retainer envelope even after cleanup; do not turn a one-time recovery project into a permanently underpriced monthly service. Preserve a concise issue ledger so the new reviewer can see why a transaction remains unresolved.

Close the cash and data handoffs as well as the file

Invoice onboarding/cleanup separately from recurring work, specify deposits or milestones if negotiated, and match the forecast to actual collection terms. This model recognizes completed work in the service month and leaves a net receivable tail; it does not assume a nonrefundable advance or revenue earned at a signature. For base month 6 billings, shifting 20.0% from current to next-month collection adds $2,174 to the end-month receivable and reduces current receipts by the same amount before fee timing. Revenue billed is unchanged; payroll and debt dates are not moved.

Client offboarding should return agreed records, identify outstanding exceptions and remove access through the documented process. Keep individual client files out of the public model dossier. The future owner plan can describe anonymized work and controls, while actual lender/client disclosures follow their agreed secure requirements.

Reconnect the queue to the monthly cash forecast and funding prerequisites. The base forecast already has a cash gap, so promising cleanup outside paid capacity would make an unresolved launch more fragile. Approve the scope, readiness, paid roster, review and collection dates together before giving the next client a firm close date.