feat(investments): net worth tracking — chequing + savings + investments combined

Open
#246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
api, backend, database

Research direction

Start at the existing MCP tool entry points and account-balance/Plaid sync flow, then trace where chat requests are routed. Implement the net_worth(as_of) result and net_worth_snapshots storage across the stated account types, and add unit tests covering sums, snapshots, and the chat trigger.

Written by the indexing model from the issue text.

Description

Summary

Add net worth as a first-class concept: the sum of all account balances (chequing, savings, investment) minus any liabilities (credit card balances, mortgages if tracked).

MCP tool

def net_worth(as_of: str | None = None) -> dict

Sample output

{
  "as_of": "2026-05-26",
  "net_worth": 121400.00,
  "assets": {
    "chequing_savings": 8200.00,
    "investments": 48200.00,
    "property_equity": 65000.00    
  },
  "liabilities": {
    "credit_cards": 0.00,
    "mortgages": 0.00
  },
  "breakdown": [
    {"account": "RBC Chequing", "balance": 5200.00, "type": "chequing"},
    {"account": "Wealthsimple TFSA", "balance": 28400.00, "type": "investment"},
    {"account": "Sunlife RRSP", "balance": 19800.00, "type": "investment"}
  ]
}

Notes

  • Property equity is out of scope v1 (requires property valuation — tracked separately via rental ledgers)
  • Liabilities: credit card balances already available from Plaid; mortgages are manual
  • Net worth snapshots stored over time → trend tracking

Acceptance criteria

  • net_worth() returns correct sum across account types
  • Snapshots stored on each sync (new net_worth_snapshots table)
  • Chat: "What's my net worth?" triggers this tool
  • Unit tests

Part of Epic #239

Dominant language
Python
Stars
1
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Riddy21/Friday_Budgeting_Pro

All issues in Riddy21/Friday_Budgeting_Pro

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.