Market Data

Every projection rests on an assumption about what each investment earns. FinZot draws that assumption from one built-in catalog of funds and their real market history. The catalog is a fixed, curated menu, like a brokerage’s fund list. A plan cannot invent its own funds. Everything it holds resolves to a catalog fund or a user’s custom asset based on one. The full, current list of funds is the generated Supported Assets page. It shows each fund’s ticker, asset class, expense ratio, risk rating, and the years of history behind it. This section covers how that data behaves.

Returns are the one part of a plan FinZot never claims to know. The catalog’s histories are facts, but carrying them forward is an assumption, and detailed output is only ever as good as that assumption. Start with returns and distributions for where each fund’s default return comes from and how it splits into price growth and taxable distributions. Asset return overrides and custom assets are the two ways a scenario substitutes its own assumptions: a scenario-wide override, or a private custom asset. Market data in each run ties every input to the runs it reaches, including the fallbacks used when an override is absent or a fund’s history is too short.

• Returns and Distributions — Where each fund’s default return comes from, how FinZot splits it into price growth and distributions, how each distribution type is taxed, and which funds track a cost basis.
• Asset Return Overrides — How a scenario replaces a catalog fund’s default return and tax mix with its own assumption, and which runs a return-rate override reaches compared with a tax-mix override.
• Custom Assets — User-named copies of a catalog fund that inherit its returns and let a scenario layer its own return and tax-mix assumptions on top.
• Market Data in Each Run — Which market data input feeds the detailed projection and which feeds the Monte Carlo trials, and the fallbacks FinZot uses when an override is absent or a fund’s history is too short.