financial-document-parser

onewave-ai/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/onewave-ai/claude-skills --skill financial-document-parser
0 commentsdiscussion
summary

Extract structured data from financial documents with automatic categorization and analysis.

skill.md

Financial Document Parser

Extract structured data from financial documents with automatic categorization and analysis.

When to Use This Skill

Activate when the user:

  • Provides invoices, receipts, or bank statements
  • Asks to "parse this invoice" or "extract data from this receipt"
  • Needs expense categorization
  • Wants to track spending patterns
  • Asks to generate expense reports
  • Mentions financial document analysis
  • Provides PDF or image of financial documents

Instructions

  1. Identify Document Type

    • Invoice (business to business)
    • Receipt (point of sale)
    • Bank statement
    • Credit card statement
    • Expense report
    • Tax document
  2. Extract Core Information

    For Invoices:

    • Invoice number
    • Invoice date and due date
    • Vendor/supplier name and contact
    • Client/recipient name
    • Line items (description, quantity, unit price, total)
    • Subtotal, tax, and grand total
    • Payment terms
    • Payment methods accepted

    For Receipts:

    • Merchant name and location
    • Date and time
    • Items purchased
    • Individual prices
    • Subtotal, tax, total
    • Payment method
    • Last 4 digits of card (if present)

    For Bank/Credit Card Statements:

    • Statement period
    • Account number (last 4 digits)
    • All transactions (date, description, amount, balance)
    • Beginning and ending balance
    • Total credits and debits
    • Fees or interest charges
  3. Categorize Expenses

    • Business expenses: Office supplies, software, equipment
    • Travel: Transportation, lodging, meals
    • Utilities: Internet, phone, electricity
    • Professional services: Legal, accounting, consulting
    • Marketing: Advertising, subscriptions
    • Entertainment: Client meals, events
    • Other: Miscellaneous
  4. Identify Patterns

    • Recurring charges (subscriptions)
    • Duplicate charges
    • Unusual or high-value transactions
    • Tax-deductible expenses
    • Foreign currency transactions
  5. Generate Structured Output

    • Create CSV-ready format
    • Summarize totals by category
    • Flag items needing attention
    • Calculate tax implications (if relevant)

Output Format

# Financial Document Analysis

## Document Details
- **Type**: Invoice / Receipt / Statement
- **Date**: [Date]
- **Vendor/Merchant**: [Name]
- **Document Number**: [Number]
- **Total Amount**: $X,XXX.XX

## Line Items
| Description | Quantity | Unit Price | Total |
|-------------|----------|------------|-------|
| [Item] | X | $XX.XX | $XX.XX |

## Financial Summary
- **Subtotal**: $X,XXX.XX
- **Tax**: $XXX.XX
- **Total**: $X,XXX.XX
- **Payment Method**: [Method]

## Expense Categorization
| Category | Amount | Items |
|----------|--------|-------|
| Software | $XXX | Slack, GitHub |
| Office | $XX | Supplies |

## Insights
- ✓ Tax-deductible business expenses: $X,XXX
- ⚠ Recurring charges detected: 3 subscriptions ($XXX/month)
- ℹ Foreign transaction fees: $XX

## Flagged Items
- [ ] Large expense ($X,XXX) - verify approval
- [ ] Duplicate charge detected on [date]

## Export Data (CSV Format)
```csv
Date,Vendor,Description,Category,Amount,Tax Deductible
2025-01-15,Adobe,Creative Cloud,Software,52.99,Yes

Recommendations

  • Track recurring $XXX/month for [subscription]
  • Consider negotiating bulk discount with [vendor]
  • Set up payment reminder for [invoice due date]

## Examples

**User**: "Extract data from this invoice PDF"
**Response**: Parse PDF → Extract vendor info, line items, totals → Categorize as business expense → Format as structured data → Generate CSV export

**User**: "Analyze my bank statement and categorize expenses"
**Response**: Extract all transactions → Categorize each (dining, software, travel) → Identify recurring charges → Calculate totals by category → Flag unusual transactions → Generate spending report

**User**: "Parse these 10 receipts and create an expense report"
**Response**: Process each receipt → Extract merchant, date, amount, items → Categorize expenses → Calculate totals → Generate consolidated report → Create CSV for expense submission

## Best Practices

- Preserve exact amounts (don't round)
- Maintain currency symbols and formats
- Note when data is unclear or illegible
- Flag suspicious or duplicate transactions
- Provide tax-relevant categorization
- Use standard expense categories
- Generate export-ready formats (CSV, JSON)
- Protect sensitive info (mask account numbers)
- Identify missing information (no date, unclear vendor)
- Calculate totals and verify against document
- Note discrepancies or calculation errors
- Include exchange rates for foreign currency
how to use financial-document-parser

How to use financial-document-parser on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add financial-document-parser
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/onewave-ai/claude-skills --skill financial-document-parser

The skills CLI fetches financial-document-parser from GitHub repository onewave-ai/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/financial-document-parser

Reload or restart Cursor to activate financial-document-parser. Access the skill through slash commands (e.g., /financial-document-parser) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.541 reviews
  • Ira Li· Dec 20, 2024

    financial-document-parser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Maya Sharma· Dec 12, 2024

    financial-document-parser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Shikha Mishra· Dec 8, 2024

    We added financial-document-parser from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ira Ramirez· Dec 4, 2024

    financial-document-parser reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Yash Thakker· Nov 27, 2024

    financial-document-parser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Carlos Patel· Nov 23, 2024

    financial-document-parser has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ishan Garcia· Nov 11, 2024

    Solid pick for teams standardizing on skills: financial-document-parser is focused, and the summary matches what you get after install.

  • Ira Robinson· Nov 7, 2024

    Keeps context tight: financial-document-parser is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Alexander Chawla· Nov 3, 2024

    We added financial-document-parser from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ishan Chawla· Oct 26, 2024

    Registry listing for financial-document-parser matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 41

1 / 5