A first-week plan for a remote bookkeeper

Name a primary reviewer and a backup. Choose one or two bounded tasks, such as updating a reconciliation from provided statements or preparing an accounts-receivable aging follow-up list. Assemble the current procedure, redacted examples, file locations, deadline, expected output, and escalation contacts.

Create named accounts with least-privilege access; do not send shared passwords through chat or email. Enable multifactor authentication where supported and decide how sensitive records may be downloaded, stored, and deleted. CISA provides general guidance on multifactor authentication. The company should apply its own security and retention requirements.

Walk through the business entities, accounting calendar, systems, chart-of-accounts conventions, and communication channels. Then review a responsibility map: what the bookkeeper prepares, what the reviewer checks, and what stays with an authorized owner.

Be explicit that payment release, bank-detail changes, payroll approval, customer credits, vendor setup, write-offs, tax positions, and accounting-policy decisions are not implied by “bookkeeping support.” Confirm working hours, response expectations, urgent-event contacts, and how to report a suspected access or data issue.

The day-one output is a written scope and questions list, not a live posting target.

Test each approved login, permission, source folder, and report. Record access granted, owner, purpose, and review date. Stop if permissions are broader than requested or prevent the assigned work.

Follow one transaction from source document through system entry, reconciliation, review, and archive. The bookkeeper should identify which record is authoritative, the cutoff rule, naming convention, and evidence required to close the item. Update the procedure when the actual system differs from the written instructions.

Use redacted historical examples that include a normal item and several exceptions. Ask the bookkeeper to produce the expected worksheet, evidence links, and exception notes while sharing their reasoning. The reviewer checks whether the process was followed and whether questions were raised at the right point.

Correct the SOP rather than relying on verbal reminders. If an example requires judgment, document who decides it; do not turn the example into permission for the bookkeeper to make that decision later.

Assign a small current task whose source records are complete and whose impact can be reviewed promptly. Define a stop condition - for example, no posting when the control total differs or support is missing. The bookkeeper prepares the work and records exceptions; the named reviewer checks it before any consequential posting or external communication.

Evaluate evidence quality, cutoff handling, use of the escalation route, and access behavior. Speed is secondary because the sample may be too small or unfamiliar to measure normal throughput.

Hold a structured review covering completed work, errors or ambiguities, open access issues, unresolved exceptions, and procedure changes. Decide task by task whether to continue at the same scope, add a clearly defined step, provide more training, or pause. There is no arbitrary number of cycles that makes a handoff safe; review depth should reflect risk, system rights, task complexity, and observed work.

Finish with an access inventory, corrected SOP, source map, exception log, reviewer schedule, and next-week task list. The bookkeeper can own documented preparation and follow-up. Authorized business roles retain approvals, payment release, policy judgments, and exceptions that change financial reporting or business risk. IRS recordkeeping guidance offers general context when defining how source evidence will be retained.