invoice-organizer▌
composiohq/awesome-claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Automatically organize invoices and receipts into a tax-ready filing system with consistent naming and logical folder structure.
- ›Extracts key information from PDFs, images, and documents: vendor name, invoice number, date, amount, and description
- ›Renames files to a standardized format ( YYYY-MM-DD Vendor - Invoice - Description.ext ) for easy sorting and retrieval
- ›Organizes files by vendor, expense category, time period, or tax classification based on user preference
- ›Generates a C
Invoice Organizer
This skill transforms chaotic folders of invoices, receipts, and financial documents into a clean, tax-ready filing system without manual effort.
When to Use This Skill
- Preparing for tax season and need organized records
- Managing business expenses across multiple vendors
- Organizing receipts from a messy folder or email downloads
- Setting up automated invoice filing for ongoing bookkeeping
- Archiving financial records by year or category
- Reconciling expenses for reimbursement
- Preparing documentation for accountants
What This Skill Does
-
Reads Invoice Content: Extracts information from PDFs, images, and documents:
- Vendor/company name
- Invoice number
- Date
- Amount
- Product or service description
- Payment method
-
Renames Files Consistently: Creates standardized filenames:
- Format:
YYYY-MM-DD Vendor - Invoice - ProductOrService.pdf - Examples:
2024-03-15 Adobe - Invoice - Creative Cloud.pdf
- Format:
-
Organizes by Category: Sorts into logical folders:
- By vendor
- By expense category (software, office, travel, etc.)
- By time period (year, quarter, month)
- By tax category (deductible, personal, etc.)
-
Handles Multiple Formats: Works with:
- PDF invoices
- Scanned receipts (JPG, PNG)
- Email attachments
- Screenshots
- Bank statements
-
Maintains Originals: Preserves original files while organizing copies
How to Use
Basic Usage
Navigate to your messy invoice folder:
cd ~/Desktop/receipts-to-sort
Then ask Claude Code:
Organize these invoices for taxes
Or more specifically:
Read all invoices in this folder, rename them to
"YYYY-MM-DD Vendor - Invoice - Product.pdf" format,
and organize them by vendor
Advanced Organization
Organize these invoices:
1. Extract date, vendor, and description from each file
2. Rename to standard format
3. Sort into folders by expense category (Software, Office, Travel, etc.)
4. Create a CSV spreadsheet with all invoice details for my accountant
Instructions
When a user requests invoice organization:
-
Scan the Folder
Identify all invoice files:
# Find all invoice-related files find . -type f \( -name "*.pdf" -o -name "*.jpg" -o -name "*.png" \) -printReport findings:
- Total number of files
- File types
- Date range (if discernible from names)
- Current organization (or lack thereof)
-
Extract Information from Each File
For each invoice, extract:
From PDF invoices:
- Use text extraction to read invoice content
- Look for common patterns:
- "Invoice Date:", "Date:", "Issued:"
- "Invoice #:", "Invoice Number:"
- Company name (usually at top)
- "Amount Due:", "Total:", "Amount:"
- "Description:", "Service:", "Product:"
From image receipts:
- Read visible text from images
- Identify vendor name (often at top)
- Look for date (common formats)
- Find total amount
Fallback for unclear files:
- Use filename clues
- Check file creation/modification date
- Flag for manual review if critical info missing
-
Determine Organization Strategy
Ask user preference if not specified:
I found [X] invoices from [date range]. How would you like them organized? 1. **By Vendor** (Adobe/, Amazon/, Stripe/, etc.) 2. **By Category** (Software/, Office Supplies/, Travel/, etc.) 3. **By Date** (2024/Q1/, 2024/Q2/, etc.) 4. **By Tax Category** (Deductible/, Personal/, etc.) 5. **Custom** (describe your structure) Or I can use a default structure: Year/Category/Vendor -
Create Standardized Filename
For each invoice, create a filename following this pattern:
YYYY-MM-DD Vendor - Invoice - Description.extExamples:
2024-03-15 Adobe - Invoice - Creative Cloud.pdf2024-01-10 Amazon - Receipt - Office Supplies.pdf2023-12-01 Stripe - Invoice - Monthly Payment Processing.pdf
Filename Best Practices:
- Remove special characters except hyphens
- Capitalize vendor names properly
- Keep descriptions concise but meaningful
- Use consistent date format (YYYY-MM-DD) for sorting
- Preserve original file extension
-
Execute Organization
Before moving files, show the plan:
# Organization Plan ## Proposed StructureInvoices/ ├── 2023/ │ ├── Software/ │ │ ├── Adobe/ │ │ └── Microsoft/ │ ├── Services/ │ └── Office/ └── 2024/ ├── Software/ ├── Services/ └── Office/
## Sample Changes Before: `invoice_adobe_march.pdf` After: `2024-03-15 Adobe - Invoice - Creative Cloud.pdf` Location: `Invoices/2024/Software/Adobe/` Before: `IMG_2847.jpg` After: `2024-02-10 Staples - Receipt - Office Supplies.jpg` Location: `Invoices/2024/Office/Staples/` Process [X] files? (yes/no)After approval:
# Create folder structure mkdir -p "Invoices/2024/Software/Adobe" # Copy (don't move) to preserve originals cp "original.pdf" "Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf" # Or move if user prefers mv "original.pdf" "new/path/standardized-name.pdf" -
Generate Summary Report
Create a CSV file with all invoice details:
Date,Vendor,Invoice Number,Description,Amount,Category,File Path 2024-03-15,Adobe,INV-12345,Creative Cloud,52.99,Software,Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf 2024-03-10,Amazon,123-4567890-1234567,Office Supplies,127.45,Office,Invoices/2024/Office/Amazon/2024-03-10 Amazon - Receipt - Office Supplies.pdf ...This CSV is useful for:
- Importing into accounting software
- Sharing with accountants
- Expense tracking and reporting
- Tax preparation
-
Provide Completion Summary
# Organization Complete! 📊 ## Summary - **Processed**: [X] invoices - **Date range**: [earliest] to [latest] - **Total amount**: $[sum] (if amounts extracted) - **Vendors**: [Y] unique vendors ## New StructureInvoices/ ├── 2024/ (45 files) │ ├── Software/ (23 files) │ ├── Services/ (12 files) │ └── Office/ (10 files) └── 2023/ (12 files)
## Files Created - `/Invoices/` - Organized invoices - `/Invoices/invoice-summary.csv` - Spreadsheet for accounting - `/Invoices/originals/` - Original files (if copied) ## Files Needing Review [List any files where information couldn't be extracted completely] ## Next Steps 1. Review the `invoice-summary.csv` file 2. Check files in "Needs Review" folder 3. Import CSV into your accounting software 4. Set up auto-organization for future invoices Ready for tax season! 🎉
Examples
Example 1: Tax Preparation (From Martin Merschroth)
User: "I have a messy folder of invoices for taxes. Sort them and rename properly."
Process:
- Scans folder: finds 147 PDFs and images
- Reads each invoice to extract:
- Date
- Vendor name
- Invoice number
- Product/service description
- Renames all files:
YYYY-MM-DD Vendor - Invoice - Product.pdf - Organizes into:
2024/Software/,2024/Travel/, etc. - Creates
invoice-summary.csvfor accountant - Result: Tax-ready organized invoices in minutes
Example 2: Monthly Expense Reconciliation
User: "Organize my business receipts from last month by category."
Output:
# March 2024 Receipts Organized
## By Category
- Software & Tools: $847.32 (12 invoices)
- Office Supplies: $234.18 (8 receipts)
- Travel & Meals: $1,456.90 (15 receipts)
- Professional Services: $2,500.00 (3 invoices)
Total: $5,038.40
All receipts renamed and filed in:
`Business-Receipts/2024/03-March/[Category]/`
CSV export: `march-2024-expenses.csv`
Example 3: Multi-Year Archive
User: "I have 3 years of random invoices. Organize them by year, then by vendor."
Output: Creates structure:
Invoices/
├── 2022/
│ ├── Adobe/
│ ├── Amazon/
│ └── ...
├── 2023/
│ ├── Adobe/
│ ├── Amazon/
│ └── ...
└── 2024/
├── Adobe/
├── Amazon/
└── ...
Each file properly renamed with date and description.
Example 4: Email Downloads Cleanup
User: "I download invoices from Gmail. They're all named 'invoice.pdf', 'invoice(1).pdf', etc. Fix this mess."
Output:
Found 89 files all named "invoice*.pdf"
Reading each file to extract real information...
Renamed examples:
- invoice.pdf → 2024-03-15 Shopify - Invoice - Monthly Subscription.pdf
- invoice(1).pdf → 2024-03-14 Google - Invoice - Workspace.pdf
- invoice(2).pdf → 2024-03-10 Netlify - Invoice - Pro Plan.pdf
All files renamed and organized by vendor.
Common Organization Patterns
By Vendor (Simple)
Invoices/
├── Adobe/
├── Amazon/
├── Google/
└── Microsoft/
By Year and Category (Tax-Friendly)
Invoices/
├── 2023/
│ ├── Software/
│ ├── Hardware/
│ ├── Services/
│ └── Travel/
└── 2024/
└── ...
By Quarter (Detailed Tracking)
Invoices/
├── 2024/
│ ├── Q1/
│ │ ├── Software/
│ │ ├── Office/
│ │ └── Travel/
│ └── Q2/
│ └── ...
By Tax Category (Accountant-Ready)
Invoices/
├── Deductible/
│ ├── Software/
│ ├── Office/
│ └── Professional-Services/
├── Partially-Deductible/
│ └── Meals-Travel/
└── Personal/
Automation Setup
For ongoing organization:
Create a script that watches my ~/Downloads/invoices folder
and auto-organizes any new invoice files using our standard
naming and folder structure.
This creates a persistent solution that organizes invoices as they arrive.
Pro Tips
- Scan emails to PDF: Use Preview or similar to save email invoices as PDFs first
- Consistent downloads: Save all invoices to one folder for batch processing
- Monthly routine: Organize invoices monthly, not annually
- Backup originals: Keep original files before reorganizing
- Include amounts in CSV: Useful for budget tracking
- Tag by deductibility: Note which expenses are tax-deductible
- Keep receipts 7 years: Standard audit period
Handling Special Cases
Missing Information
If date/vendor can't be extracted:
- Flag file for manual review
- Use file modification date as fallback
- Create "Needs-Review/" folder
Duplicate Invoices
If same invoice appears multiple times:
- Compare file hashes
- Keep highest quality version
- Note duplicates in summary
Multi-Page Invoices
For invoices split across files:
- Merge PDFs if needed
- Use consistent naming for parts
- Note in CSV if invoice is split
Non-Standard Formats
For unusual receipt formats:
- Extract what's possible
- Standardize what you can
- Flag for review if critical info missing
Related Use Cases
- Creating expense reports for reimbursement
- Organizing bank statements
- Managing vendor contracts
- Archiving old financial records
- Preparing for audits
- Tracking subscription costs over time
How to use invoice-organizer on Cursor
AI-first code editor with Composer
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 invoice-organizer
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches invoice-organizer from GitHub repository composiohq/awesome-claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate invoice-organizer. Access the skill through slash commands (e.g., /invoice-organizer) 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
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★32 reviews- ★★★★★Anika Patel· Dec 16, 2024
Useful defaults in invoice-organizer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Dec 8, 2024
invoice-organizer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sakshi Patil· Nov 27, 2024
Registry listing for invoice-organizer matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Fatima Sethi· Nov 7, 2024
invoice-organizer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Fatima Sharma· Oct 26, 2024
Keeps context tight: invoice-organizer is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Oct 18, 2024
invoice-organizer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ama Torres· Sep 17, 2024
We added invoice-organizer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Liam Gupta· Sep 9, 2024
invoice-organizer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Alexander Thomas· Aug 28, 2024
We added invoice-organizer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hiroshi Lopez· Aug 8, 2024
invoice-organizer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 32