Invoice & Receipt Organizer

/invoice-organizer

Transform chaotic collections of invoices, receipts, and financial documents into a clean, tax-ready filing system. The user uploads or pastes the documents; you extract the key information, propose standardized names and a folder structure, and produce a summary spreadsheet.

When to Use This Skill

• Preparing for tax season and needing organized records
• Managing business expenses across multiple vendors
• Organizing receipts from messy downloads or email attachments
• Archiving financial records by year or category
• Reconciling expenses for reimbursement
• Preparing documentation for accountants

What This Skill Does

1. Reads invoice content: extracts from uploaded PDFs, images, and pasted text:
   • Vendor/company name
   • Invoice number
   • Date
   • Amount
   • Product or service description
   • Payment method
2. Proposes consistent filenames: YYYY-MM-DD Vendor - Invoice - ProductOrService.pdf
   • Example: 2024-03-15 Adobe - Invoice - Creative Cloud.pdf
3. Organizes by category: by vendor, expense category (software, office, travel), time period, or tax category (deductible, personal)
4. Handles multiple formats: PDF invoices, scanned receipts (JPG, PNG), email attachments, screenshots, bank statements
5. Preserves originals: the plan always keeps original files; renames and moves are user-applied copies

Workflow

When a user requests invoice organization:

1. Intake the documents

   • Ask the user to upload the invoice files (PDFs, images) or paste their contents. If they only have a file listing, ask them to paste it.
   • Report findings: total number of documents, formats, date range, current organization (or lack thereof).

2. Extract information from each document

   • From PDF invoices, look for common patterns: "Invoice Date:", "Date:", "Issued:", "Invoice #:", company name (usually at top), "Amount Due:", "Total:", "Description:", "Service:".
   • From image receipts: read the visible text; vendor name is often at the top; find date and total amount.
   • Fallback for unclear documents: use filename clues or ask the user; flag for manual review if critical info is missing.

3. 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
   

4. Create standardized filenames

   Pattern: YYYY-MM-DD Vendor - Invoice - Description.ext

   Examples:

   • 2024-03-15 Adobe - Invoice - Creative Cloud.pdf
   • 2024-01-10 Amazon - Receipt - Office Supplies.pdf
   • 2023-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 YYYY-MM-DD date format for sorting
   • Preserve the original file extension

5. Present the organization plan as a chat artifact

   Show the full plan before the user applies it:

   # Organization Plan
   
   ## Proposed Structure
   Invoices/
     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/
   

   Deliver the complete rename map (old name -> new name -> destination folder) so the user can apply it. If they want automation, provide a small script (bash or Python) as a chat artifact that performs the copies/renames on their machine, defaulting to copy (not move) to preserve originals.

6. Generate a summary spreadsheet

   Produce a CSV as a chat artifact 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
   

   Useful for importing into accounting software, sharing with accountants, expense tracking, and tax preparation.

7. Provide a completion summary

   # Organization Complete
   
   ## Summary
   - Processed: [X] invoices
   - Date range: [earliest] to [latest]
   - Total amount: $[sum] (if amounts extracted)
   - Vendors: [Y] unique vendors
   
   ## Files Needing Review
   [List any documents where information could not be extracted completely]
   
   ## Next Steps
   1. Review the invoice summary CSV
   2. Check documents flagged "Needs Review"
   3. Import the CSV into your accounting software
   

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/

Pro Tips

1. Save email invoices as PDFs first for batch processing
2. Keep all invoices in one folder for batch intake
3. Organize monthly, not annually
4. Back up originals before reorganizing
5. Include amounts in the CSV for budget tracking
6. Tag which expenses are tax-deductible
7. Keep receipts 7 years (standard audit period)

Handling Special Cases

Missing Information

If date/vendor cannot be extracted: flag the document for manual review, use any date visible in the document or filename as fallback, and list it in a "Needs Review" section.

Duplicate Invoices

If the same invoice appears multiple times: keep the highest quality version and note the duplicates in the summary.

Multi-Page Invoices

For invoices split across files: use consistent naming for the parts and note in the CSV that the invoice is split.

Non-Standard Formats

For unusual receipt formats: extract what is possible, standardize what you can, and flag for review if critical info is 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

Usage

/invoice-organizer $ARGUMENTS