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

Entity vs Personal Wallet Separation: Don't Let the Books Touch the Tax Return (2026)

Portfolio·

Entity vs Personal Wallet Separation: Don't Let the Books Touch the Tax Return (2026)

Mixing a company's wallets with personal ones corrupts both the corporate books and the personal tax return. Why entity and personal holdings need separate inventories, bases, and destinations (Ledger/FEC vs Folio), and why an entity↔personal transfer is never a plain self-transfer.
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 entity/personal separation principle (separate inventories/bases/destinations) and the entity↔personal-transfer caution · Last reviewed May 2026

Entity vs Personal Wallet Separation: Don't Let the Books Touch the Tax Return

The cheapest crypto disaster to avoid is also the most common: one wallet used for both the company and yourself. The moment they touch, the corporate books and your personal return are both wrong. This guide is why separation is structural, not cosmetic.

TL;DR

  • Entity and personal crypto feed different systems and obligations — keep them structurally separate.
  • Entity → corporate accounting (GL, statutory, FEC, corporate tax) — a Ledger concern.
  • Personal → personal tax computation, jurisdiction method — a Folio concern.
  • Separate inventories, separate bases, separate destinations — tagged by owner.
  • An entity↔personal transfer is NOT a plain self-transfer (different persons) — flag for characterisation.
  • Commingling corrupts both sides and breaks the audit trail; fix it structurally, not at year-end.

Different owners, different systems

A company and an individual are different persons with different obligations. Their crypto must go to different places:

Entity cryptoPersonal crypto
DestinationCorporate accounting (GL, statutory, FEC, corporate tax)Personal tax computation
Wag3s productLedgerFolio
Basis/ownershipThe entity'sThe individual's

Commingle them and the company's books absorb personal activity while the personal return inherits company transactions — both misstated. This is the FEC reconcilability and the per-person attribution disciplines, applied across the entity/personal boundary.

The entity↔personal transfer is not a self-transfer

A movement between a company wallet and a personal wallet is not the own-wallet internal transfer where basis simply carries — because the owners differ. Depending on the jurisdiction it may be a contribution, a distribution, remuneration, a loan, or a sale — each with different tax and accounting consequences. It must be flagged for characterisation, never silently treated as a personal self-transfer. Auto-classifying it as basis-carrying is a structural error with real tax exposure.

What commingling breaks

When entity and personal wallets are mixed:

  • cost basis and ownership become unattributable;
  • the company's books include non-company transactions (and vice versa);
  • audit trails break (the chemin de révision fails);
  • both the corporate position and the personal return are misstated;
  • some jurisdictions raise legal-separation / substantiation concerns.

The fix is structural separation from the start — not a year-end untangling, which is expensive and often impossible to do cleanly.

Enforce it in tracking

  • Maintain distinct wallet inventories tagged by owner (entity vs each individual).
  • Keep separate cost bases and separate reporting destinations.
  • Flag entity↔personal transfers for jurisdiction-specific characterisation.
  • Treat the corporate books and personal/household views as different systems — separate by design, not merged for one dashboard.

A tracker that merges entity and personal for a single net-worth screen is optimising for the wrong thing.

Practical guidance

  1. Separate wallets by owner from day one — entity vs each individual.
  2. Route entity crypto to corporate accounting (Ledger/FEC), personal to personal tax.
  3. Never auto-classify an entity↔personal transfer as a self-transfer — flag it.
  4. Keep separate inventories and bases; tag every wallet by owner.
  5. Confirm characterisation (contribution/distribution/remuneration/loan/sale) per jurisdiction.
  6. Do not rely on year-end untangling — separation is structural.

How vendor tools handle entity/personal separation

Cryptio (B2B) and Koinly (individual) sit on different sides of this line by design. Confirm the tooling keeps entity and personal inventories separate, tags wallets by owner, routes to the correct destination (corporate books vs personal tax), and flags entity↔personal transfers — a single merged pool is the structural failure.

How Wag3s helps

Wag3s Ledger holds entity crypto for corporate accounting and the FEC, while Wag3s Folio holds personal crypto for the individual's tax computation — separate inventories, separate bases, separate destinations, with entity↔personal transfers flagged for jurisdiction-specific characterisation rather than auto-classified. See the Ledger and Folio pages and the Wag3s for accountants page.


Further reading

Sources

  • Entity/personal separation principle: a company and an individual are different persons with different obligations and destinations (corporate accounting/FEC vs personal tax) — separate inventories/bases/destinations
  • An entity↔personal transfer is not a basis-carrying self-transfer (different owners) — may be contribution/distribution/remuneration/loan/sale, jurisdiction-specific
  • Commingling makes ownership/basis unattributable, breaks audit trails, and misstates both sides — separation must be structural, not a year-end fix
Editorial disclaimer
This article is informational and does not constitute tax, accounting, or legal advice. Entity/personal characterisation and commingling consequences are jurisdiction-specific. Confirm with a qualified adviser.