# Bank Statement Parsing

> Guidelines for parsing bank statements using YOLO layout detection + OCR + LLM.

- Skill: `johnsonhk88/bank-statement-parsing-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add johnsonhk88/bank-statement-parsing-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/johnsonhk88/bank-statement-parsing-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: johnsonhk88 (https://skillmd.com/u/johnsonhk88)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/johnsonhk88/bank-statement-parsing-2

---


# Bank Statement Parsing Skill

## Core Rules
- Always start by calling the `pdf_extract` 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.