Statement period vs calendar month: avoid gaps and overlaps

Read the printed period before using the filename

Chase’s statement guidance notes that the covered period can be a calendar month or another roughly monthly interval. A filename or download-menu label is therefore not enough to establish exact coverage.

Record the account and the printed first and last dates from every PDF. Preserve those dates when preparing a spreadsheet. Renaming a file January does not change the document’s actual coverage, and sorting files by download date does not put their transactions in chronological order.

Work through an off-calendar example

Suppose a fictional account issues one statement for January 18 through February 17 and the next for February 18 through March 17. Together they cover February 1 through February 28, but neither file alone covers that calendar month.

If the task is a February transaction analysis, you may need rows from both documents. Keep both complete originals, then create a clearly labeled working view using the relevant dates. If the task is to provide bank-issued statements to a recipient, ask which documents they require instead of editing a source PDF to make its period appear to match.

Make a coverage list before converting a batch

A small coverage list can reveal a missing period before you spend time reviewing extracted rows. Use one entry per source statement and keep accounts separate.

• Original filename and masked account identifier.
• Printed statement start date and end date.
• Printed opening and closing balances, where provided.
• PDF page count and whether the file appears complete.
• The part of the requested period this file covers.
• Any overlap or unresolved gap that needs clarification.

Distinguish overlapping documents from duplicate transactions

A monthly statement and a custom bank export can cover some of the same days. Overlapping dates tell you where to inspect; they do not prove that every transaction in the intersection is duplicated. One file may use posting dates while another exposes a different date field.

For a fictional September 1–30 statement and a September 15–October 15 export, review the September 15–30 overlap using source references and transaction details. Do not remove every same-day row or combine both totals without checking what each source includes.

Explain gaps instead of filling them with guesses

If the required range begins January 1 but your earliest statement begins January 18, record the uncovered January 1–17 interval. Look for the preceding statement or ask the issuer for the appropriate record. A balance from January 18 does not reconstruct the missing transactions.

A statement that is not yet available is a different problem from an incomplete set of existing files. Use the linked availability guide for that situation. Once the sources are complete, the batch conversion guide explains how to prepare the PDFs and review their output.

Keep the source boundary visible in the result

When reviewing combined rows, retain enough source information to trace a transaction back to its document and page. A final spreadsheet filtered to one month should not erase the wider statement periods from your review records.

Before handing it off, state whether the file contains full statement cycles or a selected calendar-month view. That description prevents another reviewer from interpreting a deliberately filtered result as a complete bank-issued statement.