A controlled routine for a corrected bank statement

A bank sometimes reissues a statement after the original close. A deposit may have been posted twice in the bank's system, a fee may have been reversed, or a check may have cleared in a different period than the first file showed. The client forwards the new PDF with a short note, and the bookkeeping team is expected to make the ledger agree again. Re-importing the file without a routine is how duplicate lines, stale reconciliations, and unexplained differences enter the close.

The right response is to treat the corrected statement as a replacement record with a controlled transition. The team needs to know what changed, which ledger entries already relied on the old version, and who approved the replacement. This article sets out a practical routine for a small team handling bank feeds, reconciliations, and month-end evidence for multiple clients. A short written routine keeps the correction visible from the first difference to the final sign-off.

Start by stopping the normal import process for that account. If the bank feed is still active, pause it or record the exact point at which the team stopped accepting new lines. The goal is to prevent a partial re-import from mixing old and new statement lines while nobody is watching the difference. Save the original statement file in a dated archive with a clear status label. Record the date received, the period covered, and the person who first reconciled it.

Do not rename the old file to match the new one, because two files with the same name make the history impossible to follow. Add a short line to the reconciliation workpaper stating that a corrected statement is expected. That note tells a later reviewer why the account is temporarily out of balance and prevents someone from "fixing" the difference with a plug entry. It also creates a timestamp for the start of the correction.

Put the old and new statements side by side, or export both to a spreadsheet with date, description, amount, and reference columns. Match lines in a stable order and mark the additions, removals, and amount changes. A visual scan is not enough, because a single changed digit can move a balance without changing the page count. For each difference, write a short explanation in plain language. "Bank reversed duplicate deposit on the twelfth" is useful.

"Statement changed" is not, because the next reviewer cannot tell whether the ledger or the bank record is wrong. Check the opening and closing balances separately from the transaction detail. A corrected closing balance with no matching detail change usually means the bank fixed a carry-forward error or supplied a missing page. That case needs its own note, not a transaction-level adjustment.

Before importing anything, list the ledger entries that came from the old statement. For each one, decide whether it stays, reverses, or changes amount. A line removed by the bank should normally be reversed in the ledger with the original date reference, not deleted without a trace. Use the team's existing correction method for bank errors and never edit a posted entry silently. If the accounting software allows a deletion, prefer a reversing entry with a note that points to the corrected statement.

Deletions hide the path from the original close to the replacement, and that path is the evidence a reviewer needs. Assign the decision to a named person. The bookkeeper can propose the treatment and prepare the entry, but the client's accounting owner should approve any change that affects a reported balance. Record the approval reference next to the correction, even when the amount looks small.

The replacement note belongs with the reconciliation, not in a chat thread. State the account, period, old and new statement dates, and the reason the bank gave. List the differences that affect the ledger and the differences that do not. Say explicitly which version is now authoritative. A reviewer who opens two statements with no status label will guess, and the guess may favor the file with the later download date.

Mark the old file as superseded in the note and in the archive folder name. Link the note to the affected journal entries, the reconciliation, and any downstream report that changed. If the correction moves a balance in the profit and loss, also link the variance note that explains the movement to the owner. The note should let someone reconstruct the sequence without interviewing the bookkeeper.

After the entries are posted, rerun the reconciliation from the corrected statement. Do not reuse the old reconciliation and change only the ending balance, because the outstanding item list may also have changed. Recalculate the cleared items, the deposits in transit, and the outstanding checks from the new detail, then compare the result with the outstanding items list. Update the evidence index with the new file version and a pointer to the superseded copy. If the index uses a single link per account, add a version column rather than replacing the original link in place.

Versioning makes a later audit or tax question much easier to answer. Compare the new reconciled balance with the general ledger and with the bank's closing balance. If the numbers do not agree, stop and return to the difference list. A reconciliation that balances by construction, without a clear mapping to the statement lines, is not evidence of anything.

A corrected statement can change cash, expenses, receivables, or a loan balance. Identify every report that used the old number and decide which ones need a refresh. Cash flow summaries, board packs, and tax workpapers may all depend on it. A corrected payable balance can also change the evidence in a vendor statement review. Tell the report owner what moved and why. Do not send a revised report without a short change note, because the reader will otherwise compare two versions and assume an error.

The note can be three lines: what changed, which period, and what action the reader should take. Check any automated alert or dashboard that reads the ledger. A corrected balance can trigger a false covenant warning or hide a real one. If the change is material to a lender or investor report, route it through the same approval path the original report used.

The routine ends with a review, not a successful import. The reviewer should confirm the old statement is archived, differences are explained, entries are posted with references, and the reconciliation matches the corrected file. Record the reviewer's name and the date. Keep the replacement note with the period's close evidence and mention it in the handoff summary. A future bookkeeper who sees a reversing entry should be able to find the reason in one step. The GAO's internal-control standards emphasize records a reviewer can reconstruct, which is the standard this routine is trying to meet.

That is the practical test of a controlled correction. Finally, review whether the bank or the feed caused the problem. If the same account produces corrected statements repeatedly, raise it with the client and adjust the reconciliation timing. A routine that only cleans up after each correction will keep repeating the same work. A routine that also tracks the cause reduces the next one.