Family & Household Crypto Portfolio: One Dashboard, Separate Taxpayers

The specific danger of a household crypto view is that the thing that makes it convenient is also what makes it wrong for tax. Pooling a couple's or family's wallets into one dashboard is great for a net-worth number, but ownership and cost basis are personal facts: who acquired an asset, when, and at what cost decides that person's gain. The moment a household view pools everyone into one basis, it produces a figure that fits no single member's return. So the rule this article defends is that per-person attribution has to survive the roll-up, and the tax unit (household versus individual) is strictly jurisdiction-specific and no dashboard can encode it globally. This is the multi-wallet pillar with an added owner dimension; the corporate boundary is covered in entity separation.

What is distinct about a household view

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

Convenient for net worth, dangerous for tax

A family or 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, for 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 or 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.

Jurisdiction examples across different countries

The household view is useful in all of these contexts for net-worth monitoring; the tax computation in each case must go back to the per-person records.

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, rather than silently treat them as basis-carrying self-transfers.

When an inter-member transfer is a gift

In many jurisdictions a transfer between family members of an asset worth more than the original acquisition cost constitutes a gift. The donor may trigger a disposal (realising a gain); the recipient may receive the asset at a new cost basis (the gift value). Some jurisdictions have gift tax exemptions for small amounts or for transfers between spouses; others do not. A portfolio tracker must:

• record which person's wallet sent and which received;
• flag the event as a potential gift;
• not automatically carry the donor's cost basis to the recipient.

Confirming the characterisation with an adviser is the only safe approach.

Step-by-step: setting up a household crypto portfolio

1. Create a separate wallet inventory for each household member. Label each wallet with the owner's name or identifier. This is a tagging step, not a technical split — the same tool can aggregate all, but must track ownership per wallet.
2. Import wallets per owner. Person A's wallets (hardware, hot wallets, exchange accounts) are all tagged "Person A". Person B's wallets are tagged "Person B". Etc.
3. For minors: decide whether to track under the minor's own profile or the parent's. In foyer-fiscal jurisdictions the minor's holdings may eventually be aggregated with the parents'; in individually-taxed jurisdictions they are separate. Tag accordingly; the tracking is the same.
4. Classify inter-member transfers explicitly. When a transaction moves assets from Person A's wallet to Person B's wallet, do not auto-classify it as an internal transfer. Create a "pending characterisation" flag for each such event and confirm with an adviser whether it is a gift, a loan repayment, a sale, or some other event.
5. Build the household view as a roll-up. The dashboard aggregates net worth across all owners for the household total. The per-person records underneath remain intact.
6. Generate per-person reports for tax. For each person, produce a transaction history and gain/loss summary from their own wallets only. Apply the jurisdiction's method (individual or joint as required).
7. Review the roll-up for consistency. The household total should equal the sum of all per-person totals. A discrepancy indicates an unclassified inter-member transfer or a wallet attributed to the wrong owner.

Common errors and how to fix them

Error 1 — One shared wallet for a couple. Many couples use a single hardware wallet for all holdings. When it comes time to report, there is no record of who bought what. All cost basis is shared by default, which may be wrong for individually-taxed jurisdictions. Fix: if possible, maintain separate wallets from the start. If not, reconstruct ownership from purchase records (bank statements, exchange confirmations) for each transaction.

Error 2 — Treating a gift between spouses as a self-transfer. In some jurisdictions a transfer between spouses is treated differently from a transfer to a third party but still not automatically basis-carrying. Treating it as a plain self-transfer may miss a disposal or a basis step-up. Fix: flag spouse-to-spouse transfers explicitly for jurisdiction-specific characterisation.

Error 3 — Aggregating HIFO or FIFO across household members. Applying a cost-basis method across the pooled household history produces a result that matches no individual's tax position. Fix: apply the cost-basis method per person to their own transaction history; aggregate gain/loss figures only after the per-person computation.

Error 4 — Not updating ownership tags after wallet transfers within the family. Assets moved from one family member's wallet to another change the per-person allocation. A tracker that does not update ownership attribution after an inter-member transfer will show the wrong owner holding the asset going forward. Fix: treat each inter-member transfer as requiring an explicit ownership update in the tracker, not just a balance movement.

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 pooling first.
3. Do not assume the tax unit; confirm household-versus-individual per jurisdiction.
4. Treat France's foyer fiscal as an example, not a global default.
5. Flag inter-member transfers for gift or other treatment, not as plain self-transfers.
6. Confirm couple/minor treatment with an adviser for the relevant country.

Choosing a tool for a household

Koinly and CoinTracker both offer multi-account or household views, but the family-specific points to confirm are:

• it keeps per-person ownership and cost basis beneath the household roll-up, rather than pooling members into one global basis;
• it applies the cost-basis method per person to their own history, then aggregates the gain or loss figures, not the other way round;
• it does not auto-classify a transfer between two different members as a basis-carrying self-transfer, since that can be a gift or other event;
• it does not assume one tax unit for every country.

Pooled-family basis is the recurring, expensive error.

How Wag3s handles household tracking

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-versus-individual tax unit to the per-jurisdiction setting. See the Folio product page.

Further reading

• Multi-Wallet Aggregation
• France Crypto Tax for Couples
• France Crypto Tax for a Minor
• Internal Transfer vs Disposal in Crypto
• Entity vs Personal Wallet Separation
• Crypto Cost Basis Methods 2026

Sources

• IRS — Digital assets for the US treatment, where gains are reported per taxpayer and a married-filing-jointly return still relies on each spouse's traceable basis, and where a gift has its own characterisation.
• The household-versus-individual tax unit is jurisdiction-specific; the French foyer-fiscal example is covered in the linked couple and minor articles, and the per-person-attribution rule itself is operational tracking practice rather than an external authority.