An automatic net worth tracker can combine current bank balances, investment holdings, loan balances and manually valued assets in related BankSync Tables, then calculate a dated total with transparent valuation rules.
What this system should answer
It should answer total assets, total liabilities, net worth, change over time and the contribution of each account or asset class. It should also show the last updated date and whether a value came from a live source, a scheduled feed or manual input.
BankSync works best when each layer has a clear responsibility. Feeds collect one data type from selected accounts. Enrichments transform, guard, watch or learn from rows before writing. Tables store typed or custom relational data. Dashboards query that evidence and present KPIs, charts, filters and detail.
Preserve original amount, currency, date, account and provider identifier. Add personal or management classifications in separate fields. That separation is what makes a custom tracker trustworthy rather than merely attractive.
Model the evidence first
Create Accounts, Assets and Liabilities Tables. Relate balance observations to accounts and manual valuations to assets. Holdings should retain quantity, quoted currency and source account. Loans should retain outstanding balance and timestamp. Add valuation method, valuation date, source and confidence fields for manual assets. A net-worth snapshot Table can store one dated rollup so historical changes are not rewritten by a later house or investment valuation.
Use relations instead of repeated labels
Create reference Tables for concepts that have their own properties: assets, liabilities, securities, categories, vendors or budget periods. Relate financial rows to those records, then use lookups, counts and rollups. Rollups can calculate sums, averages, medians, ranges, date extrema, percentages and option counts; formulas can read same-row and related values and produce stored, sortable, filterable results.
Choose views deliberately
Grid is the general editing surface. Board writes status when cards move. Calendar and Timeline write date fields when items move. Gallery suits attachment-led records, List provides a calm summary and Form adds rows. Views may be shared or personal and save filters, grouping, sorting, columns and row colours.
Aggregate safely
Use the latest valid observation for each component at the snapshot date. Do not sum balance history. Avoid mixing original cost, market value and estimated value in the same field; preserve them as separate measures. BankSync uses strict multi-currency aggregation by default. Any converted reporting amount should keep the native amount, currency, exchange rate and rate date visible.
Connected values
Bank balances, loans and supported brokerage holdings can refresh on their feed schedules. Keep source time and native currency beside each value.
Manual values
Property, private investments and other estimates need a valuation method, source, effective date and a deliberate refresh cadence.
Build the tracker
List every component
Separate connected and manual assets and liabilities.
Create reference Tables
Model accounts, assets and liabilities.
Connect balance and holdings feeds
Keep data types separate.
Add valuation fields
Record method, date and source.
Select latest observations
Avoid summing snapshots.
Create dated net-worth snapshots
Preserve history.
Build allocation and trend views
Pair totals with detail.
Review stale values
Refresh manual assets on a defined cadence.
Copy this build: a net-worth tracker that does not rewrite history
Imagine someone with cash accounts, a mortgage, a brokerage portfolio and a home. The tempting shortcut is one editable total per asset. That makes last year’s chart change when today’s home estimate is updated.
Create separate Assets, Liabilities and Accounts Tables. Add valuation method, source and effective date to manual assets. Select the latest connected observation at each snapshot date, then write one dated Net Worth Snapshot. The snapshot preserves what was known at that time.
On the dashboard, show assets, liabilities, net worth and period change, followed by allocation and a component table. Pin source and freshness columns so an estimate cannot look identical to a recently synced bank balance.
What success looks like after one week
A later valuation updates the current picture without silently changing prior snapshots, and the reader can see which components are connected facts versus estimates.
Dashboard and operating design
Lead with net worth, assets, liabilities and period change. Add an asset-allocation chart, liability composition, historical trend and a detail table with source and freshness. A manual-asset Form view makes infrequent valuations approachable without exposing the rest of the model.
Apply filters at the source when they change aggregates. Browser-only filtering is a presentation option, not an access-control boundary. Where a view is scoped to a household member, account or entity, use a locked source-applied filter that fails closed.
Enrichments and watches
Feed Monitor is important because stale balances can make net worth appear stable. Alert can watch a liability balance or large movement. Merchant categorisation is secondary here; the primary evidence is balances, holdings and loans. Use rules for deterministic asset classes rather than asking AI to infer ownership or valuation.
Guard steps run first, followed by Memory, lookups, rules, AI fill and finally watch enrichments. Suppressed records never write, teach Memory or fire alerts. Use Live Preview before enabling hard filters, splits or suppression. Alert freshness follows the feed schedule.
Limitations and controls
A connected balance is not a formal valuation. Property, private companies, pensions and collectibles require a policy. Market values move at different frequencies. Label estimated values and never present the result as investment advice.
Dashboards are beta by workspace. Public links and indexed tiers are for intentional public data, not personal finance. External-agent authoring is a staging workflow; open and review generated dashboards in the normal editor.
Operate the tracker
Check feed history before trusting a quiet chart. Review exceptions and low-confidence categories on a regular cadence. Document formulas, filters and model changes. A reliable tracker is one whose total can be reproduced from source rows and explicit assumptions.