Guide
How to reconcile a bank statement PDF
Reconciliation is not just extracting rows. A practical review compares extracted transactions to statement-level controls—balances and totals—when those cues are available and reliable on the PDF.
What bank statement reconciliation means
For most review teams, reconciliation means checking that the activity on a statement hangs together: the transactions you would export or re-key should line up with the statement's own summary controls—opening and closing balances, total credits, total debits, and other printed cues—when the document provides them.
If you stop at "we got rows into a spreadsheet," you may miss tension between printed totals and extracted activity. That gap is exactly what downstream reviewers, underwriters, and QC workflows care about.
Core control formula
A common starting check—when the statement prints the needed fields—is:
This relationship is only useful when both sides are readable from the PDF: the summary bands must be clear, and your extraction must faithfully capture credits, debits, and any printed adjustments (for example fees or section-specific subtotals on some layouts). If controls are missing, obscured, or ambiguous, treat validation as incomplete—not "pass by default."
Why PDF bank statements are difficult
PDFs are a presentation format, not a database dump. Even when tables look clean on screen, practical failures include:
- Poor scans, skew, or compression that breaks row boundaries
- Missing or reordered pages
- Bank-specific layouts, multi-column sections, or wrapped description lines
- Summary totals that do not map one-to-one to visible transaction buckets
- Fees, holds, and footnotes that change how totals should be read
- Rows that are plausible as text but ambiguous for automated grouping
Because of this variability, teams should expect some files to need human review—and should be skeptical of any process that treats every PDF as equally reliable.
Reviewer checklist
- Confirm the statement period and that pages appear complete.
- Identify opening and closing balances and the statement's printed total credits and debits when present.
- Compare extracted transaction rollups to those controls; investigate rounding, fees, and section-specific adjustments.
- Watch for review flags, missing sections, or low-confidence extraction notes — escalate before treating exports as final.
- Document what you relied on (printed cues vs. assumptions) so the next reviewer can follow your reasoning.
Treat CSV and Excel exports as review data
A structured export is a workflow accelerant: it makes comparison, filtering, and handoff easier. It is not automatically final truth without your firm's review standards, especially when reconciliation signals are mixed or negative.
Keep the distinction explicit in operating procedures: exports support decisions—they should not silently replace controls your team would have run on the source PDF.
How GrassLedger helps
For supported PDF bank statement layouts, GrassLedger combines extraction with verification-oriented outputs:
- Transaction and summary extraction when the parser can validate the layout
- CSV/Excel-style structured exports for review workflows
- Reconciliation status and review flags when statement controls support checks
- Human-readable HTML reporting and machine-readable JSON report outputs (product surfaces vary by workflow)
Coverage is intentionally not universal: not every bank and not every PDF is supported. Unsupported or low-confidence files should be identified so teams can route them to manual handling.
GrassLedger does not guarantee fraud detection, certify 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.
For current layout coverage, see Supported banks.
Frequently asked questions
- Is reconciling a bank statement just exporting transactions to Excel?
- No. Reconciliation checks whether extracted activity lines up with statement-level controls, such as balances and totals, when those controls exist. It is more than copying rows from a PDF.
- Does opening balance plus credits minus debits always equal closing balance?
- Often, when the statement presents those totals clearly, but fees, holds, missing pages, layout-specific sections, or ambiguous summary bands can affect what can be validated from the PDF alone.
- Can every bank PDF be reconciled the same way?
- No. What can be verified depends on bank layout, statement type, printed controls, and whether the file is a supported statement class. Unsupported or low-confidence files should be flagged for review.
- If totals match, does that prove the statement is authentic or fraud-free?
- No. Internal consistency checks support review workflows, but they do not certify authenticity, guarantee fraud detection, or replace professional judgment.
- Should I treat a CSV or Excel export as final for underwriting or legal use?
- Not without your own review. Treat exports as structured review inputs, especially when review flags or non-PASS reconciliation status appear. GrassLedger does not make lending decisions or legal conclusions.
Apply this checklist to a supported statement
Upload a supported PDF through intake, or walk a static sample to see transactions, reconciliation context, and review flags side by side.