Productivity
Bank Statement to Excel
SKILLOpen-source projectAn accounting workflow skill that extracts PDF statement transactions into Excel and checks completeness against statement balance controls.
Key Features
- Extract transaction dates, descriptions, debits, credits, and balances from bank and related financial statements into a workbook.
- Tie extracted transactions to the statement's opening and closing balances and stop for exceptions when the figures do not reconcile.
- Record source pages for extracted rows and use local OCR for supported scanned statements when configured.
Target Demographics
Accounting teams, bookkeepers, and finance operators who need to turn PDF bank or card statements into traceable transaction workpapers before reconciliation or analysis.
Our Take
The skill's value is its completeness gate: extraction is supposed to tie to the statement's own control balances, with ambiguous rows surfaced instead of guessed. It is a workpaper aid for trained reviewers, not evidence that OCR is infallible or that a converted workbook is ready for filing or audit without inspection.
Pros
- Defines an explicit statement-level check instead of treating a mostly complete transaction table as finished.
- Captures transaction source pages and directs uncertain values to an exception path rather than back-solving or inventing them.
Cons
- Requires Python and workbook/PDF libraries; scanned-statement OCR adds separate local software setup.
- Financial data remains sensitive even when processing is local, and a human must resolve extraction exceptions and verify the resulting workpaper.
Pricing
The CPA skills repository is MIT-licensed and lists no paid fee for the skill. Its documented workflow requires Python 3.9+, openpyxl, and pdfplumber; OCR for scanned statements is optional and has separate local dependencies. Agent/model usage is separate.