# Budget UX reference analysis from external finance apps

Use when the user asks to study external finance/bookkeeping apps (for example ezBookkeeping) as a reference for JARVIS FinanceManager Budget/Cashflow UX, architecture, data model, imports, or analytics.

## Intent

This is a **reference-analysis workflow**, not an implementation sprint.

Do:

- Clone or inspect the external app in a separate reference directory, never inside FinanceManager source/frontend trees.
- Check the license first and document it.
- Analyze stack, build system, folder structure, routing, state management, API structure, data models, import flow, transaction UX, analytics/statistics, charts, and mobile/desktop differences.
- Compare against FinanceManager using source code only; do not read or mutate runtime DB/files.
- Produce a Markdown document under `docs/budget/` or another user-approved docs path.
- Include explicit compliance statements: no code/assets copied, no runtime data used, no implementation started.

Do not:

- Copy code, icons, assets, templates, screenshots, branding, or proprietary wording.
- Treat MIT/open-source status as permission to bypass the user's stricter no-copy preference.
- Start new Budget/Import/OCR/Provider/Rule implementations unless the user explicitly authorizes a feature sprint.
- Use real amounts/IDs in chat or docs.

## Recommended document shape

1. Scope and compliance
2. License note
3. External app technical structure
4. Folder/component/API/routing/state patterns
5. Data-model comparison against JARVIS
6. Transaction-list UX recommendations
7. Statistics/analytics/chart recommendations
8. Function matrix with columns:
   - Area
   - External app function
   - JARVIS current state
   - Gap
   - Recommendation
   - Priority
9. Concrete UI proposals for:
   - Buchungen prüfen
   - Effektive Ausgaben
   - Budgetstatus nach Kategorie
   - Budget-Auswertung
   - Daten-Explorer
10. Navigation recommendation
11. 4-stage roadmap:
   - Budget UX v2
   - Budget Analytics v1
   - Budget Imports v1
   - Budget Advanced
12. What may be reused as ideas vs what must not be copied
13. Final checklist

## JARVIS-specific conclusions from ezBookkeeping analysis

- Keep JARVIS as a safe budget system, not an ezBookkeeping clone.
- Budget Cockpit remains the central truth: plan/actual/forecast/audit.
- Transaction Review and Effective Expenses should adopt mature list/filter/drilldown patterns.
- Use external app concepts only as inspiration: date jumps, grouped transactions, category/account/tag filters, chart drilldowns, import wizard, read-only explorer.
- Prioritize tags, merchant normalization, clearer filters, and User Mode polish before exotic charts.
- Data Explorer should be read-only first and whitelist-based; no raw SQL and no batch updates outside Preview/Confirm/Audit.
- Scheduled transactions should generate expected candidates, not silent bookings.
- Splits should become more complete before advanced merchant/category analytics.

## Verification before reporting

- Re-read the generated Markdown.
- Verify required sections exist.
- Verify FinanceManager git status shows only intended docs changes unless implementation was explicitly authorized.
- Verify the external reference repo remains clean/read-only.
- Report yes/no status and path to the document.