BankStatementDesk

Check bank statement periods, opening balances and closing balances

Two files named January and February can cover overlapping dates. A statement released in February may describe activity that closed in January. A report downloaded on the last day of a month may stop before the final posting batch. Before combining transaction worksheets, establish exactly what each source covers. A small coverage sheet connects each statement to an account, a printed period, a pair of balances and the next file in the sequence.

In this guide
  1. Read printed identifiers before filenames
  2. Build a coverage sheet with one row per scope
  3. Follow a three-statement chain
  4. Interpret unusual date boundaries
  5. Extract opening and closing balances correctly
  6. Work with revised or incomplete documents
  7. Turn the checks into a handoff

Read printed identifiers before filenames

Open each PDF and locate the section naming the period. Copy dates as printed, retaining year and date order. Record any issue date or download date in separately named columns. A file created on March 4 can cover February 1 through February 28. Naming a folder by issue month is fine for storage, but using it as the activity period would move a full cycle into the wrong reporting bucket.

Choose the account and balance type

Identify the account alias and currency for the balance being collected. Some institutions put several accounts on one consolidated statement and repeat a total across the cover. Use individual account opening and closing amounts for account-level checks. A combined total is a separate control. Distinguish posted balances from available balances and use the same printed basis across the boundary. Mask unnecessary identifiers while retaining enough information to tell accounts with similar names apart.

Build a coverage sheet with one row per scope

Create one row per account, currency and statement interval. Store filename, printed start, printed end, opening balance, closing balance, completeness and notes. If the first page is missing, write opening unknown rather than assuming zero or borrowing another account's balance. Keep a reference to the page where each number appears. Fifteen clear coverage rows can uncover mistakes difficult to see among thousands of correctly extracted transactions.

Separate coverage from movement

Coverage asks whether the document sequence spans the intended dates. Movement asks whether included postings explain balance changes within each document. Both matter. An account can show the same closing balance for two months despite a missing statement with offsetting transactions. Conversely, adjacent complete statements can disagree because someone transcribed the wrong summary balance. Put date continuity and balance continuity in separate columns. Avoid collapsing these observations into one broad pass or fail field.

Follow a three-statement chain

Consider an account with a January 1 to January 31 statement opening at 600.00 and closing at 735.00. February 1 to February 28 opens at 735.00 and closes at 690.00. March 1 to March 31 opens at 690.00 and closes at 810.00. January activity contributes plus 135.00, February minus 45.00 and March plus 120.00. Across three months the net movement is 210.00. Check months separately before accepting the quarter's total.

Diagnose a missing February

Imagine the folder contains January and March only. January closes at 735.00 while the next available opening is 690.00. The 45.00 difference is change during an uncovered interval. It does not establish that one transaction of 45.00 is missing. February might contain 1,100.00 in receipts and 1,145.00 in withdrawals. Request the intervening statement or document the coverage gap. A synthetic adjustment could force totals to match while erasing a large volume of genuine activity.

Diagnose a zero-movement gap

Now imagine February had net movement of zero. January and March boundary balances agree even with February absent. The date check continues to flag missing coverage. If the institution issued no separate statement during inactivity, record the evidence for that arrangement where available and identify the supported span. With no evidence, describe what remains unknown. “February not supplied” conveys more useful information than an unsupported declaration that nothing happened.

Interpret unusual date boundaries

Statements can run on business-day cycles instead of calendar months. A period from April 19 through May 18 is entirely suitable as one source interval. Keep those dates in the reconciliation view. If the user needs May-only activity, build a calendar report from individual postings after reconciliation. A calendar report can draw on two adjacent statements. A statement report should match the institution's printed selection and may include postings from two calendar months.

Same-day boundaries need transaction-level evidence

Custom downloads may use inclusive date filters. One report for May 1 through May 15 and another for May 15 through May 31 can both include May 15. Compare account, posting reference, amount and source position for that day. Identical dates alone cannot establish duplication. Several distinct transactions can share a posting date. Mark overlapping coverage and select one source for confirmed duplicates. Keep uncertain matches for review, especially where descriptions change between preliminary and final documents.

Extract opening and closing balances correctly

An opening figure may appear in a summary box, a first row labeled Balance brought forward or both. Its purpose is to establish a starting position. Avoid counting it as a deposit simply because a PDF parser placed it in a numeric column. A closing balance is also a checkpoint. A subtotal called Total credits measures movement, whereas a closing balance measures position. Retain the printed label with each number in the controls sheet.

Use the balance equation for one interval

For a deposit account using signed increases and decreases, calculated closing equals opening plus the posted changes during the interval. Opening at 735.00 with 420.00 in additions and 465.00 in withdrawals produces a closing balance of 690.00. Enter controls independently from the statement and transaction detail when possible. A closing figure copied from the worksheet's own formula cannot validate its input. If differences persist, consult the statement balance troubleshooting guide.

Keep currencies apart

A statement may present a dollar account beside a euro account and include a translated household total. Separate original currency sections first. A dollar closing cannot serve as a euro opening, even when the numeric amounts agree. Translated summaries may fluctuate with rates or presentation conventions. Apply their documented basis if you need a reporting-currency view. Preserve native statement checks so an exchange conversion cannot conceal a missing row.

Work with revised or incomplete documents

A corrected statement can carry the exact dates of an earlier file. Compare identifiers, issue dates and revision labels. Store both when allowed, clearly marking which supports the current worksheet. Replacing a file upstream without updating references leaves reviewers unable to reproduce earlier totals. If a revision changes the closing balance, revisit the next interval's opening and document what the new evidence explains. Avoid silently editing a historical control purely to clear an exception.

Accounts opening or closing mid-cycle

The first available statement may start after an account opened, and the last available may precede closure. Look for evidence that it is actually the first or final statement. A new account can start with a transfer in while an existing account can have a zero opening. Those are separate observations. A zero balance after a transfer out also does not establish closure. Name the supported interval without implying complete account history unless evidence establishes it.

Record a partial upload

Someone provides pages two and three of a four-page statement. These may contain complete-looking activity for much of the period, yet they cannot establish opening or closing controls independently. Enter the known period if printed, identify pages received and mark status partial. The rows can support a limited query as long as their restricted scope is visible wherever they appear.

When the complete copy arrives, compare the overlapping pages before switching references. Confirm account, dates and posting sequence. If the complete statement differs, treat it as a different version and explain the change. This prevents an earlier partial extraction being appended to a complete extraction and counting middle pages twice. If the institution uses page numbering across several accounts, describe missing pages by section as well as by number.

Turn the checks into a handoff

Sort by account alias, currency and printed start. Compare the prior end and prior closing within that group. Keep visible exceptions for a missing date interval, unexplained overlap, inconsistent balance basis or absent page. Attach a next action such as requesting the April statement or checking whether files are revisions. The recipient should distinguish missing documentation from a simple extraction error during a covered interval.

Reconcile in the right order

Once coverage is established, use the bank statement converter for eligible digital files. Resolve each period before appending transactions. Compare the sum of period movements with the change from first opening to last closing. The GnuCash manual on reconciling statements illustrates the relationship between cutoff and balance. Preserve the coverage sheet alongside the export so the next import begins at the right boundary.

When several people maintain the workbook, keep one coverage row marked as the latest independently checked boundary per account. The next person can start by finding the first statement after that date. If a file arrives for an earlier interval, they will know to investigate a correction or late submission before appending its transactions. This small distinction prevents a routine monthly refresh from modifying previously checked balances without explanation.

A useful final exception report lists account, cutoff date, coverage days missing and first available page after the gap. For example, if the next document begins on March 3 instead of March 1, February's closing amount might still match its opening. The absent March dates remain unknown. If a user needs only March 15 activity, the gap may have little effect on that particular query. If they need a quarterly receipts total, the same gap prevents a complete answer. State the consequence for the intended report. Once missing pages arrive, mark the exception resolved only after a fresh date check and a separate balance check. Keep the original gap note with its resolution date so previously issued incomplete reports can be identified quickly.