Option C: Hierarchical Tree Flow

Transactions → Rules → Structure (where they land)

Transactions

ACME CORP 11/20 +$2,500 ✓
UPWORK 11/18 +$850 ✓
LANDLORD LLC 11/15 -$1,800
STATE FARM 11/12 -$125 ✓
KROGER #4532 11/10 -$87 ✓
WALMART 11/09 -$62 ✓
SHELL GAS 11/08 -$45

Auto-Tag Rules

Contains "ACME" → Paycheck
Contains "SALARY" → Paycheck
Contains "UPWORK" → Freelance
No rules defined → Rent
Contains "STATE FARM" → Insurance
Contains "KROGER" → Groceries
Contains "WALMART" → Groceries
Contains "ALDI" → Groceries
No rules defined → Gas

Structure

💰 Income 2
Paycheck ✓ 2
Freelance ✓ 1
🏠 Housing 2 • ⚠1
Rent ⚠ 0
Insurance ✓ 1
🍔 Food 1
Groceries ✓ 3
🚗 Transportation 1 • ⚠1
Gas ⚠ 0
7 Staged
5 matched, 2 need rules
8 Rules Active
4 items covered
2 Need Rules
Rent, Gas
6 Line Items
All categories covered
4 Categories
2 Income, 2 Expense

✓ Pros

  • Hierarchical tree shows category/item relationship naturally
  • Compact - saves horizontal space (only 3 columns)
  • Clear left-to-right data flow (transactions → rules → structure)
  • Easy to collapse/expand categories
  • Similar to file explorer - familiar pattern
  • Items with no rules stand out visually
  • Rules column filters by selected item (stays short)
  • Most compact option overall
  • Drag handle for category reordering
  • Real transactions (staged/actual) instead of mock data
  • Onboarding-friendly: test rules before importing
  • Create rules directly from unmatched transactions (+)

✗ Cons

  • Requires click interaction to filter rules/transactions
  • Can't see all rules at once (must select items)
  • Visual connections harder to show across 3 columns
  • No overview of all items without expanding categories

💡 Interaction Model (Master-Detail)