OpenParable
Skip to content
← Back to skills

Bank Statement Parsing

Documents
bank-statement-parsing

Bank Statement Parsing is an Agent Skill for documents published in the johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Prediction repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Prediction/blob/HEAD/backend/app/skills/bank-statement-parsing/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/bank-statement-parsing, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.