Folio v0.9 — CEX + On-chain Consolidation is liveSee what's new →

Family & Household Crypto Portfolio: One Dashboard, Separate Taxpayers (2026)

Portfolio·

Family & Household Crypto Portfolio: One Dashboard, Separate Taxpayers (2026)

A household view is convenient for net worth but dangerous for tax: aggregating a couple's or family's wallets into one pool can mis-assign ownership and basis. Why per-person attribution must survive the household roll-up, and why the household-vs-individual tax unit is strictly jurisdiction-specific.
Author avatar Wag3s TeamEditorial team specializing in Web3 finance, crypto tax, and DAO operations. Based in Zurich, Switzerland.

Reviewed by Wag3s Editorial Team — verified against the per-person-attribution requirement and the jurisdiction-specific household-vs-individual tax-unit distinction · Last reviewed May 2026

Family & Household Crypto Portfolio: One Dashboard, Separate Taxpayers

A household crypto dashboard answers "what are we worth?" beautifully and "what does each of us owe?" disastrously — if it pools everyone into one basis. This guide is why per-person attribution must survive the roll-up, and why the tax unit is a question no dashboard can answer globally.

TL;DR

  • A household view is great for net worth, risky for tax if it pools members into one basis.
  • Ownership and cost basis are personal facts — they must survive any household roll-up.
  • Per-person records first; household view on top — never the reverse.
  • Tax unit (household vs individual) is strictly jurisdiction-specific — do not assume.
  • France taxes the foyer fiscal (couple/minor aggregate there) — a jurisdiction example, not a global rule (see couple, minor).
  • Inter-member transfers may carry gift/other consequences — preserve per-person identity, confirm tax.

Convenient for net worth, dangerous for tax

A family/household dashboard is useful for a consolidated net-worth picture. It becomes dangerous the moment it pools every member's wallets into one cost basis for tax. Two reasons:

  • where individuals are taxed separately, a pooled household figure is wrong for each return;
  • even where a household is the tax unit, the computation still usually depends on per-person ownership and acquisition.

So the household roll-up must be a presentation layer, never a replacement for correct per-person records.

Per-person attribution is the invariant

Ownership and cost basis are personal facts: who acquired an asset, when, and at what cost determines that person's gain on disposal. A dashboard that averages or pools across members loses this and produces a number that fits no one's actual position. The rule is constant across every jurisdiction:

Per-person records first. Household view on top. Never the reverse.

This is the multi-wallet completeness discipline with an added owner dimension.

The tax unit is jurisdiction-specific

Whether the household or the individual is the tax unit is strictly jurisdiction-specific and must not be assumed:

  • some jurisdictions assess a household/family unit;
  • others tax each individual separately.

France taxes the foyer fiscal, which is why the French couple and minor cases aggregate at that level — but that is a jurisdiction example, not a global rule. A household dashboard cannot encode one answer for every country; the unit is applied on top of per-person records, per jurisdiction, with an adviser.

Couples and minors

Track each person's wallets with that person's ownership and basis, then aggregate for the household view. Whether a couple is then taxed jointly or separately, or a minor's holdings fold into a parent's unit, is a jurisdiction question (in France, foyer-fiscal cases). The tracking rule does not change: per-person first; tax unit on top.

Inter-member transfers are not plain self-transfers

A transfer between different people (even within a family) is not automatically the same as an own-wallet internal transfer. In some jurisdictions it can have gift or other tax consequences. So the system must preserve per-person identity on each wallet and flag inter-member transfers for jurisdiction-specific treatment — not silently treat them as basis-carrying self-transfers.

Practical guidance

  1. Keep per-person ownership and basis on every wallet.
  2. Build the household view as a roll-up of correct per-person records — never pool first.
  3. Do not assume the tax unit — confirm household-vs-individual per jurisdiction.
  4. Treat France's foyer fiscal as an example, not a global default.
  5. Flag inter-member transfers for gift/other treatment — not plain self-transfers.
  6. Confirm couple/minor treatment with an adviser for the relevant country.

How vendor tools handle family portfolios

Koinly and CoinTracker offer multi-account/household views. Confirm the tool keeps per-person ownership and basis beneath the household roll-up, does not pool members into one global basis, and does not assume a single tax unit — pooled-family basis is the recurring, expensive error.

How Wag3s helps

Wag3s Folio holds per-person ownership and cost basis on every wallet, presents the household view strictly as a roll-up of correct individual records, flags inter-member transfers for jurisdiction-specific treatment, and leaves the household-vs-individual tax unit to the per-jurisdiction setting. See the Folio product page.


Further reading

Sources

  • Per-person attribution requirement: ownership and cost basis are personal facts that must survive any household roll-up (household view = presentation over per-person records)
  • Household-vs-individual tax unit is strictly jurisdiction-specific (France taxes the foyer fiscal — a jurisdiction example, not a global rule)
  • Inter-member transfers may carry gift/other tax consequences in some jurisdictions (not automatically plain self-transfers) — confirm per jurisdiction
Editorial disclaimer
This article is informational and does not constitute tax advice. Whether tax is assessed per individual or per household is strictly jurisdiction-specific. Confirm with a qualified adviser for your country.