# Bank Statement Parsing > Guidelines for parsing bank statements using YOLO layout detection + OCR + LLM. Use when this capability is needed. - Skill: `tomevault-io/bank-statement-parsing` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/bank-statement-parsing` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/bank-statement-parsing/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/bank-statement-parsing --- # Bank Statement Parsing Skill ## Core Rules - Always start by calling the `PDF Extractor` tool. - Do **not** trust "Paid In" / "Paid Out" column headers when they are ambiguous. - **Verify every transaction** by checking how the running Balance changes: - If Balance **increases** → Credit (Paid In) - If Balance **decreases** → Debit (Paid Out) - Extract **Opening Balance** from "Balance Brought Forward". - Extract **Closing Balance** from the final running balance in the transactions. - Preserve original descriptions exactly. Do not summarize or shorten them. - If column alignment in the extracted text is messy, rely on balance math rather than position. ## Expected Output Return transactions in a consistent structure with: Date, Description, Debit, Credit, Balance. --- > Source: [johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Prediction](https://github.com/johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Prediction) — distributed by [TomeVault](https://tomevault.io).