Set up and navigate MoneyKai
MoneyKai Docs is a practical map for the web workspace. Use it to understand what each section owns, where to make changes, and which production constraints matter before shipping or relying on data.
What you will understand
•
Confirm the reporting month before reviewing any workspace totals.
•
Start from Dashboard, then move into the specific section that owns the data you need to correct.
•
Use local transactions and budgets as the source of truth for summaries.
•
Treat cloud sync, SMS capture, Gmail sync, bank sync, Financial AI, wealth, and provider account features as out of scope for the current Android release.
Workspace overview
Dashboard
Use Dashboard as the first read of monthly financial state: balances, budget pressure, recent movement, emergency posture, and the next useful action.
•
Understand month-to-date income, expense, savings, and budget movement from one screen.
•
Identify categories and recent transactions that need review before totals are trusted.
•
Move quickly into related workspaces without losing the current reporting month context.
•
Open Dashboard after sign-in and confirm the reporting month in the workspace header.
•
Review the top summary cards first, then inspect recent transactions and category signals.
•
Use the linked cards to move into Transactions, Budgets, Reports, or Goals when a deeper correction is needed.
•
Dashboard should remain read-first and low-friction; avoid adding heavy forms directly to this surface.
•
Every metric should be traceable back to user-owned records or deterministic local state.
•
Empty local data should explain what is missing instead of showing blank analytical panels.
Money movement ledger
Transactions
Transactions is the canonical workspace for income and expense records, including manual corrections, filters, categories, and review status.
•
Add, edit, filter, and delete user-owned records without changing unrelated financial state.
•
Separate income, expense, transfer, and recurring movement for cleaner summaries.
•
Use reviewed local records as the trusted input for budgets and analytics.
•
Filter by reporting month, account, capture source, payment method, or category.
•
Open a transaction row when a category, amount, note, or payment method needs correction.
•
Review manual entries carefully so duplicates do not pollute the ledger.
•
Mutations must preserve user ownership and never trust client-provided user IDs for authorization.
•
Delete and bulk actions need clear confirmation or reversible handling where practical.
•
Manual records should carry enough context for review and deduplication.
Monthly spending control
Budgets
Budgets provides the monthly guardrails for categories, daily pace, remaining room, and budget health signals.
•
Set category limits that map to real spending behavior.
•
Understand whether current pace is safe, tight, or critical for the month.
•
Use budget coaching to decide what to adjust before the month closes.
•
Confirm the reporting month and review overall budget health.
•
Inspect category tiles for overspend, unused room, and pacing risk.
•
Adjust limits or return to Transactions when the underlying categorization is wrong.
•
Budget calculations should be deterministic and reproducible from transaction state.
•
Coaching copy should avoid financial-advice claims and focus on operational next steps.
•
Limit changes should persist per user and not leak into shared or sample records.
Savings and habit progress
Goals
Goals exposes active and completed challenge progress as practical financial habit tracking without duplicating another goal engine.
•
Track active goal count, completed goals, deactivated goals, and earned XP.
•
See progress against challenge duration and current streak.
•
Use completed history to understand which financial habits are actually sticking.
•
Start from Reports when a real challenge or savings habit is ready to track.
•
Review active progress and streak state from Goals.
•
Move completed items out of the active workflow while preserving their history.
•
Goal state should not be duplicated across unrelated stores.
•
Progress labels must handle zero and missing durations safely.
•
Deactivated goals should remain visible enough for audit without competing with active work.
Review and import analysis
Reports
Reports turns local transaction history into reviewable monthly patterns, category trends, and practical next steps.
•
Understand category distribution, recurring movement, and month-level patterns.
•
Review local transaction history before relying on category trends.
•
Launch challenges or follow-up workflows from observed spending signals.
•
Use the report month context to inspect trends and category summaries.
•
Check source transactions when a category total looks wrong.
•
Return to Transactions when source rows or categories need correction.
•
Reports should stay deterministic from local transaction and budget state.
•
Any future file import must validate accepted formats, size limits, and parse failures before release.
•
Reports should expose assumptions in plain language rather than hiding calculation gaps.