Check a bank statement PDF for missing pages before conversion

A successful download is not a completeness check

Opening a PDF proves that the viewer can read the file; it does not prove that every statement page is present. A saved print range, partial scan or incomplete packet can still produce a valid PDF.

Bank statements typically identify an account, a covered period and its activity, although layouts vary. Start by confirming that the pages belong to the same account and period. A mixed packet can contain the expected number of pages while still omitting part of the statement you need.

Compare viewer pages with printed page labels

Consider a fictional PDF viewer showing two pages. The first printed page says 1 of 3 and the second says 3 of 3. That is a concrete reason to look for page 2 before conversion. Do not infer its rows from the opening and closing totals.

Viewer counts and printed numbering need not always match: a cover, notice or combined account packet may use a different numbering scheme. Read the document’s own labels and section boundaries. The goal is to explain the sequence, not to reject every file whose printed number differs from the viewer position.

Follow continuations through the transaction list

Inspect the last transaction area on one page and the first on the next. A heading marked continued, a partial description, or a carried-forward balance can point to a section that needs another page. Check whether the next page actually continues that section.

A gap between transaction dates is not, by itself, proof of missing pages; there may have been no completed transactions on those days. Similarly, a matching closing balance cannot establish completeness when other errors offset. Use several source cues together.

• Printed page numbering and account identifiers.
• Statement period and transaction-section headings.
• Descriptions or tables visibly cut off at a page boundary.
• Opening, carried-forward and closing values where present.
• Pages that are blank, cropped, duplicated or unreadable.

Resolve the source problem before extracting rows

Return to the issuer’s statement download and obtain the complete original PDF when possible. For a scan, check the source packet and rescan missing or cropped pages in order. If a page is unavailable, record that limitation and request it instead of creating substitute transactions.

A screenshot of an account balance or a later transaction list does not silently replace a missing statement page. It may be useful supporting information, but label its source and scope separately so a reviewer knows what the statement itself contains.

Repeat the coverage check after conversion

Once the source is complete, compare the extracted rows with every transaction-bearing page. Keep page references during review, confirm the first and last relevant rows, and inspect descriptions that cross page boundaries.

Fulla’s review flow uses source pages and row evidence to help with this comparison. It cannot recover transaction evidence that was never included in the uploaded file. The linked preparation guide covers scan quality and password handling; this checklist addresses whether the source packet is complete.