Why?

One's finances are affected by events. These events can include bi-weekly salary cheques, dividends, rent payments, and more. There are generally two types of events for our purposes, income events and expense events. For the simulation, there will be the notion of event streams which will generate an event for a particular day if it matches certain conditions. I'm also looking to implement the notion of scheduled events within the simulation.

TODO

• Implement event streams
• Implement scheduled events
• Distinguish between income events and expense events
• Model changes in the events produced by an event stream over time (ex. model annual rent increases)

A crate to make handling money easy for the purposes of finsim.

Why?

Modelling investment strategies and deciding asset allocation in response to events. This is probably best modelled as a struct that contains a binary function whose parameters are the relevant event and the current portfolio and the return value is the new portfolio.

TODO

• Model investment strategy as a struct with a function
• Implement call of investment strategy in simulation

Why?

For software engineers, equity is a common part of compensation. For public companies, equity can be reasonably be thought of as equivalent to cash but this isn't necessarily the case; public company stock can be sufficiently volatile that considering it to be equivalent to cash can be mistaken. For startups, it is useful to consider equity as worth nothing but if you're optimistic about the startup's chances, it might be worth it to think about the equity package as rising in value.

TODO

• Implement notion of equity as asset
• Implement notion of equity package as event streams

It probably isn't reasonable to expect folks to use this library straight from Rust. It's much better to add bindings to let this library be used elsewhere. These bindings should have plenty of docs to encourage folks to use it.

Why?

Build out a system for supporting tax calculations in the simulation. Since, I'm a software engineer it probably makes sense to focus on jurisdictions in Canada that I as a software engineer am likely to spend time in. America can be handled later.

TODO

• Implement progressive income tax
• Implement flexible deductions system
• Figure out what tax credits are worth representing
• Validate currencies in tax bracket
• Make deductions_map internal in TaxRegime
• Validate currencies in TaxRegime
• Correct variable names throughout current implementation
• Use thiserror and unify errors that can occur in tax calculator
• Implement ordering on tax brackets
• Replace tax credit enum with String and then have an enum at the country/province level to force certain inputs
• Build out ability to handle parallel tax regimes (ex. Ontario income tax + federal income tax + Ontario health premium)
• Add more comprehensive test suite
• Add tax regime generator system for easily building out tax regimes
• Implement federal tax regime
• Implement BC tax regime
• Implement Alberta tax regime
• Implement Ontario tax regime
• Implement Quebec tax regime

Why?

A financial simulation is impossible to build without the notion of a portfolio. A portfolio provides a mechanism to model the growth of one's capital assets. To model this properly, we need to also model assets, inflation, and registered accounts. To be clear here, registered accounts refers to special accounts with unique properties. The two target account types that are relevant for this ticket are the TFSA and the RRSP which are crucial tools for Canadian financial planning.

TODO

• Implement concept of assets (ex. equities, bonds)
• Implement concept of growth of assets over time (ex. modelling the historical growth rate of stocks)
• Implement inflation
• Implement notion of accounts
• Implement notion of a portfolio which is just a collection of accounts