Major improvements to receipt parsing:
Voided Item Handling:
- Add Voided boolean field to ReceiptLineItem model and database
- Never skip any line items - include voided items with voided=true and lineTotal=0.00
- Strong parser hints: "CONTINUE reading", "do NOT stop parsing", "Read ENTIRE receipt"
- Ensures all items after void markers are captured
UPC/Barcode Extraction:
- Extract UPC codes (12-13 digits) and store in Sku field
- Enables price tracking over time even when descriptions change
Quantity Defaults:
- ALWAYS default to 1.0 for ALL retail products (groceries, goods, merchandise)
- Only use null for utility bills, service fees, or taxes
- Emphatic instructions: "MUST be 1.0", "do NOT leave it null"
- Prevents missing quantities on retail items
Model Selection:
- Add AI model dropdown in ViewReceipt UI (gpt-4o-mini vs gpt-4o)
- Update IReceiptParser interface to accept optional model parameter
- Pass selected model through to OpenAI API
- Store model name in parse logs for history tracking
- Allows using smarter model for complex receipts
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Move hardcoded prompt from OpenAIReceiptParser.cs to Prompts/ReceiptParserPrompt.txt for easier maintenance and editing without recompilation. Add caching to LoadPromptTemplateAsync for performance. Configure .csproj to copy Prompts folder to output directory.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Implemented word-based relevance scoring to intelligently sort transactions when multiple matches exist within the amount tolerance. The system now:
1. Splits receipt merchant name into words (handling spaces, dashes, underscores, dots)
2. Compares each word against transaction merchant name and transaction name
3. Scores based on matching word count (bidirectional substring matching)
4. Exact matches get highest priority (score 1000)
5. Word matches get scored (10 points per matching word)
6. Sorts by relevance score, then by date
Examples:
- Receipt "Duke Energy" matches "DUKE ENERGY CORPORATION" better than "WALMART"
- Receipt "McDonald's" matches "MCDONALD'S #12345" better than "BURGER KING"
- Receipt "Comcast" matches "COMCAST CABLE" better than "VERIZON"
This dramatically improves auto-mapping success rate and puts the most likely transaction at the top of the manual selection list.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Changed amount matching from a fixed ±$0.10 tolerance to a percentage-based ±10% tolerance. This dramatically narrows down the transaction list for manual mapping, often to just 1-2 transactions.
Changes:
- Manual mapping: Filters candidates to ±10% of receipt total
- Manual mapping: Green highlighting for very close matches (±2%)
- Auto-mapping: Uses same ±10% tolerance for filtering
- UI: Updated help text to explain the filtering
Example: A $100 receipt will only show transactions between $90-$110, making it much easier to find the correct match.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Fixed bug where manual receipt mapping was only showing transactions near the due date instead of the full range from bill date to due date + 5 days. The issue was that we were taking only the top 100 most recent transactions before applying merchant relevance sorting, which cut off older transactions near the bill date.
Now the query retrieves ALL transactions within the date range (bill date to due date + 5), then sorts by merchant relevance and date. This ensures bills like electric bills show all transactions from the bill date through the payment date.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Receipts are now automatically parsed using OpenAI Vision API immediately after upload. The parsing runs in the background and triggers auto-mapping if successful. This streamlines the workflow - users just upload a receipt and it's automatically parsed and mapped to the matching transaction without any additional clicks.
The parsing happens asynchronously via Task.Run to not block the upload response. If parsing fails, the upload is still considered successful.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Updated documentation to reflect v1.2 changes:
- Unmapped receipts with nullable TransactionId
- Duplicate detection with blocking modal
- Auto-mapping service with intelligent date range logic
- Due date support for bills (bill date to due date + 5 days)
- Enhanced manual mapping UI with transaction selector
- Transactions page improvements (search, filters, ID column)
- New Receipts page with comprehensive workflow
- Updated service layer, database schema, and workflows sections
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Updated both auto-mapping and manual mapping logic to search for transactions from bill date to due date + 5 days. This accounts for auto-pay processing delays, weekends, and bank processing times when bills are auto-paid on the due date.
This fixes the issue where electric bills and other auto-paid utilities were missing their matching transactions because the payment posted a few days after the due date.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Removed "Upload CSV" from the main navigation menu and added an "Upload CSV" button to the Transactions page header. This makes CSV upload more contextual since it's primarily used when viewing/managing transactions.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
When opening the map receipt modal, the transaction list now automatically scrolls to center on the first green-highlighted amount match (if one exists). This makes it easier to quickly find and select the most likely matching transaction without having to manually scroll through the list.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Enhanced receipt parsing and mapping to support bills with due dates (like utility bills):
- Updated OpenAI prompt to extract due date from bills
- Added DueDate property to Receipt model with database migration
- Modified auto-mapping logic to use bill date to due date range when both dates are present
- For regular receipts without due dates, continues to use ±3 day window
- Updated manual mapping UI to display due dates and adjust date range explanation
- Receipt list now shows due dates in orange "Due:" text for clarity
This allows electric bills and similar documents with 20+ day payment windows to be properly matched to their payment transactions.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Added ID column as the first column in the transactions table to make it easy to reference transaction IDs when manually mapping receipts. The ID is displayed with a "#" prefix in a small, muted style.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Changed merchant filtering from exclusionary to relevance-based sorting.
This fixes the issue where transactions don't appear if the merchant
name doesn't exactly match.
Changes:
- Date range (±3 days) remains the primary hard filter
- Merchant name now sorts results by relevance instead of excluding
- Retrieves 100 candidates, sorts by match quality, returns top 50
- Case-insensitive matching using ToLower()
Relevance Scoring:
- Score 3: Exact match on merchant or transaction name
- Score 2: Partial match on merchant name (Contains)
- Score 1: Partial match on transaction name (Contains)
- Score 0: No match (still included if within date range)
Results sorted by: Match score → Date → ID
Benefits:
- McDonald's receipt will show all transactions in date range
- Best matches appear at top
- No transactions excluded due to name variations
- More forgiving for typos, abbreviations, etc.
- User can still see and select any transaction in date window
Example: Receipt says "McDonald's" but transaction says "MCDONALD'S #1234"
- Before: Excluded (no exact Contains match)
- After: Included, sorted to top (partial match score 2)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Changed duplicate detection from informational alert to a modal dialog
that requires user decision before proceeding with upload.
Upload Flow Changes:
1. Initial upload detects duplicates and uploads temporarily
2. If duplicates found:
- Deletes the uploaded file
- Stores warnings and filename in TempData
- Redirects to show modal
3. Modal blocks with two options:
- Cancel: Don't upload (returns to page)
- Upload Anyway: Re-upload with confirmation flag
Modal Features:
- Non-dismissible (static backdrop, no keyboard close)
- Yellow warning header
- Table showing all potential duplicates with:
- Receipt ID and filename
- Upload timestamp
- Reason for match (hash/name+size)
- Transaction mapping status
- View button to compare
- Clear explanation of options
- Prompts user to re-select file for confirmed upload
Benefits:
- Prevents accidental duplicate uploads
- Forces user acknowledgment
- Provides context for decision-making
- Links to view existing receipts for comparison
- Better UX than passive alert banner
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Changed from using .ToHashSet() extension method (which may not be
available in some EF Core versions) to .ToListAsync() followed by
creating a HashSet from the list.
This ensures compatibility across different EF Core versions while
maintaining the same performance characteristics.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Enhanced the receipt mapping modal with intelligent transaction filtering
and a clean table-based selection interface.
Smart Filtering (per receipt):
- If receipt has a date: Show transactions within ±3 days
- If receipt has merchant: Filter by merchant name match
- Calculate amount matches (within $0.10 tolerance)
- Only show transactions without receipts
- Limit to 50 most recent matches
- Fallback to recent 50 transactions if no matches
UI Improvements:
- Replaced confusing listbox with formatted data table
- Proper column alignment with fixed widths
- Sticky header for scrollable table (max 400px height)
- Clickable rows with radio button selection
- Visual feedback:
- Green highlight for amount matches
- Blue highlight for selected row
- Hover effect on rows
- Context-aware helper text explaining filter criteria
- Shows which transactions match the receipt date range
Features:
- Click anywhere on row to select
- Radio buttons for explicit selection
- Hidden input field stores selected transaction ID
- Manual ID entry still available as fallback
- Clear visual indicators for best matches
This provides a much better UX for manual mapping by showing only
relevant transactions and making it easy to identify likely matches.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Replaced the manual transaction ID input with a user-friendly
transaction selector dropdown in the map receipt modal.
Changes:
- Added RecentTransactions list to Receipts page model
- Load last 100 transactions without receipts for dropdown
- Updated modal dialog:
- Larger modal (modal-lg) for better visibility
- Multi-select dropdown showing formatted transaction details:
- Date | Amount | Name | (Merchant)
- Monospace font for aligned columns
- Size 10 to show multiple options at once
- Receipt info displayed in styled info box
- Manual ID input field as fallback option
- Link to Transactions page for finding IDs
- Two-way binding between selector and manual input
User Experience:
- Users can now visually browse and select transactions
- Transaction details are formatted for easy scanning
- Only shows transactions that don't already have receipts
- Fallback to manual ID entry for edge cases
- Receipt parsed data clearly displayed for comparison
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Renamed static factory method from 'MultipleMatches' to
'WithMultipleMatches' to avoid conflict with the 'MultipleMatches'
property in the same class.
This resolves the compilation error: "The type 'ReceiptAutoMapResult'
already contains a definition for 'MultipleMatches'".
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Implemented automatic mapping of parsed receipts to matching
transactions, with both automatic (after parsing) and manual
(via button) triggers.
New Service - ReceiptAutoMapper:
- AutoMapReceiptAsync: Maps a single receipt to a transaction
- AutoMapUnmappedReceiptsAsync: Bulk maps all unmapped receipts
- FindMatchingTransactionsAsync: Smart matching algorithm using:
- Receipt date (+/- 3 days for processing delays)
- Merchant name (matches against transaction merchant or name)
- Total amount (within $0.10 tolerance)
- Excludes transactions that already have receipts
- Returns single match, multiple matches, or no match
Matching Strategy:
- Single match: Automatically maps
- Multiple matches: Reports count for manual review
- No match: Reports for manual intervention
- Not parsed: Skips (requires merchant, date, or total)
Integration Points:
- OpenAIReceiptParser: Triggers auto-mapping after successful parse
(only for unmapped receipts, errors ignored to not fail parse)
- Receipts page: Added "Auto-Map Unmapped Receipts" button
- Only shows when unmapped parsed receipts exist
- Displays detailed results (mapped count, no match, multi-match)
This enables a streamlined workflow:
1. Upload receipt → 2. Parse receipt → 3. Auto-map to transaction
Users can also trigger bulk auto-mapping for all unmapped receipts.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Implemented duplicate detection to warn users when uploading receipts
that may already exist in the system.
Changes:
- Extended ReceiptUploadResult to include DuplicateWarning list
- Added CheckForDuplicatesAsync method to ReceiptManager that checks:
1. Identical file content (same SHA256 hash)
2. Same file name and size (potential duplicate saved/edited)
- Updated upload flow to check for duplicates before saving
- Enhanced Receipts page to:
- Display warning alert when duplicates are detected
- Show details of each potential duplicate (receipt ID, filename,
upload date, mapped transaction, and reason)
- Provide quick link to view the duplicate receipt
- Use TempData to persist warnings across redirect
Duplicate detection runs on every upload and provides actionable
information to help users avoid uploading the same receipt multiple
times. The check uses hash-based detection for exact duplicates and
name+size matching for potential duplicates.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
The previous commit had the model changes but the database wasn't
properly migrated. This commit adds the missing migrations to make
TransactionId nullable in the Receipts table.
Changes:
- Updated MoneyMapContext to make Transaction relationship optional
for Receipt (IsRequired(false))
- Created additional migrations to properly handle:
- Making TransactionId column nullable
- Updating the unique index to handle NULL values with WHERE clause
- Applied all migrations to database successfully
The Receipts page should now work correctly for uploading unmapped
receipts without a TransactionId.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Added functionality to upload and manage receipts without initially
associating them to a transaction, with the ability to map them later.
Changes:
- Modified Receipt model to make TransactionId nullable
- Updated ReceiptManager service with new methods:
- UploadUnmappedReceiptAsync: Upload receipts without a transaction
- MapReceiptToTransactionAsync: Map an existing receipt to a transaction
- Created Receipts page (Receipts.cshtml) with:
- Upload form for new receipts
- List view of all receipts (mapped and unmapped)
- Status badges (Mapped/Unmapped)
- Map to Transaction modal dialog
- Delete receipt functionality
- Added "Receipts" link to navigation menu
- Fixed Transactions page receipt count query for nullable TransactionId
- Created migration: MakeReceiptTransactionIdNullable
This enables workflows where receipts are uploaded first and matched
to transactions later, useful for batch receipt processing.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Added convenient buttons for common date ranges:
- Last 30 Days
- Last 60 Days
- Last 90 Days
- Last Year
- This Month
- Last Month
Clicking these buttons automatically populates the Start Date and End
Date filter fields. Users can still manually adjust the dates or use
the Filter button to apply the selected range.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Added a search bar that allows users to filter transactions by:
- Transaction name
- Memo
- Category
- Notes
- Merchant name
The search uses a case-sensitive contains filter across all these
fields. The search parameter is preserved across pagination links and
included in the "Clear Filters" button logic.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Previously, selecting "(blank)" from the category dropdown would submit
an empty string value, causing no transactions to appear. The backend
expects the literal string "(blank)" to filter for uncategorized items.
Updated the dropdown to submit "(blank)" as the value when the category
is empty, matching the backend's filter logic in Transactions.cshtml.cs.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add explicit column type configuration for Confidence field to avoid
SQL Server truncation warnings. Use decimal(5,4) to store values from
0.0000 to 1.0000 with 4 decimal places of precision.
Also add MaxLength constraint for CreatedBy field.
Migration applied successfully to database.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add AI categorization service that suggests categories, merchants, and
rules for uncategorized transactions. Users can review and approve
suggestions before applying them.
Features:
- TransactionAICategorizer service using OpenAI GPT-4o-mini
- Batch processing (5 transactions at a time) to avoid rate limits
- Confidence scoring (0-100%) for each suggestion
- AI suggests category, canonical merchant name, and pattern rule
- ReviewAISuggestions page to list uncategorized transactions
- ReviewAISuggestionsWithProposals page for manual review
- Apply individual suggestions or bulk apply high confidence (≥80%)
- Optional rule creation for future auto-categorization
- Cost: ~$0.00015 per transaction (~$0.015 per 100)
CategoryMapping enhancements:
- Confidence field to track AI confidence score
- CreatedBy field ("AI" or "User") to track rule origin
- CreatedAt timestamp for audit trail
Updated ARCHITECTURE.md with complete documentation of:
- TransactionAICategorizer service details
- ReviewAISuggestions page descriptions
- AI categorization workflow (Phase 1)
- Updated CategoryMappings schema
Next steps (Phase 2):
- Auto-apply high confidence suggestions
- Background job processing
- Batch API requests for better efficiency
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add prominent reminders in both CLAUDE.md and AGENTS.md to update
the shared ARCHITECTURE.md file when making architectural changes.
This helps ensure the documentation stays current and both AI tools
have accurate context.
Changes include:
- Added step in development workflow to update docs
- Added "Important: Keep Documentation Updated" section
- Listed specific types of changes that require doc updates
- Emphasized that this keeps both tools in sync
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Split documentation into three files to eliminate duplication:
- ARCHITECTURE.md: Shared technical documentation (domain models,
services, database schema, workflows, patterns)
- CLAUDE.md: Claude Code-specific context referencing ARCHITECTURE.md
- AGENTS.md: Codex agent context referencing ARCHITECTURE.md
This allows both Claude Code and Codex CLI to share the same source
of truth for architecture details while maintaining tool-specific
configuration in separate files.
Benefits:
- Single source of truth for technical details
- Easier maintenance (update once, not twice)
- Consistent documentation across tools
- Clear separation of concerns
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Display the average spend per transaction for each category on the
dashboard's top expense categories table. This helps users understand
spending patterns beyond just total amounts.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Ensure merchant data is eagerly loaded when querying transactions
on the Transactions page to avoid N+1 queries.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Allow users to set or change the merchant for a transaction from the
EditTransaction page. Users can select from existing merchants or
create new ones on the fly.
Changes:
- Add merchant dropdown with existing merchants
- Support creating new merchants via custom input
- Update transaction merchant when saving
- Rename "Merchant Name" label to "Transaction Name" for clarity
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Created a dedicated page for viewing and managing merchants:
**Backend (Merchants.cshtml.cs):**
- List all merchants with transaction and mapping counts
- Add new merchant with duplicate name validation
- Edit merchant name (updates all linked transactions/mappings)
- Delete merchant (unlinks from transactions/mappings via SET NULL)
- Full CRUD operations with proper validation
**Frontend (Merchants.cshtml):**
- Clean table view showing merchant name, transaction count, mapping count
- Add modal for creating new merchants
- Edit modal for renaming merchants (click row or Edit button)
- Delete with confirmation showing impact (# of transactions/mappings)
- Success/error message display
- Responsive Bootstrap layout
**Navigation:**
- Added "Merchants" link to main navigation bar
- Positioned between "Categories" and "Recategorize"
**Features:**
- Shows transaction count per merchant (useful for seeing merchant usage)
- Shows mapping count per merchant (useful for seeing pattern coverage)
- Inline edit with modal dialog (consistent with CategoryMappings UI)
- Safe delete with SET NULL (transactions/mappings remain, just unlinked)
- Duplicate name prevention on add/edit
**Benefits:**
- Easy merchant management without SQL queries
- Visual feedback on merchant usage
- Rename propagates to all transactions/mappings automatically
- Consistent UI with rest of application
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Improved UX for adding/editing category mappings:
**Backend Changes:**
- Added AvailableCategories list (distinct categories from existing mappings)
- Added AvailableMerchants list (all merchants from Merchants table)
- Updated LoadDataAsync() to populate both lists
**UI Changes:**
- Replaced plain text input with HTML5 datalist for Category field
- Replaced plain text input with HTML5 datalist for Merchant field
- Both fields support autocomplete while allowing new values
- Added "required" attribute to Category field for validation
- Added helper text to guide users
- Removed custom JavaScript dropdown logic (now using native datalist)
**Benefits:**
- Consistent category naming (autocomplete suggests existing categories)
- Consistent merchant naming (autocomplete suggests existing merchants)
- Better UX with native browser autocomplete behavior
- Still allows creating new categories/merchants on the fly
- Cleaner, simpler code without custom dropdown implementation
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
This refactors the merchant field from a simple string column to a normalized
entity with proper foreign key relationships:
**Database Changes:**
- Created Merchant entity/table with unique Name constraint
- Replaced Transaction.Merchant (string) with Transaction.MerchantId (FK)
- Replaced CategoryMapping.Merchant (string) with CategoryMapping.MerchantId (FK)
- Added proper foreign key constraints with SET NULL on delete
- Added indexes on MerchantId columns for performance
**Backend Changes:**
- Created MerchantService for finding/creating merchants
- Updated CategorizationResult to return MerchantId instead of merchant name
- Modified TransactionCategorizer to return MerchantId from pattern matches
- Updated Upload, Recategorize, and CategoryMappings to use merchant service
- Updated OpenAIReceiptParser to create/link merchants from parsed receipts
- Registered IMerchantService in dependency injection
**UI Changes:**
- Updated CategoryMappings UI to handle merchant entities (display as Merchant.Name)
- Updated Transactions page merchant filter to query by merchant entity
- Modified category mapping add/edit/import to create merchants on-the-fly
- Updated JavaScript to pass merchant names for edit modal
**Migration:**
- ConvertMerchantToEntity migration handles schema conversion
- Drops old string columns and creates new FK relationships
- All existing merchant data is lost (acceptable for this refactoring)
**Benefits:**
- Database normalization - merchants stored once, referenced many times
- Referential integrity with foreign keys
- Easier merchant management (rename once, updates everywhere)
- Foundation for future merchant features (logos, categories, etc.)
- Improved query performance with proper indexes
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
This feature enables easy filtering and identification of transactions by merchant name:
- Added Merchant column to Transaction model (nullable, max 100 chars)
- Added Merchant field to CategoryMapping model
- Modified ITransactionCategorizer to return CategorizationResult (category + merchant)
- Updated auto-categorization logic to assign merchant from category mappings
- Updated category mappings UI to include merchant field in add/edit forms
- Added merchant filter dropdown to transactions page with full pagination support
- Updated receipt parser to set transaction merchant from parsed receipt data
- Created two database migrations for the schema changes
- Updated helper methods to support merchant names in default mappings
Benefits:
- Consistent merchant naming across variant patterns (e.g., "Walmart" for all "WAL-MART*" patterns)
- Easy filtering by merchant on transactions page
- No CSV changes required - merchant is derived from category mapping patterns
- Receipt parsing can also populate merchant field automatically
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Show what percentage of total expenses each category represents in the top categories table. This helps quickly identify which categories consume the largest portion of spending.
Changes:
- Add PercentageOfTotal property to TopCategoryRow
- Calculate percentage based on total expenses in the period
- Display percentage as a badge in the table (e.g., "23.5%")
- Add new "% of Total" column header
- Format to 1 decimal place for clarity
Example: If "Groceries" is $500 and total expenses are $2000, it shows 25.0%
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add the ability to export and import category mappings as JSON files:
Export:
- Downloads all category mappings as a formatted JSON file
- Ordered by category and priority
Import:
- Upload JSON file with category mappings
- Option to replace all existing mappings or merge with current ones
- Validates JSON format and data integrity
- Shows clear error messages for invalid files
UI additions:
- Export to JSON button in header
- Import from JSON button with modal dialog
- Shows example JSON format in import modal
- Replace/merge option with clear explanation
This allows users to:
- Backup their custom category mappings
- Share mappings between instances
- Version control their categorization rules
- Easily restore default or custom configurations
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Pass the transaction name from the bank statement to OpenAI when parsing receipts. This helps identify merchants when receipts have cryptic or unclear merchant names (e.g., Arby's receipts).
The transaction name is included as additional context in the prompt: "This transaction was recorded as 'XXX' in the bank statement, which may help identify the merchant if the receipt is unclear."
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Remove the Cards navigation item since card management is now nested under the Accounts page. Users access cards by navigating to Accounts -> View Account -> Manage Cards.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Modify EditCard page to:
- Accept optional accountId parameter to pre-select account for new cards
- Redirect to AccountDetails page after save (if card has linked account)
- Update navigation to go back to Accounts instead of Cards page
This integrates card management into the account-centric workflow.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
