A document-retention map for offshore bookkeeping work

List bank statements, invoices, receipts, payroll sources, reconciliations, journals, approvals, reports, exception logs, and handoff notes. Name the process, entity, period, owner, and system. A document map should reflect how work is actually performed, including files created by an offshore bookkeeper and files received from the client. Avoid a single “finance” folder with no purpose or owner.

For every record type, state which system or folder is authoritative, who may edit it, and how versions are identified. A chat message may be a notification while the approval record belongs in the finance system. The bookkeeper can link sources and flag duplicates. The owner decides which copy controls when systems disagree.

Keep the submitted source, preparer note, reviewer question, response, replacement evidence, and final decision according to policy. Do not delete a prior version to make the folder look clean. Mark it superseded and link the replacement. This makes a handoff understandable when people work different hours or a reviewer returns months later.

Use named accounts, multifactor authentication, and role-based permissions. Separate payroll, bank, customer, vendor, and general bookkeeping access where practical. The map should name the access group and owner, not a shared password. Review permissions after staffing changes and remove access when an assignment ends. Evidence access must be controlled even when the task is routine.

Record the client’s policy reference, effective date, and disposal authority. Do not invent a period based on convenience or copy a generic rule from another business. If the policy is unclear, escalate before deleting or archiving. The bookkeeper can prepare an ageing report and identify records approaching the policy boundary. An authorized owner decides action.

A record subject to an investigation, dispute, audit, or other client-defined hold should not be disposed of under the normal schedule. The owner places, releases, and documents the hold. The offshore role can update the inventory and preserve links. Never remove a record because a task is complete if another process still relies on it.

Select a bank reconciliation, vendor approval, payroll source, and reporting pack. Ask a second person to locate the source, version, reviewer decision, and retention rule without coaching. Record broken links, confusing names, and missing owner fields. Retrieval is a practical test of the map; a list of filenames is not enough.

Revisit the map when an accounting system, shared drive, workflow, entity, or staffing arrangement changes. Confirm exports still contain identifiers and that permissions match the role. Archive the prior map with its effective date. Update procedures before a migration so evidence is not lost between systems.

The map should also identify the person who handles retrieval requests and the system where the authoritative copy is held.

Retention rules should be reviewed when a system, entity, process, or client policy changes. The offshore bookkeeper can inventory folders, identify records without an owner or retention class, and prepare a list of conflicts. The client decides which legal, tax, regulatory, or contractual requirements apply. Do not infer a retention period from a file name or from how long a folder has existed. Preserve the decision, effective date, and approving owner with the map.

A practical review also checks retrieval. Select a sample from a closed period and confirm that an authorized reviewer can locate the source, understand its relationship to the ledger entry, and distinguish the original from later annotations. Note missing permissions or duplicate repositories as control issues, not as reasons to copy everything into a new location. A document-retention map gives offshore bookkeeping support a safe route through evidence, versions, access, retention, and retrieval. The bookkeeper maintains inventory and links. The client decides policy, holds, access ownership, and disposal. Map records by process and purpose, keep approval history, test retrieval, and treat a system change as a reason to review the whole evidence trail.

Every record category needs one person who can answer where the authoritative copy lives and what happens when it is missing. The bookkeeper can maintain the index and request a source. The process owner decides whether a substitute is acceptable and whether the record is complete. Put the escalation route beside the record type so a missing invoice or bank statement does not remain an unassigned task.

Broken links are evidence failures even when the underlying file still exists. At each close, sample links from reconciliations, AP approvals, AR notes, payroll packets, and reporting files. Record the sample date, result, and repair owner. Do not replace a broken link without retaining the original reference and explaining the change. This small check protects continuity for distributed teams.

Multiple copies create uncertainty about which approval or version controls. Use identifiers and a source register to point to the authoritative record. If a working copy is necessary, label it as such and state when it must be removed under the approved policy. The offshore bookkeeping role can identify duplicates; an owner decides which record remains authoritative. Name a handoff owner for every record category. Sample links at close, label working copies, and record broken links, missing owner fields, and the approved action for duplicates.