Review stale checks during bank reconciliation without hiding open liabilities

The records for stale and outstanding checks rarely live in one system or arrive at the same time. A dependable packet connects the bank statement, check register, payee record, invoice, void history, stop-payment evidence, unclaimed-property review, and general ledger. Posting only the final net amount removes the trail needed to explain timing, ownership, deductions, approvals, and unresolved differences.

Useful background includes IRS recordkeeping guidance and the NIST definition of data integrity. These sources support disciplined record handling; they do not decide the company’s accounting treatment, contractual obligations, approval policy, or local compliance. Record the source and access date when changing guidance affects the procedure.

The goal is not a cosmetically clean spreadsheet. It is a reproducible bridge from original records to the proposed bookkeeping result. A reviewer should be able to identify the population, reproduce the arithmetic, inspect every material exception, and understand which decisions remain open.

Start by fixing the legal entity, reporting period, local time zone, cutoff, currency, source systems, preparer, and reviewer. Download untouched reports with extraction timestamps, filters, row counts, and control totals. Keep a dated copy when a report can change. Missing evidence must stay visible rather than being replaced with an estimate presented as fact.

Build the population from stable identifiers, not descriptions or amounts alone. Capture the source date, effective date, service period, gross amount, deductions, fees, tax, refunds, currency, account, evidence link, current status, owner, and next action. Preserve original and corrected values. Do not merge unrelated events merely because they share a date or net to the same amount.

Create an evidence index before investigating discrepancies. For every file, note who supplied it, where the approved copy is stored, its extraction parameters, the covered period, and whether it is complete. Compare its record count and total with an independent control such as a system summary, signed schedule, statement, or ledger report.

Document late-arriving records separately. A transaction received after cutoff may still belong to the period, but the authorized finance owner decides treatment under the company’s policy. The bookkeeper records the facts, quantifies the effect, and routes the decision.

Reproduce each source total before comparing systems. Roll the opening position through additions, applications, releases, reversals, transfers, refunds, credits, corrections, and the closing position. Tie the result to the operating report, subledger, general ledger, and bank activity where applicable. A net agreement can conceal equal and opposite errors.

A concrete example

The register contains 18 checks older than 90 days totaling $31,400. Two cleared after cutoff, five have documented replacements, and eleven still need payee and policy review. The schedule keeps each liability open until an authorized decision is supported.

First reproduce the arithmetic in every source. Then compare the result with the approved agreement or operating procedure. Finally show the ledger effect. Describe an exception as an observed fact: one source reports a value, another reports a different value, and the difference is quantified. Keep possible causes in a separate note until evidence confirms them.

Use statuses that tell the next person what to do: ready to match, matched, timing item, missing evidence, amount mismatch, duplicate risk, policy question, awaiting approval, disputed, and closed with evidence. Every open row needs an owner, due date, value, and focused question. When an exception carries forward, retain its original age.

Set escalation thresholds through company policy, but do not use dollars as the only signal. A small repeated error, altered payment instructions, unusual access, an approaching deadline, or a missing approval may deserve immediate attention. Aging and recurrence often reveal broken handoffs that a single-period total hides.

An offshore bookkeeper can collect approved exports, compare identifiers and values, reperform calculations, request missing documents, update statuses, and draft a proposed entry. The bookkeeper should not interpret a contract, approve a credit, release money, decide accounting policy, change master data, or close a disputed item without the authorized reviewer.

Make each decision request answerable without rebuilding the file. Include the entity, period, amount, deadline, evidence links, observed difference, available options, and operational consequence of delay. Save the response with the workpaper rather than relying on a private message. If the response changes, retain the earlier version and explain the superseding decision.

Protect access as carefully as the arithmetic. Use named accounts, multifactor authentication, and least-privilege permissions. Separate preparation from payment release, bank-detail changes, customer credits, refunds, write-offs, journal approval, period locking, and deletion. Store sensitive evidence only in approved systems and mask identifiers that the task does not need.

Trace samples from the untouched source into the workpaper, then select workpaper rows and trace them back to source evidence. Reperform large, unusual, old, manual, zero-value, and post-cutoff transactions. Investigate repeated exceptions even when each amount is individually small.

The reviewer confirms the population, control totals, formulas, exception ownership, proposed entries, and judgment calls. A review note should state one question, its owner, the response date, the response, and closure evidence. Review is not complete merely because every spreadsheet cell is populated.

Useful operating measures include population count, matched and unmatched value, oldest exception, returned corrections, records missing evidence, and percentage reviewed by the agreed deadline. These are workflow signals, not promises of accuracy, savings, compliance, or financial performance. Changes in volume, systems, policies, or reviewer availability should be noted beside the measures.

When a recurring difference appears, repair the intake form, export, naming convention, mapping rule, or approval path. Do not silently add a spreadsheet plug. A controlled procedure makes the exception easier to prevent or diagnose next period.

Close with the untouched exports, reconciliation, evidence index, exception log, approved entries, decisions, and a concise summary. State what tied, what remains open, the amount involved, the next owner, and the next review date. Link the packet from the close checklist using a consistent entity-process-period-version name.

Archive the reviewed version under the company’s retention and access rules. Do not overwrite the approved packet when a late item arrives; create a new version with a change note. If a proposed entry is rejected or changed, preserve both the proposal and the authorized outcome.

For help defining the preparation lane, see the relevant Offshore Bookkeepers service. If your company needs a Philippines-based bookkeeper to maintain this schedule while its finance owner retains approval, plan the role with Offshore Bookkeepers.