Build a bank reconciliation evidence index that survives review

A reconciliation index is only as reliable as the list it is meant to describe. Begin with the legal entity, bank account, currency, statement period, and ledger account. Record accounts that are inactive, newly opened, or intentionally excluded. A remote bookkeeper can assemble that population from the chart of accounts, bank portal, and prior close packet. The finance owner should approve the scope because an omitted account can make the close appear cleaner than it is. Keep the extraction date in the index. When an account is added later, show when it entered the population and why. Do not overwrite the original scope note. A reviewer should be able to compare this month with the previous month without guessing whether a missing line means “not applicable” or “not performed.”

Use a stable identifier that combines entity, account, and period. The identifier should travel with the statement, working file, exception note, and reviewer response. Avoid names such as final-new.xlsx, which say nothing about ownership or period. A useful row includes the account number, statement end date, book balance, bank balance, preparer, preparation date, reviewer, review date, and status. Add a link to the statement and the supporting workpaper. A bookkeeper may maintain these fields and flag missing values. The reviewer decides whether an incomplete row can be accepted, held, or returned. If files move between folders, update the link while retaining the old location in the audit note. Small details matter here because a later reviewer often starts with the index rather than the bank portal.

The reconciliation line should explain the nature of the difference, not merely show a number. Separate deposits in transit, outstanding payments, bank fees, timing differences, duplicate entries, and items with no clear explanation. Attach the source that supports the category. If a difference is only an assumption, label it as a question. The bookkeeper can calculate the gap and identify the transactions that appear related. The authorized reviewer decides whether a correction, reclassification, write-off, or policy treatment is appropriate. Never force the ledger to the statement simply because the close date is near. A temporary match without evidence creates work for the next period and can conceal an error. A short plain-language note is more useful than a polished status that does not explain what happened.

Reviewers need to know what changed since the last pass. Add a prior status, current status, movement reason, and open question. If an item was cleared, link the clearing evidence. If it was carried forward, state why it remains open and who owns the next action. A remote handoff should not say “please check.” It should ask, for example, whether a deposit belongs to a named customer receipt, whether a payment cleared in the following period, or whether a fee should be recorded under the existing policy. The bookkeeper can prepare that bounded question after checking the source trail. The owner, controller, or CPA supplies the decision. This division lets preparation continue across time zones without turning an unclear message into an unauthorized journal entry.

Keep original statements in a controlled location and record the statement date used in the workpaper. Do not rely on a screenshot when the portal provides a downloadable statement, and do not replace a source file with an edited copy. Named accounts and multifactor authentication are appropriate for bank and accounting tools. The bookkeeper should have only the access required for preparation and should not change bank permissions, add signers, release funds, or approve their own exception. If access is temporarily expanded, record the approver and removal date. A clean index cannot compensate for weak access controls. Treat downloads containing account information as sensitive, limit sharing, and use a documented handoff when another person takes over the queue.

Age each unresolved item from the date it was first identified, not from the date someone last touched the row. Use age bands that help a reviewer decide what to do next. An old item may need a source request, a customer confirmation, a bank inquiry, or an accounting decision. The bookkeeper can send a permitted request and record the response. Escalate when evidence conflicts, a balance crosses entities, an item would change reported results, or the next step requires authority the bookkeeper does not have. Measure the count of carried items, reopened items, missing statements, and time waiting on an owner. Do not reward closure alone. A queue that shrinks because unresolved rows are deleted is less trustworthy than a larger queue with clear ownership.

Use a small review sample that includes an ordinary reconciled account, an old reconciling item, a timing difference, and a row with incomplete support. Ask a second preparer to locate the source and understand the next action without verbal coaching. Inspect whether the identifier is consistent, the statement is present, the difference is described, and the reviewer decision is distinct from the preparer note. If two people reach different conclusions about what a status means, change the instructions before adding accounts. The goal is a reproducible handoff, not a spreadsheet that only its creator understands. Keep a short record of the test and any changes made to the template.

At the end of the cycle, the packet should contain the index, statements, workpapers, open-item notes, and reviewer decisions. Preserve the version used for sign-off. If a correction is posted later, add the entry reference and reason rather than editing history. Offshore bookkeeping support is most useful when it makes the next review faster and safer. A bank reconciliation evidence index does that by showing the population, source trail, difference, owner, age, and decision in one place. Keep preparation visible, keep protected judgment with the authorized finance lead, and let the evidence tell the story of the close.