Guide
Bank statement review checklist
Before relying on a bank statement PDF or a CSV/Excel export, run quality control on the source file, the extracted rows, and reconciliation signals. This checklist helps accountants, lenders, underwriters, and operations teams catch gaps early.
What a bank statement review checklist covers
A bank statement review checklist is structured QC: it ties together the source PDF, extracted data, and reconciliation signals (when statement-level controls exist). The goal is not decorative diligence—it is to know whether balances, credits, debits, fees, and activity lines can be trusted for your workflow before downstream teams build on them.
Reviewers should explicitly consider identity and context, the statement period, page completeness, printed balances and credit/debit totals, fees and special sections, transaction extraction quality, product review flags, and reconciliation status when available.
CSV and Excel exports are structured review inputs, not final truth without your own standards—especially when controls are missing, ambiguous, or flagged.
Before conversion — PDF/source checks
Start from the file your organization will defend: the PDF (or equivalent source). Weak or mislabeled sources propagate through every later step. Before any spreadsheet workflow, confirm the file is readable, complete for the intended period, and plausibly the correct statement.
Generic PDF-to-Excel passes often fail in ways that look fine on screen—see Why bank statement PDF to Excel conversions fail for common failure modes. Reconciliation concepts are covered in How to reconcile a bank statement PDF and Bank statement reconciliation.
Practical checklist
Use the sections below as a working guide; adapt ordering to your policy and statement type.
A. Source PDF checks
- Readability: text selectable where expected; password protection resolved through proper channels
- Native PDF vs. scan: expect more review burden on image-only or low-quality scans
- Crops, redactions, or partial exports that could hide transaction rows or summary bands
- Wrong-month or wrong-account file risk: cross-check filenames, cover lines, and intended period
B. Statement identity and period
- Account holder and institution context as printed
- Account identifiers (masked or full) consistent with your intake records
- Statement start and end dates; currency; business vs. personal product cues if your policy requires them
- Product type cues (checking, savings, card, etc.) when they affect how you read fees and totals
C. Page completeness
- Continuous page numbering where the issuer prints it; flag unexplained gaps
- No duplicated or obviously reordered pages
- Tables marked "continued" are followed on the next page; headers repeat as expected
D. Summary totals and balances
- Opening balance and closing balance when printed
- Total credits and total debits (or equivalent statement rollups) when the document provides them
- Subtotals or section summaries; note anything that should roll into statement-level controls
E. Transaction extraction quality
- Row counts plausible for the period and account activity
- Dates within the statement window; watch boundary-day edge cases
- Amount signs and debit/credit column semantics match the PDF
- Split or merged description lines; duplicated rows; obvious OCR substitutions
- Spot-check high-value lines against the PDF before approving the export
F. Fees, adjustments, and special sections
- Service fees, returned items, interest, and rewards adjustments when applicable
- Holds, pending items, or informational bands that may not be standard transaction rows
- Summary sections or footnotes that change how totals should be read
G. Reconciliation result
- When printed controls exist, compare exported rollups to statement totals and balances; document what you relied on
- If checks are inconclusive—missing controls, ambiguous bands, or partial extraction—say so explicitly
- Do not treat "no obvious error" as equivalent to a completed reconciliation pass
H. Manual review and escalation
- Stop rules: review flags, non-PASS reconciliation signals, missing summary fields, or parser uncertainty
- Poor scan quality or heavy OCR noise—route to re-scan, alternate source, or senior review
- Resourcing: who may approve exports for the next stage; when re-keying or alternate evidence is required
After conversion — CSV/Excel checks
After conversion, prioritize row fidelity: do the exported columns mean what the PDF says (credits vs. debits, signs, dates), and did multi-line descriptions, cross-page rows, or fee lines survive the extract? This layer catches mistakes that a polished spreadsheet layout can hide.
Treat the file as a structured review input until your checklist—including reconciliation against printed controls when available—is complete. For intake on supported layouts, use Try bank statement converter.
Reconciliation checks
Reconciliation goes beyond row-by-row tidiness: when the statement prints balances and rollups, you compare summarized activity to those controls. That is often where missing fees, wrong signs, or skipped pages show up—as tension between the grid and the statement's own totals.
Follow the reconciliation guide for control-first thinking, and the reconciliation product overview for how GrassLedger surfaces verification-oriented outputs on supported PDFs.
Review flags and escalation
Review flags and non-PASS reconciliation signals are not annoyances—they are routing data. When automation is uncertain or statement controls cannot be closed, downstream teams should not inherit silent risk. Escalate per your policy, capture what was unknown, and avoid declaring exports "final" without sign-off.
Internal consistency supports review; it does not certify authenticity, guarantee fraud detection, or replace professional judgment.
How GrassLedger helps
For supported PDF bank statement layouts, GrassLedger combines extraction with verification-oriented outputs for review teams:
- Layout-aware parsing when the statement class is recognized
- Transaction extraction with CSV/Excel-style structured exports for handoff
- Reconciliation status and review flags when statement controls support checks
- Human-readable HTML reporting and machine-readable JSON report outputs where product surfaces provide them
Coverage is intentionally limited: not every bank and not every PDF is supported. Unsupported or ambiguous files should be identified early for manual handling.
GrassLedger does not guarantee fraud detection, certify document authenticity, make lending decisions, provide legal conclusions, or claim SOC 2, GLBA, HIPAA, or other compliance certifications. Customers remain responsible for their own policies and professional judgment.
Current layout coverage: Supported banks. To run a file through intake: Try bank statement converter. For common spreadsheet pitfalls: PDF-to-Excel problems guide.
Frequently asked questions
- Is a bank statement review checklist only for accountants?
- No. Any team that relies on balances and transaction activity, including lending operations, underwriters, auditors, and financial review teams, benefits from systematic checks. Roles differ in sign-off, but the source and export quality checks are similar.
- Should I review the PDF if the CSV or Excel export looks fine?
- Yes, when your workflow depends on accuracy. The PDF is the evidence anchor for statement period, page completeness, printed totals, and sections that may not land cleanly in the export.
- What is the difference between post-conversion checks and reconciliation?
- Post-conversion checks focus on row fidelity, such as columns, signs, split descriptions, and missing rows. Reconciliation compares rolled-up activity to statement-level balances and totals when those controls are available.
- If reconciliation passes, is the statement authentic or ready for a lending decision?
- No. Internal consistency supports review, but it does not certify authenticity, guarantee fraud detection, or replace underwriting, legal, or professional judgment. GrassLedger does not make lending decisions or legal conclusions.
- Can GrassLedger replace manual review?
- No. For supported PDFs, GrassLedger can speed extraction and surface reconciliation status and review flags. Not every bank or PDF is supported, and non-PASS or ambiguous outcomes should be escalated according to your policy.
Apply this checklist to a supported statement
Upload a supported PDF through intake, or review a sample report to see transactions, reconciliation context, and flags together.