bank-statement-parser

Bank statement parsing extracts transactions from PDFs using document parsing tools, then applies deduplication logic to identify and remove duplicate checks listed across multiple sections. This Skill uses Docling for PDF extraction and implements intelligent deduplication to ensure each transaction appears once in your database.

Yes. Smart validation checks whether deposit and withdrawal totals match the bank's summary and ending balance, detecting anomalies and statement errors. The Skill stops import on validation failures, ensuring data integrity before transactions load into your database.

After parsing and validation, the Skill migrates deduplicated transactions directly into MySQL, preventing duplicate entries through database safeguards. This prepares data for expense tracking and UI display in nonprofit finance workflows.

Deduplication logic identifies checks listed across multiple sections of a bank statement and consolidates them into single entries. The Skill applies this before database import, so your records reflect actual transactions without redundancy.

Yes. The Skill requires Docling for PDF parsing, SQLAlchemy for database operations, and Pandas for transaction handling. These dependencies enable end-to-end PDF extraction, validation, and database migration.

Strict error handling stops the import process entirely when ending balance mismatches or other validation failures occur. This prevents corrupted or incomplete data from entering your database, ensuring accuracy in financial records.